From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] kvm: apic: save and restore x2APIC LDR
Date: Wed, 22 Nov 2017 20:26:14 +0100 [thread overview]
Message-ID: <adada925-d23d-af1c-8965-f18904f5184d@redhat.com> (raw)
In-Reply-To: <20171122180908.31389-1-rkrcmar@redhat.com>
On 22/11/2017 19:09, Radim Krčmář wrote:
> QEMU saves only 8 bits of APIC LDR, which means that it does not support
> x2APIC. The correct way of fixing this would be to save and restore the
> full 32 bit register, but because x2APIC LDR is a function of x2APIC ID,
> we can also compute it and keep the migration format untouched.
>
> KVM always expected the LDR format to follow the xAPIC/x2APIC standard,
> but pre 4.1 KVMs used non-standard x2APIC ID in case the OS changed
> xAPIC ID before switching to x2APIC, which means that QEMU has to use
> the kvm_x2apic_api feature to derive the x2APIC ID.
>
> This bug has also been addressed on the KVM side with patch 5849d75a5c9b
> ("KVM: lapic: Fixup LDR on load in x2apic").
> + if (s->apicbase & MSR_IA32_APICBASE_EXTD) {
> + kvm_apic_set_reg(kapic, 0xd, kvm_apic_calc_x2apic_ldr(s));
Is this correct if the kernel doesn't support the new-style x2APIC API?
In the end, it seems simpler to just fix it in the kernel.
Paolo
> + } else {
> + kvm_apic_set_reg(kapic, 0xd, s->log_dest << 24);
> + }
next prev parent reply other threads:[~2017-11-22 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 18:09 [Qemu-devel] [PATCH] kvm: apic: save and restore x2APIC LDR Radim Krčmář
2017-11-22 18:37 ` no-reply
2017-11-22 19:26 ` Paolo Bonzini [this message]
2017-11-22 20:57 ` Radim Krčmář
2017-11-22 20:28 ` Eduardo Habkost
2017-11-22 21:01 ` Radim Krčmář
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=adada925-d23d-af1c-8965-f18904f5184d@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=rth@twiddle.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 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).