stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jitindar SIngh, Suraj" <surajjs@amazon.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: stable/4.14.y: kvm: vmx: Basic APIC virtualization controls have three settings
Date: Thu, 24 Oct 2019 17:24:44 +0000	[thread overview]
Message-ID: <17bb312d55c6a00e27941e12cf4898fac2d2cb14.camel@amazon.com> (raw)

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

             reply	other threads:[~2019-10-24 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 17:24 Jitindar SIngh, Suraj [this message]
2019-10-27 15:58 ` stable/4.14.y: kvm: vmx: Basic APIC virtualization controls have three settings Greg KH

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=17bb312d55c6a00e27941e12cf4898fac2d2cb14.camel@amazon.com \
    --to=surajjs@amazon.com \
    --cc=stable@vger.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).