From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v2 uq/master 2/2] x86: cpuid: reconstruct leaf 0Dh data
Date: Wed, 2 Oct 2013 18:39:30 +0300 [thread overview]
Message-ID: <20131002153929.GP17294@redhat.com> (raw)
In-Reply-To: <524C3DBB.4040300@redhat.com>
On Wed, Oct 02, 2013 at 05:37:31PM +0200, Paolo Bonzini wrote:
> Il 02/10/2013 17:21, Gleb Natapov ha scritto:
> >> - if (kvm_enabled()) {
> >> - KVMState *s = cs->kvm_state;
> >> + kvm_mask =
> >> + kvm_arch_get_supported_cpuid(s, 0xd, 0, R_EAX) |
> >> + ((uint64_t)kvm_arch_get_supported_cpuid(s, 0xd, 0, R_EDX) << 32);
> >>
> >> - *eax = kvm_arch_get_supported_cpuid(s, 0xd, count, R_EAX);
> >> - *ebx = kvm_arch_get_supported_cpuid(s, 0xd, count, R_EBX);
> >> - *ecx = kvm_arch_get_supported_cpuid(s, 0xd, count, R_ECX);
> >> - *edx = kvm_arch_get_supported_cpuid(s, 0xd, count, R_EDX);
> >> - } else {
> >> - *eax = 0;
> >> - *ebx = 0;
> >> - *ecx = 0;
> >> - *edx = 0;
> >> + if (count == 0) {
> >> + *ecx = 0x240;
> >> + for (i = 2; i < ARRAY_SIZE(ext_save_areas); i++) {
> >> + const ExtSaveArea *esa = &ext_save_areas[i];
> >> + if ((env->features[esa->feature] & esa->bits) == esa->bits &&
> >> + (kvm_mask & (1 << i)) != 0) {
> >> + if (i < 32) {
> >> + *eax |= 1 << i;
> >> + } else {
> >> + *edx |= 1 << (i - 32);
> >> + }
> >> + *ecx = MAX(*ecx, esa->offset + esa->size);
> >> + }
> >> + }
> >> + *eax |= kvm_mask & 3;
> > Lets use define from previous patch.
>
> Right.
>
> >> + *ebx = *ecx;
> >> + } else if (count == 1) {
> >> + *eax = kvm_arch_get_supported_cpuid(s, 0xd, 1, R_EAX);
> >> + } else if (count < ARRAY_SIZE(ext_save_areas)) {
> >> + const ExtSaveArea *esa = &ext_save_areas[count];
> >> + if ((env->features[esa->feature] & esa->bits) == esa->bits &&
> >> + (kvm_mask & (1 << count)) != 0) {
> >> + *eax = esa->offset;
> >> + *ebx = esa->size;
> > Why do you hard code them instead of querying kernel? What if they
> > depend on cpu type? (well if this happens we can forget about
> > migration, but still...)
>
> HPA confirmed (on xen-devel) that they will not depend on the CPU type.
> All offsets are documented in the SDM and in the additional Skylake
> manual except for MPX, and he reported that he'd ask for MPX to be
> documented as well. As you said, if they changed it would be a total mess.
>
> I hardcoded them because this is not KVM-specific knowledge. TCG could
> in principle reuse the same code, just skipping the part where it masks
> away features not supported by KVM.
>
OK. Can you send new version with defines please?
--
Gleb.
next prev parent reply other threads:[~2013-10-02 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 13:55 [Qemu-devel] [PATCH v2 uq/master 0/2] KVM: issues with XSAVE support Paolo Bonzini
2013-09-13 13:55 ` [Qemu-devel] [PATCH v2 uq/master 1/2] x86: fix migration from pre-version 12 Paolo Bonzini
2013-09-13 13:55 ` [Qemu-devel] [PATCH v2 uq/master 2/2] x86: cpuid: reconstruct leaf 0Dh data Paolo Bonzini
2013-10-02 15:21 ` Gleb Natapov
2013-10-02 15:37 ` Paolo Bonzini
2013-10-02 15:39 ` Gleb Natapov [this message]
2013-10-02 15:54 ` [Qemu-devel] [PATCH v3 " Paolo Bonzini
2013-10-02 16:03 ` Gleb Natapov
2013-10-03 9:59 ` Igor Mammedov
2013-10-03 10:01 ` Gleb Natapov
2013-10-03 10:14 ` Igor Mammedov
2013-10-02 12:41 ` [Qemu-devel] [PATCH v2 uq/master 0/2] KVM: issues with XSAVE support Paolo Bonzini
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=20131002153929.GP17294@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).