From: Yan Zhao <yan.y.zhao@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<isaku.yamahata@intel.com>, <binbin.wu@linux.intel.com>,
<rick.p.edgecombe@intel.com>
Subject: Re: [PATCH 13/18] KVM: x86/tdp_mmu: Propagate attr_filter to MMU notifier callbacks
Date: Tue, 17 Dec 2024 20:53:04 +0800 [thread overview]
Message-ID: <Z2F0MMiHf/CHwGjd@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <20241213195711.316050-14-pbonzini@redhat.com>
On Fri, Dec 13, 2024 at 02:57:06PM -0500, Paolo Bonzini wrote:
> Teach the MMU notifier callbacks how to check kvm_gfn_range.process to
> filter which KVM MMU root types to operate on.
>
> The private GPAs are backed by guest memfd. Such memory is not subjected
> to MMU notifier callbacks because it can't be mapped into the host user
> address space. Now kvm_gfn_range conveys info about which root to operate
> on. Enhance the callback to filter the root page table type.
>
> The KVM MMU notifier comes down to two functions.
> kvm_tdp_mmu_unmap_gfn_range() and __kvm_tdp_mmu_age_gfn_range():
> - invalidate_range_start() calls kvm_tdp_mmu_unmap_gfn_range()
> - invalidate_range_end() doesn't call into arch code
> - the other callbacks call __kvm_tdp_mmu_age_gfn_range()
>
> For VM's without a private/shared split in the EPT, all operations
> should target the normal(direct) root.
>
> With the switch from for_each_tdp_mmu_root() to
> __for_each_tdp_mmu_root() in kvm_tdp_mmu_handle_gfn(), there are no
> longer any users of for_each_tdp_mmu_root(). Remove it.
>
> Signed-off-by: Isaku Yamahata <isaku.yamahata@intel.com>
> Signed-off-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
> Message-ID: <20240718211230.1492011-14-rick.p.edgecombe@intel.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/x86/kvm/mmu/tdp_mmu.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu/tdp_mmu.c b/arch/x86/kvm/mmu/tdp_mmu.c
> index d17a3cf1596d..9a004c999a28 100644
> --- a/arch/x86/kvm/mmu/tdp_mmu.c
> +++ b/arch/x86/kvm/mmu/tdp_mmu.c
> @@ -193,9 +193,6 @@ static struct kvm_mmu_page *tdp_mmu_next_root(struct kvm *kvm,
> !tdp_mmu_root_match((_root), (_types)))) { \
> } else
>
> -#define for_each_tdp_mmu_root(_kvm, _root, _as_id) \
> - __for_each_tdp_mmu_root(_kvm, _root, _as_id, KVM_ALL_ROOTS)
> -
> #define for_each_valid_tdp_mmu_root(_kvm, _root, _as_id) \
> __for_each_tdp_mmu_root(_kvm, _root, _as_id, KVM_VALID_ROOTS)
>
> @@ -1172,12 +1169,16 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)
> return ret;
> }
>
> +/* Used by mmu notifier via kvm_unmap_gfn_range() */
> bool kvm_tdp_mmu_unmap_gfn_range(struct kvm *kvm, struct kvm_gfn_range *range,
> bool flush)
> {
> + enum kvm_tdp_mmu_root_types types;
> struct kvm_mmu_page *root;
>
> - __for_each_tdp_mmu_root_yield_safe(kvm, root, range->slot->as_id, KVM_ALL_ROOTS)
> + types = kvm_gfn_range_filter_to_root_types(kvm, range->attr_filter) | KVM_INVALID_ROOTS;
Just curious:
though adding KVM_INVALID_ROOTS matches the old KVM_ALL_ROOTS, why do we need
to unmap an invalid root?
> +
> + __for_each_tdp_mmu_root_yield_safe(kvm, root, range->slot->as_id, types)
> flush = tdp_mmu_zap_leafs(kvm, root, range->start, range->end,
> range->may_block, flush);
>
> @@ -1217,17 +1218,21 @@ static bool __kvm_tdp_mmu_age_gfn_range(struct kvm *kvm,
> struct kvm_gfn_range *range,
> bool test_only)
> {
> + enum kvm_tdp_mmu_root_types types;
> struct kvm_mmu_page *root;
> struct tdp_iter iter;
> bool ret = false;
>
> + types = kvm_gfn_range_filter_to_root_types(kvm, range->attr_filter);
> +
> /*
> * Don't support rescheduling, none of the MMU notifiers that funnel
> * into this helper allow blocking; it'd be dead, wasteful code. Note,
> * this helper must NOT be used to unmap GFNs, as it processes only
> * valid roots!
> */
> - for_each_valid_tdp_mmu_root(kvm, root, range->slot->as_id) {
> + WARN_ON(types & ~KVM_VALID_ROOTS);
> + __for_each_tdp_mmu_root(kvm, root, range->slot->as_id, types) {
> guard(rcu)();
>
> tdp_root_for_each_leaf_pte(iter, kvm, root, range->start, range->end) {
> --
> 2.43.5
>
>
next prev parent reply other threads:[~2024-12-17 13:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:56 [PATCH v5 00/18] TDX MMU prep series part 1 Paolo Bonzini
2024-12-13 19:56 ` [PATCH 01/18] KVM: x86/mmu: Zap invalid roots with mmu_lock holding for write at uninit Paolo Bonzini
2024-12-13 19:56 ` [PATCH 02/18] KVM: Add member to struct kvm_gfn_range for target alias Paolo Bonzini
2024-12-13 19:56 ` [PATCH 03/18] KVM: x86: Add a VM type define for TDX Paolo Bonzini
2024-12-13 19:56 ` [PATCH 04/18] KVM: x86/mmu: Add an external pointer to struct kvm_mmu_page Paolo Bonzini
2024-12-16 12:31 ` Huang, Kai
2024-12-13 19:56 ` [PATCH 05/18] KVM: x86/mmu: Add an is_mirror member for union kvm_mmu_page_role Paolo Bonzini
2024-12-13 19:56 ` [PATCH 06/18] KVM: x86/mmu: Make kvm_tdp_mmu_alloc_root() return void Paolo Bonzini
2024-12-13 19:57 ` [PATCH 07/18] KVM: x86/tdp_mmu: Take struct kvm in iter loops Paolo Bonzini
2024-12-13 19:57 ` [PATCH 08/18] KVM: x86/mmu: Support GFN direct bits Paolo Bonzini
2024-12-13 19:57 ` [PATCH 09/18] KVM: x86/tdp_mmu: Extract root invalid check from tdx_mmu_next_root() Paolo Bonzini
2024-12-16 12:35 ` Huang, Kai
2024-12-13 19:57 ` [PATCH 10/18] KVM: x86/tdp_mmu: Introduce KVM MMU root types to specify page table type Paolo Bonzini
2024-12-13 19:57 ` [PATCH 11/18] KVM: x86/tdp_mmu: Take root in tdp_mmu_for_each_pte() Paolo Bonzini
2024-12-13 19:57 ` [PATCH 12/18] KVM: x86/tdp_mmu: Support mirror root for TDP MMU Paolo Bonzini
2024-12-13 19:57 ` [PATCH 13/18] KVM: x86/tdp_mmu: Propagate attr_filter to MMU notifier callbacks Paolo Bonzini
2024-12-17 12:53 ` Yan Zhao [this message]
2024-12-13 19:57 ` [PATCH 14/18] KVM: x86/tdp_mmu: Propagate building mirror page tables Paolo Bonzini
2024-12-13 19:57 ` [PATCH 15/18] KVM: x86/tdp_mmu: Propagate tearing down " Paolo Bonzini
2024-12-13 19:57 ` [PATCH 16/18] KVM: x86/tdp_mmu: Take root types for kvm_tdp_mmu_invalidate_all_roots() Paolo Bonzini
2024-12-13 19:57 ` [PATCH 17/18] KVM: x86/tdp_mmu: Don't zap valid mirror roots in kvm_tdp_mmu_zap_all() Paolo Bonzini
2024-12-18 2:49 ` Yan Zhao
2024-12-13 19:57 ` [PATCH 18/18] KVM: x86/mmu: Prevent aliased memslot GFNs Paolo Bonzini
2024-12-18 0:34 ` [PATCH v5 00/18] TDX MMU prep series part 1 Edgecombe, Rick P
2024-12-20 9:32 ` Yan Zhao
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=Z2F0MMiHf/CHwGjd@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=binbin.wu@linux.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 \
/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®