From: Paolo Bonzini <pbonzini@redhat.com>
To: Xinlong Lin <linxl3@wangsu.com>,
Eiichi Tsukata <eiichi.tsukata@nutanix.com>
Cc: "sean.j.christopherson" <sean.j.christopherson@intel.com>,
vkuznets <vkuznets@redhat.com>, wanpengli <wanpengli@tencent.com>,
jmattson <jmattson@google.com>, joro <joro@8bytes.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>, kvm <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Felipe Franciosi <felipe@nutanix.com>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [RFC PATCH] KVM: x86: Fix APIC page invalidation race
Date: Fri, 19 Jun 2020 14:12:16 +0200 [thread overview]
Message-ID: <09bc7ef5-445f-b2df-aa55-a23710ecc481@redhat.com> (raw)
In-Reply-To: <202006191317431160122@wangsu.com>
On 19/06/20 07:17, Xinlong Lin wrote:
>> Because of the above race, there can be a mismatch between the
>> host physical address stored in the APIC_ACCESS_PAGE VMCS field and
>> the host physical address stored in the EPT entry for the APIC GPA
>> (0xfee0000). When this happens, the processor will not trap APIC
>
> Is the APIC GPA shoud be 0xfee00000?
Yes, there's a missing zero.
Paolo
prev parent reply other threads:[~2020-06-19 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 4:26 [RFC PATCH] KVM: x86: Fix APIC page invalidation race Eiichi Tsukata
2020-06-06 5:00 ` Eiichi Tsukata
2020-06-08 13:13 ` Paolo Bonzini
2020-06-09 1:04 ` Eiichi Tsukata
2020-06-09 9:54 ` Paolo Bonzini
2020-06-09 13:36 ` Eiichi Tsukata
[not found] ` <202006191317431160122@wangsu.com>
2020-06-19 12:12 ` Paolo Bonzini [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=09bc7ef5-445f-b2df-aa55-a23710ecc481@redhat.com \
--to=pbonzini@redhat.com \
--cc=aarcange@redhat.com \
--cc=bp@alien8.de \
--cc=eiichi.tsukata@nutanix.com \
--cc=felipe@nutanix.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linxl3@wangsu.com \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.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).