drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups
Subsystems (6)
Sean Christopherson
maintainerv2 cover drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups
Fix a variety of found-by-inspection bugs in KVMGT, and overhaul KVM's page-track APIs to provide a leaner and cleaner interface. The motivation for this series is to (significantly) reduce the number of KVM APIs that KVMGT uses, with a long-term goal of making all kvm_host.h headers KVM-internal.
As was the case in v1, tThe KVMGT changes are compile tested only.
Based on "git://git.kernel.org/pub/scm/virt/kvm/kvm.git next".
v2:
- Reuse vgpu_lock to protect gfn hash instead of introducing a new (and buggy) mutext. [Yan]
- Remove a spurious return from kvm_page_track_init(). [Yan]
- Take @kvm directly in the inner __kvm_page_track_write(). [Yan]
- Delete the gfn sanity check that relies on kvm_is_visible_gfn() instead of providing a dedicated interface. [Yan]
v1: https://lore.kernel.org/lkml/[email protected]
Sean Christopherson (23):
drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
KVM: x86/mmu: Factor out helper to get max mapping size of a memslot drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT
entry
drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt
entry
drm/i915/gvt: Put the page reference obtained by KVM's gfn_to_pfn() drm/i915/gvt: Don't rely on KVM's gfn_to_pfn() to query possible 2M
GTT
drm/i915/gvt: Use an "unsigned long" to iterate over memslot gfns drm/i915/gvt: Drop unused helper intel_vgpu_reset_gtt() drm/i915/gvt: Protect gfn hash table with vgpu_lock
KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot
change
KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs
KVM: drm/i915/gvt: Drop @vcpu from KVM's ->track_write() hook
KVM: x86: Reject memslot MOVE operations if KVMGT is attached drm/i915/gvt: Don't bother removing write-protection on to-be-deleted
slot
KVM: x86/mmu: Move KVM-only page-track declarations to internal header
KVM: x86/mmu: Use page-track notifiers iff there are external users
KVM: x86/mmu: Drop infrastructure for multiple page-track modes
KVM: x86/mmu: Rename page-track APIs to reflect the new reality
KVM: x86/mmu: Assert that correct locks are held for page
write-tracking
KVM: x86/mmu: Bug the VM if write-tracking is used but not enabled
KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
KVM: x86/mmu: Handle KVM bookkeeping in page-track APIs, not callers drm/i915/gvt: Drop final dependencies on KVM internal details
Yan Zhao (4):
drm/i915/gvt: remove interface intel_gvt_is_valid_gfn
KVM: x86: Add a new page-track hook to handle memslot deletion drm/i915/gvt: switch from ->track_flush_slot() to
->track_remove_region()
KVM: x86: Remove the unused page-track hook track_flush_slot()
arch/x86/include/asm/kvm_host.h | 16 +- arch/x86/include/asm/kvm_page_track.h | 66 +++---- arch/x86/kvm/mmu.h | 2 + arch/x86/kvm/mmu/mmu.c | 61 +++--- arch/x86/kvm/mmu/mmu_internal.h | 2 + arch/x86/kvm/mmu/page_track.c | 270 ++++++++++++++------------ arch/x86/kvm/mmu/page_track.h | 58 ++++++ arch/x86/kvm/x86.c | 13 +- drivers/gpu/drm/i915/gvt/gtt.c | 88 ++------- drivers/gpu/drm/i915/gvt/gtt.h | 1 - drivers/gpu/drm/i915/gvt/gvt.h | 3 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 132 ++++++------- drivers/gpu/drm/i915/gvt/page_track.c | 10 +- 13 files changed, 361 insertions(+), 361 deletions(-) create mode 100644 arch/x86/kvm/mmu/page_track.h
base-commit: 45dd9bc75d9adc9483f0c7d662ba6e73ed698a0b
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 1/27 drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
Check that the pfn found by gfn_to_pfn() is actually backed by "struct page" memory prior to retrieving and dereferencing the page. KVM supports backing guest memory with VM_PFNMAP, VM_IO, etc., and so there is no guarantee the pfn returned by gfn_to_pfn() has an associated "struct page".
--- drivers/gpu/drm/i915/gvt/gtt.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/gpu/drm/i915/gvt/gtt.c +4 -0
@@ -1183,6 +1183,10 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, pfn =gfn_to_pfn (vgpu->vfio_device.kvm, ops->get_pfn (entry));if (is_error_noslot_pfn (pfn))return -EINVAL ; + +if (!pfn_valid (pfn)) +return -EINVAL ; +return PageTransHuge (pfn_to_page (pfn)); }
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
RE: [PATCH v2 01/27] drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
drivers/gpu/drm/i915/gvt/gtt.c static int is_2MB_gtt_possible(struct intel_vgpu · line 1190
Quoted 13 lines · Sean Christopherson
drivers/gpu/drm/i915/gvt/gtt.c +4
-0@@ -1183,6 +1183,10 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, pfn =gfn_to_pfn (vgpu->vfio_device.kvm, ops->get_pfn (entry));if (is_error_noslot_pfn (pfn))return -EINVAL ; + +if (!pfn_valid (pfn)) +return -EINVAL ; +
Merge the two errors in one "if" to have less LOC? i.e.
if (is_error_noslot_pfn(pfn) || !pfn_valid(pfn))
return -EINVAL;
Re: [Intel-gfx] [PATCH v2 01/27] drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
Quoted 18 lines · Wei W
drivers/gpu/drm/i915/gvt/gtt.c static int is_2MB_gtt_possible(struct intel_vgpu · line 1190
Quoted 13 lines · Sean Christopherson
drivers/gpu/drm/i915/gvt/gtt.c +4
-0@@ -1183,6 +1183,10 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, pfn =gfn_to_pfn (vgpu->vfio_device.kvm, ops->get_pfn (entry));if (is_error_noslot_pfn (pfn))return -EINVAL ; + +if (!pfn_valid (pfn)) +return -EINVAL ; +Merge the two errors in one "if" to have less LOC? i.e.
if (is_error_noslot_pfn(pfn)|| !pfn_valid(pfn))
Quoted 1 line
return -EINVAL;
you can just replace "if (is_error_noslot_pfn(pfn))" with "if (!pfn_valid(pfn))", it covers both cases.
Regards
Andrzej
Sean Christopherson
maintainerRe: [Intel-gfx] [PATCH v2 01/27] drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
Quoted 21 lines · Andrzej Hajda
Quoted 18 lines · Wei W
drivers/gpu/drm/i915/gvt/gtt.c static int is_2MB_gtt_possible(struct intel_vgpu · line 1190
Quoted 13 lines · Sean Christopherson
drivers/gpu/drm/i915/gvt/gtt.c +4
-0@@ -1183,6 +1183,10 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, pfn =gfn_to_pfn (vgpu->vfio_device.kvm, ops->get_pfn (entry));if (is_error_noslot_pfn (pfn))return -EINVAL ; + +if (!pfn_valid (pfn)) +return -EINVAL ; +Merge the two errors in one "if" to have less LOC? i.e.
if (is_error_noslot_pfn(pfn)|| !pfn_valid(pfn))Quoted 1 line
return -EINVAL;
Quoted 2 lines
you can just replace "if (
is_error_noslot_pfn(pfn))" with "if (!pfn_valid(pfn))", it covers both cases.
Technically, yes, but the two checks are for very different things. Practically speaking, there can never be false negatives without KVM breaking horribly as overlap between struct page pfns and KVM's error/noslot would prevent mapping legal memory into a KVM guest. But I'd rather not hide the "did KVM find a valid mapping" in the "is this pfn backed by struct page" check, especially since this code goes away entirely by the end of the series.
Re: [PATCH v2 01/27] drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
In reply to Sean ChristophersonQuoted 30 lines · Sean Christopherson
Check that the pfn found by
gfn_to_pfn()is actually backed by "struct page" memory prior to retrieving and dereferencing the page. KVM supports backing guest memory withVM_PFNMAP,VM_IO, etc., and so there is no guarantee the pfn returned bygfn_to_pfn()has an associated "struct page".Fixes b901b252b6cf ("drm/i915/gvt: Add 2M huge gtt support")Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/gtt.c | 4 ++++ 1 file changed, 4 insertions(+)drivers/gpu/drm/i915/gvt/gtt.c +4
-0@@ -1183,6 +1183,10 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, pfn =gfn_to_pfn (vgpu->vfio_device.kvm, ops->get_pfn (entry));if (is_error_noslot_pfn (pfn))return -EINVAL ; + +if (!pfn_valid (pfn)) +return -EINVAL ; +return PageTransHuge (pfn_to_page (pfn)); }Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 2/27 KVM: x86/mmu: Factor out helper to get max mapping size of a memslot
In reply to Sean ChristophersonExtract the memslot-related logic of kvm_mmu_max_mapping_level() into a new helper so that KVMGT can determine whether or not mapping a 2MiB page into the guest is (dis)allowed per KVM's memslots.
No functional change intended.
--- arch/x86/kvm/mmu/mmu.c | 21 +++++++++++++++------ arch/x86/kvm/mmu/mmu_internal.h | 2 ++ 2 files changed, 17 insertions(+), 6 deletions(-)
arch/x86/kvm/mmu/mmu.c +15 -6
@@ -3083,20 +3083,29 @@ static int host_pfn_mapping_level(struct kvm *kvm, gfn_t gfn,return level; } +int kvm_mmu_max_slot_mapping_level (const struct kvm_memory_slot *slot, +gfn_t gfn,int max_level) +{ +struct kvm_lpage_info *linfo; + +for ( ; max_level >PG_LEVEL_4K ; max_level--) { + linfo =lpage_info_slot (gfn, slot, max_level); +if (!linfo->disallow_lpage) +break ; + } +return max_level; +} +int kvm_mmu_max_mapping_level (struct kvm *kvm,const struct kvm_memory_slot *slot,gfn_t gfn,int max_level) { -struct kvm_lpage_info *linfo;int host_level; max_level =min (max_level, max_huge_page_level); -for ( ; max_level >PG_LEVEL_4K ; max_level--) { - linfo =lpage_info_slot (gfn, slot, max_level); -if (!linfo->disallow_lpage) -break ; - } + max_level =kvm_mmu_max_slot_mapping_level (slot, gfn, max_level); +/* Avoid walking the host page tables if a hugepage is impossible. */ if (max_level ==PG_LEVEL_4K )return PG_LEVEL_4K ;
arch/x86/kvm/mmu/mmu_internal.h +2 -0
@@ -328,6 +328,8 @@ static inline int kvm_mmu_do_page_fault(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa,return r; } +int kvm_mmu_max_slot_mapping_level (const struct kvm_memory_slot *slot, +gfn_t gfn,int max_level);int kvm_mmu_max_mapping_level (struct kvm *kvm,const struct kvm_memory_slot *slot,gfn_t gfn,int max_level);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
RE: [PATCH v2 02/27] KVM: x86/mmu: Factor out helper to get max mapping size of a memslot
Quoted 17 lines · Sean Christopherson
Extract the memslot-related logic of
kvm_mmu_max_mapping_level()into a new helper so that KVMGT can determine whether or not mapping a 2MiB page into the guest is (dis)allowed per KVM's memslots.No functional change intended.
Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/kvm/mmu/mmu.c | 21 +++++++++++++++------ arch/x86/kvm/mmu/mmu_internal.h | 2 ++ 2 files changed, 17 insertions(+), 6 deletions(-)arch/x86/kvm/mmu/mmu.c index renamed from arch/x86/kvm/mmu/mmu.c +0
-0
c8ebe542c565..4685c80e441b100644
arch/x86/kvm/mmu/mmu.c static int host_pfn_mapping_level(struct kvm · line 3088
Quoted 6 lines
arch/x86/kvm/mmu/mmu.c +2
-0@@ -3083,20 +3083,29 @@ static int host_pfn_mapping_level(struct kvm *kvm, gfn_t gfn, return level; } +int kvm_mmu_max_slot_mapping_level (const struct kvm_memory_slot *slot, +gfn_t gfn,int max_level)
It seems more common to be named "kvm_mmu_slot_max_mapping_level" (we have other kvm_mmu_slot_* functions defined already)
Quoted 9 lines
arch/x86/kvm/mmu/mmu.c +9
-0+{ +struct kvm_lpage_info *linfo; + +for ( ; max_level >PG_LEVEL_4K ; max_level--) { + linfo =lpage_info_slot (gfn, slot, max_level); +if (!linfo->disallow_lpage) +break ; + } +return max_level;
arch/x86/kvm/mmu/mmu.c static int host_pfn_mapping_level(struct kvm *kvm, gfn_t gfn, · line 3105
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +2
-1+} +int kvm_mmu_max_mapping_level (struct kvm *kvm,const struct kvm_memory_slot *slot,gfn_t gfn,int max_level) { -struct kvm_lpage_info *linfo;int host_level; max_level =min (max_level, max_huge_page_level);
Better to also have this min(,) moved to the helper?
E.g. if max_huge_page_level has been 4KB, no need to check into lpage_info in the helper.
Sean Christopherson
maintainerPATCH v2 3/27 drm/i915/gvt: remove interface intel_gvt_is_valid_gfn
In reply to Sean ChristophersonFrom: Yan Zhao <[email protected]>
Currently intel_gvt_is_valid_gfn() is called in two places:
(1) shadowing guest GGTT entry
(2) shadowing guest PPGTT leaf entry,
which was introduced in commit cc753fbe1ac4 ("drm/i915/gvt: validate gfn before set shadow page entry").
However, now it's not necessary to call this interface any more, because a. GGTT partial write issue has been fixed by
commit bc0686ff5fad
("drm/i915/gvt: support inconsecutive partial gtt entry write") commit 510fe10b6180
("drm/i915/gvt: fix a bug of partially write ggtt enties")
b. PPGTT resides in normal guest RAM and we only treat 8-byte writes
as valid page table writes. Any invalid GPA found is regarded as an error, either due to guest misbehavior/attack or bug in host shadow code.
So,rather than do GFN pre-checking and replace invalid GFNs with scratch GFN and continue silently, just remove the pre-checking and abort PPGTT shadowing on error detected.
c. GFN validity check is still performed in
intel_gvt_dma_map_guest_page() --> gvt_pin_guest_page(). It's more desirable to call VFIO interface to do both validity check and mapping.
Calling intel_gvt_is_valid_gfn() to do GFN validity check from KVM side while later mapping the GFN through VFIO interface is unnecessarily fragile and confusing for unaware readers.
--- drivers/gpu/drm/i915/gvt/gtt.c | 36 +--------------------------------- 1 file changed, 1 insertion(+), 35 deletions(-)
drivers/gpu/drm/i915/gvt/gtt.c +1 -35
@@ -49,22 +49,6 @@static bool enable_out_of_sync = false;static int preallocated_oos_pages =8192 ; -static bool intel_gvt_is_valid_gfn (struct intel_vgpu *vgpu,unsigned long gfn) -{ -struct kvm *kvm = vgpu->vfio_device.kvm; -int idx; -bool ret; - -if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , vgpu->status)) -return false; - - idx =srcu_read_lock (&kvm->srcu); - ret =kvm_is_visible_gfn (kvm, gfn); -srcu_read_unlock (&kvm->srcu, idx); - -return ret; -} -/* * validate a gm address and related range size, * translate it to host gm address
@@ -1333,11 +1317,9 @@ static int ppgtt_populate_shadow_entry(struct intel_vgpu *vgpu,static int ppgtt_populate_spt (struct intel_vgpu_ppgtt_spt *spt) {struct intel_vgpu *vgpu = spt->vgpu; -struct intel_gvt *gvt = vgpu->gvt; -const struct intel_gvt_gtt_pte_ops *ops = gvt->gtt.pte_ops;struct intel_vgpu_ppgtt_spt *s;struct intel_gvt_gtt_entry se, ge; -unsigned long gfn, i; +unsigned long i;int ret; trace_spt_change(spt->vgpu->id, "born", spt,
@@ -1354,13 +1336,6 @@ static int ppgtt_populate_spt(struct intel_vgpu_ppgtt_spt *spt)ppgtt_generate_shadow_entry (&se, s, &ge);ppgtt_set_shadow_entry (spt, &se, i); }else { - gfn = ops->get_pfn (&ge); -if (!intel_gvt_is_valid_gfn (vgpu, gfn)) { - ops->set_pfn (&se, gvt->gtt.scratch_mfn); -ppgtt_set_shadow_entry (spt, &se, i); -continue ; - } - ret =ppgtt_populate_shadow_entry (vgpu, spt, i, &ge);if (ret) goto fail;
@@ -2335,14 +2310,6 @@ static int emulate_ggtt_mmio_write(struct intel_vgpu *vgpu, unsigned int off, m.val64 = e.val64; m.type = e.type; -/* one PTE update may be issued in multiple writes and the -* first write may not construct a valid gfn -*/ -if (!intel_gvt_is_valid_gfn (vgpu, gfn)) { - ops->set_pfn (&m, gvt->gtt.scratch_mfn); - goto out; - } - ret =intel_gvt_dma_map_guest_page (vgpu, gfn,PAGE_SIZE , &dma_addr);if (ret) {
@@ -2359,7 +2326,6 @@ static int emulate_ggtt_mmio_write(struct intel_vgpu *vgpu, unsigned int off, ops->clear_present (&m); } -out:ggtt_set_guest_entry (ggtt_mm, &e, g_gtt_index);ggtt_get_host_entry (ggtt_mm, &e, g_gtt_index);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 03/27] drm/i915/gvt: remove interface intel_gvt_is_valid_gfn
Quoted 116 lines · Sean Christopherson
From: Yan Zhao <[email protected]>
Currently
intel_gvt_is_valid_gfn()is called in two places:
(1) shadowing guest GGTT entry
(2) shadowing guest PPGTT leaf entry,
which was introduced in commitcc753fbe1ac4("drm/i915/gvt: validate gfn before set shadow page entry").However, now it's not necessary to call this interface any more, because a. GGTT partial write issue has been fixed by
commitbc0686ff5fad
("drm/i915/gvt: support inconsecutive partial gtt entry write") commit510fe10b6180
("drm/i915/gvt: fix a bug of partially write ggtt enties")
b. PPGTT resides in normal guest RAM and we only treat 8-byte writes
as valid page table writes. Any invalid GPA found is regarded as an error, either due to guest misbehavior/attack or bug in host shadow code.
So,rather than do GFN pre-checking and replace invalid GFNs with scratch GFN and continue silently, just remove the pre-checking and abort PPGTT shadowing on error detected.
c. GFN validity check is still performed in
intel_gvt_dma_map_guest_page()-->gvt_pin_guest_page(). It's more desirable to call VFIO interface to do both validity check and mapping.
Callingintel_gvt_is_valid_gfn()to do GFN validity check from KVM side while later mapping the GFN through VFIO interface is unnecessarily fragile and confusing for unaware readers.Signed-off-by Yan Zhao <[email protected]>[sean: remove now-unused local variables]Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/gtt.c | 36 +--------------------------------- 1 file changed, 1 insertion(+), 35 deletions(-)drivers/gpu/drm/i915/gvt/gtt.c +1
-35@@ -49,22 +49,6 @@static bool enable_out_of_sync = false;static int preallocated_oos_pages =8192 ; -static bool intel_gvt_is_valid_gfn (struct intel_vgpu *vgpu,unsigned long gfn) -{ -struct kvm *kvm = vgpu->vfio_device.kvm; -int idx; -bool ret; - -if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , vgpu->status)) -return false; - - idx =srcu_read_lock (&kvm->srcu); - ret =kvm_is_visible_gfn (kvm, gfn); -srcu_read_unlock (&kvm->srcu, idx); - -return ret; -} -/* * validate a gm address and related range size, * translate it to host gm address @@ -1333,11 +1317,9 @@ static int ppgtt_populate_shadow_entry(struct intel_vgpu *vgpu,static int ppgtt_populate_spt (struct intel_vgpu_ppgtt_spt *spt) {struct intel_vgpu *vgpu = spt->vgpu; -struct intel_gvt *gvt = vgpu->gvt; -const struct intel_gvt_gtt_pte_ops *ops = gvt->gtt.pte_ops;struct intel_vgpu_ppgtt_spt *s;struct intel_gvt_gtt_entry se, ge; -unsigned long gfn, i; +unsigned long i;int ret; trace_spt_change(spt->vgpu->id, "born", spt,@@ -1354,13 +1336,6 @@ static int ppgtt_populate_spt(struct intel_vgpu_ppgtt_spt *spt)ppgtt_generate_shadow_entry (&se, s, &ge);ppgtt_set_shadow_entry (spt, &se, i); }else { - gfn = ops->get_pfn (&ge); -if (!intel_gvt_is_valid_gfn (vgpu, gfn)) { - ops->set_pfn (&se, gvt->gtt.scratch_mfn); -ppgtt_set_shadow_entry (spt, &se, i); -continue ; - } - ret =ppgtt_populate_shadow_entry (vgpu, spt, i, &ge);if (ret) goto fail;@@ -2335,14 +2310,6 @@ static int emulate_ggtt_mmio_write(struct intel_vgpu *vgpu, unsigned int off, m.val64 = e.val64; m.type = e.type; -/* one PTE update may be issued in multiple writes and the -* first write may not construct a valid gfn -*/ -if (!intel_gvt_is_valid_gfn (vgpu, gfn)) { - ops->set_pfn (&m, gvt->gtt.scratch_mfn); - goto out; - } - ret =intel_gvt_dma_map_guest_page (vgpu, gfn,PAGE_SIZE , &dma_addr);if (ret) {@@ -2359,7 +2326,6 @@ static int emulate_ggtt_mmio_write(struct intel_vgpu *vgpu, unsigned int off, ops->clear_present (&m); } -out:ggtt_set_guest_entry (ggtt_mm, &e, g_gtt_index);ggtt_get_host_entry (ggtt_mm, &e, g_gtt_index);Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 4/27 drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT entry
In reply to Sean ChristophersonHonor KVM's max allowed page size when determining whether or not a 2MiB GTT shadow page can be created for the guest. Querying KVM's max allowed size is somewhat odd as there's no strict requirement that KVM's memslots and VFIO's mappings are configured with the same gfn=>hva mapping, but the check will be accurate if userspace wants to have a functional guest, and at the very least checking KVM's memslots guarantees that the entire 2MiB range has been exposed to the guest.
Note, KVM may also restrict the mapping size for reasons that aren't relevant to KVMGT, e.g. for KVM's iTLB multi-hit workaround or if the gfn is write-tracked (KVM's write-tracking only handles writes from vCPUs). However, such scenarios are unlikely to occur with a well-behaved guest, and at worst will result in sub-optimal performance.
--- arch/x86/include/asm/kvm_page_track.h | 2 ++ arch/x86/kvm/mmu/page_track.c | 18 ++++++++++++++++++ drivers/gpu/drm/i915/gvt/gtt.c | 10 +++++++++- 3 files changed, 29 insertions(+), 1 deletion(-)
arch/x86/include/asm/kvm_page_track.h +2 -0
@@ -51,6 +51,8 @@ void kvm_page_track_cleanup(struct kvm *kvm);bool kvm_page_track_write_tracking_enabled (struct kvm *kvm);int kvm_page_track_write_tracking_alloc (struct kvm_memory_slot *slot); +enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn, +enum pg_level max_level);void kvm_page_track_free_memslot (struct kvm_memory_slot *slot); int kvm_page_track_create_memslot(struct kvm *kvm,
arch/x86/kvm/mmu/page_track.c +18 -0
@@ -301,3 +301,21 @@ void kvm_page_track_flush_slot(struct kvm *kvm, struct kvm_memory_slot *slot) n->track_flush_slot (kvm, slot, n);srcu_read_unlock (&head->track_srcu, idx); } + +enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn, +enum pg_level max_level) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + slot =gfn_to_memslot (kvm, gfn); +if (!slot || slot->flags &KVM_MEMSLOT_INVALID ) + max_level =PG_LEVEL_4K ; +else + max_level =kvm_mmu_max_slot_mapping_level (slot, gfn, max_level); +srcu_read_unlock (&kvm->srcu, idx); + +return max_level; +} +EXPORT_SYMBOL_GPL (kvm_page_track_max_mapping_level);
drivers/gpu/drm/i915/gvt/gtt.c +9 -1
@@ -1157,14 +1157,22 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, struct intel_gvt_gtt_entry *entry) {const struct intel_gvt_gtt_pte_ops *ops = vgpu->gvt->gtt.pte_ops; +unsigned long gfn = ops->get_pfn (entry);kvm_pfn_t pfn; +int max_level;if (!HAS_PAGE_SIZES (vgpu->gvt->gt->i915,I915_GTT_PAGE_SIZE_2M ))return 0 ;if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , vgpu->status))return -EINVAL ; - pfn =gfn_to_pfn (vgpu->vfio_device.kvm, ops->get_pfn (entry)); + + max_level =kvm_page_track_max_mapping_level (vgpu->vfio_device.kvm, + gfn,PG_LEVEL_2M ); +if (max_level <PG_LEVEL_2M ) +return 0 ; + + pfn =gfn_to_pfn (vgpu->vfio_device.kvm, gfn);if (is_error_noslot_pfn (pfn))return -EINVAL ;
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 04/27] drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT entry
Quoted 8 lines · Sean Christopherson
Honor KVM's max allowed page size when determining whether or not a 2MiB GTT shadow page can be created for the guest. Querying KVM's max allowed size is somewhat odd as there's no strict requirement that KVM's memslots and VFIO's mappings are configured with the same gfn=>hva mapping, but the check will be accurate if userspace wants to have a functional guest, and at the very least checking KVM's memslots guarantees that the entire 2MiB range has been exposed to the guest.
hi Sean,
I remember in our last discussion, the conclusion was that we can safely just use VFIO ABI (which is intel_gvt_dma_map_guest_page() introduced in patch 7) to check max mapping size. [1][2]
"Though checking kvm_page_track_max_mapping_level() is also fine, it makes DMA mapping size unnecessarily smaller."
This is especially true when the guest page is page tracked by kvm internally for nested VMs, but is not page tracked by kvmgt as ppgtt page table pages. kvmgt is ok to map those pages as huge when 4k is returned in kvm_page_track_max_mapping_level() for this reason.
"I'm totally fine if KVMGT's ABI is that VFIO is the source of truth for mappings and permissions, and that the only requirement for KVM memslots is that GTT page tables need to be visible in KVM's memslots. But if that's the ABI, then intel_gvt_is_valid_gfn() should be probing VFIO, not KVM (commit cc753fbe1ac4 ("drm/i915/gvt: validate gfn before set shadow page entry").
In other words, pick either VFIO or KVM. Checking that X is valid according to KVM and then mapping X through VFIO is confusing and makes assumptions about how userspace configures KVM and VFIO. It works because QEMU always configures KVM and VFIO as expected, but IMO it's unnecessarily fragile and again confusing for unaware readers because the code is technically flawed.
"
[1] https://lore.kernel.org/all/[email protected]/
[2] https://lore.kernel.org/all/[email protected]/
Quoted 5 lines
Note, KVM may also restrict the mapping size for reasons that aren't relevant to KVMGT, e.g. for KVM's iTLB multi-hit workaround or if the gfn is write-tracked (KVM's write-tracking only handles writes from vCPUs). However, such scenarios are unlikely to occur with a well-behaved guest, and at worst will result in sub-optimal performance.
As being confirmed in [3], there's no risk of iTLB multi-hit even for not-well-behaved guests if page tables for DMA mappings in IOMMU page tables are in a separated set of tables from EPT/NPT (which is the by default condition currently).
[3] https://lore.kernel.org/all/Y7%[email protected]/
So, I'm fine with exporting this kvm_page_track_max_mapping_level() interface, but I don't think KVMGT is a user of it.
Quoted 80 lines
Fixes b901b252b6cf ("drm/i915/gvt: Add 2M huge gtt support")Signed-off-by Yan Zhao <[email protected]>Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_page_track.h | 2 ++ arch/x86/kvm/mmu/page_track.c | 18 ++++++++++++++++++ drivers/gpu/drm/i915/gvt/gtt.c | 10 +++++++++- 3 files changed, 29 insertions(+), 1 deletion(-)arch/x86/include/asm/kvm_page_track.h +2
-0@@ -51,6 +51,8 @@ void kvm_page_track_cleanup(struct kvm *kvm);bool kvm_page_track_write_tracking_enabled (struct kvm *kvm);int kvm_page_track_write_tracking_alloc (struct kvm_memory_slot *slot); +enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn, +enum pg_level max_level);void kvm_page_track_free_memslot (struct kvm_memory_slot *slot); int kvm_page_track_create_memslot(struct kvm *kvm,arch/x86/kvm/mmu/page_track.c +18
-0@@ -301,3 +301,21 @@ void kvm_page_track_flush_slot(struct kvm *kvm, struct kvm_memory_slot *slot) n->track_flush_slot (kvm, slot, n);srcu_read_unlock (&head->track_srcu, idx); } + +enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn, +enum pg_level max_level) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + slot =gfn_to_memslot (kvm, gfn); +if (!slot || slot->flags &KVM_MEMSLOT_INVALID ) + max_level =PG_LEVEL_4K ; +else + max_level =kvm_mmu_max_slot_mapping_level (slot, gfn, max_level); +srcu_read_unlock (&kvm->srcu, idx); + +return max_level; +} +EXPORT_SYMBOL_GPL (kvm_page_track_max_mapping_level);drivers/gpu/drm/i915/gvt/gtt.c +9
-1@@ -1157,14 +1157,22 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, struct intel_gvt_gtt_entry *entry) {const struct intel_gvt_gtt_pte_ops *ops = vgpu->gvt->gtt.pte_ops; +unsigned long gfn = ops->get_pfn (entry);kvm_pfn_t pfn; +int max_level;if (!HAS_PAGE_SIZES (vgpu->gvt->gt->i915,I915_GTT_PAGE_SIZE_2M ))return 0 ;if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , vgpu->status))return -EINVAL ; - pfn =gfn_to_pfn (vgpu->vfio_device.kvm, ops->get_pfn (entry)); + + max_level =kvm_page_track_max_mapping_level (vgpu->vfio_device.kvm, + gfn,PG_LEVEL_2M ); +if (max_level <PG_LEVEL_2M ) +return 0 ; + + pfn =gfn_to_pfn (vgpu->vfio_device.kvm, gfn);if (is_error_noslot_pfn (pfn))return -EINVAL ;Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerRe: [PATCH v2 04/27] drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT entry
Quoted 9 lines · Yan Zhao
Quoted 8 lines · Sean Christopherson
Honor KVM's max allowed page size when determining whether or not a 2MiB GTT shadow page can be created for the guest. Querying KVM's max allowed size is somewhat odd as there's no strict requirement that KVM's memslots and VFIO's mappings are configured with the same gfn=>hva mapping, but the check will be accurate if userspace wants to have a functional guest, and at the very least checking KVM's memslots guarantees that the entire 2MiB range has been exposed to the guest.
Quoted 4 lines
hi Sean,
I remember in our last discussion, the conclusion was that we can safely just use VFIO ABI (which isintel_gvt_dma_map_guest_page()introduced in patch 7) to check max mapping size. [1][2]
Gah, my apologies. I completely forgot about dropping KVM's mapping size check. I was pretty sure I was forgetting something, but couldn't figure out what I was forgetting. I'll drop this in the next version.
Thanks!
Sean Christopherson
maintainerPATCH v2 5/27 drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
In reply to Sean ChristophersonWhen shadowing a GTT entry with a 2M page, explicitly verify that the first page pinned by VFIO is a transparent hugepage instead of assuming that page observed by is_2MB_gtt_possible() is the same page pinned by vfio_pin_pages(). E.g. if userspace is doing something funky with the guest's memslots, or if the page is demoted between is_2MB_gtt_possible() and vfio_pin_pages().
This is more of a performance optimization than a bug fix as the check for contiguous struct pages should guard against incorrect mapping (even though assuming struct pages are virtually contiguous is wrong).
The real motivation for explicitly checking for a transparent hugepage after pinning is that it will reduce the risk of introducing a bug in a future fix for a page refcount leak (KVMGT doesn't put the reference acquired by gfn_to_pfn()), and eventually will allow KVMGT to stop using KVM's gfn_to_pfn() altogether.
--- drivers/gpu/drm/i915/gvt/kvmgt.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/gvt/kvmgt.c +16 -2
@@ -159,11 +159,25 @@ static int gvt_pin_guest_page(struct intel_vgpu *vgpu, unsigned long gfn, goto err; } -if (npage ==0 ) - base_page = cur_page; +if (npage ==0 ) { +/* +* Bail immediately to avoid unnecessary pinning when +* trying to shadow a 2M page and the host page isn't +* a transparent hugepage. +* +* TODO: support other type hugepages, e.g. HugeTLB. +*/ +if (size ==I915_GTT_PAGE_SIZE_2M && + !PageTransHuge (cur_page)) + ret = -EIO ; +else + base_page = cur_page; + }else if (base_page + npage != cur_page) {gvt_vgpu_err ("The pages are not continuous\n" ); ret = -EINVAL ; + } +if (ret <0 ) { npage++; goto err; }
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 05/27] drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
Quoted 32 lines · Sean Christopherson
When shadowing a GTT entry with a 2M page, explicitly verify that the first page pinned by VFIO is a transparent hugepage instead of assuming that page observed by
is_2MB_gtt_possible()is the same page pinned byvfio_pin_pages(). E.g. if userspace is doing something funky with the guest's memslots, or if the page is demoted betweenis_2MB_gtt_possible()andvfio_pin_pages().This is more of a performance optimization than a bug fix as the check for contiguous struct pages should guard against incorrect mapping (even though assuming struct pages are virtually contiguous is wrong).
The real motivation for explicitly checking for a transparent hugepage after pinning is that it will reduce the risk of introducing a bug in a future fix for a page refcount leak (KVMGT doesn't put the reference acquired by
gfn_to_pfn()), and eventually will allow KVMGT to stop using KVM'sgfn_to_pfn()altogether.Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gvt/kvmgt.c +0
-2@@ -159,11 +159,25 @@ static int gvt_pin_guest_page(struct intel_vgpu *vgpu, unsigned long gfn, goto err; } -if (npage ==0 ) - base_page = cur_page;
drivers/gpu/drm/i915/gvt/kvmgt.c static int gvt_pin_guest_page(struct intel_vgpu *vgpu, unsigned long gfn, · line 171
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-0+if (npage ==0 ) { +/* +* Bail immediately to avoid unnecessary pinning when +* trying to shadow a 2M page and the host page isn't +* a transparent hugepage. +* +* TODO: support other type hugepages, e.g. HugeTLB. +*/ +if (size ==I915_GTT_PAGE_SIZE_2M && + !PageTransHuge (cur_page))
Maybe the checking of PageTransHuge(cur_page) and bailing out is not necessary. If a page is not transparent huge, but there are 512 contigous 4K pages, I think it's still good to map them in IOMMU in 2M.
See vfio_pin_map_dma() who does similar things.
Quoted 15 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ ret = -EIO ; + else + base_page = cur_page; + }else if (base_page + npage != cur_page) {gvt_vgpu_err ("The pages are not continuous\n" ); ret = -EINVAL ; + } +if (ret <0 ) { npage++; goto err; }Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerRe: [PATCH v2 05/27] drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
Quoted 31 lines · Yan Zhao
Quoted 30 lines · Sean Christopherson
When shadowing a GTT entry with a 2M page, explicitly verify that the first page pinned by VFIO is a transparent hugepage instead of assuming that page observed by
is_2MB_gtt_possible()is the same page pinned byvfio_pin_pages(). E.g. if userspace is doing something funky with the guest's memslots, or if the page is demoted betweenis_2MB_gtt_possible()andvfio_pin_pages().This is more of a performance optimization than a bug fix as the check for contiguous struct pages should guard against incorrect mapping (even though assuming struct pages are virtually contiguous is wrong).
The real motivation for explicitly checking for a transparent hugepage after pinning is that it will reduce the risk of introducing a bug in a future fix for a page refcount leak (KVMGT doesn't put the reference acquired by
gfn_to_pfn()), and eventually will allow KVMGT to stop using KVM'sgfn_to_pfn()altogether.Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gvt/kvmgt.c +0
-0@@ -159,11 +159,25 @@ static int gvt_pin_guest_page(struct intel_vgpu *vgpu, unsigned long gfn, goto err; }
Quoted 16 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int gvt_pin_guest_page(struct intel_vgpu *vgpu, unsigned long gfn, · line 171
Quoted 12 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-2-if (npage ==0 ) - base_page = cur_page; +if (npage ==0 ) { +/* +* Bail immediately to avoid unnecessary pinning when +* trying to shadow a 2M page and the host page isn't +* a transparent hugepage. +* +* TODO: support other type hugepages, e.g. HugeTLB. +*/ +if (size ==I915_GTT_PAGE_SIZE_2M && + !PageTransHuge (cur_page))Maybe the checking of
PageTransHuge(cur_page)and bailing out is not necessary. If a page is not transparent huge, but there are 512 contigous 4K pages, I think it's still good to map them in IOMMU in 2M.
Seevfio_pin_map_dma()who does similar things.
I agree that bailing isn't strictly necessary, and processing "blindly" should Just Work for HugeTLB and other hugepage types. I was going to argue that it would be safer to add this and then drop it at the end, but I think that's a specious argument. If not checking the page type is unsafe, then the existing code is buggy, and this changelog literally states that the check for contiguous pages guards against any such problems.
I do think there's a (very, very theoretical) issue though. For "CONFIG_SPARSEMEM=y && CONFIG_SPARSEMEM_VMEMMAP=n", struct pages aren't virtually contiguous with respect to their pfns, i.e. it's possible (again, very theoretically) that two struct pages could be virtually contiguous but physically discontiguous. I suspect I'm being ridiculously paranoid, but for the efficient cases where pages are guaranteed to be contiguous, the extra page_to_pfn() checks should be optimized away by the compiler, i.e. there's no meaningful downside to the paranoia.
TL;DR: My plan is to drop this patch and instead harden the continuity check.
Re: [PATCH v2 05/27] drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
Quoted 12 lines
Quoted 4 lines
Maybe the checking of
PageTransHuge(cur_page)and bailing out is not necessary. If a page is not transparent huge, but there are 512 contigous 4K pages, I think it's still good to map them in IOMMU in 2M.
Seevfio_pin_map_dma()who does similar things.I agree that bailing isn't strictly necessary, and processing "blindly" should Just Work for HugeTLB and other hugepage types. I was going to argue that it would be safer to add this and then drop it at the end, but I think that's a specious argument. If not checking the page type is unsafe, then the existing code is buggy, and this changelog literally states that the check for contiguous pages guards against any such problems.
Quoted 7 lines
I do think there's a (very, very theoretical) issue though. For "
CONFIG_SPARSEMEM=y&&CONFIG_SPARSEMEM_VMEMMAP=n", struct pages aren't virtually contiguous with respect to their pfns, i.e. it's possible (again, very theoretically) that two struct pages could be virtually contiguous but physically discontiguous. I suspect I'm being ridiculously paranoid, but for the efficient cases where pages are guaranteed to be contiguous, the extrapage_to_pfn()checks should be optimized away by the compiler, i.e. there's no meaningful downside to the paranoia.
To make sure I understand it correctly:
There are 3 conditions:
(1) Two struct pages aren't virtually contiguous, but there PFNs are contiguous.
(2) Two struct pages are virtually contiguous but their PFNs aren't contiguous. (Looks this will not happen?)
(3) Two struct pages are virtually contiguous, and their PFNs are contiguous, too. But they have different backends, e.g.
PFN 1 and PFN 2 are contiguous, while PFN 1 belongs to RAM, and PFN 2 belongs to DEVMEM.
I think you mean condition (3) is problematic, am I right?
Quoted 2 lines
TL;DR: My plan is to drop this patch and instead harden the continuity check.
So you want to check page zone?
Re: [PATCH v2 05/27] drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
Quoted 29 lines · Yan Zhao
Quoted 12 lines
Quoted 4 lines
Maybe the checking of
PageTransHuge(cur_page)and bailing out is not necessary. If a page is not transparent huge, but there are 512 contigous 4K pages, I think it's still good to map them in IOMMU in 2M.
Seevfio_pin_map_dma()who does similar things.I agree that bailing isn't strictly necessary, and processing "blindly" should Just Work for HugeTLB and other hugepage types. I was going to argue that it would be safer to add this and then drop it at the end, but I think that's a specious argument. If not checking the page type is unsafe, then the existing code is buggy, and this changelog literally states that the check for contiguous pages guards against any such problems.
Quoted 7 lines
I do think there's a (very, very theoretical) issue though. For "
CONFIG_SPARSEMEM=y&&CONFIG_SPARSEMEM_VMEMMAP=n", struct pages aren't virtually contiguous with respect to their pfns, i.e. it's possible (again, very theoretically) that two struct pages could be virtually contiguous but physically discontiguous. I suspect I'm being ridiculously paranoid, but for the efficient cases where pages are guaranteed to be contiguous, the extrapage_to_pfn()checks should be optimized away by the compiler, i.e. there's no meaningful downside to the paranoia.To make sure I understand it correctly:
There are 3 conditions:
(1) Two struct pages aren't virtually contiguous, but there PFNs are contiguous.
(2) Two struct pages are virtually contiguous but their PFNs aren't contiguous. (Looks this will not happen?)
(3) Two struct pages are virtually contiguous, and their PFNs are contiguous, too. But they have different backends, e.g.
PFN 1 and PFN 2 are contiguous, while PFN 1 belongs to RAM, and PFN 2 belongs to DEVMEM.
Quoted 1 line
I think you mean condition (3) is problematic, am I right?
Oh, I got it now.
You are saying about condition (2), with "CONFIG_SPARSEMEM=y && CONFIG_SPARSEMEM_VMEMMAP=n".
Two struct pages are contiguous if one is at one section's tail and another at another section's head, but the two sections aren't for contiguous PFNs.
Quoted 4 lines
Quoted 2 lines
TL;DR: My plan is to drop this patch and instead harden the continuity check.
So you want to check page zone?
Sean Christopherson
maintainerRe: [PATCH v2 05/27] drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
Quoted 30 lines · Yan Zhao
Quoted 29 lines · Yan Zhao
Quoted 12 lines
Quoted 4 lines
Maybe the checking of
PageTransHuge(cur_page)and bailing out is not necessary. If a page is not transparent huge, but there are 512 contigous 4K pages, I think it's still good to map them in IOMMU in 2M.
Seevfio_pin_map_dma()who does similar things.I agree that bailing isn't strictly necessary, and processing "blindly" should Just Work for HugeTLB and other hugepage types. I was going to argue that it would be safer to add this and then drop it at the end, but I think that's a specious argument. If not checking the page type is unsafe, then the existing code is buggy, and this changelog literally states that the check for contiguous pages guards against any such problems.
Quoted 7 lines
I do think there's a (very, very theoretical) issue though. For "
CONFIG_SPARSEMEM=y&&CONFIG_SPARSEMEM_VMEMMAP=n", struct pages aren't virtually contiguous with respect to their pfns, i.e. it's possible (again, very theoretically) that two struct pages could be virtually contiguous but physically discontiguous. I suspect I'm being ridiculously paranoid, but for the efficient cases where pages are guaranteed to be contiguous, the extrapage_to_pfn()checks should be optimized away by the compiler, i.e. there's no meaningful downside to the paranoia.To make sure I understand it correctly:
There are 3 conditions:
(1) Two struct pages aren't virtually contiguous, but there PFNs are contiguous.
(2) Two struct pages are virtually contiguous but their PFNs aren't contiguous. (Looks this will not happen?)
(3) Two struct pages are virtually contiguous, and their PFNs are contiguous, too. But they have different backends, e.g.
PFN 1 and PFN 2 are contiguous, while PFN 1 belongs to RAM, and PFN 2 belongs to DEVMEM.
Quoted 6 lines
Quoted 1 line
I think you mean condition (3) is problematic, am I right?
Oh, I got it now.
You are saying about condition (2), with "CONFIG_SPARSEMEM=y&&CONFIG_SPARSEMEM_VMEMMAP=n".
Two struct pages are contiguous if one is at one section's tail and another at another section's head, but the two sections aren't for contiguous PFNs.
Yep, exactly.
Sean Christopherson
maintainerPATCH v2 6/27 drm/i915/gvt: Put the page reference obtained by KVM's gfn_to_pfn()
In reply to Sean ChristophersonPut the struct page reference acquired by gfn_to_pfn(), KVM's API is that the caller is ultimately responsible for dropping any reference.
Note, kvm_release_pfn_clean() ensures the pfn is actually a refcounted struct page before trying to put any references.
--- drivers/gpu/drm/i915/gvt/gtt.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gvt/gtt.c +4 -1
@@ -1160,6 +1160,7 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu,unsigned long gfn = ops->get_pfn (entry);kvm_pfn_t pfn;int max_level; +int ret;if (!HAS_PAGE_SIZES (vgpu->gvt->gt->i915,I915_GTT_PAGE_SIZE_2M ))return 0 ;
@@ -1179,7 +1180,9 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu,if (!pfn_valid (pfn))return -EINVAL ; -return PageTransHuge (pfn_to_page (pfn)); + ret =PageTransHuge (pfn_to_page (pfn)); +kvm_release_pfn_clean (pfn); +return ret; } static int split_2MB_gtt_entry(struct intel_vgpu *vgpu,
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 06/27] drm/i915/gvt: Put the page reference obtained by KVM's gfn_to_pfn()
Quoted 38 lines · Sean Christopherson
Put the struct page reference acquired by
gfn_to_pfn(), KVM's API is that the caller is ultimately responsible for dropping any reference.Note,
kvm_release_pfn_clean()ensures the pfn is actually a refcounted struct page before trying to put any references.Fixes b901b252b6cf ("drm/i915/gvt: Add 2M huge gtt support")Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/gtt.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/gvt/gtt.c +4
-1@@ -1160,6 +1160,7 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu,unsigned long gfn = ops->get_pfn (entry);kvm_pfn_t pfn;int max_level; +int ret;if (!HAS_PAGE_SIZES (vgpu->gvt->gt->i915,I915_GTT_PAGE_SIZE_2M ))return 0 ;@@ -1179,7 +1180,9 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu,if (!pfn_valid (pfn))return -EINVAL ; -return PageTransHuge (pfn_to_page (pfn)); + ret =PageTransHuge (pfn_to_page (pfn)); +kvm_release_pfn_clean (pfn); +return ret; } static int split_2MB_gtt_entry(struct intel_vgpu *vgpu,Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 7/27 drm/i915/gvt: Don't rely on KVM's gfn_to_pfn() to query possible 2M GTT
In reply to Sean ChristophersonNow that gvt_pin_guest_page() explicitly verifies the pinned PFN is a transparent hugepage page, don't use KVM's gfn_to_pfn() to pre-check if a 2M GTT entry is possible and instead just try to map the GFN with a 2MB entry. Using KVM to query pfn that is ultimately managed through VFIO is odd, and KVM's gfn_to_pfn() is not intended for non-KVM consumption; it's exported only because of KVM vendor modules (x86 and PPC).
--- drivers/gpu/drm/i915/gvt/gtt.c | 33 +++++++++++---------------------- 1 file changed, 11 insertions(+), 22 deletions(-)
drivers/gpu/drm/i915/gvt/gtt.c +11 -22
@@ -1146,21 +1146,19 @@ static inline void ppgtt_generate_shadow_entry(struct intel_gvt_gtt_entry *se, }/* -* Check if can do 2M page +* Try to map a 2M gtt entry. * @vgpu: target vgpu * @entry: target pfn's gtt entry * -* Return 1 if 2MB huge gtt shadowing is possible, 0 if miscondition, -* negative if found err. +* Return 1 if 2MB huge gtt shadow was creation, 0 if the entry needs to be +* split, negative if found err. */ -static int is_2MB_gtt_possible (struct intel_vgpu *vgpu, -struct intel_gvt_gtt_entry *entry) +static int try_map_2MB_gtt_entry (struct intel_vgpu *vgpu, +struct intel_gvt_gtt_entry *entry,dma_addr_t *dma_addr) {const struct intel_gvt_gtt_pte_ops *ops = vgpu->gvt->gtt.pte_ops;unsigned long gfn = ops->get_pfn (entry); -kvm_pfn_t pfn;int max_level; -int ret;if (!HAS_PAGE_SIZES (vgpu->gvt->gt->i915,I915_GTT_PAGE_SIZE_2M ))return 0 ;
@@ -1173,16 +1171,7 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu,if (max_level <PG_LEVEL_2M )return 0 ; - pfn =gfn_to_pfn (vgpu->vfio_device.kvm, gfn); -if (is_error_noslot_pfn (pfn)) -return -EINVAL ; - -if (!pfn_valid (pfn)) -return -EINVAL ; - - ret =PageTransHuge (pfn_to_page (pfn)); -kvm_release_pfn_clean (pfn); -return ret; +return intel_gvt_dma_map_guest_page (vgpu, gfn,I915_GTT_PAGE_SIZE_2M , dma_addr); } static int split_2MB_gtt_entry(struct intel_vgpu *vgpu,
@@ -1278,7 +1267,7 @@ static int ppgtt_populate_shadow_entry(struct intel_vgpu *vgpu, {const struct intel_gvt_gtt_pte_ops *pte_ops = vgpu->gvt->gtt.pte_ops;struct intel_gvt_gtt_entry se = *ge; -unsigned long gfn, page_size =PAGE_SIZE ; +unsigned long gfn;dma_addr_t dma_addr;int ret;
@@ -1301,13 +1290,12 @@ static int ppgtt_populate_shadow_entry(struct intel_vgpu *vgpu,return split_64KB_gtt_entry (vgpu, spt, index, &se);case GTT_TYPE_PPGTT_PTE_2M_ENTRY :gvt_vdbg_mm ("shadow 2M gtt entry\n" ); - ret =is_2MB_gtt_possible (vgpu, ge); + ret =try_map_2MB_gtt_entry (vgpu, ge, &dma_addr);if (ret ==0 )return split_2MB_gtt_entry (vgpu, spt, index, &se);else if (ret <0 )return ret; - page_size =I915_GTT_PAGE_SIZE_2M ; -break ; + goto set_shadow_entry;case GTT_TYPE_PPGTT_PTE_1G_ENTRY :gvt_vgpu_err ("GVT doesn't support 1GB entry\n" );return -EINVAL ;
@@ -1316,10 +1304,11 @@ static int ppgtt_populate_shadow_entry(struct intel_vgpu *vgpu, }/* direct shadow */ - ret =intel_gvt_dma_map_guest_page (vgpu, gfn, page_size, &dma_addr); + ret =intel_gvt_dma_map_guest_page (vgpu, gfn,PAGE_SIZE , &dma_addr);if (ret)return -ENXIO ; +set_shadow_entry: pte_ops->set_pfn (&se, dma_addr >>PAGE_SHIFT );ppgtt_set_shadow_entry (spt, &se, index);return 0 ;
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 07/27] drm/i915/gvt: Don't rely on KVM's gfn_to_pfn() to query possible 2M GTT
Quoted 29 lines · Sean Christopherson
/*
- * Check if can do 2M page
+ * Try to map a 2M gtt entry.
* @vgpu: target vgpu
* @entry: target pfn's gtt entry
*
- * Return 1 if 2MB huge gtt shadowing is possible, 0 if miscondition,
- * negative if found err.
+ * Return 1 if 2MB huge gtt shadow was creation, 0 if the entry needs to be
+ * split, negative if found err.
*/drivers/gpu/drm/i915/gvt/gtt.c +2
-5-static int is_2MB_gtt_possible (struct intel_vgpu *vgpu, -struct intel_gvt_gtt_entry *entry) +static int try_map_2MB_gtt_entry (struct intel_vgpu *vgpu, +struct intel_gvt_gtt_entry *entry,dma_addr_t *dma_addr) {const struct intel_gvt_gtt_pte_ops *ops = vgpu->gvt->gtt.pte_ops;unsigned long gfn = ops->get_pfn (entry); -kvm_pfn_t pfn;int max_level; -int ret;if (!HAS_PAGE_SIZES (vgpu->gvt->gt->i915,I915_GTT_PAGE_SIZE_2M ))return 0 ;@@ -1173,16 +1171,7 @@ static int is_2MB_gtt_possible(struct intel_vgpu *vgpu,if (max_level <PG_LEVEL_2M )return 0 ; - pfn =gfn_to_pfn (vgpu->vfio_device.kvm, gfn);
drivers/gpu/drm/i915/gvt/gtt.c static int is_2MB_gtt_possible(struct intel_vgpu *vgpu, · line 1174
Quoted 10 lines
drivers/gpu/drm/i915/gvt/gtt.c +1
-9-if (is_error_noslot_pfn (pfn)) -return -EINVAL ; - -if (!pfn_valid (pfn)) -return -EINVAL ; - - ret =PageTransHuge (pfn_to_page (pfn)); -kvm_release_pfn_clean (pfn); -return ret; +return intel_gvt_dma_map_guest_page (vgpu, gfn,I915_GTT_PAGE_SIZE_2M , dma_addr);
intel_gvt_dma_map_guest_page() returns 0 on success, which is not in consistent with the expected return value of this function, i.e. "
Return 1 if 2MB huge gtt shadow was creation, 0 if the entry needs to be split, negative if found err.
"
Sean Christopherson
maintainerPATCH v2 8/27 drm/i915/gvt: Use an "unsigned long" to iterate over memslot gfns
In reply to Sean ChristophersonUse an "unsigned long" instead of an "int" when iterating over the gfns in a memslot. The number of pages in the memslot is tracked as an "unsigned long", e.g. KVMGT could theoretically break if a KVM memslot larger than 16TiB were deleted (2^32 * 4KiB).
--- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/gvt/kvmgt.c +1 -1
@@ -1634,7 +1634,7 @@ static void kvmgt_page_track_flush_slot(struct kvm *kvm,struct kvm_memory_slot *slot, struct kvm_page_track_notifier_node *node) { - int i; + unsigned long i;gfn_t gfn;struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 08/27] drm/i915/gvt: Use an "unsigned long" to iterate over memslot gfns
Quoted 26 lines · Sean Christopherson
Use an "unsigned long" instead of an "int" when iterating over the gfns in a memslot. The number of pages in the memslot is tracked as an "unsigned long", e.g. KVMGT could theoretically break if a KVM memslot larger than 16TiB were deleted (2^32 * 4KiB).
Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/gpu/drm/i915/gvt/kvmgt.c +1
-1@@ -1634,7 +1634,7 @@ static void kvmgt_page_track_flush_slot(struct kvm *kvm,struct kvm_memory_slot *slot, struct kvm_page_track_notifier_node *node) { - int i; + unsigned long i;gfn_t gfn;struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node);Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 9/27 drm/i915/gvt: Drop unused helper intel_vgpu_reset_gtt()
In reply to Sean ChristophersonDrop intel_vgpu_reset_gtt() as it no longer has any callers. In addition to eliminating dead code, this eliminates the last possible scenario where __kvmgt_protect_table_find() can be reached without holding vgpu_lock. Requiring vgpu_lock to be held when calling __kvmgt_protect_table_find() will allow a protecting the gfn hash with vgpu_lock without too much fuss.
No functional change intended.
--- drivers/gpu/drm/i915/gvt/gtt.c | 18 ------------------ drivers/gpu/drm/i915/gvt/gtt.h | 1 - 2 files changed, 19 deletions(-)
drivers/gpu/drm/i915/gvt/gtt.c +0 -18
@@ -2845,24 +2845,6 @@ void intel_vgpu_reset_ggtt(struct intel_vgpu *vgpu, bool invalidate_old)ggtt_invalidate (gvt->gt); } -/** -* intel_vgpu_reset_gtt - reset the all GTT related status -* @vgpu: a vGPU -* -* This function is called from vfio core to reset reset all -* GTT related status, including GGTT, PPGTT, scratch page. -* -*/ -void intel_vgpu_reset_gtt (struct intel_vgpu *vgpu) -{ -/* Shadow pages are only created when there is no page -* table tracking data, so remove page tracking data after -* removing the shadow pages. -*/ -intel_vgpu_destroy_all_ppgtt_mm (vgpu); -intel_vgpu_reset_ggtt (vgpu, true); -} -/** * intel_gvt_restore_ggtt - restore all vGPU's ggtt entries * @gvt: intel gvt device
drivers/gpu/drm/i915/gvt/gtt.h +0 -1
@@ -224,7 +224,6 @@ void intel_vgpu_reset_ggtt(struct intel_vgpu *vgpu, bool invalidate_old);void intel_vgpu_invalidate_ppgtt (struct intel_vgpu *vgpu);int intel_gvt_init_gtt (struct intel_gvt *gvt); -void intel_vgpu_reset_gtt (struct intel_vgpu *vgpu);void intel_gvt_clean_gtt (struct intel_gvt *gvt); struct intel_vgpu_mm *intel_gvt_find_ppgtt_mm(struct intel_vgpu *vgpu,
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 09/27] drm/i915/gvt: Drop unused helper intel_vgpu_reset_gtt()
Quoted 59 lines · Sean Christopherson
Drop
intel_vgpu_reset_gtt()as it no longer has any callers. In addition to eliminating dead code, this eliminates the last possible scenario where__kvmgt_protect_table_find()can be reached without holdingvgpu_lock. Requiringvgpu_lockto be held when calling__kvmgt_protect_table_find()will allow a protecting the gfn hash withvgpu_lockwithout too much fuss.No functional change intended.
Fixes ba25d977571e ("drm/i915/gvt: Do not destroy ppgtt_mm during vGPU D3->D0.")Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/gtt.c | 18 ------------------ drivers/gpu/drm/i915/gvt/gtt.h | 1 - 2 files changed, 19 deletions(-)drivers/gpu/drm/i915/gvt/gtt.c +0
-18@@ -2845,24 +2845,6 @@ void intel_vgpu_reset_ggtt(struct intel_vgpu *vgpu, bool invalidate_old)ggtt_invalidate (gvt->gt); } -/** -* intel_vgpu_reset_gtt - reset the all GTT related status -* @vgpu: a vGPU -* -* This function is called from vfio core to reset reset all -* GTT related status, including GGTT, PPGTT, scratch page. -* -*/ -void intel_vgpu_reset_gtt (struct intel_vgpu *vgpu) -{ -/* Shadow pages are only created when there is no page -* table tracking data, so remove page tracking data after -* removing the shadow pages. -*/ -intel_vgpu_destroy_all_ppgtt_mm (vgpu); -intel_vgpu_reset_ggtt (vgpu, true); -} -/** * intel_gvt_restore_ggtt - restore all vGPU's ggtt entries * @gvt: intel gvt device drivers/gpu/drm/i915/gvt/gtt.h +0
-1@@ -224,7 +224,6 @@ void intel_vgpu_reset_ggtt(struct intel_vgpu *vgpu, bool invalidate_old);void intel_vgpu_invalidate_ppgtt (struct intel_vgpu *vgpu);int intel_gvt_init_gtt (struct intel_gvt *gvt); -void intel_vgpu_reset_gtt (struct intel_vgpu *vgpu);void intel_gvt_clean_gtt (struct intel_gvt *gvt); struct intel_vgpu_mm *intel_gvt_find_ppgtt_mm(struct intel_vgpu *vgpu,Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 10/27 drm/i915/gvt: Protect gfn hash table with vgpu_lock
In reply to Sean ChristophersonUse vgpu_lock instead of KVM's mmu_lock to protect accesses to the hash table used to track which gfns are write-protected when shadowing the guest's GTT, and hoist the acquisition of vgpu_lock from intel_vgpu_page_track_handler() out to its sole caller, kvmgt_page_track_write().
This fixes a bug where kvmgt_page_track_write(), which doesn't hold kvm->mmu_lock, could race with intel_gvt_page_track_remove() and trigger a use-after-free.
Fixing kvmgt_page_track_write() by taking kvm->mmu_lock is not an option as mmu_lock is a r/w spinlock, and intel_vgpu_page_track_handler() might sleep when acquiring vgpu->cache_lock deep down the callstack:
intel_vgpu_page_track_handler()
|
|-> page_track->handler / ppgtt_write_protection_handler()
|
|-> ppgtt_handle_guest_write_page_table_bytes()
|
|-> ppgtt_handle_guest_write_page_table()
|
|-> ppgtt_handle_guest_entry_removal()
|
|-> ppgtt_invalidate_pte()
|
|-> intel_gvt_dma_unmap_guest_page()
|
|-> mutex_lock(&vgpu->cache_lock);--- drivers/gpu/drm/i915/gvt/kvmgt.c | 55 +++++++++++++++------------ drivers/gpu/drm/i915/gvt/page_track.c | 10 +---- 2 files changed, 33 insertions(+), 32 deletions(-)
drivers/gpu/drm/i915/gvt/kvmgt.c +31 -24
@@ -366,6 +366,8 @@ __kvmgt_protect_table_find(struct intel_vgpu *info, gfn_t gfn) {struct kvmgt_pgfn *p, *res =NULL ; +lockdep_assert_held (&info->vgpu_lock); +hash_for_each_possible (info->ptable, p, hnode, gfn) {if (gfn == p->gfn) { res = p;
@@ -1567,6 +1569,9 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn)if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , info->status))return -ESRCH ; +if (kvmgt_gfn_is_write_protected (info, gfn)) +return 0 ; + idx =srcu_read_lock (&kvm->srcu); slot =gfn_to_memslot (kvm, gfn);if (!slot) {
@@ -1575,16 +1580,12 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn) }write_lock (&kvm->mmu_lock); - -if (kvmgt_gfn_is_write_protected (info, gfn)) - goto out; -kvm_slot_page_track_add_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +write_unlock (&kvm->mmu_lock); + +srcu_read_unlock (&kvm->srcu, idx); +kvmgt_protect_table_add (info, gfn); - -out: -write_unlock (&kvm->mmu_lock); -srcu_read_unlock (&kvm->srcu, idx);return 0 ; }
@@ -1597,24 +1598,22 @@ int intel_gvt_page_track_remove(struct intel_vgpu *info, u64 gfn)if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , info->status))return -ESRCH ; - idx =srcu_read_lock (&kvm->srcu); - slot =gfn_to_memslot (kvm, gfn); -if (!slot) { -srcu_read_unlock (&kvm->srcu, idx); -return -EINVAL ; - } - -write_lock (&kvm->mmu_lock); -if (!kvmgt_gfn_is_write_protected (info, gfn)) - goto out; +return 0 ; + idx =srcu_read_lock (&kvm->srcu); + slot =gfn_to_memslot (kvm, gfn); +if (!slot) { +srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } + +write_lock (&kvm->mmu_lock);kvm_slot_page_track_remove_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +write_unlock (&kvm->mmu_lock); +srcu_read_unlock (&kvm->srcu, idx); +kvmgt_protect_table_del (info, gfn); - -out: -write_unlock (&kvm->mmu_lock); -srcu_read_unlock (&kvm->srcu, idx);return 0 ; }
@@ -1625,9 +1624,13 @@ static void kvmgt_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa,struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node); +mutex_lock (&info->vgpu_lock); +if (kvmgt_gfn_is_write_protected (info,gpa_to_gfn (gpa)))intel_vgpu_page_track_handler (info, gpa, (void *)val, len); + +mutex_unlock (&info->vgpu_lock); } static void kvmgt_page_track_flush_slot(struct kvm *kvm,
@@ -1639,16 +1642,20 @@ static void kvmgt_page_track_flush_slot(struct kvm *kvm,struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node); -write_lock (&kvm->mmu_lock); +mutex_lock (&info->vgpu_lock); +for (i =0 ; i < slot->npages; i++) { gfn = slot->base_gfn + i;if (kvmgt_gfn_is_write_protected (info, gfn)) { +write_lock (&kvm->mmu_lock);kvm_slot_page_track_remove_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +write_unlock (&kvm->mmu_lock); +kvmgt_protect_table_del (info, gfn); } } -write_unlock (&kvm->mmu_lock); +mutex_unlock (&info->vgpu_lock); }void intel_vgpu_detach_regions (struct intel_vgpu *vgpu)
drivers/gpu/drm/i915/gvt/page_track.c +2 -8
@@ -162,13 +162,9 @@ int intel_vgpu_page_track_handler(struct intel_vgpu *vgpu, u64 gpa,struct intel_vgpu_page_track *page_track;int ret =0 ; -mutex_lock (&vgpu->vgpu_lock); - page_track =intel_vgpu_find_page_track (vgpu, gpa >>PAGE_SHIFT ); -if (!page_track) { - ret = -ENXIO ; - goto out; - } +if (!page_track) +return -ENXIO ;if (unlikely (vgpu->failsafe)) {/* Remove write protection to prevent furture traps. */
@@ -179,7 +175,5 @@ int intel_vgpu_page_track_handler(struct intel_vgpu *vgpu, u64 gpa,gvt_err ("guest page write error, gpa %llx\n" , gpa); } -out: -mutex_unlock (&vgpu->vgpu_lock);return ret; }
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 10/27] drm/i915/gvt: Protect gfn hash table with vgpu_lock
Quoted 185 lines · Sean Christopherson
Use
vgpu_lockinstead of KVM'smmu_lockto protect accesses to the hash table used to track which gfns are write-protected when shadowing the guest's GTT, and hoist the acquisition ofvgpu_lockfromintel_vgpu_page_track_handler()out to its sole caller,kvmgt_page_track_write().This fixes a bug where
kvmgt_page_track_write(), which doesn't holdkvm->mmu_lock, could race withintel_gvt_page_track_remove()and trigger a use-after-free.Fixing
kvmgt_page_track_write()by takingkvm->mmu_lockis not an option asmmu_lockis a r/w spinlock, andintel_vgpu_page_track_handler()might sleep when acquiringvgpu->cache_lockdeep down the callstack:intel_vgpu_page_track_handler() | |-> page_track->handler / ppgtt_write_protection_handler() | |-> ppgtt_handle_guest_write_page_table_bytes() | |-> ppgtt_handle_guest_write_page_table() | |-> ppgtt_handle_guest_entry_removal() | |-> ppgtt_invalidate_pte() | |-> intel_gvt_dma_unmap_guest_page() | |-> mutex_lock(&vgpu->cache_lock);Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 55 +++++++++++++++------------ drivers/gpu/drm/i915/gvt/page_track.c | 10 +---- 2 files changed, 33 insertions(+), 32 deletions(-)drivers/gpu/drm/i915/gvt/kvmgt.c +31
-24@@ -366,6 +366,8 @@ __kvmgt_protect_table_find(struct intel_vgpu *info, gfn_t gfn) {struct kvmgt_pgfn *p, *res =NULL ; +lockdep_assert_held (&info->vgpu_lock); +hash_for_each_possible (info->ptable, p, hnode, gfn) {if (gfn == p->gfn) { res = p;@@ -1567,6 +1569,9 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn)if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , info->status))return -ESRCH ; +if (kvmgt_gfn_is_write_protected (info, gfn)) +return 0 ; + idx =srcu_read_lock (&kvm->srcu); slot =gfn_to_memslot (kvm, gfn);if (!slot) {@@ -1575,16 +1580,12 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn) }write_lock (&kvm->mmu_lock); - -if (kvmgt_gfn_is_write_protected (info, gfn)) - goto out; -kvm_slot_page_track_add_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +write_unlock (&kvm->mmu_lock); + +srcu_read_unlock (&kvm->srcu, idx); +kvmgt_protect_table_add (info, gfn); - -out: -write_unlock (&kvm->mmu_lock); -srcu_read_unlock (&kvm->srcu, idx);return 0 ; }@@ -1597,24 +1598,22 @@ int intel_gvt_page_track_remove(struct intel_vgpu *info, u64 gfn)if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , info->status))return -ESRCH ; - idx =srcu_read_lock (&kvm->srcu); - slot =gfn_to_memslot (kvm, gfn); -if (!slot) { -srcu_read_unlock (&kvm->srcu, idx); -return -EINVAL ; - } - -write_lock (&kvm->mmu_lock); -if (!kvmgt_gfn_is_write_protected (info, gfn)) - goto out; +return 0 ; + idx =srcu_read_lock (&kvm->srcu); + slot =gfn_to_memslot (kvm, gfn); +if (!slot) { +srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } + +write_lock (&kvm->mmu_lock);kvm_slot_page_track_remove_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +write_unlock (&kvm->mmu_lock); +srcu_read_unlock (&kvm->srcu, idx); +kvmgt_protect_table_del (info, gfn); - -out: -write_unlock (&kvm->mmu_lock); -srcu_read_unlock (&kvm->srcu, idx);return 0 ; }@@ -1625,9 +1624,13 @@ static void kvmgt_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa,struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node); +mutex_lock (&info->vgpu_lock); +if (kvmgt_gfn_is_write_protected (info,gpa_to_gfn (gpa)))intel_vgpu_page_track_handler (info, gpa, (void *)val, len); + +mutex_unlock (&info->vgpu_lock); } static void kvmgt_page_track_flush_slot(struct kvm *kvm,@@ -1639,16 +1642,20 @@ static void kvmgt_page_track_flush_slot(struct kvm *kvm,struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node); -write_lock (&kvm->mmu_lock); +mutex_lock (&info->vgpu_lock); +for (i =0 ; i < slot->npages; i++) { gfn = slot->base_gfn + i;if (kvmgt_gfn_is_write_protected (info, gfn)) { +write_lock (&kvm->mmu_lock);kvm_slot_page_track_remove_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +write_unlock (&kvm->mmu_lock); +kvmgt_protect_table_del (info, gfn); } } -write_unlock (&kvm->mmu_lock); +mutex_unlock (&info->vgpu_lock); }void intel_vgpu_detach_regions (struct intel_vgpu *vgpu)drivers/gpu/drm/i915/gvt/page_track.c +2
-8@@ -162,13 +162,9 @@ int intel_vgpu_page_track_handler(struct intel_vgpu *vgpu, u64 gpa,struct intel_vgpu_page_track *page_track;int ret =0 ; -mutex_lock (&vgpu->vgpu_lock); - page_track =intel_vgpu_find_page_track (vgpu, gpa >>PAGE_SHIFT ); -if (!page_track) { - ret = -ENXIO ; - goto out; - } +if (!page_track) +return -ENXIO ;if (unlikely (vgpu->failsafe)) {/* Remove write protection to prevent furture traps. */ @@ -179,7 +175,5 @@ int intel_vgpu_page_track_handler(struct intel_vgpu *vgpu, u64 gpa,gvt_err ("guest page write error, gpa %llx\n" , gpa); } -out: -mutex_unlock (&vgpu->vgpu_lock);return ret; }Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 11/27 KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change
In reply to Sean ChristophersonCall kvm_mmu_zap_all_fast() directly when flushing a memslot instead of bouncing through the page-track mechanism. KVM (unfortunately) needs to zap and flush all page tables on memslot DELETE/MOVE irrespective of whether KVM is shadowing guest page tables.
This will allow changing KVM to register a page-track notifier on the first shadow root allocation, and will also allow deleting the misguided kvm_page_track_flush_slot() hook itself once KVM-GT also moves to a different method for reacting to memslot changes.
No functional change intended.
--- arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kvm/mmu/mmu.c | 10 +--------- arch/x86/kvm/x86.c | 2 ++ 3 files changed, 4 insertions(+), 9 deletions(-)
arch/x86/include/asm/kvm_host.h +1 -0
@@ -1844,6 +1844,7 @@ void kvm_mmu_zap_collapsible_sptes(struct kvm *kvm,void kvm_mmu_slot_leaf_clear_dirty (struct kvm *kvm,const struct kvm_memory_slot *memslot);void kvm_mmu_zap_all (struct kvm *kvm); +void kvm_mmu_zap_all_fast (struct kvm *kvm);void kvm_mmu_invalidate_mmio_sptes (struct kvm *kvm,u64 gen);void kvm_mmu_change_mmu_pages (struct kvm *kvm,unsigned long kvm_nr_mmu_pages);
arch/x86/kvm/mmu/mmu.c +1 -9
@@ -6030,7 +6030,7 @@ static void kvm_zap_obsolete_pages(struct kvm *kvm)* not use any resource of the being-deleted slot or all slots * after calling the function. */ -static void kvm_mmu_zap_all_fast (struct kvm *kvm) +void kvm_mmu_zap_all_fast (struct kvm *kvm) {lockdep_assert_held (&kvm->slots_lock);
@@ -6086,13 +6086,6 @@ static bool kvm_has_zapped_obsolete_pages(struct kvm *kvm)return unlikely (!list_empty_careful (&kvm->arch.zapped_obsolete_pages)); } -static void kvm_mmu_invalidate_zap_pages_in_memslot (struct kvm *kvm, -struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node) -{ -kvm_mmu_zap_all_fast (kvm); -} -int kvm_mmu_init_vm (struct kvm *kvm) {struct kvm_page_track_notifier_node *node = &kvm->arch.mmu_sp_tracker;
@@ -6110,7 +6103,6 @@ int kvm_mmu_init_vm(struct kvm *kvm) } node->track_write = kvm_mmu_pte_write; - node->track_flush_slot = kvm_mmu_invalidate_zap_pages_in_memslot;kvm_page_track_register_notifier (kvm, node); kvm->arch.split_page_header_cache.kmem_cache = mmu_page_header_cache;
arch/x86/kvm/x86.c +2 -0
@@ -12662,6 +12662,8 @@ void kvm_arch_flush_shadow_all(struct kvm *kvm)void kvm_arch_flush_shadow_memslot (struct kvm *kvm,struct kvm_memory_slot *slot) { +kvm_mmu_zap_all_fast (kvm); +kvm_page_track_flush_slot (kvm, slot); }
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 11/27] KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change
On Fri, Mar 10, 2023 at 04:22:42PM -0800, Sean Christopherson wrote:
...
Quoted 23 lines
arch/x86/kvm/mmu/mmu.c +0
-8-static void kvm_mmu_invalidate_zap_pages_in_memslot (struct kvm *kvm, -struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node) -{ -kvm_mmu_zap_all_fast (kvm); -} -int kvm_mmu_init_vm (struct kvm *kvm) {struct kvm_page_track_notifier_node *node = &kvm->arch.mmu_sp_tracker;@@ -6110,7 +6103,6 @@ int kvm_mmu_init_vm(struct kvm *kvm) } node->track_write = kvm_mmu_pte_write; - node->track_flush_slot = kvm_mmu_invalidate_zap_pages_in_memslot;kvm_page_track_register_notifier (kvm, node); kvm->arch.split_page_header_cache.kmem_cache = mmu_page_header_cache;arch/x86/kvm/x86.c +0
-0
arch/x86/kvm/x86.c void kvm_arch_flush_shadow_all(struct kvm *kvm) · line 12665
Quoted 4 lines
arch/x86/kvm/x86.c +1
-0@@ -12662,6 +12662,8 @@ void kvm_arch_flush_shadow_all(struct kvm *kvm)void kvm_arch_flush_shadow_memslot (struct kvm *kvm,struct kvm_memory_slot *slot) { +kvm_mmu_zap_all_fast (kvm);
Could we still call kvm_mmu_invalidate_zap_pages_in_memslot() here? As I know, for TDX, its version of kvm_mmu_invalidate_zap_pages_in_memslot() is like
static void kvm_mmu_invalidate_zap_pages_in_memslot(struct kvm *kvm,
struct kvm_memory_slot *slot, struct kvm_page_track_notifier_node *node)
{
if (kvm_gfn_shared_mask(kvm))
kvm_mmu_zap_memslot(kvm, slot);
else
kvm_mmu_zap_all_fast(kvm);
}Maybe this kind of judegment is better to be confined in mmu.c?
Thanks
Yan
Quoted 4 lines
arch/x86/kvm/x86.c +1
-0+kvm_page_track_flush_slot (kvm, slot); }
Sean Christopherson
maintainerRe: [PATCH v2 11/27] KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change
Quoted 36 lines · Yan Zhao
On Fri, Mar 10, 2023 at 04:22:42PM -0800, Sean Christopherson wrote:
...Quoted 23 lines
arch/x86/kvm/mmu/mmu.c +0
-8-static void kvm_mmu_invalidate_zap_pages_in_memslot (struct kvm *kvm, -struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node) -{ -kvm_mmu_zap_all_fast (kvm); -} -int kvm_mmu_init_vm (struct kvm *kvm) {struct kvm_page_track_notifier_node *node = &kvm->arch.mmu_sp_tracker;@@ -6110,7 +6103,6 @@ int kvm_mmu_init_vm(struct kvm *kvm) } node->track_write = kvm_mmu_pte_write; - node->track_flush_slot = kvm_mmu_invalidate_zap_pages_in_memslot;kvm_page_track_register_notifier (kvm, node); kvm->arch.split_page_header_cache.kmem_cache = mmu_page_header_cache;arch/x86/kvm/x86.c +0
-0arch/x86/kvm/x86.c void kvm_arch_flush_shadow_all(struct kvm *kvm) · line 12665
Quoted 4 lines
arch/x86/kvm/x86.c +1
-0@@ -12662,6 +12662,8 @@ void kvm_arch_flush_shadow_all(struct kvm *kvm)void kvm_arch_flush_shadow_memslot (struct kvm *kvm,struct kvm_memory_slot *slot) { +kvm_mmu_zap_all_fast (kvm);Could we still call
kvm_mmu_invalidate_zap_pages_in_memslot()here? As I know, for TDX, its version ofkvm_mmu_invalidate_zap_pages_in_memslot()is likestatic void kvm_mmu_invalidate_zap_pages_in_memslot(struct kvm *kvm,
structkvm_memory_slot*slot, structkvm_page_track_notifier_node*node)
Quoted 8 lines
{ if (kvm_gfn_shared_mask(kvm)) kvm_mmu_zap_memslot(kvm, slot); else kvm_mmu_zap_all_fast(kvm); }Maybe this kind of judegment is better to be confined in
mmu.c?
Hmm, yeah, I agree. The only reason I exposed kvm_mmu_zap_all_fast() is because kvm_mmu_zap_all() is already exposed for kvm_arch_flush_shadow_all() and it felt weird/wrong to split those. But that's the only usage of kvm_mmu_zap_all(), so a better approach to maintain consistency would be to move kvm_arch_flush_shadow_{all,memslot}() into mmu.c. I'll do that in the next version.
Sean Christopherson
maintainerPATCH v2 12/27 KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs
In reply to Sean ChristophersonDon't use the generic page-track mechanism to handle writes to guest PTEs in KVM's MMU. KVM's MMU needs access to information that should not be exposed to external page-track users, e.g. KVM needs (for some definitions of "need") the vCPU to query the current paging mode, whereas external users, i.e. KVMGT, have no ties to the current vCPU and so should never need the vCPU.
Moving away from the page-track mechanism will allow dropping use of the page-track mechanism for KVM's own MMU, and will also allow simplifying and cleaning up the page-track APIs.
--- arch/x86/include/asm/kvm_host.h | 1 - arch/x86/kvm/mmu.h | 2 ++ arch/x86/kvm/mmu/mmu.c | 13 ++----------- arch/x86/kvm/mmu/page_track.c | 2 ++ 4 files changed, 6 insertions(+), 12 deletions(-)
arch/x86/include/asm/kvm_host.h +0 -1
@@ -1265,7 +1265,6 @@ struct kvm_arch {* create an NX huge page (without hanging the guest). */ struct list_head possible_nx_huge_pages; -struct kvm_page_track_notifier_node mmu_sp_tracker;struct kvm_page_track_notifier_head track_notifier_head;/* * Protects marking pages unsync during page faults, as TDP MMU page
arch/x86/kvm/mmu.h +2 -0
@@ -119,6 +119,8 @@ void kvm_mmu_unload(struct kvm_vcpu *vcpu);void kvm_mmu_free_obsolete_roots (struct kvm_vcpu *vcpu);void kvm_mmu_sync_roots (struct kvm_vcpu *vcpu);void kvm_mmu_sync_prev_roots (struct kvm_vcpu *vcpu); +void kvm_mmu_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, +int bytes);static inline int kvm_mmu_reload (struct kvm_vcpu *vcpu) {
arch/x86/kvm/mmu/mmu.c +2 -11
@@ -5603,9 +5603,8 @@ static u64 *get_written_sptes(struct kvm_mmu_page *sp, gpa_t gpa, int *nspte)return spte; } -static void kvm_mmu_pte_write (struct kvm_vcpu *vcpu,gpa_t gpa, -const u8 *new,int bytes, -struct kvm_page_track_notifier_node *node) +void kvm_mmu_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, +int bytes) {gfn_t gfn = gpa >>PAGE_SHIFT ;struct kvm_mmu_page *sp;
@@ -6088,7 +6087,6 @@ static bool kvm_has_zapped_obsolete_pages(struct kvm *kvm)int kvm_mmu_init_vm (struct kvm *kvm) { -struct kvm_page_track_notifier_node *node = &kvm->arch.mmu_sp_tracker;int r;INIT_LIST_HEAD (&kvm->arch.active_mmu_pages);
@@ -6102,9 +6100,6 @@ int kvm_mmu_init_vm(struct kvm *kvm)return r; } - node->track_write = kvm_mmu_pte_write; -kvm_page_track_register_notifier (kvm, node); - kvm->arch.split_page_header_cache.kmem_cache = mmu_page_header_cache; kvm->arch.split_page_header_cache.gfp_zero = __GFP_ZERO;
@@ -6125,10 +6120,6 @@ static void mmu_free_vm_memory_caches(struct kvm *kvm)void kvm_mmu_uninit_vm (struct kvm *kvm) { -struct kvm_page_track_notifier_node *node = &kvm->arch.mmu_sp_tracker; - -kvm_page_track_unregister_notifier (kvm, node); -if (tdp_mmu_enabled)kvm_mmu_uninit_tdp_mmu (kvm);
arch/x86/kvm/mmu/page_track.c +2 -0
@@ -274,6 +274,8 @@ void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,if (n->track_write) n->track_write (vcpu, gpa, new, bytes, n);srcu_read_unlock (&head->track_srcu, idx); + +kvm_mmu_track_write (vcpu, gpa, new, bytes); }/*
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 12/27] KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs
Quoted 105 lines · Sean Christopherson
Don't use the generic page-track mechanism to handle writes to guest PTEs in KVM's MMU. KVM's MMU needs access to information that should not be exposed to external page-track users, e.g. KVM needs (for some definitions of "need") the vCPU to query the current paging mode, whereas external users, i.e. KVMGT, have no ties to the current vCPU and so should never need the vCPU.
Moving away from the page-track mechanism will allow dropping use of the page-track mechanism for KVM's own MMU, and will also allow simplifying and cleaning up the page-track APIs.
Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_host.h | 1 - arch/x86/kvm/mmu.h | 2 ++ arch/x86/kvm/mmu/mmu.c | 13 ++----------- arch/x86/kvm/mmu/page_track.c | 2 ++ 4 files changed, 6 insertions(+), 12 deletions(-)arch/x86/include/asm/kvm_host.h +0
-1@@ -1265,7 +1265,6 @@ struct kvm_arch {* create an NX huge page (without hanging the guest). */ struct list_head possible_nx_huge_pages; -struct kvm_page_track_notifier_node mmu_sp_tracker;struct kvm_page_track_notifier_head track_notifier_head;/* * Protects marking pages unsync during page faults, as TDP MMU page arch/x86/kvm/mmu.h +2
-0@@ -119,6 +119,8 @@ void kvm_mmu_unload(struct kvm_vcpu *vcpu);void kvm_mmu_free_obsolete_roots (struct kvm_vcpu *vcpu);void kvm_mmu_sync_roots (struct kvm_vcpu *vcpu);void kvm_mmu_sync_prev_roots (struct kvm_vcpu *vcpu); +void kvm_mmu_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, +int bytes);static inline int kvm_mmu_reload (struct kvm_vcpu *vcpu) {arch/x86/kvm/mmu/mmu.c +2
-11@@ -5603,9 +5603,8 @@ static u64 *get_written_sptes(struct kvm_mmu_page *sp, gpa_t gpa, int *nspte)return spte; } -static void kvm_mmu_pte_write (struct kvm_vcpu *vcpu,gpa_t gpa, -const u8 *new,int bytes, -struct kvm_page_track_notifier_node *node) +void kvm_mmu_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, +int bytes) {gfn_t gfn = gpa >>PAGE_SHIFT ;struct kvm_mmu_page *sp;@@ -6088,7 +6087,6 @@ static bool kvm_has_zapped_obsolete_pages(struct kvm *kvm)int kvm_mmu_init_vm (struct kvm *kvm) { -struct kvm_page_track_notifier_node *node = &kvm->arch.mmu_sp_tracker;int r;INIT_LIST_HEAD (&kvm->arch.active_mmu_pages);@@ -6102,9 +6100,6 @@ int kvm_mmu_init_vm(struct kvm *kvm)return r; } - node->track_write = kvm_mmu_pte_write; -kvm_page_track_register_notifier (kvm, node); - kvm->arch.split_page_header_cache.kmem_cache = mmu_page_header_cache; kvm->arch.split_page_header_cache.gfp_zero = __GFP_ZERO;@@ -6125,10 +6120,6 @@ static void mmu_free_vm_memory_caches(struct kvm *kvm)void kvm_mmu_uninit_vm (struct kvm *kvm) { -struct kvm_page_track_notifier_node *node = &kvm->arch.mmu_sp_tracker; - -kvm_page_track_unregister_notifier (kvm, node); -if (tdp_mmu_enabled)kvm_mmu_uninit_tdp_mmu (kvm);arch/x86/kvm/mmu/page_track.c +2
-0@@ -274,6 +274,8 @@ void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,if (n->track_write) n->track_write (vcpu, gpa, new, bytes, n);srcu_read_unlock (&head->track_srcu, idx); + +kvm_mmu_track_write (vcpu, gpa, new, bytes); }/* Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 13/27 KVM: drm/i915/gvt: Drop @vcpu from KVM's ->track_write() hook
In reply to Sean ChristophersonDrop @vcpu from KVM's ->track_write() hook provided for external users of the page-track APIs now that KVM itself doesn't use the page-track mechanism.
--- arch/x86/include/asm/kvm_page_track.h | 5 ++--- arch/x86/kvm/mmu/page_track.c | 2 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 10 ++++------ 3 files changed, 7 insertions(+), 10 deletions(-)
arch/x86/include/asm/kvm_page_track.h +2 -3
@@ -26,14 +26,13 @@ struct kvm_page_track_notifier_node {* It is called when guest is writing the write-tracked page * and write emulation is finished at that time. * -* @vcpu: the vcpu where the write access happened. * @gpa: the physical address written by guest. * @new: the data was written to the address. * @bytes: the written length. * @node: this node */ -void (*track_write)(struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes,struct kvm_page_track_notifier_node *node); +void (*track_write)(gpa_t gpa,const u8 *new,int bytes, +struct kvm_page_track_notifier_node *node);/* * It is called when memory slot is being moved or removed * users can drop write-protection for the pages in that memory slot
arch/x86/kvm/mmu/page_track.c +1 -1
@@ -272,7 +272,7 @@ void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,hlist_for_each_entry_srcu (n, &head->track_notifier_list, node,srcu_read_lock_held (&head->track_srcu))if (n->track_write) - n->track_write (vcpu, gpa, new, bytes, n); + n->track_write (gpa, new, bytes, n);srcu_read_unlock (&head->track_srcu, idx);kvm_mmu_track_write (vcpu, gpa, new, bytes);
drivers/gpu/drm/i915/gvt/kvmgt.c +4 -6
@@ -106,9 +106,8 @@ struct gvt_dma {#define vfio_dev_to_vgpu (vfio_dev) \ container_of((vfio_dev), struct intel_vgpu, vfio_device) -static void kvmgt_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa, -const u8 *val,int len, -struct kvm_page_track_notifier_node *node); +static void kvmgt_page_track_write (gpa_t gpa,const u8 *val,int len, +struct kvm_page_track_notifier_node *node);static void kvmgt_page_track_flush_slot (struct kvm *kvm,struct kvm_memory_slot *slot,struct kvm_page_track_notifier_node *node);
@@ -1617,9 +1616,8 @@ int intel_gvt_page_track_remove(struct intel_vgpu *info, u64 gfn)return 0 ; } -static void kvmgt_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa, -const u8 *val,int len, -struct kvm_page_track_notifier_node *node) +static void kvmgt_page_track_write (gpa_t gpa,const u8 *val,int len, +struct kvm_page_track_notifier_node *node) {struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 13/27] KVM: drm/i915/gvt: Drop @vcpu from KVM's ->track_write() hook
Quoted 76 lines · Sean Christopherson
Drop @vcpu from KVM's ->track_write() hook provided for external users of the page-track APIs now that KVM itself doesn't use the page-track mechanism.
Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_page_track.h | 5 ++--- arch/x86/kvm/mmu/page_track.c | 2 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 10 ++++------ 3 files changed, 7 insertions(+), 10 deletions(-)arch/x86/include/asm/kvm_page_track.h +2
-3@@ -26,14 +26,13 @@ struct kvm_page_track_notifier_node {* It is called when guest is writing the write-tracked page * and write emulation is finished at that time. * -* @vcpu: the vcpu where the write access happened. * @gpa: the physical address written by guest. * @new: the data was written to the address. * @bytes: the written length. * @node: this node */ -void (*track_write)(struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes,struct kvm_page_track_notifier_node *node); +void (*track_write)(gpa_t gpa,const u8 *new,int bytes, +struct kvm_page_track_notifier_node *node);/* * It is called when memory slot is being moved or removed * users can drop write-protection for the pages in that memory slot arch/x86/kvm/mmu/page_track.c +1
-1@@ -272,7 +272,7 @@ void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,hlist_for_each_entry_srcu (n, &head->track_notifier_list, node,srcu_read_lock_held (&head->track_srcu))if (n->track_write) - n->track_write (vcpu, gpa, new, bytes, n); + n->track_write (gpa, new, bytes, n);srcu_read_unlock (&head->track_srcu, idx);kvm_mmu_track_write (vcpu, gpa, new, bytes);drivers/gpu/drm/i915/gvt/kvmgt.c +4
-6@@ -106,9 +106,8 @@ struct gvt_dma {#define vfio_dev_to_vgpu (vfio_dev) \ container_of((vfio_dev), struct intel_vgpu, vfio_device) -static void kvmgt_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa, -const u8 *val,int len, -struct kvm_page_track_notifier_node *node); +static void kvmgt_page_track_write (gpa_t gpa,const u8 *val,int len, +struct kvm_page_track_notifier_node *node);static void kvmgt_page_track_flush_slot (struct kvm *kvm,struct kvm_memory_slot *slot,struct kvm_page_track_notifier_node *node);@@ -1617,9 +1616,8 @@ int intel_gvt_page_track_remove(struct intel_vgpu *info, u64 gfn)return 0 ; } -static void kvmgt_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa, -const u8 *val,int len, -struct kvm_page_track_notifier_node *node) +static void kvmgt_page_track_write (gpa_t gpa,const u8 *val,int len, +struct kvm_page_track_notifier_node *node) {struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node);Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 14/27 KVM: x86: Reject memslot MOVE operations if KVMGT is attached
In reply to Sean ChristophersonDisallow moving memslots if the VM has external page-track users, i.e. if KVMGT is being used to expose a virtual GPU to the guest, as KVM doesn't correctly handle moving memory regions.
Note, this is potential ABI breakage! E.g. userspace could move regions that aren't shadowed by KVMGT without harming the guest. However, the only known user of KVMGT is QEMU, and QEMU doesn't move generic memory regions. KVM's own support for moving memory regions was also broken for multiple years (albeit for an edge case, but arguably moving RAM is itself an edge case), e.g. see commit edd4fa37baa6 ("KVM: x86: Allocate new rmap and large page tracking when moving memslot").
--- arch/x86/include/asm/kvm_page_track.h | 3 +++ arch/x86/kvm/mmu/page_track.c | 5 +++++ arch/x86/kvm/x86.c | 7 +++++++ 3 files changed, 15 insertions(+)
arch/x86/include/asm/kvm_page_track.h +3 -0
@@ -77,4 +77,7 @@ kvm_page_track_unregister_notifier(struct kvm *kvm,void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new,int bytes);void kvm_page_track_flush_slot (struct kvm *kvm,struct kvm_memory_slot *slot); + +bool kvm_page_track_has_external_user (struct kvm *kvm); +#endif
arch/x86/kvm/mmu/page_track.c +5 -0
@@ -321,3 +321,8 @@ enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn,return max_level; }EXPORT_SYMBOL_GPL (kvm_page_track_max_mapping_level); + +bool kvm_page_track_has_external_user (struct kvm *kvm) +{ +return hlist_empty (&kvm->arch.track_notifier_head.track_notifier_list); +}
arch/x86/kvm/x86.c +7 -0
@@ -12484,6 +12484,13 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm, struct kvm_memory_slot *new, enum kvm_mr_change change) { +/* +* KVM doesn't support moving memslots when there are external page +* trackers attached to the VM, i.e. if KVMGT is in use. +*/ +if (change ==KVM_MR_MOVE &&kvm_page_track_has_external_user (kvm)) +return -EINVAL ; +if (change ==KVM_MR_CREATE || change ==KVM_MR_MOVE ) {if ((new->base_gfn + new->npages -1 ) >kvm_mmu_max_gfn ())return -EINVAL ;
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 14/27] KVM: x86: Reject memslot MOVE operations if KVMGT is attached
Quoted 13 lines · Sean Christopherson
Disallow moving memslots if the VM has external page-track users, i.e. if KVMGT is being used to expose a virtual GPU to the guest, as KVM doesn't correctly handle moving memory regions.
Note, this is potential ABI breakage! E.g. userspace could move regions that aren't shadowed by KVMGT without harming the guest. However, the only known user of KVMGT is QEMU, and QEMU doesn't move generic memory regions. KVM's own support for moving memory regions was also broken for multiple years (albeit for an edge case, but arguably moving RAM is itself an edge case), e.g. see commit
edd4fa37baa6("KVM: x86: Allocate new rmap and large page tracking when moving memslot").Signed-off-by Sean Christopherson <[email protected]>
...
Quoted 5 lines
arch/x86/kvm/x86.c +0
-0
arch/x86/kvm/x86.c int kvm_arch_prepare_memory_region(struct kvm *kvm, · line 12492
Quoted 9 lines
arch/x86/kvm/x86.c +6
-0@@ -12484,6 +12484,13 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm, struct kvm_memory_slot *new, enum kvm_mr_change change) { +/* +* KVM doesn't support moving memslots when there are external page +* trackers attached to the VM, i.e. if KVMGT is in use. +*/ +if (change ==KVM_MR_MOVE &&kvm_page_track_has_external_user (kvm)) +return -EINVAL ;
Hmm, will page track work correctly on moving memslots when there's no external users?
in case of KVM_MR_MOVE, kvm_prepare_memory_region(kvm, old, new, change)
|->kvm_arch_prepare_memory_region(kvm, old, new, change)
|->kvm_alloc_memslot_metadata(kvm, new)
|->memset(&slot->arch, 0, sizeof(slot->arch));
|->kvm_page_track_create_memslot(kvm, slot, npages)The new->arch.arch.gfn_write_track will be fresh empty.
kvm_arch_commit_memory_region(kvm, old, new, change);
|->kvm_arch_free_memslot(kvm, old);
|->kvm_page_track_free_memslot(slot);The old->arch.gfn_write_track is freed afterwards.
So, in theory, the new GFNs are not write tracked though the old ones are.
Is that acceptable for the internal page-track user?
Quoted 6 lines
arch/x86/kvm/x86.c +0
-0if (change ==KVM_MR_CREATE || change ==KVM_MR_MOVE ) {if ((new->base_gfn + new->npages -1 ) >kvm_mmu_max_gfn ())return -EINVAL ;Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerRe: [PATCH v2 14/27] KVM: x86: Reject memslot MOVE operations if KVMGT is attached
Quoted 41 lines · Yan Zhao
Quoted 13 lines · Sean Christopherson
Disallow moving memslots if the VM has external page-track users, i.e. if KVMGT is being used to expose a virtual GPU to the guest, as KVM doesn't correctly handle moving memory regions.
Note, this is potential ABI breakage! E.g. userspace could move regions that aren't shadowed by KVMGT without harming the guest. However, the only known user of KVMGT is QEMU, and QEMU doesn't move generic memory regions. KVM's own support for moving memory regions was also broken for multiple years (albeit for an edge case, but arguably moving RAM is itself an edge case), e.g. see commit
edd4fa37baa6("KVM: x86: Allocate new rmap and large page tracking when moving memslot").Signed-off-by Sean Christopherson <[email protected]>...
Quoted 5 lines
arch/x86/kvm/x86.c +0
-0arch/x86/kvm/x86.c int kvm_arch_prepare_memory_region(struct kvm *kvm, · line 12492
Quoted 9 lines
arch/x86/kvm/x86.c +6
-0@@ -12484,6 +12484,13 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm, struct kvm_memory_slot *new, enum kvm_mr_change change) { +/* +* KVM doesn't support moving memslots when there are external page +* trackers attached to the VM, i.e. if KVMGT is in use. +*/ +if (change ==KVM_MR_MOVE &&kvm_page_track_has_external_user (kvm)) +return -EINVAL ;Hmm, will page track work correctly on moving memslots when there's no external users?
in case of
KVM_MR_MOVE,kvm_prepare_memory_region(kvm, old, new, change)
|->kvm_arch_prepare_memory_region(kvm, old, new, change)|->kvm_alloc_memslot_metadata(kvm, new) |->memset(&slot->arch, 0, sizeof(slot->arch)); |->kvm_page_track_create_memslot(kvm, slot, npages)The
new->arch.arch.gfn_write_trackwill be fresh empty.
Quoted 8 lines
kvm_arch_commit_memory_region(kvm, old, new, change);|->kvm_arch_free_memslot(kvm, old); |->kvm_page_track_free_memslot(slot);The
old->arch.gfn_write_trackis freed afterwards.So, in theory, the new GFNs are not write tracked though the old ones are.
Is that acceptable for the internal page-track user?
It works because KVM zaps all SPTEs when a memslot is moved, i.e. the fact that KVM loses the write-tracking counts is benign. I suspect no VMM actually does does KVM_MR_MOVE in conjunction with shadow paging, but the ongoing maintenance cost of supporting KVM_MR_MOVE is quite low at this point, so trying to rip it out isn't worth the pain of having to deal with potential ABI breakage.
Though in hindsight I wish I had tried disallowed moving memslots instead of fixing the various bugs a few years back. :-(
Re: [PATCH v2 14/27] KVM: x86: Reject memslot MOVE operations if KVMGT is attached
Quoted 5 lines · Sean Christopherson
Quoted 3 lines
So, in theory, the new GFNs are not write tracked though the old ones are.
Is that acceptable for the internal page-track user?
It works because KVM zaps all SPTEs when a memslot is moved, i.e. the fact that
Oh, yes!
And KVM will not shadow SPTEs for a invalid memslot, so there's no problem.
Thanks~
Quoted 7 lines
KVM loses the write-tracking counts is benign. I suspect no VMM actually does does
KVM_MR_MOVEin conjunction with shadow paging, but the ongoing maintenance cost of supportingKVM_MR_MOVEis quite low at this point, so trying to rip it out isn't worth the pain of having to deal with potential ABI breakage.Though in hindsight I wish I had tried disallowed moving memslots instead of fixing the various bugs a few years back. :-(
Re: [PATCH v2 14/27] KVM: x86: Reject memslot MOVE operations if KVMGT is attached
In reply to Sean ChristophersonQuoted 65 lines · Sean Christopherson
Disallow moving memslots if the VM has external page-track users, i.e. if KVMGT is being used to expose a virtual GPU to the guest, as KVM doesn't correctly handle moving memory regions.
Note, this is potential ABI breakage! E.g. userspace could move regions that aren't shadowed by KVMGT without harming the guest. However, the only known user of KVMGT is QEMU, and QEMU doesn't move generic memory regions. KVM's own support for moving memory regions was also broken for multiple years (albeit for an edge case, but arguably moving RAM is itself an edge case), e.g. see commit
edd4fa37baa6("KVM: x86: Allocate new rmap and large page tracking when moving memslot").Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_page_track.h | 3 +++ arch/x86/kvm/mmu/page_track.c | 5 +++++ arch/x86/kvm/x86.c | 7 +++++++ 3 files changed, 15 insertions(+)arch/x86/include/asm/kvm_page_track.h +3
-0@@ -77,4 +77,7 @@ kvm_page_track_unregister_notifier(struct kvm *kvm,void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new,int bytes);void kvm_page_track_flush_slot (struct kvm *kvm,struct kvm_memory_slot *slot); + +bool kvm_page_track_has_external_user (struct kvm *kvm); +#endif arch/x86/kvm/mmu/page_track.c +5
-0@@ -321,3 +321,8 @@ enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn,return max_level; }EXPORT_SYMBOL_GPL (kvm_page_track_max_mapping_level); + +bool kvm_page_track_has_external_user (struct kvm *kvm) +{ +return hlist_empty (&kvm->arch.track_notifier_head.track_notifier_list); +}arch/x86/kvm/x86.c +7
-0@@ -12484,6 +12484,13 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm, struct kvm_memory_slot *new, enum kvm_mr_change change) { +/* +* KVM doesn't support moving memslots when there are external page +* trackers attached to the VM, i.e. if KVMGT is in use. +*/ +if (change ==KVM_MR_MOVE &&kvm_page_track_has_external_user (kvm)) +return -EINVAL ; +if (change ==KVM_MR_CREATE || change ==KVM_MR_MOVE ) {if ((new->base_gfn + new->npages -1 ) >kvm_mmu_max_gfn ())return -EINVAL ;Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 15/27 drm/i915/gvt: Don't bother removing write-protection on to-be-deleted slot
In reply to Sean ChristophersonWhen handling a slot "flush", don't call back into KVM to drop write protection for gfns in the slot. Now that KVM rejects attempts to move memory slots while KVMGT is attached, the only time a slot is "flushed" is when it's being removed, i.e. the memslot and all its write-tracking metadata is about to be deleted.
--- drivers/gpu/drm/i915/gvt/kvmgt.c | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)
drivers/gpu/drm/i915/gvt/kvmgt.c +1 -7
@@ -1644,14 +1644,8 @@ static void kvmgt_page_track_flush_slot(struct kvm *kvm,for (i =0 ; i < slot->npages; i++) { gfn = slot->base_gfn + i; -if (kvmgt_gfn_is_write_protected (info, gfn)) { -write_lock (&kvm->mmu_lock); -kvm_slot_page_track_remove_page (kvm, slot, gfn, -KVM_PAGE_TRACK_WRITE ); -write_unlock (&kvm->mmu_lock); - +if (kvmgt_gfn_is_write_protected (info, gfn))kvmgt_protect_table_del (info, gfn); - } }mutex_unlock (&info->vgpu_lock); }
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 15/27] drm/i915/gvt: Don't bother removing write-protection on to-be-deleted slot
Quoted 34 lines · Sean Christopherson
When handling a slot "flush", don't call back into KVM to drop write protection for gfns in the slot. Now that KVM rejects attempts to move memory slots while KVMGT is attached, the only time a slot is "flushed" is when it's being removed, i.e. the memslot and all its write-tracking metadata is about to be deleted.
Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)drivers/gpu/drm/i915/gvt/kvmgt.c +1
-7@@ -1644,14 +1644,8 @@ static void kvmgt_page_track_flush_slot(struct kvm *kvm,for (i =0 ; i < slot->npages; i++) { gfn = slot->base_gfn + i; -if (kvmgt_gfn_is_write_protected (info, gfn)) { -write_lock (&kvm->mmu_lock); -kvm_slot_page_track_remove_page (kvm, slot, gfn, -KVM_PAGE_TRACK_WRITE ); -write_unlock (&kvm->mmu_lock); - +if (kvmgt_gfn_is_write_protected (info, gfn))kvmgt_protect_table_del (info, gfn); - } }mutex_unlock (&info->vgpu_lock); }Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 16/27 KVM: x86: Add a new page-track hook to handle memslot deletion
In reply to Sean ChristophersonFrom: Yan Zhao <[email protected]>
Add a new page-track hook, track_remove_region(), that is called when a memslot DELETE operation is about to be committed. The "remove" hook will be used by KVMGT and will effectively replace the existing track_flush_slot() altogether now that KVM itself doesn't rely on the "flush" hook either.
The "flush" hook is flawed as it's invoked before the memslot operation is guaranteed to succeed, i.e. KVM might ultimately keep the existing memslot without notifying external page track users, a.k.a. KVMGT. In practice, this can't currently happen on x86, but there are no guarantees that won't change in the future, not to mention that "flush" does a very poor job of describing what is happening.
Pass in the gfn+nr_pages instead of the slot itself so external users, i.e. KVMGT, don't need to exposed to KVM internals (memslots). This will help set the stage for additional cleanups to the page-track APIs.
--- arch/x86/include/asm/kvm_page_track.h | 12 ++++++++++++ arch/x86/kvm/mmu/page_track.c | 23 +++++++++++++++++++++++ arch/x86/kvm/x86.c | 3 +++ 3 files changed, 38 insertions(+)
arch/x86/include/asm/kvm_page_track.h +12 -0
@@ -43,6 +43,17 @@ struct kvm_page_track_notifier_node {*/ void (*track_flush_slot)(struct kvm *kvm,struct kvm_memory_slot *slot,struct kvm_page_track_notifier_node *node); + +/* +* Invoked when a memory region is removed from the guest. Or in KVM +* terms, when a memslot is deleted. +* +* @gfn: base gfn of the region being removed +* @nr_pages: number of pages in the to-be-removed region +* @node: this node +*/ +void (*track_remove_region)(gfn_t gfn,unsigned long nr_pages, +struct kvm_page_track_notifier_node *node); };int kvm_page_track_init (struct kvm *kvm);
@@ -77,6 +88,7 @@ kvm_page_track_unregister_notifier(struct kvm *kvm,void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new,int bytes);void kvm_page_track_flush_slot (struct kvm *kvm,struct kvm_memory_slot *slot); +void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot);bool kvm_page_track_has_external_user (struct kvm *kvm);
arch/x86/kvm/mmu/page_track.c +23 -0
@@ -304,6 +304,29 @@ void kvm_page_track_flush_slot(struct kvm *kvm, struct kvm_memory_slot *slot)srcu_read_unlock (&head->track_srcu, idx); } +/* +* Notify external page track nodes that a memory region is being removed from +* the VM, e.g. so that users can free any associated metadata. +*/ +void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot) +{ +struct kvm_page_track_notifier_head *head; +struct kvm_page_track_notifier_node *n; +int idx; + + head = &kvm->arch.track_notifier_head; + +if (hlist_empty (&head->track_notifier_list)) +return ; + + idx =srcu_read_lock (&head->track_srcu); +hlist_for_each_entry_srcu (n, &head->track_notifier_list, node, +srcu_read_lock_held (&head->track_srcu)) +if (n->track_remove_region) + n->track_remove_region (slot->base_gfn, slot->npages, n); +srcu_read_unlock (&head->track_srcu, idx); +} +enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn,enum pg_level max_level) {
arch/x86/kvm/x86.c +3 -0
@@ -12645,6 +12645,9 @@ void kvm_arch_commit_memory_region(struct kvm *kvm, const struct kvm_memory_slot *new, enum kvm_mr_change change) { + if (change == KVM_MR_DELETE) + kvm_page_track_delete_slot(kvm, old); +if (!kvm->arch.n_requested_mmu_pages && (change ==KVM_MR_CREATE || change ==KVM_MR_DELETE )) {unsigned long nr_mmu_pages;
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 16/27] KVM: x86: Add a new page-track hook to handle memslot deletion
Quoted 23 lines · Sean Christopherson
From: Yan Zhao <[email protected]>
Add a new page-track hook,
track_remove_region(), that is called when a memslot DELETE operation is about to be committed. The "remove" hook will be used by KVMGT and will effectively replace the existingtrack_flush_slot()altogether now that KVM itself doesn't rely on the "flush" hook either.The "flush" hook is flawed as it's invoked before the memslot operation is guaranteed to succeed, i.e. KVM might ultimately keep the existing memslot without notifying external page track users, a.k.a. KVMGT. In practice, this can't currently happen on x86, but there are no guarantees that won't change in the future, not to mention that "flush" does a very poor job of describing what is happening.
Pass in the gfn+nr_pages instead of the slot itself so external users, i.e. KVMGT, don't need to exposed to KVM internals (memslots). This will help set the stage for additional cleanups to the page-track APIs.
Cc Zhenyu Wang <[email protected]>Signed-off-by Yan Zhao <[email protected]>Co-developed-by Sean Christopherson <[email protected]>Signed-off-by Sean Christopherson <[email protected]>
...
Quoted 4 lines
arch/x86/kvm/mmu/page_track.c +4
-0+void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot) +{ +struct kvm_page_track_notifier_head *head; +struct kvm_page_track_notifier_node *n;
arch/x86/kvm/mmu/page_track.c void kvm_page_track_flush_slot(struct kvm *kvm, struct kvm_memory_slot *slot) · line 324
Quoted 10 lines
arch/x86/kvm/mmu/page_track.c +10
-0+int idx; + + head = &kvm->arch.track_notifier_head; + +if (hlist_empty (&head->track_notifier_list)) +return ; + + idx =srcu_read_lock (&head->track_srcu); +hlist_for_each_entry_srcu (n, &head->track_notifier_list, node, +srcu_read_lock_held (&head->track_srcu))
Sorry, not sure why the alignment here is not right. Patchwork just sent me a mail to complain about it. Would you mind helping fix it in the next version?
Thanks a lot!
Quoted 5 lines
arch/x86/kvm/mmu/page_track.c +5
-0+if (n->track_remove_region) + n->track_remove_region (slot->base_gfn, slot->npages, n); +srcu_read_unlock (&head->track_srcu, idx); +} +
Sean Christopherson
maintainerRe: [PATCH v2 16/27] KVM: x86: Add a new page-track hook to handle memslot deletion
Quoted 35 lines · Yan Zhao
Quoted 23 lines · Sean Christopherson
From: Yan Zhao <[email protected]>
Add a new page-track hook,
track_remove_region(), that is called when a memslot DELETE operation is about to be committed. The "remove" hook will be used by KVMGT and will effectively replace the existingtrack_flush_slot()altogether now that KVM itself doesn't rely on the "flush" hook either.The "flush" hook is flawed as it's invoked before the memslot operation is guaranteed to succeed, i.e. KVM might ultimately keep the existing memslot without notifying external page track users, a.k.a. KVMGT. In practice, this can't currently happen on x86, but there are no guarantees that won't change in the future, not to mention that "flush" does a very poor job of describing what is happening.
Pass in the gfn+nr_pages instead of the slot itself so external users, i.e. KVMGT, don't need to exposed to KVM internals (memslots). This will help set the stage for additional cleanups to the page-track APIs.
Cc Zhenyu Wang <[email protected]>Signed-off-by Yan Zhao <[email protected]>Co-developed-by Sean Christopherson <[email protected]>Signed-off-by Sean Christopherson <[email protected]>...
Quoted 9 lines
arch/x86/kvm/mmu/page_track.c +9
-0+void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot) +{ +struct kvm_page_track_notifier_head *head; +struct kvm_page_track_notifier_node *n; +int idx; + + head = &kvm->arch.track_notifier_head; + +if (hlist_empty (&head->track_notifier_list))
Quoted 8 lines
arch/x86/kvm/mmu/page_track.c void kvm_page_track_flush_slot(struct kvm *kvm, struct kvm_memory_slot *slot) · line 324
Quoted 5 lines
arch/x86/kvm/mmu/page_track.c +5
-0+return ; + + idx =srcu_read_lock (&head->track_srcu); +hlist_for_each_entry_srcu (n, &head->track_notifier_list, node, +srcu_read_lock_held (&head->track_srcu))Sorry, not sure why the alignment here is not right. Patchwork just sent me a mail to complain about it. Would you mind helping fix it in the next version?
Ah, it's off by two spaces, should be
hlist_for_each_entry_srcu(n, &head->track_notifier_list, node, srcu_read_lock_held(&head->track_srcu))
I'll get it fixed in the next version.
Sean Christopherson
maintainerPATCH v2 17/27 drm/i915/gvt: switch from ->track_flush_slot() to ->track_remove_region()
In reply to Sean ChristophersonFrom: Yan Zhao <[email protected]>
Switch from the poorly named and flawed ->track_flush_slot() to the newly introduced ->track_remove_region(). From KVMGT's perspective, the two hooks are functionally equivalent, the only difference being that ->track_remove_region() is called only when KVM is 100% certain the memory region will be removed, i.e. is invoked slightly later in KVM's memslot modification flow.
--- drivers/gpu/drm/i915/gvt/kvmgt.c | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-)
drivers/gpu/drm/i915/gvt/kvmgt.c +9 -12
@@ -108,9 +108,8 @@ struct gvt_dma {static void kvmgt_page_track_write (gpa_t gpa,const u8 *val,int len,struct kvm_page_track_notifier_node *node); -static void kvmgt_page_track_flush_slot (struct kvm *kvm, -struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node); +static void kvmgt_page_track_remove_region (gfn_t gfn,unsigned long nr_pages, +struct kvm_page_track_notifier_node *node);static ssize_t intel_vgpu_show_description (struct mdev_type *mtype,char *buf) {
@@ -680,7 +679,7 @@ static int intel_vgpu_open_device(struct vfio_device *vfio_dev)return -EEXIST ; vgpu->track_node.track_write = kvmgt_page_track_write; - vgpu->track_node.track_flush_slot = kvmgt_page_track_flush_slot; + vgpu->track_node.track_remove_region = kvmgt_page_track_remove_region;kvm_get_kvm (vgpu->vfio_device.kvm);kvm_page_track_register_notifier (vgpu->vfio_device.kvm, &vgpu->track_node);
@@ -1631,22 +1630,20 @@ static void kvmgt_page_track_write(gpa_t gpa, const u8 *val, int len,mutex_unlock (&info->vgpu_lock); } -static void kvmgt_page_track_flush_slot (struct kvm *kvm, -struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node) +static void kvmgt_page_track_remove_region (gfn_t gfn,unsigned long nr_pages, +struct kvm_page_track_notifier_node *node) {unsigned long i; -gfn_t gfn;struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node);mutex_lock (&info->vgpu_lock); -for (i =0 ; i < slot->npages; i++) { - gfn = slot->base_gfn + i; -if (kvmgt_gfn_is_write_protected (info, gfn)) -kvmgt_protect_table_del (info, gfn); +for (i =0 ; i < nr_pages; i++) { +if (kvmgt_gfn_is_write_protected (info, gfn + i)) +kvmgt_protect_table_del (info, gfn + i); } +mutex_unlock (&info->vgpu_lock); }
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 17/27] drm/i915/gvt: switch from ->track_flush_slot() to ->track_remove_region()
Quoted 75 lines · Sean Christopherson
From: Yan Zhao <[email protected]>
Switch from the poorly named and flawed ->track_flush_slot() to the newly introduced ->track_remove_region(). From KVMGT's perspective, the two hooks are functionally equivalent, the only difference being that ->track_remove_region() is called only when KVM is 100% certain the memory region will be removed, i.e. is invoked slightly later in KVM's memslot modification flow.
Cc Zhenyu Wang <[email protected]>Suggested-by Sean Christopherson <[email protected]>Signed-off-by Yan Zhao <[email protected]>[sean: handle name change, massage changelog, rebase]Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-)drivers/gpu/drm/i915/gvt/kvmgt.c +9
-12@@ -108,9 +108,8 @@ struct gvt_dma {static void kvmgt_page_track_write (gpa_t gpa,const u8 *val,int len,struct kvm_page_track_notifier_node *node); -static void kvmgt_page_track_flush_slot (struct kvm *kvm, -struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node); +static void kvmgt_page_track_remove_region (gfn_t gfn,unsigned long nr_pages, +struct kvm_page_track_notifier_node *node);static ssize_t intel_vgpu_show_description (struct mdev_type *mtype,char *buf) {@@ -680,7 +679,7 @@ static int intel_vgpu_open_device(struct vfio_device *vfio_dev)return -EEXIST ; vgpu->track_node.track_write = kvmgt_page_track_write; - vgpu->track_node.track_flush_slot = kvmgt_page_track_flush_slot; + vgpu->track_node.track_remove_region = kvmgt_page_track_remove_region;kvm_get_kvm (vgpu->vfio_device.kvm);kvm_page_track_register_notifier (vgpu->vfio_device.kvm, &vgpu->track_node);@@ -1631,22 +1630,20 @@ static void kvmgt_page_track_write(gpa_t gpa, const u8 *val, int len,mutex_unlock (&info->vgpu_lock); } -static void kvmgt_page_track_flush_slot (struct kvm *kvm, -struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node) +static void kvmgt_page_track_remove_region (gfn_t gfn,unsigned long nr_pages, +struct kvm_page_track_notifier_node *node) {unsigned long i; -gfn_t gfn;struct intel_vgpu *info = container_of(node, struct intel_vgpu, track_node);mutex_lock (&info->vgpu_lock); -for (i =0 ; i < slot->npages; i++) { - gfn = slot->base_gfn + i; -if (kvmgt_gfn_is_write_protected (info, gfn)) -kvmgt_protect_table_del (info, gfn); +for (i =0 ; i < nr_pages; i++) { +if (kvmgt_gfn_is_write_protected (info, gfn + i)) +kvmgt_protect_table_del (info, gfn + i); } +mutex_unlock (&info->vgpu_lock); }Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 18/27 KVM: x86: Remove the unused page-track hook track_flush_slot()
In reply to Sean ChristophersonFrom: Yan Zhao <[email protected]>
Remove ->track_remove_slot(), there are no longer any users and it's unlikely a "flush" hook will ever be the correct API to provide to an external page-track user.
--- arch/x86/include/asm/kvm_page_track.h | 11 ----------- arch/x86/kvm/mmu/page_track.c | 26 -------------------------- arch/x86/kvm/x86.c | 2 -- 3 files changed, 39 deletions(-)
arch/x86/include/asm/kvm_page_track.h +0 -11
@@ -33,16 +33,6 @@ struct kvm_page_track_notifier_node {*/ void (*track_write)(gpa_t gpa,const u8 *new,int bytes,struct kvm_page_track_notifier_node *node); -/* -* It is called when memory slot is being moved or removed -* users can drop write-protection for the pages in that memory slot -* -* @kvm: the kvm where memory slot being moved or removed -* @slot: the memory slot being moved or removed -* @node: this node -*/ -void (*track_flush_slot)(struct kvm *kvm,struct kvm_memory_slot *slot, -struct kvm_page_track_notifier_node *node);/* * Invoked when a memory region is removed from the guest. Or in KVM
@@ -87,7 +77,6 @@ kvm_page_track_unregister_notifier(struct kvm *kvm, struct kvm_page_track_notifier_node *n);void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new,int bytes); -void kvm_page_track_flush_slot (struct kvm *kvm,struct kvm_memory_slot *slot);void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot);bool kvm_page_track_has_external_user (struct kvm *kvm);
arch/x86/kvm/mmu/page_track.c +0 -26
@@ -278,32 +278,6 @@ void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,kvm_mmu_track_write (vcpu, gpa, new, bytes); } -/* -* Notify the node that memory slot is being removed or moved so that it can -* drop write-protection for the pages in the memory slot. -* -* The node should figure out it has any write-protected pages in this slot -* by itself. -*/ -void kvm_page_track_flush_slot (struct kvm *kvm,struct kvm_memory_slot *slot) -{ -struct kvm_page_track_notifier_head *head; -struct kvm_page_track_notifier_node *n; -int idx; - - head = &kvm->arch.track_notifier_head; - -if (hlist_empty (&head->track_notifier_list)) -return ; - - idx =srcu_read_lock (&head->track_srcu); -hlist_for_each_entry_srcu (n, &head->track_notifier_list, node, -srcu_read_lock_held (&head->track_srcu)) -if (n->track_flush_slot) - n->track_flush_slot (kvm, slot, n); -srcu_read_unlock (&head->track_srcu, idx); -} -/* * Notify external page track nodes that a memory region is being removed from * the VM, e.g. so that users can free any associated metadata.
arch/x86/kvm/x86.c +0 -2
@@ -12673,8 +12673,6 @@ void kvm_arch_flush_shadow_memslot(struct kvm *kvm, struct kvm_memory_slot *slot) {kvm_mmu_zap_all_fast (kvm); - -kvm_page_track_flush_slot (kvm, slot); }static inline bool kvm_guest_apic_has_interrupt (struct kvm_vcpu *vcpu)
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 19/27 KVM: x86/mmu: Move KVM-only page-track declarations to internal header
In reply to Sean ChristophersonBury the declaration of the page-track helpers that are intended only for internal KVM use in a "private" header. In addition to guarding against unwanted usage of the internal-only helpers, dropping their definitions avoids exposing other structures that should be KVM-internal, e.g. for memslots. This is a baby step toward making kvm_host.h a KVM-internal header in the very distant future.
--- arch/x86/include/asm/kvm_page_track.h | 26 ++++----------------- arch/x86/kvm/mmu/mmu.c | 3 ++- arch/x86/kvm/mmu/page_track.c | 8 +------ arch/x86/kvm/mmu/page_track.h | 33 +++++++++++++++++++++++++++ arch/x86/kvm/x86.c | 1 + 5 files changed, 42 insertions(+), 29 deletions(-) create mode 100644 arch/x86/kvm/mmu/page_track.h
arch/x86/include/asm/kvm_page_track.h +5 -21
@@ -2,6 +2,8 @@#ifndef _ASM_X86_KVM_PAGE_TRACK_H#define _ASM_X86_KVM_PAGE_TRACK_H +#include <linux/kvm_types.h> +enum kvm_page_track_mode {KVM_PAGE_TRACK_WRITE , KVM_PAGE_TRACK_MAX,
@@ -46,28 +48,15 @@ struct kvm_page_track_notifier_node { struct kvm_page_track_notifier_node *node); }; -int kvm_page_track_init (struct kvm *kvm); -void kvm_page_track_cleanup (struct kvm *kvm); - -bool kvm_page_track_write_tracking_enabled (struct kvm *kvm); -int kvm_page_track_write_tracking_alloc (struct kvm_memory_slot *slot); -enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn, -enum pg_level max_level); - -void kvm_page_track_free_memslot (struct kvm_memory_slot *slot); -int kvm_page_track_create_memslot (struct kvm *kvm, -struct kvm_memory_slot *slot, -unsigned long npages); -void kvm_slot_page_track_add_page (struct kvm *kvm,struct kvm_memory_slot *slot,gfn_t gfn,enum kvm_page_track_mode mode);void kvm_slot_page_track_remove_page (struct kvm *kvm,struct kvm_memory_slot *slot,gfn_t gfn,enum kvm_page_track_mode mode); -bool kvm_slot_page_track_is_active (struct kvm *kvm, -const struct kvm_memory_slot *slot, -gfn_t gfn,enum kvm_page_track_mode mode); + +enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn, +enum pg_level max_level); void kvm_page_track_register_notifier(struct kvm *kvm,
@@ -75,10 +64,5 @@ kvm_page_track_register_notifier(struct kvm *kvm,void kvm_page_track_unregister_notifier (struct kvm *kvm,struct kvm_page_track_notifier_node *n); -void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes); -void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot); - -bool kvm_page_track_has_external_user (struct kvm *kvm);#endif
arch/x86/kvm/mmu/mmu.c +2 -1
@@ -25,6 +25,7 @@#include "kvm_cache_regs.h" #include "smm.h" #include "kvm_emulate.h" +#include "page_track.h" #include "cpuid.h" #include "spte.h"
@@ -53,7 +54,7 @@#include <asm/io.h> #include <asm/set_memory.h> #include <asm/vmx.h> -#include <asm/kvm_page_track.h> +#include "trace.h" extern bool itlb_multihit_kvm_mitigation;
arch/x86/kvm/mmu/page_track.c +1 -7
@@ -15,10 +15,9 @@#include <linux/kvm_host.h> #include <linux/rculist.h> -#include <asm/kvm_page_track.h> -#include "mmu.h" #include "mmu_internal.h" +#include "page_track.h" bool kvm_page_track_write_tracking_enabled (struct kvm *kvm) {
@@ -318,8 +317,3 @@ enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn,return max_level; }EXPORT_SYMBOL_GPL (kvm_page_track_max_mapping_level); - -bool kvm_page_track_has_external_user (struct kvm *kvm) -{ -return hlist_empty (&kvm->arch.track_notifier_head.track_notifier_list); -}
arch/x86/kvm/mmu/page_track.h new file +33 -0
@@ -0,0 +1,33 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#ifndef __KVM_X86_PAGE_TRACK_H +#define __KVM_X86_PAGE_TRACK_H + +#include <linux/kvm_host.h> + +#include <asm/kvm_page_track.h> + +int kvm_page_track_init (struct kvm *kvm); +void kvm_page_track_cleanup (struct kvm *kvm); + +bool kvm_page_track_write_tracking_enabled (struct kvm *kvm); +int kvm_page_track_write_tracking_alloc (struct kvm_memory_slot *slot); + +void kvm_page_track_free_memslot (struct kvm_memory_slot *slot); +int kvm_page_track_create_memslot (struct kvm *kvm, +struct kvm_memory_slot *slot, +unsigned long npages); + +bool kvm_slot_page_track_is_active (struct kvm *kvm, +const struct kvm_memory_slot *slot, +gfn_t gfn,enum kvm_page_track_mode mode); + +void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, +int bytes); +void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot); + +static inline bool kvm_page_track_has_external_user (struct kvm *kvm) +{ +return hlist_empty (&kvm->arch.track_notifier_head.track_notifier_list); +} + +#endif /* __KVM_X86_PAGE_TRACK_H */
arch/x86/kvm/x86.c +1 -0
@@ -25,6 +25,7 @@#include "tss.h" #include "kvm_cache_regs.h" #include "kvm_emulate.h" +#include "mmu/page_track.h" #include "x86.h" #include "cpuid.h" #include "pmu.h"
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 19/27] KVM: x86/mmu: Move KVM-only page-track declarations to internal header
arch/x86/include/asm/kvm_page_track.h
Quoted 21 lines · Sean Christopherson
Bury the declaration of the page-track helpers that are intended only for internal KVM use in a "private" header. In addition to guarding against unwanted usage of the internal-only helpers, dropping their definitions avoids exposing other structures that should be KVM-internal, e.g. for memslots. This is a baby step toward making
kvm_host.ha KVM-internal header in the very distant future.Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_page_track.h | 26 ++++----------------- arch/x86/kvm/mmu/mmu.c | 3 ++- arch/x86/kvm/mmu/page_track.c | 8 +------ arch/x86/kvm/mmu/page_track.h | 33 +++++++++++++++++++++++++++ arch/x86/kvm/x86.c | 1 + 5 files changed, 42 insertions(+), 29 deletions(-) create mode 100644 arch/x86/kvm/mmu/page_track.harch/x86/include/asm/kvm_page_track.h +0
-0
A curious question:
are arch/x86/include/asm/kvm_*.h all expected to be external accessible?
Thanks
Yan
Sean Christopherson
maintainerRe: [PATCH v2 19/27] KVM: x86/mmu: Move KVM-only page-track declarations to internal header
Quoted 18 lines · Yan Zhao
Quoted 17 lines · Sean Christopherson
Bury the declaration of the page-track helpers that are intended only for internal KVM use in a "private" header. In addition to guarding against unwanted usage of the internal-only helpers, dropping their definitions avoids exposing other structures that should be KVM-internal, e.g. for memslots. This is a baby step toward making
kvm_host.ha KVM-internal header in the very distant future.Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_page_track.h | 26 ++++----------------- arch/x86/kvm/mmu/mmu.c | 3 ++- arch/x86/kvm/mmu/page_track.c | 8 +------ arch/x86/kvm/mmu/page_track.h | 33 +++++++++++++++++++++++++++ arch/x86/kvm/x86.c | 1 + 5 files changed, 42 insertions(+), 29 deletions(-) create mode 100644 arch/x86/kvm/mmu/page_track.h
Quoted 7 lines
arch/x86/include/asm/kvm_page_track.h
Quoted 4 lines
arch/x86/include/asm/kvm_page_track.h +0
-0A curious question:
arearch/x86/include/asm/kvm_*.hall expected to be external accessible?
Depends on what you mean by "expected". Currently, yes, everything in there is globally visible. But the vast majority of structs, defines, functions, etc. aren't intended for external non-KVM consumption, things ended up being globally visible largely through carelessness and/or a lack of a forcing function.
E.g. there is absolutely no reason anything outside of KVM should need arch/x86/include/asm/kvm-x86-ops.h, but it landed in asm/ because, at the time it was added, nothing would be harmed by making kvm-x86-ops.h "public" and we didn't scrutinize the patches well enough.
My primary motivation for this series is to (eventually) get to a state where only select symbols/defines/etc. are exposed by KVM to the outside world, and everything else is internal only. The end goal of tightly restricting KVM's global API is to allow concurrently loading multiple instances of kvm.ko so that userspace can upgrade/rollback KVM without needed to move VMs off the host, i.e. by performing intrahost migration between differenate instances of KVM on the same host. To do that safely, anything that is visible outside of KVM needs to be compatible across different instances of KVM, e.g. if kvm_vcpu is "public" then a KVM upgrade/rollback wouldn't be able to touch "struct kvm_vcpu" in any way. We'll definitely want to be able to modify things like the vCPU structures, thus the push to restrict the API.
But even if we never realize that end goal, IMO drastically reducing KVM's "public" API surface is worthy goal in and of itself.
Re: [PATCH v2 19/27] KVM: x86/mmu: Move KVM-only page-track declarations to internal header
Quoted 24 lines · Sean Christopherson
Quoted 2 lines
A curious question:
arearch/x86/include/asm/kvm_*.hall expected to be external accessible?Depends on what you mean by "expected". Currently, yes, everything in there is globally visible. But the vast majority of structs, defines, functions, etc. aren't intended for external non-KVM consumption, things ended up being globally visible largely through carelessness and/or a lack of a forcing function.
E.g. there is absolutely no reason anything outside of KVM should need
arch/x86/include/asm/kvm-x86-ops.h, but it landed in asm/ because, at the time it was added, nothing would be harmed by makingkvm-x86-ops.h"public" and we didn't scrutinize the patches well enough.My primary motivation for this series is to (eventually) get to a state where only select symbols/defines/etc. are exposed by KVM to the outside world, and everything else is internal only. The end goal of tightly restricting KVM's global API is to allow concurrently loading multiple instances of kvm.ko so that userspace can upgrade/rollback KVM without needed to move VMs off the host, i.e. by performing intrahost migration between differenate instances of KVM on the same host. To do that safely, anything that is visible outside of KVM needs to be compatible across different instances of KVM, e.g. if
kvm_vcpuis "public" then a KVM upgrade/rollback wouldn't be able to touch "structkvm_vcpu" in any way. We'll definitely want to be able to modify things like the vCPU structures, thus the push to restrict the API.
Quoted 2 lines
But even if we never realize that end goal, IMO drastically reducing KVM's "public" API surface is worthy goal in and of itself.
Got it. Thanks for explanation!
Sean Christopherson
maintainerPATCH v2 20/27 KVM: x86/mmu: Use page-track notifiers iff there are external users
In reply to Sean ChristophersonDisable the page-track notifier code at compile time if there are no external users, i.e. if CONFIG_KVM_EXTERNAL_WRITE_TRACKING=n. KVM itself now hooks emulated writes directly instead of relying on the page-track mechanism.
--- arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/include/asm/kvm_page_track.h | 2 ++ arch/x86/kvm/mmu/page_track.c | 9 ++++----- arch/x86/kvm/mmu/page_track.h | 29 +++++++++++++++++++++++---- 4 files changed, 33 insertions(+), 9 deletions(-)
arch/x86/include/asm/kvm_host.h +2 -0
@@ -1265,7 +1265,9 @@ struct kvm_arch {* create an NX huge page (without hanging the guest). */ struct list_head possible_nx_huge_pages; +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING struct kvm_page_track_notifier_head track_notifier_head; +#endif /* * Protects marking pages unsync during page faults, as TDP MMU page * faults only take mmu_lock for read. For simplicity, the unsync
arch/x86/include/asm/kvm_page_track.h +2 -0
@@ -55,6 +55,7 @@ void kvm_slot_page_track_remove_page(struct kvm *kvm, struct kvm_memory_slot *slot, gfn_t gfn, enum kvm_page_track_mode mode); +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn,enum pg_level max_level);
@@ -64,5 +65,6 @@ kvm_page_track_register_notifier(struct kvm *kvm,void kvm_page_track_unregister_notifier (struct kvm *kvm,struct kvm_page_track_notifier_node *n); +#endif /* CONFIG_KVM_EXTERNAL_WRITE_TRACKING */ #endif
arch/x86/kvm/mmu/page_track.c +4 -5
@@ -194,6 +194,7 @@ bool kvm_slot_page_track_is_active(struct kvm *kvm,return !!READ_ONCE (slot->arch.gfn_track[mode][index]); } +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING void kvm_page_track_cleanup (struct kvm *kvm) {struct kvm_page_track_notifier_head *head;
@@ -255,14 +256,13 @@ EXPORT_SYMBOL_GPL(kvm_page_track_unregister_notifier);* The node should figure out if the written page is the one that node is * interested in by itself. */ -void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes) +void __kvm_page_track_write (struct kvm *kvm,gpa_t gpa,const u8 *new,int bytes) {struct kvm_page_track_notifier_head *head;struct kvm_page_track_notifier_node *n;int idx; - head = &vcpu->kvm->arch.track_notifier_head; + head = &kvm->arch.track_notifier_head;if (hlist_empty (&head->track_notifier_list))return ;
@@ -273,8 +273,6 @@ void kvm_page_track_write(struct kvm_vcpu *vcpu, gpa_t gpa, const u8 *new,if (n->track_write) n->track_write (gpa, new, bytes, n);srcu_read_unlock (&head->track_srcu, idx); - -kvm_mmu_track_write (vcpu, gpa, new, bytes); }/*
@@ -317,3 +315,4 @@ enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, return max_level; }EXPORT_SYMBOL_GPL (kvm_page_track_max_mapping_level); +#endif
arch/x86/kvm/mmu/page_track.h +25 -4
@@ -6,8 +6,6 @@#include <asm/kvm_page_track.h> -int kvm_page_track_init (struct kvm *kvm); -void kvm_page_track_cleanup (struct kvm *kvm);bool kvm_page_track_write_tracking_enabled (struct kvm *kvm);int kvm_page_track_write_tracking_alloc (struct kvm_memory_slot *slot);
@@ -21,13 +19,36 @@ bool kvm_slot_page_track_is_active(struct kvm *kvm,const struct kvm_memory_slot *slot, gfn_t gfn, enum kvm_page_track_mode mode); -void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes); +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING +int kvm_page_track_init (struct kvm *kvm); +void kvm_page_track_cleanup (struct kvm *kvm); + +void __kvm_page_track_write (struct kvm *kvm,gpa_t gpa,const u8 *new,int bytes);void kvm_page_track_delete_slot (struct kvm *kvm,struct kvm_memory_slot *slot);static inline bool kvm_page_track_has_external_user (struct kvm *kvm) {return hlist_empty (&kvm->arch.track_notifier_head.track_notifier_list); } +#else +static inline int kvm_page_track_init (struct kvm *kvm) {return 0 ; } +static inline void kvm_page_track_cleanup (struct kvm *kvm) { } + +static inline void __kvm_page_track_write (struct kvm *kvm,gpa_t gpa, +const u8 *new,int bytes) { } +static inline void kvm_page_track_delete_slot (struct kvm *kvm, +struct kvm_memory_slot *slot) { } + +static inline bool kvm_page_track_has_external_user (struct kvm *kvm) {return false; } + +#endif /* CONFIG_KVM_EXTERNAL_WRITE_TRACKING */ + +static inline void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa, +const u8 *new,int bytes) +{ +__kvm_page_track_write (vcpu->kvm, gpa, new, bytes); + +kvm_mmu_track_write (vcpu, gpa, new, bytes); +}#endif /* __KVM_X86_PAGE_TRACK_H */
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 20/27] KVM: x86/mmu: Use page-track notifiers iff there are external users
Nit: there is a typo in the commit header: "iff" -> "if"
arch/x86/kvm/mmu/page_track.c EXPORT_SYMBOL_GPL(kvm_page_track_unregister_notifier); · line 259
Quoted 3 lines
arch/x86/kvm/mmu/page_track.c +1
-2-void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes) +void __kvm_page_track_write (struct kvm *kvm,gpa_t gpa,const u8 *new,int bytes)
Line length is 81 characters. A little longer than 80 :)
Quoted 1 line
+static inline bool
kvm_page_track_has_external_user(struct kvm *kvm){ return false; }
This line is also too long.
Sean Christopherson
maintainerRe: [PATCH v2 20/27] KVM: x86/mmu: Use page-track notifiers iff there are external users
Quoted 9 lines · Yan Zhao
Nit: there is a typo in the commit header: "iff" -> "if"
arch/x86/kvm/mmu/page_track.c EXPORT_SYMBOL_GPL(kvm_page_track_unregister_notifier); · line 259
Quoted 3 lines
arch/x86/kvm/mmu/page_track.c +1
-2-void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes) +void __kvm_page_track_write (struct kvm *kvm,gpa_t gpa,const u8 *new,int bytes)Line length is 81 characters. A little longer than 80 :)
Quoted 1 line
+static inline bool
kvm_page_track_has_external_user(struct kvm *kvm){ return false; }This line is also too long.
The 80 character limit is a "soft" limit these days, e.g. checkpatch only complains if a line is 100+. In KVM x86, the preferred style is to treat the 80 char limit as "firm", for lack of a better word. E.g. let a line run over if it's just a char or two and there's no other wrapping in the declaration, but don't create long lines just because checkpatch no longer yells.
There's obviously a fair bit of subjectivity, but the guideline has worked well so far (hopefully I didn't just jinx us).
Re: [PATCH v2 20/27] KVM: x86/mmu: Use page-track notifiers iff there are external users
Quoted 8 lines · Sean Christopherson
Quoted 7 lines · Yan Zhao
Nit: there is a typo in the commit header: "iff" -> "if"
arch/x86/kvm/mmu/page_track.c EXPORT_SYMBOL_GPL(kvm_page_track_unregister_notifier); · line 259
Quoted 3 lines
arch/x86/kvm/mmu/page_track.c +1
-2-void kvm_page_track_write (struct kvm_vcpu *vcpu,gpa_t gpa,const u8 *new, -int bytes) +void __kvm_page_track_write (struct kvm *kvm,gpa_t gpa,const u8 *new,int bytes)Line length is 81 characters. A little longer than 80 :)
Quoted 9 lines
Quoted 2 lines
Quoted 1 line
+static inline bool
kvm_page_track_has_external_user(struct kvm *kvm){ return false; }This line is also too long.
The 80 character limit is a "soft" limit these days, e.g. checkpatch only complains if a line is 100+. In KVM x86, the preferred style is to treat the 80 char limit as "firm", for lack of a better word. E.g. let a line run over if it's just a char or two and there's no other wrapping in the declaration, but don't create long lines just because checkpatch no longer yells.
Got it. It's helpful to me!
Quoted 2 lines
There's obviously a fair bit of subjectivity, but the guideline has worked well so far (hopefully I didn't just jinx us).
Re: [PATCH v2 20/27] KVM: x86/mmu: Use page-track notifiers iff there are external users
In reply to Sean Christophersonarch/x86/include/asm/kvm_page_track.h
Quoted 31 lines · Sean Christopherson
Disable the page-track notifier code at compile time if there are no external users, i.e. if
CONFIG_KVM_EXTERNAL_WRITE_TRACKING=n. KVM itself now hooks emulated writes directly instead of relying on the page-track mechanism.Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/include/asm/kvm_page_track.h | 2 ++ arch/x86/kvm/mmu/page_track.c | 9 ++++----- arch/x86/kvm/mmu/page_track.h | 29 +++++++++++++++++++++++---- 4 files changed, 33 insertions(+), 9 deletions(-)arch/x86/include/asm/kvm_host.h +2
-0@@ -1265,7 +1265,9 @@ struct kvm_arch {* create an NX huge page (without hanging the guest). */ struct list_head possible_nx_huge_pages; +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING struct kvm_page_track_notifier_head track_notifier_head; +#endif /* * Protects marking pages unsync during page faults, as TDP MMU page * faults only take mmu_lock for read. For simplicity, the unsync arch/x86/include/asm/kvm_page_track.h +0
-0
The "#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING" can be moved to the front of this file?
All the structures are only exposed for external users now.
Quoted 15 lines
arch/x86/include/asm/kvm_page_track.h +2
-0@@ -55,6 +55,7 @@ void kvm_slot_page_track_remove_page(struct kvm *kvm, struct kvm_memory_slot *slot, gfn_t gfn, enum kvm_page_track_mode mode); +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn,enum pg_level max_level);@@ -64,5 +65,6 @@ kvm_page_track_register_notifier(struct kvm *kvm,void kvm_page_track_unregister_notifier (struct kvm *kvm,struct kvm_page_track_notifier_node *n); +#endif /* CONFIG_KVM_EXTERNAL_WRITE_TRACKING */ #endif
Sean Christopherson
maintainerRe: [PATCH v2 20/27] KVM: x86/mmu: Use page-track notifiers iff there are external users
Quoted 27 lines · Yan Zhao
Quoted 26 lines · Sean Christopherson
Disable the page-track notifier code at compile time if there are no external users, i.e. if
CONFIG_KVM_EXTERNAL_WRITE_TRACKING=n. KVM itself now hooks emulated writes directly instead of relying on the page-track mechanism.Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/include/asm/kvm_page_track.h | 2 ++ arch/x86/kvm/mmu/page_track.c | 9 ++++----- arch/x86/kvm/mmu/page_track.h | 29 +++++++++++++++++++++++---- 4 files changed, 33 insertions(+), 9 deletions(-)arch/x86/include/asm/kvm_host.h +2
-0@@ -1265,7 +1265,9 @@ struct kvm_arch {* create an NX huge page (without hanging the guest). */ struct list_head possible_nx_huge_pages; +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING struct kvm_page_track_notifier_head track_notifier_head; +#endif /* * Protects marking pages unsync during page faults, as TDP MMU page
Quoted 8 lines
arch/x86/include/asm/kvm_page_track.h
Quoted 5 lines
arch/x86/include/asm/kvm_host.h +0
-0* faults only take mmu_lock for read. For simplicity, the unsync arch/x86/include/asm/kvm_page_track.h +0
-0The "#ifdef
CONFIG_KVM_EXTERNAL_WRITE_TRACKING" can be moved to the front of this file?
All the structures are only exposed for external users now.
Huh. I've no idea why I didn't do that. IIRC, the entire reason past me wrapped track_notifier_head in an #ifdef was to allow this change in kvm_page_track.h.
I'll do this in the next version unless I discover an edge case I'm overlooking.
Thanks yet again!
Sean Christopherson
maintainerRe: [PATCH v2 20/27] KVM: x86/mmu: Use page-track notifiers iff there are external users
Quoted 37 lines · Sean Christopherson
Quoted 27 lines · Yan Zhao
Quoted 26 lines · Sean Christopherson
Disable the page-track notifier code at compile time if there are no external users, i.e. if
CONFIG_KVM_EXTERNAL_WRITE_TRACKING=n. KVM itself now hooks emulated writes directly instead of relying on the page-track mechanism.Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/include/asm/kvm_page_track.h | 2 ++ arch/x86/kvm/mmu/page_track.c | 9 ++++----- arch/x86/kvm/mmu/page_track.h | 29 +++++++++++++++++++++++---- 4 files changed, 33 insertions(+), 9 deletions(-)arch/x86/include/asm/kvm_host.h +2
-0@@ -1265,7 +1265,9 @@ struct kvm_arch {* create an NX huge page (without hanging the guest). */ struct list_head possible_nx_huge_pages; +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING struct kvm_page_track_notifier_head track_notifier_head; +#endif /* * Protects marking pages unsync during page faults, as TDP MMU page Quoted 8 lines
arch/x86/include/asm/kvm_page_track.h
Quoted 5 lines
arch/x86/include/asm/kvm_host.h +0
-0* faults only take mmu_lock for read. For simplicity, the unsync arch/x86/include/asm/kvm_page_track.h +0
-0The "#ifdef
CONFIG_KVM_EXTERNAL_WRITE_TRACKING" can be moved to the front of this file?
All the structures are only exposed for external users now.
Quoted 4 lines
Huh. I've no idea why I didn't do that. IIRC, the entire reason past me wrapped
track_notifier_headin an #ifdef was to allow this change inkvm_page_track.h.I'll do this in the next version unless I discover an edge case I'm overlooking.
Ah, deja vu. I tried this first time around, and got yelled at by the kernel test robot. Unsuprisingly, my second attempt yielded the same result :-)
HDRTEST drivers/gpu/drm/i915/gvt/gvt.h
In file included from <command-line>:gpu/drivers/gpu/drm/i915/gvt/gvt.h:236:45: error: field ‘track_node’ has incomplete type
236 | struct kvm_page_track_notifier_node track_node;
| ^~~~~~~~~~
The problem is direct header inclusion. Nothing in the kernel includes gvt.h when CONFIG_DRM_I915_GVT=n, but the header include guard tests include headers directly on the command line. I think I'll define a "stub" specifically to play nice with this sort of testing. Guarding the guts of gvt.h with CONFIG_DRM_I915_GVT would just propagate the problem, and guarding the node definition in "struct intel_vgpu" would be confusing since the guard would be dead code for all intents and purposes.
The obvious alternative would be to leave kvm_page_track_notifier_node outside of the #ifdef, but I really want to bury kvm_page_track_notifier_head for KVM's sake, and having "head" buried but not "node" would also be weird and confusing.
arch/x86/include/asm/kvm_page_track.h +6 -0
@@ -51,6 +51,12 @@ void kvm_page_track_unregister_notifier(struct kvm *kvm,int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn);int kvm_write_track_remove_gfn (struct kvm *kvm,gfn_t gfn); +#else +/* +* Allow defining a node in a structure even if page tracking is disabled, e.g. +* to play nice with testing headers via direct inclusion from the command line. +*/ +struct kvm_page_track_notifier_node {};#endif /* CONFIG_KVM_EXTERNAL_WRITE_TRACKING */ #endif
Re: [PATCH v2 20/27] KVM: x86/mmu: Use page-track notifiers iff there are external users
Quoted 72 lines · Sean Christopherson
Quoted 37 lines · Sean Christopherson
Quoted 27 lines · Yan Zhao
Quoted 26 lines · Sean Christopherson
Disable the page-track notifier code at compile time if there are no external users, i.e. if
CONFIG_KVM_EXTERNAL_WRITE_TRACKING=n. KVM itself now hooks emulated writes directly instead of relying on the page-track mechanism.Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/include/asm/kvm_page_track.h | 2 ++ arch/x86/kvm/mmu/page_track.c | 9 ++++----- arch/x86/kvm/mmu/page_track.h | 29 +++++++++++++++++++++++---- 4 files changed, 33 insertions(+), 9 deletions(-)arch/x86/include/asm/kvm_host.h +2
-0@@ -1265,7 +1265,9 @@ struct kvm_arch {* create an NX huge page (without hanging the guest). */ struct list_head possible_nx_huge_pages; +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING struct kvm_page_track_notifier_head track_notifier_head; +#endif /* * Protects marking pages unsync during page faults, as TDP MMU page Quoted 8 lines
arch/x86/include/asm/kvm_page_track.h
Quoted 5 lines
arch/x86/include/asm/kvm_host.h +0
-0* faults only take mmu_lock for read. For simplicity, the unsync arch/x86/include/asm/kvm_page_track.h +0
-0The "#ifdef
CONFIG_KVM_EXTERNAL_WRITE_TRACKING" can be moved to the front of this file?
All the structures are only exposed for external users now.Quoted 4 lines
Huh. I've no idea why I didn't do that. IIRC, the entire reason past me wrapped
track_notifier_headin an #ifdef was to allow this change inkvm_page_track.h.I'll do this in the next version unless I discover an edge case I'm overlooking.
Ah, deja vu. I tried this first time around, and got yelled at by the kernel test robot. Unsuprisingly, my second attempt yielded the same result :-)
HDRTEST
drivers/gpu/drm/i915/gvt/gvt.h
In file included from <command-line>:gpu/drivers/gpu/drm/i915/gvt/gvt.h:236:45: error: field ‘track_node’ has incomplete type
236 | structkvm_page_track_notifier_nodetrack_node;
| ^~~~~~~~~~The problem is direct header inclusion. Nothing in the kernel includes
gvt.hwhenCONFIG_DRM_I915_GVT=n, but the header include guard tests include headers directly on the command line. I think I'll define a "stub" specifically to play nice with this sort of testing. Guarding the guts ofgvt.hwithCONFIG_DRM_I915_GVTwould just propagate the problem, and guarding the node definition in "structintel_vgpu" would be confusing since the guard would be dead code for all intents and purposes.The obvious alternative would be to leave
kvm_page_track_notifier_nodeoutside of the #ifdef, but I really want to burykvm_page_track_notifier_headfor KVM's sake, and having "head" buried but not "node" would also be weird and confusing.arch/x86/include/asm/kvm_page_track.h +0
-0@@ -51,6 +51,12 @@ void kvm_page_track_unregister_notifier(struct kvm *kvm,int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn);
arch/x86/include/asm/kvm_page_track.h void kvm_page_track_unregister_notifier(struct kvm *kvm, · line 62
Quoted 10 lines
arch/x86/include/asm/kvm_page_track.h +6
-0int kvm_write_track_remove_gfn (struct kvm *kvm,gfn_t gfn); +#else +/* +* Allow defining a node in a structure even if page tracking is disabled, e.g. +* to play nice with testing headers via direct inclusion from the command line. +*/ +struct kvm_page_track_notifier_node {};#endif /* CONFIG_KVM_EXTERNAL_WRITE_TRACKING */ #endif
Or check CONFIG_KVM_EXTERNAL_WRITE_TRACKING in gvt.h ? e.g.
drivers/gpu/drm/i915/gvt/gvt.h +2 -0
@@ -233,7 +233,9 @@ struct intel_vgpu {unsigned long nr_cache_entries;struct mutex cache_lock; +#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING struct kvm_page_track_notifier_node track_node; +#endif #define NR_BKT (1 << 18)struct hlist_head ptable[NR_BKT ];#undef NR_BKT
The justification is that gvt.h can be include without kvmgt, e.g. xengt previously.
But given currently there's no such case, I'm fine with both way :)
Sean Christopherson
maintainerPATCH v2 21/27 KVM: x86/mmu: Drop infrastructure for multiple page-track modes
In reply to Sean ChristophersonDrop "support" for multiple page-track modes, as there is no evidence that array-based and refcounted metadata is the optimal solution for other modes, nor is there any evidence that other use cases, e.g. for access-tracking, will be a good fit for the page-track machinery in general.
E.g. one potential use case of access-tracking would be to prevent guest access to poisoned memory (from the guest's perspective). In that case, the number of poisoned pages is likely to be a very small percentage of the guest memory, and there is no need to reference count the number of access-tracking users, i.e. expanding gfn_track[] for a new mode would be grossly inefficient. And for poisoned memory, host userspace would also likely want to trap accesses, e.g. to inject #MC into the guest, and that isn't currently supported by the page-track framework.
A better alternative for that poisoned page use case is likely a variation of the proposed per-gfn attributes overlay (linked), which would allow efficiently tracking the sparse set of poisoned pages, and by default would exit to userspace on access.
--- arch/x86/include/asm/kvm_host.h | 12 +-- arch/x86/include/asm/kvm_page_track.h | 11 +-- arch/x86/kvm/mmu/mmu.c | 14 ++-- arch/x86/kvm/mmu/page_track.c | 111 ++++++++------------------ arch/x86/kvm/mmu/page_track.h | 3 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 4 +- 6 files changed, 51 insertions(+), 104 deletions(-)
arch/x86/include/asm/kvm_host.h +6 -6
@@ -288,13 +288,13 @@ struct kvm_kernel_irq_routing_entry;* kvm_mmu_page_role tracks the properties of a shadow page (where shadow page * also includes TDP pages) to determine whether or not a page can be used in * the given MMU context. This is a subset of the overall kvm_cpu_role to -* minimize the size of kvm_memory_slot.arch.gfn_track, i.e. allows allocating -* 2 bytes per gfn instead of 4 bytes per gfn. +* minimize the size of kvm_memory_slot.arch.gfn_write_track, i.e. allows +* allocating 2 bytes per gfn instead of 4 bytes per gfn. * * Upper-level shadow pages having gptes are tracked for write-protection via -* gfn_track. As above, gfn_track is a 16 bit counter, so KVM must not create -* more than 2^16-1 upper-level shadow pages at a single gfn, otherwise -* gfn_track will overflow and explosions will ensure. +* gfn_write_track. As above, gfn_write_track is a 16 bit counter, so KVM must +* not create more than 2^16-1 upper-level shadow pages at a single gfn, +* otherwise gfn_write_track will overflow and explosions will ensue. * * A unique shadow page (SP) for a gfn is created if and only if an existing SP * cannot be reused. The ability to reuse a SP is tracked by its role, which
@@ -1023,7 +1023,7 @@ struct kvm_lpage_info {struct kvm_arch_memory_slot {struct kvm_rmap_head *rmap[KVM_NR_PAGE_SIZES ];struct kvm_lpage_info *lpage_info[KVM_NR_PAGE_SIZES -1 ]; -unsigned short *gfn_track[KVM_PAGE_TRACK_MAX ]; +unsigned short *gfn_write_track; };/*
arch/x86/include/asm/kvm_page_track.h +2 -9
@@ -4,11 +4,6 @@#include <linux/kvm_types.h> -enum kvm_page_track_mode { -KVM_PAGE_TRACK_WRITE , -KVM_PAGE_TRACK_MAX , -}; -/* * The notifier represented by @kvm_page_track_notifier_node is linked into * the head which will be notified when guest is triggering the track event.
@@ -49,11 +44,9 @@ struct kvm_page_track_notifier_node { };void kvm_slot_page_track_add_page (struct kvm *kvm, -struct kvm_memory_slot *slot,gfn_t gfn, -enum kvm_page_track_mode mode); +struct kvm_memory_slot *slot,gfn_t gfn);void kvm_slot_page_track_remove_page (struct kvm *kvm, -struct kvm_memory_slot *slot,gfn_t gfn, -enum kvm_page_track_mode mode); +struct kvm_memory_slot *slot,gfn_t gfn);#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn,
arch/x86/kvm/mmu/mmu.c +6 -8
@@ -820,8 +820,7 @@ static void account_shadowed(struct kvm *kvm, struct kvm_mmu_page *sp)/* the non-leaf shadow pages are keeping readonly. */ if (sp->role.level >PG_LEVEL_4K ) -return kvm_slot_page_track_add_page (kvm, slot, gfn, -KVM_PAGE_TRACK_WRITE ); +return kvm_slot_page_track_add_page (kvm, slot, gfn);kvm_mmu_gfn_disallow_lpage (slot, gfn);
@@ -867,8 +866,7 @@ static void unaccount_shadowed(struct kvm *kvm, struct kvm_mmu_page *sp) slots =kvm_memslots_for_spte_role (kvm, sp->role); slot =__gfn_to_memslot (slots, gfn);if (sp->role.level >PG_LEVEL_4K ) -return kvm_slot_page_track_remove_page (kvm, slot, gfn, -KVM_PAGE_TRACK_WRITE ); +return kvm_slot_page_track_remove_page (kvm, slot, gfn);kvm_mmu_gfn_allow_lpage (slot, gfn); }
@@ -2747,7 +2745,7 @@ int mmu_try_to_unsync_pages(struct kvm *kvm, const struct kvm_memory_slot *slot,* track machinery is used to write-protect upper-level shadow pages, * i.e. this guards the role.level == 4K assertion below! */ -if (kvm_slot_page_track_is_active (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE )) +if (kvm_slot_page_track_is_active (kvm, slot, gfn))return -EPERM ;/*
@@ -4155,7 +4153,7 @@ static bool page_fault_handle_page_track(struct kvm_vcpu *vcpu,* guest is writing the page which is write tracked which can * not be fixed by page fault handler. */ -if (kvm_slot_page_track_is_active (vcpu->kvm, fault->slot, fault->gfn,KVM_PAGE_TRACK_WRITE )) +if (kvm_slot_page_track_is_active (vcpu->kvm, fault->slot, fault->gfn))return true;return false;
@@ -5387,8 +5385,8 @@ void kvm_mmu_after_set_cpuid(struct kvm_vcpu *vcpu)* physical address properties) in a single VM would require tracking * all relevant CPUID information in kvm_mmu_page_role. That is very * undesirable as it would increase the memory requirements for -* gfn_track (see struct kvm_mmu_page_role comments). For now that -* problem is swept under the rug; KVM's CPUID API is horrific and +* gfn_write_track (see struct kvm_mmu_page_role comments). For now +* that problem is swept under the rug; KVM's CPUID API is horrific and * it's all but impossible to solve it without introducing a new API. */ vcpu->arch.root_mmu.root_role.word =0 ;
arch/x86/kvm/mmu/page_track.c +34 -77
182 lines not on this page · raw message
arch/x86/kvm/mmu/page_track.h +1 -2
@@ -16,8 +16,7 @@ int kvm_page_track_create_memslot(struct kvm *kvm, unsigned long npages);bool kvm_slot_page_track_is_active (struct kvm *kvm, -const struct kvm_memory_slot *slot, -gfn_t gfn,enum kvm_page_track_mode mode); +const struct kvm_memory_slot *slot,gfn_t gfn);#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING int kvm_page_track_init (struct kvm *kvm);
drivers/gpu/drm/i915/gvt/kvmgt.c +2 -2
@@ -1578,7 +1578,7 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn) }write_lock (&kvm->mmu_lock); -kvm_slot_page_track_add_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +kvm_slot_page_track_add_page (kvm, slot, gfn);write_unlock (&kvm->mmu_lock);srcu_read_unlock (&kvm->srcu, idx);
@@ -1607,7 +1607,7 @@ int intel_gvt_page_track_remove(struct intel_vgpu *info, u64 gfn) }write_lock (&kvm->mmu_lock); -kvm_slot_page_track_remove_page (kvm, slot, gfn,KVM_PAGE_TRACK_WRITE ); +kvm_slot_page_track_remove_page (kvm, slot, gfn);write_unlock (&kvm->mmu_lock);srcu_read_unlock (&kvm->srcu, idx);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 22/27 KVM: x86/mmu: Rename page-track APIs to reflect the new reality
In reply to Sean ChristophersonRename the page-track APIs to capture that they're all about tracking writes, now that the facade of supporting multiple modes is gone.
Opportunstically replace "slot" with "gfn" in anticipation of removing the @slot param from the external APIs.
No functional change intended.
--- arch/x86/include/asm/kvm_page_track.h | 8 ++++---- arch/x86/kvm/mmu/mmu.c | 8 ++++---- arch/x86/kvm/mmu/page_track.c | 21 +++++++++------------ arch/x86/kvm/mmu/page_track.h | 4 ++-- drivers/gpu/drm/i915/gvt/kvmgt.c | 4 ++-- 5 files changed, 21 insertions(+), 24 deletions(-)
arch/x86/include/asm/kvm_page_track.h +4 -4
@@ -43,10 +43,10 @@ struct kvm_page_track_notifier_node { struct kvm_page_track_notifier_node *node); }; -void kvm_slot_page_track_add_page (struct kvm *kvm, -struct kvm_memory_slot *slot,gfn_t gfn); -void kvm_slot_page_track_remove_page (struct kvm *kvm, -struct kvm_memory_slot *slot,gfn_t gfn); +void kvm_write_track_add_gfn (struct kvm *kvm, +struct kvm_memory_slot *slot,gfn_t gfn); +void kvm_write_track_remove_gfn (struct kvm *kvm,struct kvm_memory_slot *slot, +gfn_t gfn);#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn,
arch/x86/kvm/mmu/mmu.c +4 -4
@@ -820,7 +820,7 @@ static void account_shadowed(struct kvm *kvm, struct kvm_mmu_page *sp)/* the non-leaf shadow pages are keeping readonly. */ if (sp->role.level >PG_LEVEL_4K ) -return kvm_slot_page_track_add_page (kvm, slot, gfn); +return kvm_write_track_add_gfn (kvm, slot, gfn);kvm_mmu_gfn_disallow_lpage (slot, gfn);
@@ -866,7 +866,7 @@ static void unaccount_shadowed(struct kvm *kvm, struct kvm_mmu_page *sp) slots =kvm_memslots_for_spte_role (kvm, sp->role); slot =__gfn_to_memslot (slots, gfn);if (sp->role.level >PG_LEVEL_4K ) -return kvm_slot_page_track_remove_page (kvm, slot, gfn); +return kvm_write_track_remove_gfn (kvm, slot, gfn);kvm_mmu_gfn_allow_lpage (slot, gfn); }
@@ -2745,7 +2745,7 @@ int mmu_try_to_unsync_pages(struct kvm *kvm, const struct kvm_memory_slot *slot,* track machinery is used to write-protect upper-level shadow pages, * i.e. this guards the role.level == 4K assertion below! */ -if (kvm_slot_page_track_is_active (kvm, slot, gfn)) +if (kvm_gfn_is_write_tracked (kvm, slot, gfn))return -EPERM ;/*
@@ -4153,7 +4153,7 @@ static bool page_fault_handle_page_track(struct kvm_vcpu *vcpu,* guest is writing the page which is write tracked which can * not be fixed by page fault handler. */ -if (kvm_slot_page_track_is_active (vcpu->kvm, fault->slot, fault->gfn)) +if (kvm_gfn_is_write_tracked (vcpu->kvm, fault->slot, fault->gfn))return true;return false;
arch/x86/kvm/mmu/page_track.c +9 -12
@@ -84,10 +84,9 @@ static void update_gfn_write_track(struct kvm_memory_slot *slot, gfn_t gfn,* @slot: the @gfn belongs to. * @gfn: the guest page. */ -void kvm_slot_page_track_add_page (struct kvm *kvm, -struct kvm_memory_slot *slot,gfn_t gfn) +void kvm_write_track_add_gfn (struct kvm *kvm,struct kvm_memory_slot *slot, +gfn_t gfn) { -if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm)))return ;
@@ -102,12 +101,11 @@ void kvm_slot_page_track_add_page(struct kvm *kvm,if (kvm_mmu_slot_gfn_write_protect (kvm, slot, gfn,PG_LEVEL_4K ))kvm_flush_remote_tlbs (kvm); } -EXPORT_SYMBOL_GPL (kvm_slot_page_track_add_page); +EXPORT_SYMBOL_GPL (kvm_write_track_add_gfn);/* * remove the guest page from the tracking pool which stops the interception -* of corresponding access on that page. It is the opposed operation of -* kvm_slot_page_track_add_page(). +* of corresponding access on that page. * * It should be called under the protection both of mmu-lock and kvm->srcu * or kvm->slots_lock.
@@ -116,8 +114,8 @@ EXPORT_SYMBOL_GPL(kvm_slot_page_track_add_page);* @slot: the @gfn belongs to. * @gfn: the guest page. */ -void kvm_slot_page_track_remove_page (struct kvm *kvm, -struct kvm_memory_slot *slot,gfn_t gfn) +void kvm_write_track_remove_gfn (struct kvm *kvm, +struct kvm_memory_slot *slot,gfn_t gfn) {if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm)))return ;
@@ -130,14 +128,13 @@ void kvm_slot_page_track_remove_page(struct kvm *kvm,*/ kvm_mmu_gfn_allow_lpage (slot, gfn); } -EXPORT_SYMBOL_GPL (kvm_slot_page_track_remove_page); +EXPORT_SYMBOL_GPL (kvm_write_track_remove_gfn);/* * check if the corresponding access on the specified guest page is tracked. */ -bool kvm_slot_page_track_is_active (struct kvm *kvm, -const struct kvm_memory_slot *slot, -gfn_t gfn) +bool kvm_gfn_is_write_tracked (struct kvm *kvm, +const struct kvm_memory_slot *slot,gfn_t gfn) {int index;
arch/x86/kvm/mmu/page_track.h +2 -2
@@ -15,8 +15,8 @@ int kvm_page_track_create_memslot(struct kvm *kvm,struct kvm_memory_slot *slot, unsigned long npages); -bool kvm_slot_page_track_is_active (struct kvm *kvm, -const struct kvm_memory_slot *slot,gfn_t gfn); +bool kvm_gfn_is_write_tracked (struct kvm *kvm, +const struct kvm_memory_slot *slot,gfn_t gfn);#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING int kvm_page_track_init (struct kvm *kvm);
drivers/gpu/drm/i915/gvt/kvmgt.c +2 -2
@@ -1578,7 +1578,7 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn) }write_lock (&kvm->mmu_lock); -kvm_slot_page_track_add_page (kvm, slot, gfn); +kvm_write_track_add_gfn (kvm, slot, gfn);write_unlock (&kvm->mmu_lock);srcu_read_unlock (&kvm->srcu, idx);
@@ -1607,7 +1607,7 @@ int intel_gvt_page_track_remove(struct intel_vgpu *info, u64 gfn) }write_lock (&kvm->mmu_lock); -kvm_slot_page_track_remove_page (kvm, slot, gfn); +kvm_write_track_remove_gfn (kvm, slot, gfn);write_unlock (&kvm->mmu_lock);srcu_read_unlock (&kvm->srcu, idx);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 23/27 KVM: x86/mmu: Assert that correct locks are held for page write-tracking
In reply to Sean ChristophersonWhen adding/removing gfns to/from write-tracking, assert that mmu_lock is held for write, and that either slots_lock or kvm->srcu is held. mmu_lock must be held for write to protect gfn_write_track's refcount, and SRCU or slots_lock must be held to protect the memslot itself.
--- arch/x86/kvm/mmu/page_track.c | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-)
arch/x86/kvm/mmu/page_track.c +11 -6
@@ -12,6 +12,7 @@*/ #define pr_fmt (fmt) KBUILD_MODNAME ": " fmt +#include <linux/lockdep.h> #include <linux/kvm_host.h> #include <linux/rculist.h>
@@ -77,9 +78,6 @@ static void update_gfn_write_track(struct kvm_memory_slot *slot, gfn_t gfn,* add guest page to the tracking pool so that corresponding access on that * page will be intercepted. * -* It should be called under the protection both of mmu-lock and kvm->srcu -* or kvm->slots_lock. -* * @kvm: the guest instance we are interested in. * @slot: the @gfn belongs to. * @gfn: the guest page.
@@ -87,6 +85,11 @@ static void update_gfn_write_track(struct kvm_memory_slot *slot, gfn_t gfn,void kvm_write_track_add_gfn (struct kvm *kvm,struct kvm_memory_slot *slot,gfn_t gfn) { +lockdep_assert_held_write (&kvm->mmu_lock); + +lockdep_assert_once (lockdep_is_held (&kvm->slots_lock) || +srcu_read_lock_held (&kvm->srcu)); +if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm)))return ;
@@ -107,9 +110,6 @@ EXPORT_SYMBOL_GPL(kvm_write_track_add_gfn);* remove the guest page from the tracking pool which stops the interception * of corresponding access on that page. * -* It should be called under the protection both of mmu-lock and kvm->srcu -* or kvm->slots_lock. -* * @kvm: the guest instance we are interested in. * @slot: the @gfn belongs to. * @gfn: the guest page.
@@ -117,6 +117,11 @@ EXPORT_SYMBOL_GPL(kvm_write_track_add_gfn);void kvm_write_track_remove_gfn (struct kvm *kvm,struct kvm_memory_slot *slot,gfn_t gfn) { +lockdep_assert_held_write (&kvm->mmu_lock); + +lockdep_assert_once (lockdep_is_held (&kvm->slots_lock) || +srcu_read_lock_held (&kvm->srcu)); +if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm)))return ;
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 23/27] KVM: x86/mmu: Assert that correct locks are held for page write-tracking
Quoted 69 lines · Sean Christopherson
When adding/removing gfns to/from write-tracking, assert that
mmu_lockis held for write, and that eitherslots_lockorkvm->srcuis held.mmu_lockmust be held for write to protect gfn_write_track's refcount, and SRCU orslots_lockmust be held to protect the memslot itself.Signed-off-by Sean Christopherson <[email protected]>--- arch/x86/kvm/mmu/page_track.c | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-)arch/x86/kvm/mmu/page_track.c +11
-6@@ -12,6 +12,7 @@*/ #define pr_fmt (fmt) KBUILD_MODNAME ": " fmt +#include <linux/lockdep.h> #include <linux/kvm_host.h> #include <linux/rculist.h> @@ -77,9 +78,6 @@ static void update_gfn_write_track(struct kvm_memory_slot *slot, gfn_t gfn,* add guest page to the tracking pool so that corresponding access on that * page will be intercepted. * -* It should be called under the protection both of mmu-lock and kvm->srcu -* or kvm->slots_lock. -* * @kvm: the guest instance we are interested in. * @slot: the @gfn belongs to. * @gfn: the guest page. @@ -87,6 +85,11 @@ static void update_gfn_write_track(struct kvm_memory_slot *slot, gfn_t gfn,void kvm_write_track_add_gfn (struct kvm *kvm,struct kvm_memory_slot *slot,gfn_t gfn) { +lockdep_assert_held_write (&kvm->mmu_lock); + +lockdep_assert_once (lockdep_is_held (&kvm->slots_lock) || +srcu_read_lock_held (&kvm->srcu)); +if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm)))return ;@@ -107,9 +110,6 @@ EXPORT_SYMBOL_GPL(kvm_write_track_add_gfn);* remove the guest page from the tracking pool which stops the interception * of corresponding access on that page. * -* It should be called under the protection both of mmu-lock and kvm->srcu -* or kvm->slots_lock. -* * @kvm: the guest instance we are interested in. * @slot: the @gfn belongs to. * @gfn: the guest page. @@ -117,6 +117,11 @@ EXPORT_SYMBOL_GPL(kvm_write_track_add_gfn);void kvm_write_track_remove_gfn (struct kvm *kvm,struct kvm_memory_slot *slot,gfn_t gfn) { +lockdep_assert_held_write (&kvm->mmu_lock); + +lockdep_assert_once (lockdep_is_held (&kvm->slots_lock) || +srcu_read_lock_held (&kvm->srcu)); +if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm)))return ;Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 24/27 KVM: x86/mmu: Bug the VM if write-tracking is used but not enabled
In reply to Sean ChristophersonBug the VM if something attempts to write-track a gfn, but write-tracking isn't enabled. The VM is doomed (and KVM has an egregious bug) if KVM or KVMGT wants to shadow guest page tables but can't because write-tracking isn't enabled.
--- arch/x86/kvm/mmu/page_track.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/x86/kvm/mmu/page_track.c +2 -2
@@ -90,7 +90,7 @@ void kvm_write_track_add_gfn(struct kvm *kvm, struct kvm_memory_slot *slot,lockdep_assert_once (lockdep_is_held (&kvm->slots_lock) ||srcu_read_lock_held (&kvm->srcu)); -if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm))) +if (KVM_BUG_ON (!kvm_page_track_write_tracking_enabled (kvm), kvm))return ;update_gfn_write_track (slot, gfn,1 );
@@ -122,7 +122,7 @@ void kvm_write_track_remove_gfn(struct kvm *kvm,lockdep_assert_once (lockdep_is_held (&kvm->slots_lock) ||srcu_read_lock_held (&kvm->srcu)); -if (WARN_ON (!kvm_page_track_write_tracking_enabled (kvm))) +if (KVM_BUG_ON (!kvm_page_track_write_tracking_enabled (kvm), kvm))return ;update_gfn_write_track (slot, gfn,-1 );
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Sean Christopherson
maintainerPATCH v2 25/27 KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
In reply to Sean ChristophersonRefactor KVM's exported/external page-track, a.k.a. write-track, APIs to take only the gfn and do the required memslot lookup in KVM proper. Forcing users of the APIs to get the memslot unnecessarily bleeds KVM internals into KVMGT and complicates usage of the APIs.
No functional change intended.
--- arch/x86/include/asm/kvm_page_track.h | 8 +-- arch/x86/kvm/mmu/mmu.c | 4 +- arch/x86/kvm/mmu/page_track.c | 86 ++++++++++++++++++++------- arch/x86/kvm/mmu/page_track.h | 5 ++ drivers/gpu/drm/i915/gvt/kvmgt.c | 37 +++--------- 5 files changed, 82 insertions(+), 58 deletions(-)
arch/x86/include/asm/kvm_page_track.h +3 -5
@@ -43,11 +43,6 @@ struct kvm_page_track_notifier_node { struct kvm_page_track_notifier_node *node); }; -void kvm_write_track_add_gfn (struct kvm *kvm, -struct kvm_memory_slot *slot,gfn_t gfn); -void kvm_write_track_remove_gfn (struct kvm *kvm,struct kvm_memory_slot *slot, -gfn_t gfn); -#ifdef CONFIG_KVM_EXTERNAL_WRITE_TRACKING enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn,enum pg_level max_level);
@@ -58,6 +53,9 @@ kvm_page_track_register_notifier(struct kvm *kvm,void kvm_page_track_unregister_notifier (struct kvm *kvm,struct kvm_page_track_notifier_node *n); + +int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn); +int kvm_write_track_remove_gfn (struct kvm *kvm,gfn_t gfn);#endif /* CONFIG_KVM_EXTERNAL_WRITE_TRACKING */ #endif
arch/x86/kvm/mmu/mmu.c +2 -2
@@ -820,7 +820,7 @@ static void account_shadowed(struct kvm *kvm, struct kvm_mmu_page *sp)/* the non-leaf shadow pages are keeping readonly. */ if (sp->role.level >PG_LEVEL_4K ) -return kvm_write_track_add_gfn (kvm, slot, gfn); +return __kvm_write_track_add_gfn (kvm, slot, gfn);kvm_mmu_gfn_disallow_lpage (slot, gfn);
@@ -866,7 +866,7 @@ static void unaccount_shadowed(struct kvm *kvm, struct kvm_mmu_page *sp) slots =kvm_memslots_for_spte_role (kvm, sp->role); slot =__gfn_to_memslot (slots, gfn);if (sp->role.level >PG_LEVEL_4K ) -return kvm_write_track_remove_gfn (kvm, slot, gfn); +return __kvm_write_track_remove_gfn (kvm, slot, gfn);kvm_mmu_gfn_allow_lpage (slot, gfn); }
arch/x86/kvm/mmu/page_track.c +64 -22
109 lines not on this page · raw message
arch/x86/kvm/mmu/page_track.h +5 -0
@@ -15,6 +15,11 @@ int kvm_page_track_create_memslot(struct kvm *kvm,struct kvm_memory_slot *slot, unsigned long npages); +void __kvm_write_track_add_gfn (struct kvm *kvm,struct kvm_memory_slot *slot, +gfn_t gfn); +void __kvm_write_track_remove_gfn (struct kvm *kvm, +struct kvm_memory_slot *slot,gfn_t gfn); +bool kvm_gfn_is_write_tracked (struct kvm *kvm,const struct kvm_memory_slot *slot,gfn_t gfn);
drivers/gpu/drm/i915/gvt/kvmgt.c +8 -29
@@ -1560,9 +1560,7 @@ static struct mdev_driver intel_vgpu_mdev_driver = {int intel_gvt_page_track_add (struct intel_vgpu *info,u64 gfn) { -struct kvm *kvm = info->vfio_device.kvm; -struct kvm_memory_slot *slot; -int idx; +int r;if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , info->status))return -ESRCH ;
@@ -1570,18 +1568,9 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn)if (kvmgt_gfn_is_write_protected (info, gfn))return 0 ; - idx =srcu_read_lock (&kvm->srcu); - slot =gfn_to_memslot (kvm, gfn); -if (!slot) { -srcu_read_unlock (&kvm->srcu, idx); -return -EINVAL ; - } - -write_lock (&kvm->mmu_lock); -kvm_write_track_add_gfn (kvm, slot, gfn); -write_unlock (&kvm->mmu_lock); - -srcu_read_unlock (&kvm->srcu, idx); + r =kvm_write_track_add_gfn (info->vfio_device.kvm, gfn); +if (r) +return r;kvmgt_protect_table_add (info, gfn);return 0 ;
@@ -1589,9 +1578,7 @@ int intel_gvt_page_track_add(struct intel_vgpu *info, u64 gfn)int intel_gvt_page_track_remove (struct intel_vgpu *info,u64 gfn) { -struct kvm *kvm = info->vfio_device.kvm; -struct kvm_memory_slot *slot; -int idx; +int r;if (!test_bit (INTEL_VGPU_STATUS_ATTACHED , info->status))return -ESRCH ;
@@ -1599,17 +1586,9 @@ int intel_gvt_page_track_remove(struct intel_vgpu *info, u64 gfn)if (!kvmgt_gfn_is_write_protected (info, gfn))return 0 ; - idx =srcu_read_lock (&kvm->srcu); - slot =gfn_to_memslot (kvm, gfn); -if (!slot) { -srcu_read_unlock (&kvm->srcu, idx); -return -EINVAL ; - } - -write_lock (&kvm->mmu_lock); -kvm_write_track_remove_gfn (kvm, slot, gfn); -write_unlock (&kvm->mmu_lock); -srcu_read_unlock (&kvm->srcu, idx); + r =kvm_write_track_remove_gfn (info->vfio_device.kvm, gfn); +if (r) +return r;kvmgt_protect_table_del (info, gfn);return 0 ;
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 25/27] KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
On Fri, Mar 10, 2023 at 04:22:56PM -0800, Sean Christopherson wrote:
...
arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 279
Quoted 13 lines
arch/x86/kvm/mmu/page_track.c +13
-0+int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) { +srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +
Also fail if slot->flags & KVM_MEMSLOT_INVALID is true?
There should exist a window for external users to see an invalid slot when a slot is about to get deleted/moved.
(It happens before MOVE is rejected in kvm_arch_prepare_memory_region()).
Quoted 20 lines
arch/x86/kvm/mmu/page_track.c +20
-0+write_lock (&kvm->mmu_lock); +__kvm_write_track_add_gfn (kvm, slot, gfn); +write_unlock (&kvm->mmu_lock); + +srcu_read_unlock (&kvm->srcu, idx); + +return 0 ; +} +EXPORT_SYMBOL_GPL (kvm_write_track_add_gfn); + +/* +* remove the guest page from the tracking pool which stops the interception +* of corresponding access on that page. +* +* @kvm: the guest instance we are interested in. +* @gfn: the guest page. +*/ +int kvm_write_track_remove_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot;
arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 309
Quoted 10 lines
arch/x86/kvm/mmu/page_track.c +10
-0+int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) { +srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +
Ditto.
Quoted 9 lines
arch/x86/kvm/mmu/page_track.c +9
-0+write_lock (&kvm->mmu_lock); +__kvm_write_track_remove_gfn (kvm, slot, gfn); +write_unlock (&kvm->mmu_lock); + +srcu_read_unlock (&kvm->srcu, idx); + +return 0 ; +} +EXPORT_SYMBOL_GPL (kvm_write_track_remove_gfn);
Re: [PATCH v2 25/27] KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
Quoted 11 lines · Yan Zhao
On Fri, Mar 10, 2023 at 04:22:56PM -0800, Sean Christopherson wrote:
...Quoted 9 lines
arch/x86/kvm/mmu/page_track.c +9
-0+int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) {
Quoted 8 lines
arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 279
Quoted 4 lines
arch/x86/kvm/mmu/page_track.c +4
-0+srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +Also fail if
slot->flags&KVM_MEMSLOT_INVALIDis true?
There should exist a window for external users to see an invalid slot when a slot is about to get deleted/moved.
(It happens before MOVE is rejected inkvm_arch_prepare_memory_region()).
Or using
if (!kvm_is_visible_memslot(slot)) {
srcu_read_unlock(&kvm->srcu, idx);
return -EINVAL;
}Quoted 43 lines
Quoted 21 lines
arch/x86/kvm/mmu/page_track.c +20
-0+write_lock (&kvm->mmu_lock); +__kvm_write_track_add_gfn (kvm, slot, gfn); +write_unlock (&kvm->mmu_lock); + +srcu_read_unlock (&kvm->srcu, idx); + +return 0 ; +} +EXPORT_SYMBOL_GPL (kvm_write_track_add_gfn); + +/* +* remove the guest page from the tracking pool which stops the interception +* of corresponding access on that page. +* +* @kvm: the guest instance we are interested in. +* @gfn: the guest page. +*/ +int kvm_write_track_remove_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot;arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 309
Quoted 10 lines
arch/x86/kvm/mmu/page_track.c +10
-0+int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) { +srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +Ditto.
Quoted 9 lines
arch/x86/kvm/mmu/page_track.c +9
-0+write_lock (&kvm->mmu_lock); +__kvm_write_track_remove_gfn (kvm, slot, gfn); +write_unlock (&kvm->mmu_lock); + +srcu_read_unlock (&kvm->srcu, idx); + +return 0 ; +} +EXPORT_SYMBOL_GPL (kvm_write_track_remove_gfn);
Sean Christopherson
maintainerRe: [PATCH v2 25/27] KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
Finally getting back to this series...
Quoted 21 lines · Yan Zhao
Quoted 11 lines · Yan Zhao
On Fri, Mar 10, 2023 at 04:22:56PM -0800, Sean Christopherson wrote:
...Quoted 9 lines
arch/x86/kvm/mmu/page_track.c +9
-0+int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) {Quoted 8 lines
arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 279
Quoted 4 lines
arch/x86/kvm/mmu/page_track.c +4
-0+srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +Also fail if
slot->flags&KVM_MEMSLOT_INVALIDis true?
There should exist a window for external users to see an invalid slot when a slot is about to get deleted/moved.
(It happens before MOVE is rejected inkvm_arch_prepare_memory_region()).
Quoted 5 lines
Or using
if (!kvm_is_visible_memslot(slot)) { srcu_read_unlock(&kvm->srcu, idx); return -EINVAL; }
Hrm. If the DELETE/MOVE succeeds, then the funky accounting is ok (by the end of the series) as the tracking disappears on DELETE, KVMGT will reject MOVE, and KVM proper zaps SPTEs and resets accounting on MOVE (account_shadowed() runs under mmu_lock and thus ensures all previous SPTEs are zapped before the "flush" from kvm_arch_flush_shadow_memslot() can run).
If kvm_prepare_memory_region() fails though...
Ah, KVM itself is safe because of the aforementioned kvm_arch_flush_shadow_memslot(). Any accounting done on a temporarily invalid memslot will be unwound when the SPTEs are zapped. So for KVM, ignoring invalid memslots is correct _and necessary_. We could clean that up by having accounted_shadowed() use the @slot from the fault, which would close the window where the fault starts with a valid memslot but then sees an invalid memslot when accounting a new shadow page. But I don't think there is a bug there.
Right, and DELETE can't actually fail in the current code base, and we've established that MOVE can't possibly work. So even if this is problematic in theory, there are no _unknown_ bugs, and the known bugs are fixed by the end of the series.
And at the end of the series, KVMGT drops its tracking only when the DELETE is committed. So I _think_ allowing external trackers to add and remove gfns for write-tracking in an invalid slot is actually desirable/correct. I'm pretty sure removal should be allowed as that can lead to dangling write-protection in a
rollback scenario. And I can't think of anything that will break (in the kernel)
if write-tracking a gfn in an invalid slot is allowed, so I don't see any harm in allowing the extremely theoretical case of KVMGT shadowing a gfn in a to-be-deleted memslot _and_ the deletion being rolled back.
Re: [PATCH v2 25/27] KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
Quoted 50 lines · Sean Christopherson
Finally getting back to this series...
Quoted 21 lines · Yan Zhao
Quoted 11 lines · Yan Zhao
On Fri, Mar 10, 2023 at 04:22:56PM -0800, Sean Christopherson wrote:
...Quoted 9 lines
arch/x86/kvm/mmu/page_track.c +9
-0+int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) {Quoted 8 lines
arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 279
Quoted 4 lines
arch/x86/kvm/mmu/page_track.c +4
-0+srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +Also fail if
slot->flags&KVM_MEMSLOT_INVALIDis true?
There should exist a window for external users to see an invalid slot when a slot is about to get deleted/moved.
(It happens before MOVE is rejected inkvm_arch_prepare_memory_region()).Quoted 5 lines
Or using
if (!kvm_is_visible_memslot(slot)) { srcu_read_unlock(&kvm->srcu, idx); return -EINVAL; }Hrm. If the DELETE/MOVE succeeds, then the funky accounting is ok (by the end of the series) as the tracking disappears on DELETE, KVMGT will reject MOVE, and KVM proper zaps SPTEs and resets accounting on MOVE (
account_shadowed()runs undermmu_lockand thus ensures all previous SPTEs are zapped before the "flush" fromkvm_arch_flush_shadow_memslot()can run).If
kvm_prepare_memory_region()fails though...Ah, KVM itself is safe because of the aforementioned
kvm_arch_flush_shadow_memslot(). Any accounting done on a temporarily invalid memslot will be unwound when the SPTEs are zapped. So for KVM, ignoring invalid memslots is correct_andnecessary_. We could clean that up by havingaccounted_shadowed()use the @slot from the fault, which would close the window where the fault starts with a valid memslot but then sees an invalid memslot when accounting a new shadow page. But I don't think there is a bug there.Right, and DELETE can't actually fail in the current code base, and we've established that MOVE can't possibly work. So even if this is problematic in theory, there are no _unknown_ bugs, and the known bugs are fixed by the end of the series.
Quoted 8 lines
And at the end of the series, KVMGT drops its tracking only when the DELETE is committed. So I _think_ allowing external trackers to add and remove gfns for write-tracking in an invalid slot is actually desirable/correct. I'm pretty sure removal should be allowed as that can lead to dangling write-protection in a
rollback scenario. And I can't think of anything that will break (in the kernel)
if write-tracking a gfn in an invalid slot is allowed, so I don't see any harm in allowing the extremely theoretical case of KVMGT shadowing a gfn in a to-be-deleted memslot _and_ the deletion being rolled back.
Yes, you are right!
I previously thought thatinvalid_slot->arch.gfn_write_track and old->arch.gfn_write_track are pointing to different places. But I'm wrong.
Yes, allowing INVALID slot here is more desired for deletion rolling-back.
Re: [PATCH v2 25/27] KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
Quoted 25 lines · Yan Zhao
Quoted 24 lines · Sean Christopherson
Finally getting back to this series...
Quoted 21 lines · Yan Zhao
Quoted 19 lines · Yan Zhao
On Fri, Mar 10, 2023 at 04:22:56PM -0800, Sean Christopherson wrote:
...arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 279
Quoted 13 lines
arch/x86/kvm/mmu/page_track.c +13
-0+int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) { +srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +Also fail if
slot->flags&KVM_MEMSLOT_INVALIDis true?
There should exist a window for external users to see an invalid slot when a slot is about to get deleted/moved.
(It happens before MOVE is rejected inkvm_arch_prepare_memory_region()).
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Or using
if (!kvm_is_visible_memslot(slot)) { srcu_read_unlock(&kvm->srcu, idx); return -EINVAL; }
Hi Sean,
After more thoughts, do you think checking KVM internal memslot is necessary?
slot = gfn_to_memslot(kvm, gfn);
if (!slot || slot->id >= KVM_USER_MEM_SLOTS) {
srcu_read_unlock(&kvm->srcu, idx);
return -EINVAL;
}Do we allow write tracking to APIC access page when APIC-write VM exit is not desired?
Thanks
Yan
Quoted 34 lines
Quoted 20 lines
Hrm. If the DELETE/MOVE succeeds, then the funky accounting is ok (by the end of the series) as the tracking disappears on DELETE, KVMGT will reject MOVE, and KVM proper zaps SPTEs and resets accounting on MOVE (
account_shadowed()runs undermmu_lockand thus ensures all previous SPTEs are zapped before the "flush" fromkvm_arch_flush_shadow_memslot()can run).If
kvm_prepare_memory_region()fails though...Ah, KVM itself is safe because of the aforementioned
kvm_arch_flush_shadow_memslot(). Any accounting done on a temporarily invalid memslot will be unwound when the SPTEs are zapped. So for KVM, ignoring invalid memslots is correct_andnecessary_. We could clean that up by havingaccounted_shadowed()use the @slot from the fault, which would close the window where the fault starts with a valid memslot but then sees an invalid memslot when accounting a new shadow page. But I don't think there is a bug there.Right, and DELETE can't actually fail in the current code base, and we've established that MOVE can't possibly work. So even if this is problematic in theory, there are no _unknown_ bugs, and the known bugs are fixed by the end of the series.
Quoted 8 lines
And at the end of the series, KVMGT drops its tracking only when the DELETE is committed. So I _think_ allowing external trackers to add and remove gfns for write-tracking in an invalid slot is actually desirable/correct. I'm pretty sure removal should be allowed as that can lead to dangling write-protection in a
rollback scenario. And I can't think of anything that will break (in the kernel)
if write-tracking a gfn in an invalid slot is allowed, so I don't see any harm in allowing the extremely theoretical case of KVMGT shadowing a gfn in a to-be-deleted memslot _and_ the deletion being rolled back.Yes, you are right!
I previously thought thatinvalid_slot->arch.gfn_write_trackandold->arch.gfn_write_trackare pointing to different places. But I'm wrong.
Yes, allowing INVALID slot here is more desired for deletion rolling-back.
Sean Christopherson
maintainerRe: [PATCH v2 25/27] KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
Quoted 26 lines · Yan Zhao
Quoted 25 lines · Yan Zhao
Quoted 24 lines · Sean Christopherson
Finally getting back to this series...
Quoted 21 lines · Yan Zhao
Quoted 19 lines · Yan Zhao
On Fri, Mar 10, 2023 at 04:22:56PM -0800, Sean Christopherson wrote:
...arch/x86/kvm/mmu/page_track.c enum pg_level kvm_page_track_max_mapping_level(struct kvm *kvm, gfn_t gfn, · line 279
Quoted 13 lines
arch/x86/kvm/mmu/page_track.c +13
-0+int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn) +{ +struct kvm_memory_slot *slot; +int idx; + + idx =srcu_read_lock (&kvm->srcu); + + slot =gfn_to_memslot (kvm, gfn); +if (!slot) { +srcu_read_unlock (&kvm->srcu, idx); +return -EINVAL ; + } +Also fail if
slot->flags&KVM_MEMSLOT_INVALIDis true?
There should exist a window for external users to see an invalid slot when a slot is about to get deleted/moved.
(It happens before MOVE is rejected inkvm_arch_prepare_memory_region()).
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
Or using
if (!kvm_is_visible_memslot(slot)) { srcu_read_unlock(&kvm->srcu, idx); return -EINVAL; }Hi Sean,
After more thoughts, do you think checking KVM internal memslot is necessary?
I don't think it's necessary per se, but I also can't think of any reason to allow it.
Quoted 8 lines
slot =
gfn_to_memslot(kvm, gfn);if (!slot || slot->id >= KVM_USER_MEM_SLOTS) { srcu_read_unlock(&kvm->srcu, idx); return -EINVAL; }Do we allow write tracking to APIC access page when APIC-write VM exit is not desired?
Allow? Yes.
But KVM doesn't use write-tracking for anything APICv related, e.g. to disable APICv, KVM instead zaps the SPTEs for the APIC access page and on page fault goes straight to MMIO emulation.
Theoretically, the guest could create an intermediate PTE in the APIC access page and AFAICT KVM would shadow the access and write-protect the APIC access page. But that's benign as the resulting emulation would be handled just like emulated APIC MMIO.
FWIW, the other internal memslots, TSS and idenity mapped page tables, are used if and only if paging is disabled in the guest, i.e. there are no guest PTEs for KVM to shadow (and paging must be enabled to enable VMX, so nested EPT is also ruled out). So this is theoretically possible only for the APIC access page. That changes with KVMGT, but that again should not be problematic. KVM will emulate in response to the write-protected page and things go on. E.g. it's arguably much weirder that the guest can read/write the identity mapped page tables that are used for EPT without unrestricted guest.
There's no sane reason to allow creating PTEs in the APIC page, but I'm also not
all that motivated to "fix" things. account_shadowed() isn't expected to fail,
so KVM would need to check further up the stack, e.g. in walk_addr_generic() by open coding a form of kvm_vcpu_gfn_to_hva_prot().
I _think_ that's the only place KVM would need to add a check, as KVM already checks that the root, i.e. CR3, is in a "visible" memslot. I suppose KVM could just synthesize triple fault, like it does for the root/CR3 case, but I don't like making up behavior.
In other words, I'm not opposed to disallowing write-tracking internal memslots, but I can't think of anything that will break, and so for me personally at least, the ROI isn't sufficient to justify writing tests and dealing with any fallout.
Re: [PATCH v2 25/27] KVM: x86/mmu: Drop @slot param from exported/external page-track APIs
Quoted 40 lines
Quoted 2 lines
Hi Sean,
After more thoughts, do you think checking KVM internal memslot is necessary?I don't think it's necessary per se, but I also can't think of any reason to allow it.
Quoted 8 lines
slot =
gfn_to_memslot(kvm, gfn);if (!slot || slot->id >= KVM_USER_MEM_SLOTS) { srcu_read_unlock(&kvm->srcu, idx); return -EINVAL; }Do we allow write tracking to APIC access page when APIC-write VM exit is not desired?
Allow? Yes.
But KVM doesn't use write-tracking for anything APICv related, e.g. to disable APICv, KVM instead zaps the SPTEs for the APIC access page and on page fault goes straight to MMIO emulation.
Theoretically, the guest could create an intermediate PTE in the APIC access page and AFAICT KVM would shadow the access and write-protect the APIC access page. But that's benign as the resulting emulation would be handled just like emulated APIC MMIO.
FWIW, the other internal memslots, TSS and idenity mapped page tables, are used if and only if paging is disabled in the guest, i.e. there are no guest PTEs for KVM to shadow (and paging must be enabled to enable VMX, so nested EPT is also ruled out). So this is theoretically possible only for the APIC access page. That changes with KVMGT, but that again should not be problematic. KVM will emulate in response to the write-protected page and things go on. E.g. it's arguably much weirder that the guest can read/write the identity mapped page tables that are used for EPT without unrestricted guest.
There's no sane reason to allow creating PTEs in the APIC page, but I'm also not
all that motivated to "fix" things.account_shadowed()isn't expected to fail,
so KVM would need to check further up the stack, e.g. inwalk_addr_generic()by open coding a form ofkvm_vcpu_gfn_to_hva_prot().
Quoted 8 lines
I _think_ that's the only place KVM would need to add a check, as KVM already checks that the root, i.e. CR3, is in a "visible" memslot. I suppose KVM could just synthesize triple fault, like it does for the root/CR3 case, but I don't like making up behavior.
In other words, I'm not opposed to disallowing write-tracking internal memslots, but I can't think of anything that will break, and so for me personally at least, the ROI isn't sufficient to justify writing tests and dealing with any fallout.
It makes sense. Thanks for the explanation.
Sean Christopherson
maintainerPATCH v2 26/27 KVM: x86/mmu: Handle KVM bookkeeping in page-track APIs, not callers
In reply to Sean ChristophersonGet/put references to KVM when a page-track notifier is (un)registered instead of relying on the caller to do so. Forcing the caller to do the bookkeeping is unnecessary and adds one more thing for users to get wrong, e.g. see commit 9ed1fdee9ee3 ("drm/i915/gvt: Get reference to KVM iff attachment to VM is successful").
--- arch/x86/include/asm/kvm_page_track.h | 10 ++++------ arch/x86/kvm/mmu/page_track.c | 18 ++++++++++++------ drivers/gpu/drm/i915/gvt/kvmgt.c | 17 +++++++---------- 3 files changed, 23 insertions(+), 22 deletions(-)
arch/x86/include/asm/kvm_page_track.h +4 -6
@@ -47,12 +47,10 @@ struct kvm_page_track_notifier_node {enum pg_level kvm_page_track_max_mapping_level (struct kvm *kvm,gfn_t gfn,enum pg_level max_level); -void -kvm_page_track_register_notifier (struct kvm *kvm, -struct kvm_page_track_notifier_node *n); -void -kvm_page_track_unregister_notifier (struct kvm *kvm, -struct kvm_page_track_notifier_node *n); +int kvm_page_track_register_notifier (struct kvm *kvm, +struct kvm_page_track_notifier_node *n); +void kvm_page_track_unregister_notifier (struct kvm *kvm, +struct kvm_page_track_notifier_node *n);int kvm_write_track_add_gfn (struct kvm *kvm,gfn_t gfn);int kvm_write_track_remove_gfn (struct kvm *kvm,gfn_t gfn);
arch/x86/kvm/mmu/page_track.c +12 -6
@@ -157,17 +157,22 @@ int kvm_page_track_init(struct kvm *kvm)* register the notifier so that event interception for the tracked guest * pages can be received. */ -void -kvm_page_track_register_notifier (struct kvm *kvm, -struct kvm_page_track_notifier_node *n) +int kvm_page_track_register_notifier (struct kvm *kvm, +struct kvm_page_track_notifier_node *n) {struct kvm_page_track_notifier_head *head; +if (!kvm || kvm->mm != current->mm) +return -ESRCH ; + +kvm_get_kvm (kvm); + head = &kvm->arch.track_notifier_head;write_lock (&kvm->mmu_lock);hlist_add_head_rcu (&n->node, &head->track_notifier_list);write_unlock (&kvm->mmu_lock); +return 0 ; }EXPORT_SYMBOL_GPL (kvm_page_track_register_notifier);
@@ -175,9 +180,8 @@ EXPORT_SYMBOL_GPL(kvm_page_track_register_notifier);* stop receiving the event interception. It is the opposed operation of * kvm_page_track_register_notifier(). */ -void -kvm_page_track_unregister_notifier (struct kvm *kvm, -struct kvm_page_track_notifier_node *n) +void kvm_page_track_unregister_notifier (struct kvm *kvm, +struct kvm_page_track_notifier_node *n) {struct kvm_page_track_notifier_head *head;
@@ -187,6 +191,8 @@ kvm_page_track_unregister_notifier(struct kvm *kvm,hlist_del_rcu (&n->node);write_unlock (&kvm->mmu_lock);synchronize_srcu (&head->track_srcu); + +kvm_put_kvm (kvm); }EXPORT_SYMBOL_GPL (kvm_page_track_unregister_notifier);
drivers/gpu/drm/i915/gvt/kvmgt.c +7 -10
@@ -668,21 +668,19 @@ static bool __kvmgt_vgpu_exist(struct intel_vgpu *vgpu)static int intel_vgpu_open_device (struct vfio_device *vfio_dev) {struct intel_vgpu *vgpu =vfio_dev_to_vgpu (vfio_dev); - -if (!vgpu->vfio_device.kvm || - vgpu->vfio_device.kvm->mm != current->mm) { -gvt_vgpu_err ("KVM is required to use Intel vGPU\n" ); -return -ESRCH ; - } +int ret;if (__kvmgt_vgpu_exist (vgpu))return -EEXIST ; vgpu->track_node.track_write = kvmgt_page_track_write; vgpu->track_node.track_remove_region = kvmgt_page_track_remove_region; -kvm_get_kvm (vgpu->vfio_device.kvm); -kvm_page_track_register_notifier (vgpu->vfio_device.kvm, - &vgpu->track_node); + ret =kvm_page_track_register_notifier (vgpu->vfio_device.kvm, + &vgpu->track_node); +if (ret) { +gvt_vgpu_err ("KVM is required to use Intel vGPU\n" ); +return ret; + }set_bit (INTEL_VGPU_STATUS_ATTACHED , vgpu->status);
@@ -717,7 +715,6 @@ static void intel_vgpu_close_device(struct vfio_device *vfio_dev)kvm_page_track_unregister_notifier (vgpu->vfio_device.kvm, &vgpu->track_node); -kvm_put_kvm (vgpu->vfio_device.kvm);kvmgt_protect_table_destroy (vgpu);gvt_cache_destroy (vgpu);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 26/27] KVM: x86/mmu: Handle KVM bookkeeping in page-track APIs, not callers
Quoted 5 lines · Sean Christopherson
Get/put references to KVM when a page-track notifier is (un)registered instead of relying on the caller to do so. Forcing the caller to do the bookkeeping is unnecessary and adds one more thing for users to get wrong, e.g. see commit
9ed1fdee9ee3("drm/i915/gvt: Get reference to KVM iff attachment to VM is successful").
Just realized that "iff" stands for "if and only if" :)
Sean Christopherson
maintainerPATCH v2 27/27 drm/i915/gvt: Drop final dependencies on KVM internal details
In reply to Sean ChristophersonOpen code gpa_to_gfn() in kvmgt_page_track_write() and drop KVMGT's dependency on kvm_host.h, i.e. include only kvm_page_track.h. KVMGT assumes "gfn == gpa >> PAGE_SHIFT" all over the place, including a few lines below in the same function with the same gpa, i.e. there's no reason to use KVM's helper for this one case.
No functional change intended.
--- drivers/gpu/drm/i915/gvt/gvt.h | 3 ++- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/gvt/gvt.h +2 -1
@@ -34,10 +34,11 @@#define _GVT_H_#include <uapi/linux/pci_regs.h> -#include <linux/kvm_host.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <asm/kvm_page_track.h> +#include "i915_drv.h" #include "intel_gvt.h"
drivers/gpu/drm/i915/gvt/kvmgt.c +1 -1
@@ -1599,7 +1599,7 @@ static void kvmgt_page_track_write(gpa_t gpa, const u8 *val, int len,mutex_lock (&info->vgpu_lock); -if (kvmgt_gfn_is_write_protected (info,gpa_to_gfn (gpa))) +if (kvmgt_gfn_is_write_protected (info, gpa >>PAGE_SHIFT ))intel_vgpu_page_track_handler (info, gpa, (void *)val, len);
Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Re: [PATCH v2 27/27] drm/i915/gvt: Drop final dependencies on KVM internal details
Quoted 47 lines · Sean Christopherson
Open code
gpa_to_gfn()inkvmgt_page_track_write()and drop KVMGT's dependency onkvm_host.h, i.e. include onlykvm_page_track.h. KVMGT assumes "gfn == gpa >>PAGE_SHIFT" all over the place, including a few lines below in the same function with the same gpa, i.e. there's no reason to use KVM's helper for this one case.No functional change intended.
Signed-off-by Sean Christopherson <[email protected]>--- drivers/gpu/drm/i915/gvt/gvt.h | 3 ++- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gvt/gvt.h +2
-1@@ -34,10 +34,11 @@#define _GVT_H_#include <uapi/linux/pci_regs.h> -#include <linux/kvm_host.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <asm/kvm_page_track.h> +#include "i915_drv.h" #include "intel_gvt.h" drivers/gpu/drm/i915/gvt/kvmgt.c +1
-1@@ -1599,7 +1599,7 @@ static void kvmgt_page_track_write(gpa_t gpa, const u8 *val, int len,mutex_lock (&info->vgpu_lock); -if (kvmgt_gfn_is_write_protected (info,gpa_to_gfn (gpa))) +if (kvmgt_gfn_is_write_protected (info, gpa >>PAGE_SHIFT ))intel_vgpu_page_track_handler (info, gpa, (void *)val, len);Signature · 1 line
2.40.0.rc1.284.g88254d51c5-goog
Quoted 18 lines · Sean Christopherson
Fix a variety of found-by-inspection bugs in KVMGT, and overhaul KVM's page-track APIs to provide a leaner and cleaner interface. The motivation for this series is to (significantly) reduce the number of KVM APIs that KVMGT uses, with a long-term goal of making all
kvm_host.hheaders KVM-internal.As was the case in v1, tThe KVMGT changes are compile tested only.
Based on "
git://git.kernel.org/pub/scm/virt/kvm/kvm.gitnext".v2:
- Reusevgpu_lockto protect gfn hash instead of introducing a new (and buggy) mutext. [Yan]
- Remove a spurious return fromkvm_page_track_init(). [Yan]
- Take @kvm directly in the inner__kvm_page_track_write(). [Yan]
- Delete the gfn sanity check that relies onkvm_is_visible_gfn()instead of providing a dedicated interface. [Yan]
Quoted 2 lines
base-commit:
45dd9bc75d9adc9483f0c7d662ba6e73ed698a0b
Thanks for the update!
It passed basic tests (gvt in a single vm) at my side. Will do detailed review tomorrow.
Thanks
Yan
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups (rev5)
In reply to Sean Christopherson== Series Details ==
== Series Details ==
Series: drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups (rev5)
URL : https://patchwork.freedesktop.org/series/112196/
State : warning
== Summary ==
Error: dim checkpatch failed25a3d4a31296 drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page" 7616ee93a101 KVM: x86/mmu: Factor out helper to get max mapping size of a memslot fcb516cf24af drm/i915/gvt: remove interface intel_gvt_is_valid_gfn 4e9589b9266b drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT entry 7e1387732ec3 drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry 8b245ebb321a drm/i915/gvt: Put the page reference obtained by KVM's gfn_to_pfn() fd92a12e9d0c drm/i915/gvt: Don't rely on KVM's gfn_to_pfn() to query possible 2M GTT -:37: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #37: FILE: drivers/gpu/drm/i915/gvt/gtt.c:1157:
+static int try_map_2MB_gtt_entry(struct intel_vgpu *vgpu,
+ struct intel_gvt_gtt_entry *entry, dma_addr_t *dma_addr)
total: 0 errors, 0 warnings, 1 checks, 78 lines checkedd33f165a76b9 drm/i915/gvt: Use an "unsigned long" to iterate over memslot gfns 2f00c4873260 drm/i915/gvt: Drop unused helper intel_vgpu_reset_gtt() 524b8ca6b867 drm/i915/gvt: Protect gfn hash table with vgpu_lock da08c5987ad9 KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change 7395b953521e KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs e0945379e27a KVM: drm/i915/gvt: Drop @vcpu from KVM's ->track_write() hook ac3d05c84e2f KVM: x86: Reject memslot MOVE operations if KVMGT is attached b7d633d0df47 drm/i915/gvt: Don't bother removing write-protection on to-be-deleted slot 641942aa6bc1 KVM: x86: Add a new page-track hook to handle memslot deletion -:84: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #84: FILE: arch/x86/kvm/mmu/page_track.c:324:
+ hlist_for_each_entry_srcu(n, &head->track_notifier_list, node,
+ srcu_read_lock_held(&head->track_srcu))
total: 0 errors, 0 warnings, 1 checks, 62 lines checked813496703fa8 drm/i915/gvt: switch from ->track_flush_slot() to ->track_remove_region() 9747b5c46647 KVM: x86: Remove the unused page-track hook track_flush_slot() 22cac1f2fb48 KVM: x86/mmu: Move KVM-only page-track declarations to internal header Traceback (most recent call last):
File "scripts/spdxcheck.py", line 6, in <module>
from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
-:119: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating? #119:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 118 lines checked900cdc374edb KVM: x86/mmu: Use page-track notifiers iff there are external users edc7b922b08c KVM: x86/mmu: Drop infrastructure for multiple page-track modes 8e372f22d215 KVM: x86/mmu: Rename page-track APIs to reflect the new reality 722952f3cee5 KVM: x86/mmu: Assert that correct locks are held for page write-tracking 0ccb4868c921 KVM: x86/mmu: Bug the VM if write-tracking is used but not enabled e4fbe25725a8 KVM: x86/mmu: Drop @slot param from exported/external page-track APIs a000d410d307 KVM: x86/mmu: Handle KVM bookkeeping in page-track APIs, not callers d5ce069cc421 drm/i915/gvt: Drop final dependencies on KVM internal details
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups (rev6)
In reply to Sean Christopherson== Series Details ==
== Series Details ==
Series: drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups (rev6)
URL : https://patchwork.freedesktop.org/series/112196/
State : failure
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/112196/revisions/6/mbox/ not applied
Applying: drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
Applying: KVM: x86/mmu: Factor out helper to get max mapping size of a memslot
Applying: drm/i915/gvt: remove interface intel_gvt_is_valid_gfn
Applying: drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT entry
Applying: drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
Applying: drm/i915/gvt: Put the page reference obtained by KVM's gfn_to_pfn()
Applying: drm/i915/gvt: Don't rely on KVM's gfn_to_pfn() to query possible 2M GTT
Applying: drm/i915/gvt: Use an "unsigned long" to iterate over memslot gfns
Applying: drm/i915/gvt: Drop unused helper intel_vgpu_reset_gtt()
Applying: drm/i915/gvt: Protect gfn hash table with vgpu_lock
Applying: KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change
Applying: KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs
Applying: KVM: drm/i915/gvt: Drop @vcpu from KVM's ->track_write() hook
Applying: KVM: x86: Reject memslot MOVE operations if KVMGT is attached
Applying: drm/i915/gvt: Don't bother removing write-protection on to-be-deleted slot
Applying: KVM: x86: Add a new page-track hook to handle memslot deletion
Applying: drm/i915/gvt: switch from ->track_flush_slot() to ->track_remove_region()
Applying: KVM: x86: Remove the unused page-track hook track_flush_slot()
Applying: KVM: x86/mmu: Move KVM-only page-track declarations to internal header
Applying: KVM: x86/mmu: Use page-track notifiers iff there are external users
error: sha1 information is lacking or useless (arch/x86/include/asm/kvm_page_track.h).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0020 KVM: x86/mmu: Use page-track notifiers iff there are external users When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Build failed, no error log produced
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups (rev7)
In reply to Sean Christopherson== Series Details ==
== Series Details ==
Series: drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups (rev7)
URL : https://patchwork.freedesktop.org/series/112196/
State : failure
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/112196/revisions/7/mbox/ not applied
Applying: drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page"
Applying: KVM: x86/mmu: Factor out helper to get max mapping size of a memslot
Applying: drm/i915/gvt: remove interface intel_gvt_is_valid_gfn
Applying: drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT entry
Applying: drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry
Applying: drm/i915/gvt: Put the page reference obtained by KVM's gfn_to_pfn()
Applying: drm/i915/gvt: Don't rely on KVM's gfn_to_pfn() to query possible 2M GTT
Applying: drm/i915/gvt: Use an "unsigned long" to iterate over memslot gfns
Applying: drm/i915/gvt: Drop unused helper intel_vgpu_reset_gtt()
Applying: drm/i915/gvt: Protect gfn hash table with vgpu_lock
Applying: KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change
Applying: KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs
Applying: KVM: drm/i915/gvt: Drop @vcpu from KVM's ->track_write() hook
Applying: KVM: x86: Reject memslot MOVE operations if KVMGT is attached
Applying: drm/i915/gvt: Don't bother removing write-protection on to-be-deleted slot
Applying: KVM: x86: Add a new page-track hook to handle memslot deletion
Applying: drm/i915/gvt: switch from ->track_flush_slot() to ->track_remove_region()
Applying: KVM: x86: Remove the unused page-track hook track_flush_slot()
Applying: KVM: x86/mmu: Move KVM-only page-track declarations to internal header
Applying: KVM: x86/mmu: Use page-track notifiers iff there are external users
error: patch failed: drivers/gpu/drm/i915/gvt/gvt.h:233
error: drivers/gpu/drm/i915/gvt/gvt.h: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/gvt/gvt.h
Patch failed at 0020 KVM: x86/mmu: Use page-track notifiers iff there are external users When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Build failed, no error log produced