From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id D73C31B170 for ; Wed, 3 Jan 2018 09:11:21 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6469C20D0A; Wed, 3 Jan 2018 03:11:20 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 03 Jan 2018 03:11:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=+YB/u2o1fr2trfln26vjASSwKb oy6AFtbd4JFwjMJA0=; b=OzfG8R7zZVi5InXyzH1OD6VyyLTewAfe+doXCguneP sdVXUHC0DJ4XDfjFQr6/dCElntdgXjTYyFywKCSD8NwjXHXQBWFhzF+Dw4jDyuDQ nU5ReB3BKs2vLsg6TI8MiTqc/1+BNnUif7kISowevUiPjfdwZBGhfGf2Wlad+A33 0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=+YB/u2 o1fr2trfln26vjASSwKboy6AFtbd4JFwjMJA0=; b=mgKTQVTttyvF4Dfa/iEYgj nnB2DhORGBc6dkX2C14r16Itj5Vx6ge49Gm3LgXwyEr7aELDxiXbrEGtKyS0DKnu 0G708PA5e/nIkwus7vRf7COYkqIL5ijpm+ChTssDsA8V4JBr7JPGc+gVKXDyKiWg bVTJzhgFNB+BfblIAa21J7cM7Qwm6oUhgQQKsaUmr4T2I5fzGziNKKixkQR0CEnP lgupKhwmcLQtBkd4Arero24JpwMtM9Jla5Rl5Eq4lE4E4c/NtIXAtKg0lbx4Fmcq xhXRK8HZjwgGgZymk1qxoP6zXaAyiC1ibkLW20DALZKhnbiQroEZfqAYxKDeWa+w == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id E8EE1246D0; Wed, 3 Jan 2018 03:11:19 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, Stephen Hemminger , Jerin Jacob Date: Wed, 03 Jan 2018 09:11:02 +0100 Message-ID: <2914779.8I0g9CxD1t@xps> In-Reply-To: <20180102083405.2ffd9bed@xeon-e3> References: <20171130214720.30098-1-thomas@monjalon.net> <20171230224723.13147-1-thomas@monjalon.net> <20180102083405.2ffd9bed@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] eal/x86: get hypervisor name X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2018 08:11:22 -0000 02/01/2018 17:34, Stephen Hemminger: > On Sat, 30 Dec 2017 23:47:23 +0100 > Thomas Monjalon wrote: > > > The CPUID instruction is catched by hypervisor which can return > > a flag indicating one is running, and its name. > > > > Suggested-by: Stephen Hemminger > > Signed-off-by: Thomas Monjalon > > --- > > v2 changes: > > - remove C99 style declaration > > - move code in rte_hypervisor.* files > > - add a function to get the name string > > Looks good to me. > What about Xen? Xen is not supported in DPDK currently. So it will be handled as "unknown". Xen awareness can be added later with some driver support.