All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH v2] eal/x86: get hypervisor name
Date: Tue, 2 Jan 2018 15:50:00 +0530	[thread overview]
Message-ID: <20180102101959.GA16958@jerin> (raw)
In-Reply-To: <20171230224723.13147-1-thomas@monjalon.net>

-----Original Message-----
> Date: Sat, 30 Dec 2017 23:47:23 +0100
> From: Thomas Monjalon <thomas@monjalon.net>
> To: dev@dpdk.org
> Cc: Stephen Hemminger <sthemmin@microsoft.com>, Jerin Jacob
>  <jerin.jacob@caviumnetworks.com>
> Subject: [PATCH v2] eal/x86: get hypervisor name
> X-Mailer: git-send-email 2.15.1
> 
> The CPUID instruction is catched by hypervisor which can return
> a flag indicating one is running, and its name.
> 
> Suggested-by: Stephen Hemminger <sthemmin@microsoft.com>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> v2 changes:
> 	- remove C99 style declaration
> 	- move code in rte_hypervisor.* files
> 	- add a function to get the name string

>From the new API change perspective,
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

  reply	other threads:[~2018-01-02 10:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 21:47 [PATCH] eal/x86: get hypervisor name 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 ` [PATCH v2] " Thomas Monjalon
2018-01-02 10:20   ` Jerin Jacob [this message]
2018-01-02 16:34   ` Stephen Hemminger
2018-01-03  8:11     ` Thomas Monjalon
2018-01-07 22:20 ` [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
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=20180102101959.GA16958@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=sthemmin@microsoft.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.