From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org,
Xiangfei Ma <xiangfeix.ma@intel.com>,
Yan Zhao <yan.y.zhao@intel.com>
Subject: Re: [PATCH 0/2] nVMX: Ensure host's PAT stays sane
Date: Wed, 5 Jun 2024 16:03:21 -0700 [thread overview]
Message-ID: <ZmDuuRTkG2Y1LcTR@google.com> (raw)
In-Reply-To: <20240605224527.2907272-1-seanjc@google.com>
On Wed, Jun 05, 2024, Sean Christopherson wrote:
> Fix a bug(s) where test_load_host_pat clobbers PAT and causes all
> subsequent tests to effectively run with all memory mapped as UC. Xiangfei
> first noticed that this caused rdtsc_vmexit_diff_test to fail, but it can
> also lead to timeouts if more tests are added, i.e. if more stuff runs after
> test_load_host_pat.
>
> Sean Christopherson (2):
> nVMX: Ensure host's PAT is loaded at the end of all VMX tests
> nVMX: Verify KVM actually loads the value in HOST_PAT into the PAT MSR
>
> x86/vmx.c | 4 +++-
> x86/vmx_tests.c | 10 +++++++++-
> 2 files changed, 12 insertions(+), 2 deletions(-)
Doh, this is for kvm-unit-tests. Been a while since I sent KUT patches...
next prev parent reply other threads:[~2024-06-05 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 22:45 [PATCH 0/2] nVMX: Ensure host's PAT stays sane Sean Christopherson
2024-06-05 22:45 ` [PATCH 1/2] nVMX: Ensure host's PAT is loaded at the end of all VMX tests Sean Christopherson
2024-06-11 1:40 ` Yan Zhao
2024-06-11 1:47 ` Sean Christopherson
2024-06-11 2:03 ` Yan Zhao
2024-06-05 22:45 ` [PATCH 2/2] nVMX: Verify KVM actually loads the value in HOST_PAT into the PAT MSR Sean Christopherson
2024-06-05 23:03 ` Sean Christopherson [this message]
2024-06-12 1:18 ` [PATCH 0/2] nVMX: Ensure host's PAT stays sane Sean Christopherson
2024-06-12 1:47 ` Yan Zhao
2024-06-12 1:50 ` Sean Christopherson
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=ZmDuuRTkG2Y1LcTR@google.com \
--to=seanjc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=xiangfeix.ma@intel.com \
--cc=yan.y.zhao@intel.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