From: Robert Hoo <robert.hu@linux.intel.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Thelen <gthelen@google.com>,
David Matlack <dmatlack@google.com>,
Ben Gardon <bgardon@google.com>,
Mingwei Zhang <mizhang@google.com>
Subject: Re: [PATCH 0/5] KVM: x86/mmu: TDP MMU fixes for 6.2
Date: Wed, 14 Dec 2022 20:01:04 +0800 [thread overview]
Message-ID: <acb8adfc5a2ace34010dc70d5ccd2821ff0a1ecb.camel@linux.intel.com> (raw)
In-Reply-To: <20221213033030.83345-1-seanjc@google.com>
On Tue, 2022-12-13 at 03:30 +0000, Sean Christopherson wrote:
> Fix three fatal TDP MMU bugs introduced in 6.2,
introduced in 6.1? or earlier?
> harden related code,
> and clean up kvm_tdp_mmu_map() to eliminate the need for gotos.
>
> Sean Christopherson (5):
> KVM: x86/mmu: Don't attempt to map leaf if target TDP MMU SPTE is
> frozen
> KVM: x86/mmu: Map TDP MMU leaf SPTE iff target level is reached
> KVM: x86/mmu: Re-check under lock that TDP MMU SP hugepage is
> disallowed
> KVM: x86/mmu: Don't install TDP MMU SPTE if SP has unexpected level
> KVM: x86/mmu: Move kvm_tdp_mmu_map()'s prolog and epilog to its
> caller
>
> arch/x86/kvm/mmu/mmu.c | 9 +++++++-
> arch/x86/kvm/mmu/mmu_internal.h | 1 -
> arch/x86/kvm/mmu/tdp_mmu.c | 39 +++++++++++++++--------------
> ----
> 3 files changed, 26 insertions(+), 23 deletions(-)
>
>
> base-commit: 51229fd7872f82af07498aef5c79ad51baf81ea0
I cannot find this base commit in my tree, where I just pulled to
latest queue yesterday. But find this series can be applied to this
latest queue as well.
commit 9d75a3251adfbcf444681474511b58042a364863 (origin/queue, queue)
Author: Sean Christopherson <seanjc@google.com>
Date: Wed Dec 7 00:09:59 2022 +0000
KVM: x86: Add proper ReST tables for userspace MSR exits/flags
next prev parent reply other threads:[~2022-12-14 12:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 3:30 [PATCH 0/5] KVM: x86/mmu: TDP MMU fixes for 6.2 Sean Christopherson
2022-12-13 3:30 ` [PATCH 1/5] KVM: x86/mmu: Don't attempt to map leaf if target TDP MMU SPTE is frozen Sean Christopherson
2022-12-14 11:57 ` Robert Hoo
2022-12-13 3:30 ` [PATCH 2/5] KVM: x86/mmu: Map TDP MMU leaf SPTE iff target level is reached Sean Christopherson
2022-12-13 3:30 ` [PATCH 3/5] KVM: x86/mmu: Re-check under lock that TDP MMU SP hugepage is disallowed Sean Christopherson
2022-12-14 11:58 ` Robert Hoo
2022-12-15 0:11 ` Sean Christopherson
2022-12-15 6:26 ` Robert Hoo
2022-12-13 3:30 ` [PATCH 4/5] KVM: x86/mmu: Don't install TDP MMU SPTE if SP has unexpected level Sean Christopherson
2022-12-13 17:59 ` David Matlack
2022-12-13 18:15 ` Sean Christopherson
2022-12-20 18:24 ` David Matlack
2022-12-13 3:30 ` [PATCH 5/5] KVM: x86/mmu: Move kvm_tdp_mmu_map()'s prolog and epilog to its caller Sean Christopherson
2022-12-20 17:53 ` David Matlack
2022-12-21 18:32 ` Sean Christopherson
2022-12-29 19:51 ` David Matlack
2022-12-29 21:06 ` Paolo Bonzini
2023-01-03 22:21 ` David Matlack
2022-12-14 12:01 ` Robert Hoo [this message]
2022-12-14 15:48 ` [PATCH 0/5] KVM: x86/mmu: TDP MMU fixes for 6.2 Sean Christopherson
2022-12-23 17:32 ` 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=acb8adfc5a2ace34010dc70d5ccd2821ff0a1ecb.camel@linux.intel.com \
--to=robert.hu@linux.intel.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=gthelen@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mizhang@google.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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