From: Wanpeng Li <kernellwp@gmail.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>, Wanpeng Li <wanpeng.li@hotmail.com>,
Wincy Van <fanwenyi0529@gmail.com>,
Yang Zhang <yang.zhang.wz@gmail.com>
Subject: Re: [PATCH] KVM: VMX: Enable MSR-BASED TPR shadow even if w/o APICv
Date: Thu, 22 Sep 2016 14:48:41 +0800 [thread overview]
Message-ID: <CANRm+CyZEsM2bCDbdSwngi4ww2TssSWTQ4NHn0nx7JTCNJ4PjA@mail.gmail.com> (raw)
In-Reply-To: <20160919134438.GA14268@potion>
[...]
>
>> Btw, I heard from Tianyu from Intel, you said there was a x2apic bug
>> in kvm forum and the bug maybe in kvm, I guess I meet the same bug
>> when run a windows guest(server version of windows 7, 2008 or 2012) w/
>> x2apic enabled in guest and -machine q35,kernel_irqchip=spit -device
>> intel-iommu, intremap=on in the QEMU command line.
>
> Does it happen when you are running less than 8 VCPUs (max APIC ID < 8)?
> QEMU always enabled x2APIC support in IOMMU (EIME) even though it
> doesn't work under some configurations.
I'm digging into the bug currently. :）
Regards,
Wanpeng Li
next prev parent reply other threads:[~2016-09-22 6:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 7:58 [PATCH] KVM: VMX: Enable MSR-BASED TPR shadow even if w/o APICv Wanpeng Li
2016-09-14 9:40 ` Paolo Bonzini
2016-09-14 12:03 ` Radim Krčmář
2016-09-15 1:19 ` Wanpeng Li
2016-09-15 6:29 ` Paolo Bonzini
2016-09-15 6:40 ` Wanpeng Li
2016-09-15 7:05 ` Wanpeng Li
2016-09-15 15:58 ` Radim Krčmář
2016-09-18 6:53 ` Wanpeng Li
2016-09-18 6:55 ` Wanpeng Li
2016-09-19 13:44 ` Radim Krčmář
2016-09-20 0:18 ` Wanpeng Li
2016-09-22 6:48 ` Wanpeng Li [this message]
2016-09-15 0:07 ` Wanpeng Li
2016-09-15 0:17 ` Wanpeng Li
2016-09-15 4:08 ` Mika Penttilä
2016-09-15 4:25 ` Wanpeng Li
2016-09-15 4:46 ` Mika Penttilä
2016-09-15 6:30 ` 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=CANRm+CyZEsM2bCDbdSwngi4ww2TssSWTQ4NHn0nx7JTCNJ4PjA@mail.gmail.com \
--to=kernellwp@gmail.com \
--cc=fanwenyi0529@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.com \
--cc=yang.zhang.wz@gmail.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;
as well as URLs for NNTP newsgroup(s).