From: Greg KH <greg@kroah.com>
To: "Jitindar SIngh, Suraj" <surajjs@amazon.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: stable/4.14.y: kvm: vmx: Basic APIC virtualization controls have three settings
Date: Sun, 27 Oct 2019 16:58:35 +0100 [thread overview]
Message-ID: <20191027155835.GA2311304@kroah.com> (raw)
In-Reply-To: <17bb312d55c6a00e27941e12cf4898fac2d2cb14.camel@amazon.com>
On Thu, Oct 24, 2019 at 05:24:44PM +0000, Jitindar SIngh, Suraj wrote:
> The following patch fixes a bug where the guest is still able to access
> the apic registers via mmio once the apic has been disabled.
>
> 8d860bbeedef kvm: vmx: Basic APIC virtualization controls have three
> settings
>
> This causes the x86/apic kvm-unit-test to fail when run on a host
> missing this patch.
>
> Without:
> FAIL: apic_disable: *0xfee00030: 50014
> FAIL: apic_disable: CR8: f
> PASS: apic_disable: CR8: f
> FAIL: apic_disable: *0xfee00080: f0
> With:
> PASS: apic_disable: *0xfee00030: ffffffff
> PASS: apic_disable: CR8: 0
> PASS: apic_disable: CR8: f
> PASS: apic_disable: *0xfee00080: ffffffff
>
> This patch has been upstream as of v4.18.
>
> This patch has 3 dependencies which introduce no functional
> change, however they add context which allows the patch listed above to
> apply cleanly.
>
> c2ba05ccfde2 KVM: X86: introduce invalidate_gpa argument to tlb flush
> 588716494258 kvm: vmx: Introduce lapic_mode enumeration
> a468f2dbf921 kvm: apic: Flush TLB after APIC mode/address change if
> VPIDs are in use
>
> This patch series should be applied against 4.14.y
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-10-27 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 17:24 stable/4.14.y: kvm: vmx: Basic APIC virtualization controls have three settings Jitindar SIngh, Suraj
2019-10-27 15:58 ` Greg KH [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=20191027155835.GA2311304@kroah.com \
--to=greg@kroah.com \
--cc=stable@vger.kernel.org \
--cc=surajjs@amazon.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).