From: Stephen Hemminger <sthemmin@microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal/x86: get hypervisor name
Date: Mon, 8 Jan 2018 19:05:59 +0000 [thread overview]
Message-ID: <CY4PR21MB0837DEA54D83153146B520BBCC130@CY4PR21MB0837.namprd21.prod.outlook.com> (raw)
In-Reply-To: <5926649.YBCP5bObeR@xps>
My comment was intended as an FYI for future usage.
-----Original Message-----
From: Thomas Monjalon [mailto:thomas@monjalon.net]
Sent: Monday, January 8, 2018 10:46 AM
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org; Stephen Hemminger <sthemmin@microsoft.com>; Jerin Jacob <jerin.jacob@caviumnetworks.com>; Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal/x86: get hypervisor name
08/01/2018 17:54, Stephen Hemminger:
> On Sun, 7 Jan 2018 23:20:42 +0100
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > diff --git a/lib/librte_eal/common/arch/arm/rte_hypervisor.c b/lib/librte_eal/common/arch/arm/rte_hypervisor.c
> > new file mode 100644
> > index 000000000..3792fe2ce
> > --- /dev/null
> > +++ b/lib/librte_eal/common/arch/arm/rte_hypervisor.c
> > @@ -0,0 +1,11 @@
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > + * Copyright 2017 Mellanox Technologies, Ltd.
> > + */
> > +
> > +#include "rte_hypervisor.h"
> > +
> > +enum rte_hypervisor
> > +rte_hypervisor_get(void)
> > +{
> > + return RTE_HYPERVISOR_UNKNOWN;
> > +}
>
> Looking at util-linux for inspiration.
>
> Xen is "XenVMMXenVMM"
>
> On PowerPC, the hypervisor type can be deduced from /proc via devicetree.
>
> OpenVz/Virtuzzo can be detected by /proc/vz and /proc/bc
I really don't see any benefit of detecting Xen or OpenVz in DPDK.
next prev parent reply other threads:[~2018-01-08 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 21:47 [dpdk-dev] [PATCH] " Thomas Monjalon
2017-11-30 21:55 ` Stephen Hemminger
2017-11-30 22:03 ` Thomas Monjalon
2017-11-30 22:11 ` Stephen Hemminger
2017-12-01 8:12 ` Jerin Jacob
2017-12-01 8:52 ` Thomas Monjalon
2017-12-01 9:17 ` Jerin Jacob
2017-12-30 22:47 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2018-01-02 10:20 ` Jerin Jacob
2018-01-02 16:34 ` Stephen Hemminger
2018-01-03 8:11 ` Thomas Monjalon
2018-01-07 22:20 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2018-01-08 16:54 ` Stephen Hemminger
2018-01-08 18:45 ` Thomas Monjalon
2018-01-08 19:05 ` Stephen Hemminger [this message]
2018-01-11 23:40 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CY4PR21MB0837DEA54D83153146B520BBCC130@CY4PR21MB0837.namprd21.prod.outlook.com \
--to=sthemmin@microsoft.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).