All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Huang(Peng)" <peter.huangpeng@huawei.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
	libvir-list@redhat.com, qemu-devel@nongnu.org,
	Jiri Denemark <jdenemar@redhat.com>
Subject: [Qemu-devel] [Solved]FYI//Re: [Question] why x2apic's set by default without host support(on Nehalem CPU).
Date: Wed, 24 Jul 2013 10:54:57 +0800	[thread overview]
Message-ID: <51EF4201.9040802@huawei.com> (raw)
In-Reply-To: <51EF2469.1090402@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

FYI, just for information sharing.

KVM emulated x2apic feature no matter host supports it or not.
You can get the code from arch/x86/kvm/cpuid.c.
kvm_dev_ioctl_get_supported_cpuid ()->do_cpuid_ent()

  /* we support x2apic emulation even if host does not support

                 * it since we emulate x2apic in software */

                entry->ecx |= F(*X2APIC*);


QEMU will get this feature through kvm_ioctl().

On 2013-07-24 8:48, Peter Huang(Peng) wrote:
> Hi,Jiri
>
> Thanks for replying.
>
> So why VM identified different features from host is due to the hypervisor filtering.
> I will dig into the hypervisor of how it filter features, and update status later.
>
> Thanks again.

[-- Attachment #2: Type: text/html, Size: 43462 bytes --]

      reply	other threads:[~2013-07-24  2:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 11:24 [Qemu-devel] [Question] why x2apic's set by default without host support(on Nehalem CPU) Peter Huang(Peng)
2013-07-22 12:36 ` Peter Huang(Peng)
2013-07-22 12:36   ` [Qemu-devel] " Peter Huang(Peng)
2013-07-22 23:55   ` Marcelo Tosatti
2013-07-22 23:55     ` [Qemu-devel] " Marcelo Tosatti
2013-07-23  2:38     ` Peter Huang(Peng)
2013-07-23  2:38       ` [Qemu-devel] " Peter Huang(Peng)
2013-07-22 13:41 ` Eduardo Habkost
2013-07-23  2:44   ` Peter Huang(Peng)
2013-07-23 11:27     ` Jiri Denemark
2013-07-24  0:48       ` Peter Huang(Peng)
2013-07-24  2:54         ` Peter Huang(Peng) [this message]

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=51EF4201.9040802@huawei.com \
    --to=peter.huangpeng@huawei.com \
    --cc=ehabkost@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.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 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.