public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] always report x2apic as supported feature
Date: Wed, 15 Jul 2009 20:01:30 -0300	[thread overview]
Message-ID: <20090715230130.GB11794@amt.cnet> (raw)
In-Reply-To: <20090712131055.GB28046@redhat.com>

On Sun, Jul 12, 2009 at 04:10:55PM +0300, Gleb Natapov wrote:
> We emulate x2apic in software, so host support is not required.
> 
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 00844eb..c256da7 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -1497,6 +1497,9 @@ static void do_cpuid_ent(struct kvm_cpuid_entry2 *entry, u32 function,
>  	case 1:
>  		entry->edx &= kvm_supported_word0_x86_features;
>  		entry->ecx &= kvm_supported_word4_x86_features;
> +		/* we support x2apic emulation even if host does not support
> +		   it since we emulate x2apic in software */
> +		entry->ecx |= F(X2APIC);
>  		break;
>  	/* function 2 entries are STATEFUL. That is, repeated cpuid commands
>  	 * may return different values. This forces us to get_cpu() before
> --
> 			Gleb.

What if you have an older host that does not support emulate x2apic?


  parent reply	other threads:[~2009-07-15 23:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 13:10 [PATCH] always report x2apic as supported feature Gleb Natapov
2009-07-12 13:21 ` Avi Kivity
2009-07-15 23:01 ` Marcelo Tosatti [this message]
2009-07-16  1:46   ` Sheng Yang
2009-07-16  6:00     ` Gleb Natapov
2009-07-16  6:09       ` Sheng Yang
2009-07-16  6:12         ` Gleb Natapov

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=20090715230130.GB11794@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.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