From: Yan Zhao <yan.y.zhao@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Isaku Yamahata <isaku.yamahata@intel.com>, <kvm@vger.kernel.org>,
<sagis@google.com>, <chao.gao@intel.com>, <pbonzini@redhat.com>,
<rick.p.edgecombe@intel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86/tdp_mmu: Trigger the callback only when an interesting change
Date: Sun, 29 Sep 2024 17:29:54 +0800 [thread overview]
Message-ID: <ZvkeEtBk8BvR4Hms@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <Zva4aORxE9ljlMNe@google.com>
On Fri, Sep 27, 2024 at 06:51:58AM -0700, Sean Christopherson wrote:
> On Thu, Sep 26, 2024, Yan Zhao wrote:
> > On Thu, Sep 12, 2024 at 05:07:57PM -0700, Sean Christopherson wrote:
> > > > diff --git a/arch/x86/kvm/mmu/spte.h b/arch/x86/kvm/mmu/spte.h
> > > > index a72f0e3bde17..1726f8ec5a50 100644
> > > > --- a/arch/x86/kvm/mmu/spte.h
> > > > +++ b/arch/x86/kvm/mmu/spte.h
> > > > @@ -214,6 +214,12 @@ extern u64 __read_mostly shadow_nonpresent_or_rsvd_mask;
> > > > */
> > > > #define FROZEN_SPTE (SHADOW_NONPRESENT_VALUE | 0x5a0ULL)
> > > >
> > > > +#define EXTERNAL_SPTE_IGNORE_CHANGE_MASK \
> > > > + (shadow_acc_track_mask | \
> > > > + (SHADOW_ACC_TRACK_SAVED_BITS_MASK << \
> > > > + SHADOW_ACC_TRACK_SAVED_BITS_SHIFT) | \
> > >
> > > Just make TDX require A/D bits, there's no reason to care about access tracking.
> > If KVM_PRE_FAULT_MEMORY is allowed for TDX and if
> > cpu_has_vmx_ept_ad_bits() is false in TDX's hardware (not sure if it's possible),
>
> Make it a requirement in KVM that TDX hardware supports A/D bits and that KVM's
> module param is enabled. EPT A/D bits have been supported in all CPUs since
> Haswell, I don't expect them to ever go away.
Got it!
>
> > access tracking bit is possbile to be changed, as in below scenario:
> >
> > 1. KVM_PRE_FAULT_MEMORY ioctl calls kvm_arch_vcpu_pre_fault_memory() to map
> > a GFN, and make_spte() will call mark_spte_for_access_track() to
> > remove shadow_acc_track_mask (i.e. RWX bits) and move R+X left to
> > SHADOW_ACC_TRACK_SAVED_BITS_SHIFT.
> > 2. If a concurrent page fault occurs on the same GFN on another vCPU, then
> > make_spte() in that vCPU will not see prefetch and the new_spte is
> > with RWX bits and with no bits set in SHADOW_ACC_TRACK_SAVED_MASK.
>
> This should be fixed by the mega-series. I'll make sure to Cc you on that series.
Thanks!
> Thanks much for the input and feedback!
:)
prev parent reply other threads:[~2024-09-29 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 23:36 Isaku Yamahata
2024-09-13 0:07 ` Sean Christopherson
2024-09-13 1:22 ` Isaku Yamahata
2024-09-26 7:53 ` Yan Zhao
2024-09-27 13:51 ` Sean Christopherson
2024-09-27 14:32 ` Sean Christopherson
2024-09-27 15:06 ` Sean Christopherson
2024-10-08 2:57 ` Yan Zhao
2024-10-08 19:15 ` Sean Christopherson
2024-10-09 9:21 ` Yan Zhao
2024-10-09 13:14 ` Sean Christopherson
2024-09-29 9:27 ` Yan Zhao
2024-09-30 15:54 ` Sean Christopherson
2024-10-08 0:44 ` Yan Zhao
2024-10-08 16:07 ` Sean Christopherson
2024-09-29 9:29 ` Yan Zhao [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=ZvkeEtBk8BvR4Hms@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=chao.gao@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sagis@google.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
all inboxes | Powered by JetHome®