My comment was intended as an FYI for future usage.
-----Original Message----- From: Thomas Monjalon [mailto:tho...@monjalon.net] Sent: Monday, January 8, 2018 10:46 AM To: Stephen Hemminger <step...@networkplumber.org> Cc: dev@dpdk.org; Stephen Hemminger <sthem...@microsoft.com>; Jerin Jacob <jerin.ja...@caviumnetworks.com>; Adrien Mazarguil <adrien.mazarg...@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 <tho...@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.
