public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Anupam Chanda <achanda@nicira.com>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
	stefano.stabellini@eu.citrix.com, jeremy.fitzhardinge@citrix.com,
	eddie.dong@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Change hypervisor detection order
Date: Thu, 07 Jul 2011 17:29:05 -0700	[thread overview]
Message-ID: <4E164F51.3080301@zytor.com> (raw)
In-Reply-To: <1310062788-9445-1-git-send-email-achanda@nicira.com>

On 07/07/2011 11:19 AM, Anupam Chanda wrote:
> Detect Xen before HyperV because in Viridian compatibility mode Xen presents
> itself as HyperV.
> 
> Signed-off-by: Anupam Chanda <achanda@nicira.com>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> ---
>  arch/x86/kernel/cpu/hypervisor.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/hypervisor.c b/arch/x86/kernel/cpu/hypervisor.c
> index 8095f86..ca23091 100644
> --- a/arch/x86/kernel/cpu/hypervisor.c
> +++ b/arch/x86/kernel/cpu/hypervisor.c
> @@ -33,10 +33,10 @@
>  static const __initconst struct hypervisor_x86 * const hypervisors[] =
>  {
>  	&x86_hyper_vmware,
> -	&x86_hyper_ms_hyperv,
>  #ifdef CONFIG_XEN_PVHVM
>  	&x86_hyper_xen_hvm,
>  #endif
> +	&x86_hyper_ms_hyperv,
>  };
>  
>  const struct hypervisor_x86 *x86_hyper;

Any reason to not hoist it to the top?  I'm guessing Xen emulating
VMware is more likely than the opposite...
	
	-hpa

  parent reply	other threads:[~2011-07-08  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 18:19 [PATCH] Change hypervisor detection order Anupam Chanda
2011-07-07 23:45 ` Dong, Eddie
2011-07-08  0:29 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-08 18:42 Anupam Chanda

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=4E164F51.3080301@zytor.com \
    --to=hpa@zytor.com \
    --cc=achanda@nicira.com \
    --cc=eddie.dong@intel.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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