From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v3] eal/x86: get hypervisor name Date: Mon, 8 Jan 2018 19:05:59 +0000 Message-ID: References: <20171130214720.30098-1-thomas@monjalon.net> <20180107222042.24716-1-thomas@monjalon.net> <20180108085418.44286d47@xeon-e3> <5926649.YBCP5bObeR@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" , Jerin Jacob , Adrien Mazarguil To: Thomas Monjalon , Stephen Hemminger Return-path: Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0138.outbound.protection.outlook.com [104.47.38.138]) by dpdk.org (Postfix) with ESMTP id D9C251B014 for ; Mon, 8 Jan 2018 20:06:01 +0100 (CET) In-Reply-To: <5926649.YBCP5bObeR@xps> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" My comment was intended as an FYI for future usage. -----Original Message----- From: Thomas Monjalon [mailto:thomas@monjalon.net]=20 Sent: Monday, January 8, 2018 10:46 AM To: Stephen Hemminger Cc: dev@dpdk.org; Stephen Hemminger ; Jerin Jacob <= jerin.jacob@caviumnetworks.com>; Adrien Mazarguil 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 wrote: >=20 > > diff --git a/lib/librte_eal/common/arch/arm/rte_hypervisor.c b/lib/libr= te_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; > > +} >=20 > Looking at util-linux for inspiration. >=20 > Xen is "XenVMMXenVMM" >=20 > On PowerPC, the hypervisor type can be deduced from /proc via devicetree. >=20 > 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.