public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Liran Alon <LIRAN.ALON@ORACLE.COM>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
	kvm@vger.kernel.org
Cc: pbonzini@redhat.com
Subject: Re: [PATCH 2/2] KVM: lapic: Fixup LDR on load in x2apic
Date: Fri, 17 Nov 2017 23:03:28 +0200	[thread overview]
Message-ID: <5A0F4EA0.6080906@ORACLE.COM> (raw)
In-Reply-To: <5A0F4E1F.70303@ORACLE.COM>



On 17/11/17 23:01, Liran Alon wrote:
>
>
> On 17/11/17 13:52, Dr. David Alan Gilbert (git) wrote:
>> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>>
>> In x2apic mode the LDR is fixed based on the ID rather
>> than separately loadable like it was before x2.
>> When kvm_apic_set_state is called, the base is set, and if
>> it has the X2APIC_ENABLE flag set then the LDR is calculated;
>> however that value gets overwritten by the memcpy a few lines
>> below overwriting it with the value that came from userland.
>>
>> The symptom is a lack of EOI after loading the state
>> (e.g. after a QEMU migration) and is due to the EOI bitmap
>> being wrong due to the incorrect LDR.  This was seen with
>> a Win2016 guest under Qemu with irqchip=split whose USB mouse
>> didn't work after a VM migration.
>>
>> This corresponds to RH bug:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.redhat.com_show-5Fbug.cgi-3Fid-3D1502591&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=Jk6Q8nNzkQ6LJ6g42qARkg6ryIDGQr-yKXPNGZbpTx0&m=BDEsclkj9SNWbZXiuKgX07QVY0LqtwHA13yqtK4wreE&s=MJS_JxKV0dJS6T8qobO29j530xNJLFqgSuRMP8oEiwI&e=
>>
>>
>> Reported-by: Yiqian Wei <yiwei@redhat.com>
>> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>> ---
>>   arch/x86/kvm/lapic.c | 5 +++++
>>   1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
>> index 4991e9e51611..cff55beb0263 100644
>> --- a/arch/x86/kvm/lapic.c
>> +++ b/arch/x86/kvm/lapic.c
>> @@ -2201,7 +2201,12 @@ static int kvm_apic_state_fixup(struct kvm_vcpu
>> *vcpu,
>>   {
>>       if (apic_x2apic_mode(vcpu->arch.apic)) {
>>           u32 *id = (u32 *)(s->regs + APIC_ID);
>> +        u32 *ldr = (u32 *)(s->regs + APIC_LDR);
>>
>> +        if (set) {
>> +            /* In x2 the LDR is fixed based on the id */
>> +            *ldr = kvm_apic_calc_x2apic_ldr(*id);
>> +        }
>>           if (vcpu->kvm->arch.x2apic_format) {
>>               if (*id != vcpu->vcpu_id)
>>                   return -EINVAL;
>>
>
> I think there is a bug here of not adding the new code in the right
> place. I think diff should be instead:
>
> @@ -2245,6 +2245,7 @@ static int kvm_apic_state_fixup(struct kvm_vcpu
> *vcpu,
>   {
>          if (apic_x2apic_mode(vcpu->arch.apic)) {
>                  u32 *id = (u32 *)(s->regs + APIC_ID);
> +               u32 *ldr = (u32 *)(s->regs + APIC_LDR);
>
>                  if (vcpu->kvm->arch.x2apic_format) {
>                          if (*id != vcpu->vcpu_id)
> @@ -2255,6 +2256,8 @@ static int kvm_apic_state_fixup(struct kvm_vcpu
> *vcpu,
>                          else
>                                  *id <<= 24;
>                  }
> +
> +               *ldr = kvm_apic_calc_x2apic_ldr(*id);
>          }
>
>      return 0;
>
> This is because of the x2apic_format hack.
> (Fore more info, see commit 3713131345fb ("KVM: x86: add
> KVM_CAP_X2APIC_API")).
> Otherwise, you will use a value which can be shifted-left by 24.
>
> -Liran

Sorry I meant diff should be:
@@ -2245,6 +2245,7 @@ static int kvm_apic_state_fixup(struct kvm_vcpu *vcpu,
  {
         if (apic_x2apic_mode(vcpu->arch.apic)) {
                 u32 *id = (u32 *)(s->regs + APIC_ID);
+               u32 *ldr = (u32 *)(s->regs + APIC_LDR);

                 if (vcpu->kvm->arch.x2apic_format) {
                         if (*id != vcpu->vcpu_id)
@@ -2255,6 +2256,9 @@ static int kvm_apic_state_fixup(struct kvm_vcpu *vcpu,
                         else
                                 *id <<= 24;
                 }
+
+               if (set)
+                       *ldr = kvm_apic_calc_x2apic_ldr(*id);
         }

         return 0;

  reply	other threads:[~2017-11-17 21:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 11:52 [PATCH 0/2] Lapic LDR fixup Dr. David Alan Gilbert (git)
2017-11-17 11:52 ` [PATCH 1/2] KVM: lapic: Split out x2apic ldr calculation Dr. David Alan Gilbert (git)
2017-11-23 15:31   ` David Hildenbrand
2017-11-17 11:52 ` [PATCH 2/2] KVM: lapic: Fixup LDR on load in x2apic Dr. David Alan Gilbert (git)
2017-11-17 21:01   ` Liran Alon
2017-11-17 21:03     ` Liran Alon [this message]
2017-11-20  0:53       ` Wanpeng Li
2017-11-20  1:04         ` Liran Alon
2017-11-20 20:48           ` Paolo Bonzini
2017-11-20 10:48       ` Dr. David Alan Gilbert
2017-11-17 12:29 ` [PATCH 0/2] Lapic LDR fixup Paolo Bonzini
2017-11-17 19:37   ` Dr. David Alan Gilbert
2017-11-17 20:27     ` 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=5A0F4EA0.6080906@ORACLE.COM \
    --to=liran.alon@oracle.com \
    --cc=dgilbert@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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