KVM: x86/mmu: Eager Page Splitting for the TDP MMU
cover KVM: x86/mmu: Eager Page Splitting for the TDP MMU
This series is a first pass at implementing Eager Page Splitting for the TDP MMU. For context on the motivation and design of Eager Page Splitting, please see the RFC design proposal and discussion [1].
Paolo, I went ahead and added splitting in both the intially-all-set case (only splitting the region passed to CLEAR_DIRTY_LOG) and the case where we are not using initially-all-set (splitting the entire memslot when dirty logging is enabled) to give you an idea of what both look like.
Note: I will be on vacation all of next week so I will not be able to respond to reviews until Monday November 29. I thought it would be useful to seed discussion and reviews with an early version of the code rather than putting it off another week. But feel free to also ignore this until I get back :)
This series compiles and passes the most basic splitting test:
$ ./dirty_log_perf_test -s anonymous_hugetlb_2mb -v 2 -i 4
But please operate under the assumption that this code is probably buggy.
[1] https://lore.kernel.org/kvm/CALzav=dV_U4r1K9oDq4esb4mpBQDQ2ROQ5zH5wV3KpOaZrRW-A@mail.gmail.com/#t
David Matlack (15):
KVM: x86/mmu: Rename rmap_write_protect to kvm_vcpu_write_protect_gfn
KVM: x86/mmu: Rename __rmap_write_protect to rmap_write_protect
KVM: x86/mmu: Automatically update iter->old_spte if cmpxchg fails
KVM: x86/mmu: Factor out logic to atomically install a new page table
KVM: x86/mmu: Abstract mmu caches out to a separate struct
KVM: x86/mmu: Derive page role from parent
KVM: x86/mmu: Pass in vcpu->arch.mmu_caches instead of vcpu
KVM: x86/mmu: Helper method to check for large and present sptes
KVM: x86/mmu: Move restore_acc_track_spte to spte.c
KVM: x86/mmu: Abstract need_resched logic from
tdp_mmu_iter_cond_resched
KVM: x86/mmu: Refactor tdp_mmu iterators to take kvm_mmu_page root
KVM: x86/mmu: Split large pages when dirty logging is enabled
KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
KVM: x86/mmu: Add tracepoint for splitting large pages
KVM: x86/mmu: Update page stats when splitting large pages
arch/x86/include/asm/kvm_host.h | 22 ++- arch/x86/kvm/mmu/mmu.c | 185 +++++++++++++----- arch/x86/kvm/mmu/mmu_internal.h | 3 + arch/x86/kvm/mmu/mmutrace.h | 20 ++ arch/x86/kvm/mmu/spte.c | 64 +++++++ arch/x86/kvm/mmu/spte.h | 7 + arch/x86/kvm/mmu/tdp_iter.c | 5 +- arch/x86/kvm/mmu/tdp_iter.h | 10 +- arch/x86/kvm/mmu/tdp_mmu.c | 322 +++++++++++++++++++++++--------- arch/x86/kvm/mmu/tdp_mmu.h | 5 + arch/x86/kvm/x86.c | 6 + 11 files changed, 501 insertions(+), 148 deletions(-)
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 1/15 KVM: x86/mmu: Rename rmap_write_protect to kvm_vcpu_write_protect_gfn
rmap_write_protect is a poor name because we may not even touch the rmap if the TDP MMU is in use. It is also confusing that rmap_write_protect is not a simpler wrapper around __rmap_write_protect, since that is the typical flow for functions with double-underscore names.
Rename it to kvm_vcpu_write_protect_gfn to convey that we are write-protecting a specific gfn in the context of a vCPU.
No functional change intended.
--- arch/x86/kvm/mmu/mmu.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/x86/kvm/mmu/mmu.c +3 -3
@@ -1427,7 +1427,7 @@ bool kvm_mmu_slot_gfn_write_protect(struct kvm *kvm,return write_protected; } -static bool rmap_write_protect (struct kvm_vcpu *vcpu,u64 gfn) +static bool kvm_vcpu_write_protect_gfn (struct kvm_vcpu *vcpu,u64 gfn) {struct kvm_memory_slot *slot;
@@ -2026,7 +2026,7 @@ static int mmu_sync_children(struct kvm_vcpu *vcpu,bool protected = false;for_each_sp (pages, sp, parents, i) - protected |=rmap_write_protect (vcpu, sp->gfn); + protected |=kvm_vcpu_write_protect_gfn (vcpu, sp->gfn);if (protected) {kvm_mmu_remote_flush_or_zap (vcpu->kvm, &invalid_list, true);
@@ -2153,7 +2153,7 @@ static struct kvm_mmu_page *kvm_mmu_get_page(struct kvm_vcpu *vcpu,hlist_add_head (&sp->hash_link, sp_list);if (!direct) {account_shadowed (vcpu->kvm, sp); -if (level ==PG_LEVEL_4K &&rmap_write_protect (vcpu, gfn)) +if (level ==PG_LEVEL_4K &&kvm_vcpu_write_protect_gfn (vcpu, gfn))kvm_flush_remote_tlbs_with_address (vcpu->kvm, gfn,1 ); }trace_kvm_mmu_get_page (sp, true);
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 01/15] KVM: x86/mmu: Rename rmap_write_protect to kvm_vcpu_write_protect_gfn
Quoted 6 lines · David Matlack
rmap_write_protectis a poor name because we may not even touch the rmap if the TDP MMU is in use. It is also confusing thatrmap_write_protectis not a simpler wrapper around__rmap_write_protect, since that is the typical flow for functions with double-underscore names.
Quoted 6 lines
Rename it to
kvm_vcpu_write_protect_gfnto convey that we are write-protecting a specific gfn in the context of a vCPU.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Quoted 38 lines
--- arch/x86/kvm/mmu/mmu.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)arch/x86/kvm/mmu/mmu.c +3
-4@@ -1427,7 +1427,7 @@ bool kvm_mmu_slot_gfn_write_protect(struct kvm *kvm,return write_protected; } -static bool rmap_write_protect (struct kvm_vcpu *vcpu,u64 gfn) +static bool kvm_vcpu_write_protect_gfn (struct kvm_vcpu *vcpu,u64 gfn) {struct kvm_memory_slot *slot;@@ -2026,7 +2026,7 @@ static int mmu_sync_children(struct kvm_vcpu *vcpu,bool protected = false;for_each_sp (pages, sp, parents, i) - protected |=rmap_write_protect (vcpu, sp->gfn); + protected |=kvm_vcpu_write_protect_gfn (vcpu, sp->gfn);if (protected) {kvm_mmu_remote_flush_or_zap (vcpu->kvm, &invalid_list, true);@@ -2153,7 +2153,7 @@ static struct kvm_mmu_page *kvm_mmu_get_page(struct kvm_vcpu *vcpu,hlist_add_head (&sp->hash_link, sp_list);if (!direct) {account_shadowed (vcpu->kvm, sp); -if (level ==PG_LEVEL_4K &&rmap_write_protect (vcpu, gfn)) +if (level ==PG_LEVEL_4K &&kvm_vcpu_write_protect_gfn (vcpu, gfn))kvm_flush_remote_tlbs_with_address (vcpu->kvm, gfn,1 ); }trace_kvm_mmu_get_page (sp, true); --2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 01/15] KVM: x86/mmu: Rename rmap_write_protect to kvm_vcpu_write_protect_gfn
In reply to David MatlackQuoted 11 lines · David Matlack
rmap_write_protectis a poor name because we may not even touch the rmap if the TDP MMU is in use. It is also confusing thatrmap_write_protectis not a simpler wrapper around__rmap_write_protect, since that is the typical flow for functions with double-underscore names.Rename it to
kvm_vcpu_write_protect_gfnto convey that we are write-protecting a specific gfn in the context of a vCPU.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Signature · 1 line
Peter Xu
RFC PATCH 2/15 KVM: x86/mmu: Rename __rmap_write_protect to rmap_write_protect
In reply to David MatlackNow that rmap_write_protect has been renamed, there is no need for the double underscores in front of __rmap_write_protect.
No functional change intended.
--- arch/x86/kvm/mmu/mmu.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
arch/x86/kvm/mmu/mmu.c +6 -6
@@ -1235,9 +1235,9 @@ static bool spte_write_protect(u64 *sptep, bool pt_protect)return mmu_spte_update (sptep, spte); } -static bool __rmap_write_protect (struct kvm *kvm, -struct kvm_rmap_head *rmap_head, -bool pt_protect) +static bool rmap_write_protect (struct kvm *kvm, +struct kvm_rmap_head *rmap_head, +bool pt_protect) {u64 *sptep;struct rmap_iterator iter;
@@ -1317,7 +1317,7 @@ static void kvm_mmu_write_protect_pt_masked(struct kvm *kvm,while (mask) { rmap_head =gfn_to_rmap (slot->base_gfn + gfn_offset +__ffs (mask),PG_LEVEL_4K , slot); -__rmap_write_protect (kvm, rmap_head, false); +rmap_write_protect (kvm, rmap_head, false);/* clear the first set bit */ mask &= mask -1 ;
@@ -1416,7 +1416,7 @@ bool kvm_mmu_slot_gfn_write_protect(struct kvm *kvm,if (kvm_memslots_have_rmaps (kvm)) {for (i = min_level; i <=KVM_MAX_HUGEPAGE_LEVEL ; ++i) { rmap_head =gfn_to_rmap (gfn, i, slot); - write_protected |=__rmap_write_protect (kvm, rmap_head, true); + write_protected |=rmap_write_protect (kvm, rmap_head, true); } }
@@ -5780,7 +5780,7 @@ static bool slot_rmap_write_protect(struct kvm *kvm,struct kvm_rmap_head *rmap_head, const struct kvm_memory_slot *slot) { - return __rmap_write_protect(kvm, rmap_head, false); + return rmap_write_protect(kvm, rmap_head, false); } void kvm_mmu_slot_remove_write_access(struct kvm *kvm,
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 02/15] KVM: x86/mmu: Rename __rmap_write_protect to rmap_write_protect
Quoted 7 lines · David Matlack
Now that
rmap_write_protecthas been renamed, there is no need for the double underscores in front of__rmap_write_protect.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Quoted 51 lines
--- arch/x86/kvm/mmu/mmu.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)arch/x86/kvm/mmu/mmu.c +6
-7@@ -1235,9 +1235,9 @@ static bool spte_write_protect(u64 *sptep, bool pt_protect)return mmu_spte_update (sptep, spte); } -static bool __rmap_write_protect (struct kvm *kvm, -struct kvm_rmap_head *rmap_head, -bool pt_protect) +static bool rmap_write_protect (struct kvm *kvm, +struct kvm_rmap_head *rmap_head, +bool pt_protect) {u64 *sptep;struct rmap_iterator iter;@@ -1317,7 +1317,7 @@ static void kvm_mmu_write_protect_pt_masked(struct kvm *kvm,while (mask) { rmap_head =gfn_to_rmap (slot->base_gfn + gfn_offset +__ffs (mask),PG_LEVEL_4K , slot); -__rmap_write_protect (kvm, rmap_head, false); +rmap_write_protect (kvm, rmap_head, false);/* clear the first set bit */ mask &= mask -1 ;@@ -1416,7 +1416,7 @@ bool kvm_mmu_slot_gfn_write_protect(struct kvm *kvm,if (kvm_memslots_have_rmaps (kvm)) {for (i = min_level; i <=KVM_MAX_HUGEPAGE_LEVEL ; ++i) { rmap_head =gfn_to_rmap (gfn, i, slot); - write_protected |=__rmap_write_protect (kvm, rmap_head, true); + write_protected |=rmap_write_protect (kvm, rmap_head, true); } }@@ -5780,7 +5780,7 @@ static bool slot_rmap_write_protect(struct kvm *kvm,struct kvm_rmap_head *rmap_head, const struct kvm_memory_slot *slot) { - return __rmap_write_protect(kvm, rmap_head, false); + return rmap_write_protect(kvm, rmap_head, false); } void kvm_mmu_slot_remove_write_access(struct kvm *kvm, --2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 02/15] KVM: x86/mmu: Rename __rmap_write_protect to rmap_write_protect
In reply to David MatlackQuoted 6 lines · David Matlack
Now that
rmap_write_protecthas been renamed, there is no need for the double underscores in front of__rmap_write_protect.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Signature · 1 line
Peter Xu
RFC PATCH 3/15 KVM: x86/mmu: Automatically update iter->old_spte if cmpxchg fails
In reply to David MatlackConsolidate a bunch of code that was manually re-reading the spte if the cmpxchg fails. There is no extra cost of doing this because we already have the spte value as a result of the cmpxchg (and in fact this eliminates re-reading the spte), and none of the call sites depend on iter->old_spte retaining the stale spte value.
--- arch/x86/kvm/mmu/tdp_mmu.c | 56 ++++++++++++-------------------------- 1 file changed, 18 insertions(+), 38 deletions(-)
arch/x86/kvm/mmu/tdp_mmu.c +18 -38
@@ -492,16 +492,22 @@ static void handle_changed_spte(struct kvm *kvm, int as_id, gfn_t gfn,* and handle the associated bookkeeping. Do not mark the page dirty * in KVM's dirty bitmaps. * +* If setting the SPTE fails because it has changed, iter->old_spte will be +* updated with the updated value of the spte. +* * @kvm: kvm instance * @iter: a tdp_iter instance currently on the SPTE that should be set * @new_spte: The value the SPTE should be set to * Returns: true if the SPTE was set, false if it was not. If false is returned, -* this function will have no side-effects. +* this function will have no side-effects other than updating +* iter->old_spte to the latest value of spte. */ static inline bool tdp_mmu_set_spte_atomic (struct kvm *kvm,struct tdp_iter *iter,u64 new_spte) { +u64 old_spte; +lockdep_assert_held_read (&kvm->mmu_lock);/*
@@ -515,9 +521,11 @@ static inline bool tdp_mmu_set_spte_atomic(struct kvm *kvm,* Note, fast_pf_fix_direct_spte() can also modify TDP MMU SPTEs and * does not hold the mmu_lock. */ -if (cmpxchg64 (rcu_dereference (iter->sptep), iter->old_spte, - new_spte) != iter->old_spte) + old_spte =cmpxchg64 (rcu_dereference (iter->sptep), iter->old_spte, new_spte); +if (old_spte != iter->old_spte) { + iter->old_spte = old_spte;return false; + }__handle_changed_spte (kvm, iter->as_id, iter->gfn, iter->old_spte, new_spte, iter->level, true);
@@ -747,14 +755,8 @@ static bool zap_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,if (!shared) {tdp_mmu_set_spte (kvm, &iter,0 ); flush = true; - }else if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); + }else if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) goto retry; - } }rcu_read_unlock ();
@@ -978,13 +980,6 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) is_large_pte(iter.old_spte)) {if (!tdp_mmu_zap_spte_atomic (vcpu->kvm, &iter))break ; - -/* -* The iter must explicitly re-read the spte here -* because the new value informs the !present -* path below. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); }if (!is_shadow_present_pte (iter.old_spte)) {
@@ -1190,14 +1185,9 @@ static bool wrprot_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root, new_spte = iter.old_spte & ~PT_WRITABLE_MASK ; -if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) goto retry; - } + spte_set = true; }
@@ -1258,14 +1248,9 @@ static bool clear_dirty_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,continue ; } -if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) goto retry; - } + spte_set = true; }
@@ -1391,14 +1376,9 @@ static bool zap_collapsible_spte_range(struct kvm *kvm, pfn, PG_LEVEL_NUM))continue ; -if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) goto retry; - } + flush = true; }
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 03/15] KVM: x86/mmu: Automatically update iter->old_spte if cmpxchg fails
Quoted 41 lines · David Matlack
Consolidate a bunch of code that was manually re-reading the spte if the cmpxchg fails. There is no extra cost of doing this because we already have the spte value as a result of the cmpxchg (and in fact this eliminates re-reading the spte), and none of the call sites depend on
iter->old_spteretaining the stale spte value.Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 56 ++++++++++++-------------------------- 1 file changed, 18 insertions(+), 38 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +7
-1@@ -492,16 +492,22 @@ static void handle_changed_spte(struct kvm *kvm, int as_id, gfn_t gfn,* and handle the associated bookkeeping. Do not mark the page dirty * in KVM's dirty bitmaps. * +* If setting the SPTE fails because it has changed, iter->old_spte will be +* updated with the updated value of the spte. +* * @kvm: kvm instance * @iter: a tdp_iter instance currently on the SPTE that should be set * @new_spte: The value the SPTE should be set to * Returns: true if the SPTE was set, false if it was not. If false is returned, -* this function will have no side-effects. +* this function will have no side-effects other than updating +* iter->old_spte to the latest value of spte. */ static inline bool tdp_mmu_set_spte_atomic (struct kvm *kvm,struct tdp_iter *iter,u64 new_spte) { +u64 old_spte; +lockdep_assert_held_read (&kvm->mmu_lock);/*
arch/x86/kvm/mmu/tdp_mmu.c static inline bool tdp_mmu_set_spte_atomic(struct kvm *kvm, · line 524
Quoted 6 lines
arch/x86/kvm/mmu/tdp_mmu.c +1
-2@@ -515,9 +521,11 @@ static inline bool tdp_mmu_set_spte_atomic(struct kvm *kvm,* Note, fast_pf_fix_direct_spte() can also modify TDP MMU SPTEs and * does not hold the mmu_lock. */ -if (cmpxchg64 (rcu_dereference (iter->sptep), iter->old_spte, - new_spte) != iter->old_spte) + old_spte =cmpxchg64 (rcu_dereference (iter->sptep), iter->old_spte, new_spte);
This probably deserves a comment:
/*
* If the old_spte values differ, the cmpxchg failed. Updateiter->old_spte with the value inserted by
* another thread.
*/
Quoted 8 lines
arch/x86/kvm/mmu/tdp_mmu.c +3
-0+if (old_spte != iter->old_spte) { + iter->old_spte = old_spte;return false; + }__handle_changed_spte (kvm, iter->as_id, iter->gfn, iter->old_spte, new_spte, iter->level, true);
arch/x86/kvm/mmu/tdp_mmu.c static bool zap_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root, · line 755
Quoted 9 lines
arch/x86/kvm/mmu/tdp_mmu.c +0
-6@@ -747,14 +755,8 @@ static bool zap_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,if (!shared) {tdp_mmu_set_spte (kvm, &iter,0 ); flush = true; - }else if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep));
I think kernel style is to include the curly braces on the else if, if the if had them.
Quoted 74 lines
arch/x86/kvm/mmu/tdp_mmu.c +7
-30+ }else if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) goto retry; - } }rcu_read_unlock ();@@ -978,13 +980,6 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) is_large_pte(iter.old_spte)) {if (!tdp_mmu_zap_spte_atomic (vcpu->kvm, &iter))break ; - -/* -* The iter must explicitly re-read the spte here -* because the new value informs the !present -* path below. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); }if (!is_shadow_present_pte (iter.old_spte)) {@@ -1190,14 +1185,9 @@ static bool wrprot_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root, new_spte = iter.old_spte & ~PT_WRITABLE_MASK ; -if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) goto retry; - } + spte_set = true; }@@ -1258,14 +1248,9 @@ static bool clear_dirty_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,continue ; } -if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) goto retry; - } + spte_set = true; }@@ -1391,14 +1376,9 @@ static bool zap_collapsible_spte_range(struct kvm *kvm, pfn, PG_LEVEL_NUM))continue ; -if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) goto retry; - } + flush = true; } --2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 03/15] KVM: x86/mmu: Automatically update iter->old_spte if cmpxchg fails
Quoted 52 lines · Ben Gardon
Quoted 41 lines · David Matlack
Consolidate a bunch of code that was manually re-reading the spte if the cmpxchg fails. There is no extra cost of doing this because we already have the spte value as a result of the cmpxchg (and in fact this eliminates re-reading the spte), and none of the call sites depend on
iter->old_spteretaining the stale spte value.Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 56 ++++++++++++-------------------------- 1 file changed, 18 insertions(+), 38 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +7
-1@@ -492,16 +492,22 @@ static void handle_changed_spte(struct kvm *kvm, int as_id, gfn_t gfn,* and handle the associated bookkeeping. Do not mark the page dirty * in KVM's dirty bitmaps. * +* If setting the SPTE fails because it has changed, iter->old_spte will be +* updated with the updated value of the spte. +* * @kvm: kvm instance * @iter: a tdp_iter instance currently on the SPTE that should be set * @new_spte: The value the SPTE should be set to * Returns: true if the SPTE was set, false if it was not. If false is returned, -* this function will have no side-effects. +* this function will have no side-effects other than updating +* iter->old_spte to the latest value of spte. */ static inline bool tdp_mmu_set_spte_atomic (struct kvm *kvm,struct tdp_iter *iter,u64 new_spte) { +u64 old_spte; +lockdep_assert_held_read (&kvm->mmu_lock);/* arch/x86/kvm/mmu/tdp_mmu.c static inline bool tdp_mmu_set_spte_atomic(struct kvm *kvm, · line 524
Quoted 6 lines
arch/x86/kvm/mmu/tdp_mmu.c +1
-2@@ -515,9 +521,11 @@ static inline bool tdp_mmu_set_spte_atomic(struct kvm *kvm,* Note, fast_pf_fix_direct_spte() can also modify TDP MMU SPTEs and * does not hold the mmu_lock. */ -if (cmpxchg64 (rcu_dereference (iter->sptep), iter->old_spte, - new_spte) != iter->old_spte) + old_spte =cmpxchg64 (rcu_dereference (iter->sptep), iter->old_spte, new_spte);This probably deserves a comment:
Quoted 5 lines
/*
* If theold_sptevalues differ, the cmpxchg failed. Updateiter->old_sptewith the value inserted by
* another thread.
*/
Will do.
Quoted 6 lines
Quoted 6 lines
arch/x86/kvm/mmu/tdp_mmu.c +3
-0+if (old_spte != iter->old_spte) { + iter->old_spte = old_spte;return false; + }
Quoted 15 lines
arch/x86/kvm/mmu/tdp_mmu.c static bool zap_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root, · line 755
Quoted 12 lines
arch/x86/kvm/mmu/tdp_mmu.c +0
-6__handle_changed_spte (kvm, iter->as_id, iter->gfn, iter->old_spte, new_spte, iter->level, true);@@ -747,14 +755,8 @@ static bool zap_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,if (!shared) {tdp_mmu_set_spte (kvm, &iter,0 ); flush = true; - }else if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep));I think kernel style is to include the curly braces on the else if, if the if had them.
You are correct! Will fix in v1.
Quoted 76 lines
Quoted 76 lines
arch/x86/kvm/mmu/tdp_mmu.c +7
-30+ }else if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) goto retry; - } }rcu_read_unlock ();@@ -978,13 +980,6 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) is_large_pte(iter.old_spte)) {if (!tdp_mmu_zap_spte_atomic (vcpu->kvm, &iter))break ; - -/* -* The iter must explicitly re-read the spte here -* because the new value informs the !present -* path below. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); }if (!is_shadow_present_pte (iter.old_spte)) {@@ -1190,14 +1185,9 @@ static bool wrprot_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root, new_spte = iter.old_spte & ~PT_WRITABLE_MASK ; -if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) goto retry; - } + spte_set = true; }@@ -1258,14 +1248,9 @@ static bool clear_dirty_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,continue ; } -if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_set_spte_atomic (kvm, &iter, new_spte)) goto retry; - } + spte_set = true; }@@ -1391,14 +1376,9 @@ static bool zap_collapsible_spte_range(struct kvm *kvm, pfn, PG_LEVEL_NUM))continue ; -if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) { -/* -* The iter must explicitly re-read the SPTE because -* the atomic cmpxchg failed. -*/ - iter.old_spte =READ_ONCE (*rcu_dereference (iter.sptep)); +if (!tdp_mmu_zap_spte_atomic (kvm, &iter)) goto retry; - } + flush = true; } --2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 4/15 KVM: x86/mmu: Factor out logic to atomically install a new page table
In reply to David MatlackFactor out the logic to atomically replace an SPTE with an SPTE that points to a new page table. This will be used in a follow-up commit to split a large page SPTE into one level lower.
--- arch/x86/kvm/mmu/tdp_mmu.c | 53 ++++++++++++++++++++++++++------------ 1 file changed, 37 insertions(+), 16 deletions(-)
arch/x86/kvm/mmu/tdp_mmu.c +37 -16
@@ -945,6 +945,39 @@ static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu,return ret; } +/* +* tdp_mmu_install_sp_atomic - Atomically replace the given spte with an +* spte pointing to the provided page table. +* +* @kvm: kvm instance +* @iter: a tdp_iter instance currently on the SPTE that should be set +* @sp: The new TDP page table to install. +* @account_nx: True if this page table is being installed to split a +* non-executable huge page. +* +* Returns: True if the new page table was installed. False if spte being +* replaced changed, causing the atomic compare-exchange to fail. +* If this function returns false the sp will be freed before +* returning. +*/ +static bool tdp_mmu_install_sp_atomic (struct kvm *kvm, +struct tdp_iter *iter, +struct kvm_mmu_page *sp, +bool account_nx) +{ +u64 spte; + + spte =make_nonleaf_spte (sp->spt, !shadow_accessed_mask); + +if (tdp_mmu_set_spte_atomic (kvm, iter, spte)) { +tdp_mmu_link_page (kvm, sp, account_nx); +return true; + }else { +tdp_mmu_free_sp (sp); +return false; + } +} +/* * Handle a TDP page fault (NPT/EPT violation/misconfiguration) by installing * page tables and SPTEs to translate the faulting guest physical address.
@@ -954,8 +987,6 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)struct kvm_mmu *mmu = vcpu->arch.mmu;struct tdp_iter iter;struct kvm_mmu_page *sp; -u64 *child_pt; -u64 new_spte;int ret;kvm_mmu_hugepage_adjust (vcpu, fault);
@@ -983,6 +1014,9 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) }if (!is_shadow_present_pte (iter.old_spte)) { +bool account_nx = fault->huge_page_disallowed && + fault->req_level >= iter.level; +/* * If SPTE has been frozen by another thread, just * give up and retry, avoiding unnecessary page table
@@ -992,21 +1026,8 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)break ; sp =alloc_tdp_mmu_page (vcpu, iter.gfn, iter.level -1 ); - child_pt = sp->spt; - - new_spte =make_nonleaf_spte (child_pt, - !shadow_accessed_mask); - -if (tdp_mmu_set_spte_atomic (vcpu->kvm, &iter, new_spte)) { -tdp_mmu_link_page (vcpu->kvm, sp, - fault->huge_page_disallowed && - fault->req_level >= iter.level); - -trace_kvm_mmu_get_page (sp, true); - }else { -tdp_mmu_free_sp (sp); +if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; - } } }
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 04/15] KVM: x86/mmu: Factor out logic to atomically install a new page table
Quoted 78 lines · David Matlack
Factor out the logic to atomically replace an SPTE with an SPTE that points to a new page table. This will be used in a follow-up commit to split a large page SPTE into one level lower.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 53 ++++++++++++++++++++++++++------------ 1 file changed, 37 insertions(+), 16 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +36
-3@@ -945,6 +945,39 @@ static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu,return ret; } +/* +* tdp_mmu_install_sp_atomic - Atomically replace the given spte with an +* spte pointing to the provided page table. +* +* @kvm: kvm instance +* @iter: a tdp_iter instance currently on the SPTE that should be set +* @sp: The new TDP page table to install. +* @account_nx: True if this page table is being installed to split a +* non-executable huge page. +* +* Returns: True if the new page table was installed. False if spte being +* replaced changed, causing the atomic compare-exchange to fail. +* If this function returns false the sp will be freed before +* returning. +*/ +static bool tdp_mmu_install_sp_atomic (struct kvm *kvm, +struct tdp_iter *iter, +struct kvm_mmu_page *sp, +bool account_nx) +{ +u64 spte; + + spte =make_nonleaf_spte (sp->spt, !shadow_accessed_mask); + +if (tdp_mmu_set_spte_atomic (kvm, iter, spte)) { +tdp_mmu_link_page (kvm, sp, account_nx); +return true; + }else { +tdp_mmu_free_sp (sp); +return false; + } +} +/* * Handle a TDP page fault (NPT/EPT violation/misconfiguration) by installing * page tables and SPTEs to translate the faulting guest physical address. @@ -954,8 +987,6 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)struct kvm_mmu *mmu = vcpu->arch.mmu;struct tdp_iter iter;struct kvm_mmu_page *sp; -u64 *child_pt; -u64 new_spte;int ret;kvm_mmu_hugepage_adjust (vcpu, fault);@@ -983,6 +1014,9 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) }if (!is_shadow_present_pte (iter.old_spte)) { +bool account_nx = fault->huge_page_disallowed && + fault->req_level >= iter.level; +/* * If SPTE has been frozen by another thread, just * give up and retry, avoiding unnecessary page table @@ -992,21 +1026,8 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)break ; sp =alloc_tdp_mmu_page (vcpu, iter.gfn, iter.level -1 ); - child_pt = sp->spt;
arch/x86/kvm/mmu/tdp_mmu.c int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) · line 1005
Quoted 10 lines
arch/x86/kvm/mmu/tdp_mmu.c +0
-10- - new_spte =make_nonleaf_spte (child_pt, - !shadow_accessed_mask); - -if (tdp_mmu_set_spte_atomic (vcpu->kvm, &iter, new_spte)) { -tdp_mmu_link_page (vcpu->kvm, sp, - fault->huge_page_disallowed && - fault->req_level >= iter.level); - -trace_kvm_mmu_get_page (sp, true);
This refactoring drops this trace point. Is that intentional?
Quoted 11 lines
arch/x86/kvm/mmu/tdp_mmu.c +1
-4- }else { -tdp_mmu_free_sp (sp); +if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; - } } } --2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 04/15] KVM: x86/mmu: Factor out logic to atomically install a new page table
Quoted 78 lines · Ben Gardon
Quoted 76 lines · David Matlack
Factor out the logic to atomically replace an SPTE with an SPTE that points to a new page table. This will be used in a follow-up commit to split a large page SPTE into one level lower.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 53 ++++++++++++++++++++++++++------------ 1 file changed, 37 insertions(+), 16 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +36
-2@@ -945,6 +945,39 @@ static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu,return ret; } +/* +* tdp_mmu_install_sp_atomic - Atomically replace the given spte with an +* spte pointing to the provided page table. +* +* @kvm: kvm instance +* @iter: a tdp_iter instance currently on the SPTE that should be set +* @sp: The new TDP page table to install. +* @account_nx: True if this page table is being installed to split a +* non-executable huge page. +* +* Returns: True if the new page table was installed. False if spte being +* replaced changed, causing the atomic compare-exchange to fail. +* If this function returns false the sp will be freed before +* returning. +*/ +static bool tdp_mmu_install_sp_atomic (struct kvm *kvm, +struct tdp_iter *iter, +struct kvm_mmu_page *sp, +bool account_nx) +{ +u64 spte; + + spte =make_nonleaf_spte (sp->spt, !shadow_accessed_mask); + +if (tdp_mmu_set_spte_atomic (kvm, iter, spte)) { +tdp_mmu_link_page (kvm, sp, account_nx); +return true; + }else { +tdp_mmu_free_sp (sp); +return false; + } +} +/* * Handle a TDP page fault (NPT/EPT violation/misconfiguration) by installing * page tables and SPTEs to translate the faulting guest physical address. @@ -954,8 +987,6 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)struct kvm_mmu *mmu = vcpu->arch.mmu;struct tdp_iter iter;struct kvm_mmu_page *sp; -u64 *child_pt; -u64 new_spte;int ret;kvm_mmu_hugepage_adjust (vcpu, fault);@@ -983,6 +1014,9 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) }if (!is_shadow_present_pte (iter.old_spte)) { +bool account_nx = fault->huge_page_disallowed && + fault->req_level >= iter.level; +/* * If SPTE has been frozen by another thread, just * give up and retry, avoiding unnecessary page table @@ -992,21 +1026,8 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)break ;
Quoted 14 lines
arch/x86/kvm/mmu/tdp_mmu.c int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) · line 1005
Quoted 12 lines
arch/x86/kvm/mmu/tdp_mmu.c +0
-11sp =alloc_tdp_mmu_page (vcpu, iter.gfn, iter.level -1 ); - child_pt = sp->spt; - - new_spte =make_nonleaf_spte (child_pt, - !shadow_accessed_mask); - -if (tdp_mmu_set_spte_atomic (vcpu->kvm, &iter, new_spte)) { -tdp_mmu_link_page (vcpu->kvm, sp, - fault->huge_page_disallowed && - fault->req_level >= iter.level); - -trace_kvm_mmu_get_page (sp, true);This refactoring drops this trace point. Is that intentional?
Yes it was intentional, but I forgot to describe it in the commit message. Good catch.
This tracepoint is redundant with the one in alloc_tdp_mmu_page().
I'll update the commit message for v1.
Quoted 13 lines
Quoted 13 lines
arch/x86/kvm/mmu/tdp_mmu.c +1
-4- }else { -tdp_mmu_free_sp (sp); +if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; - } } } --2.34.0.rc2.393.gf8c9666880-goog
Sean Christopherson
maintainerRe: [RFC PATCH 04/15] KVM: x86/mmu: Factor out logic to atomically install a new page table
In reply to David MatlackQuoted 30 lines · David Matlack
Factor out the logic to atomically replace an SPTE with an SPTE that points to a new page table. This will be used in a follow-up commit to split a large page SPTE into one level lower.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 53 ++++++++++++++++++++++++++------------ 1 file changed, 37 insertions(+), 16 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +13
-0@@ -945,6 +945,39 @@ static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu,return ret; } +/* +* tdp_mmu_install_sp_atomic - Atomically replace the given spte with an +* spte pointing to the provided page table. +* +* @kvm: kvm instance +* @iter: a tdp_iter instance currently on the SPTE that should be set +* @sp: The new TDP page table to install. +* @account_nx: True if this page table is being installed to split a +* non-executable huge page. +* +* Returns: True if the new page table was installed. False if spte being +* replaced changed, causing the atomic compare-exchange to fail. +* If this function returns false the sp will be freed before
arch/x86/kvm/mmu/tdp_mmu.c static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu, · line 970
Quoted 10 lines
arch/x86/kvm/mmu/tdp_mmu.c +10
-0+* returning. +*/ +static bool tdp_mmu_install_sp_atomic (struct kvm *kvm, +struct tdp_iter *iter, +struct kvm_mmu_page *sp, +bool account_nx) +{ +u64 spte; + + spte =make_nonleaf_spte (sp->spt, !shadow_accessed_mask);
This can easily go on one line.
u64 spte = make_nonleaf_spte(sp->spt, !shadow_accessed_mask);
arch/x86/kvm/mmu/tdp_mmu.c static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu, · line 977
Quoted 7 lines
arch/x86/kvm/mmu/tdp_mmu.c +7
-0+ +if (tdp_mmu_set_spte_atomic (kvm, iter, spte)) { +tdp_mmu_link_page (kvm, sp, account_nx); +return true; + }else { +tdp_mmu_free_sp (sp); +return false;
I don't think this helper should free the sp on failure, even if that's what all paths end up doing. When reading the calling code, it really looks like the sp is being leaked because the allocation and free are in different contexts. That the sp is consumed on success is fairly intuitive given the "install" action, but freeing on failure not so much.
And for the eager splitting, freeing on failure is wasteful. It's extremely unlikely to happen often, so in practice it's unlikely to be an issue, but it's certainly odd since the loop is likely going to immediately allocate another sp, either for the current spte or for the next spte.
Side topic, tdp_mmu_set_spte_atomic() and friends really should return 0/-EBUSY. Boolean returns for errors usually end in tears sooner or later.
Re: [RFC PATCH 04/15] KVM: x86/mmu: Factor out logic to atomically install a new page table
Quoted 60 lines · Sean Christopherson
Quoted 30 lines · David Matlack
Factor out the logic to atomically replace an SPTE with an SPTE that points to a new page table. This will be used in a follow-up commit to split a large page SPTE into one level lower.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 53 ++++++++++++++++++++++++++------------ 1 file changed, 37 insertions(+), 16 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +13
-0@@ -945,6 +945,39 @@ static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu,return ret; } +/* +* tdp_mmu_install_sp_atomic - Atomically replace the given spte with an +* spte pointing to the provided page table. +* +* @kvm: kvm instance +* @iter: a tdp_iter instance currently on the SPTE that should be set +* @sp: The new TDP page table to install. +* @account_nx: True if this page table is being installed to split a +* non-executable huge page. +* +* Returns: True if the new page table was installed. False if spte being +* replaced changed, causing the atomic compare-exchange to fail. +* If this function returns false the sp will be freed before arch/x86/kvm/mmu/tdp_mmu.c static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu, · line 970
Quoted 10 lines
arch/x86/kvm/mmu/tdp_mmu.c +10
-0+* returning. +*/ +static bool tdp_mmu_install_sp_atomic (struct kvm *kvm, +struct tdp_iter *iter, +struct kvm_mmu_page *sp, +bool account_nx) +{ +u64 spte; + + spte =make_nonleaf_spte (sp->spt, !shadow_accessed_mask);This can easily go on one line.
u64 spte = make_nonleaf_spte(sp->spt, !shadow_accessed_mask);arch/x86/kvm/mmu/tdp_mmu.c static int tdp_mmu_map_handle_target_level(struct kvm_vcpu *vcpu, · line 977
Quoted 7 lines
arch/x86/kvm/mmu/tdp_mmu.c +7
-0+ +if (tdp_mmu_set_spte_atomic (kvm, iter, spte)) { +tdp_mmu_link_page (kvm, sp, account_nx); +return true; + }else { +tdp_mmu_free_sp (sp); +return false;I don't think this helper should free the sp on failure, even if that's what all paths end up doing. When reading the calling code, it really looks like the sp is being leaked because the allocation and free are in different contexts. That the sp is consumed on success is fairly intuitive given the "install" action, but freeing on failure not so much.
Quoted 4 lines
And for the eager splitting, freeing on failure is wasteful. It's extremely unlikely to happen often, so in practice it's unlikely to be an issue, but it's certainly odd since the loop is likely going to immediately allocate another sp, either for the current spte or for the next spte.
Good point. I'll fix this in v1.
Quoted 3 lines
Side topic,
tdp_mmu_set_spte_atomic()and friends really should return 0/-EBUSY. Boolean returns for errors usually end in tears sooner or later.
Agreed. I was sticking with local style here but would like to see more of this code switch to returning ints. I'll take a look at including that cleanup as well in v1, if not a separate pre-series.
RFC PATCH 5/15 KVM: x86/mmu: Abstract mmu caches out to a separate struct
In reply to David MatlackMove the kvm_mmu_memory_cache structs into a separate wrapper struct. This is in preparation for eagerly splitting all large pages during VM-ioctls (i.e. not in the vCPU fault path) which will require adding kvm_mmu_memory_cache structs to struct kvm_arch.
--- arch/x86/include/asm/kvm_host.h | 12 ++++--- arch/x86/kvm/mmu/mmu.c | 59 ++++++++++++++++++++++----------- arch/x86/kvm/mmu/tdp_mmu.c | 7 ++-- 3 files changed, 52 insertions(+), 26 deletions(-)
arch/x86/include/asm/kvm_host.h +8 -4
@@ -612,6 +612,13 @@ struct kvm_vcpu_xen {u64 runstate_times[4 ]; }; +struct kvm_mmu_memory_caches { +struct kvm_mmu_memory_cache pte_list_desc_cache; +struct kvm_mmu_memory_cache shadow_page_cache; +struct kvm_mmu_memory_cache gfn_array_cache; +struct kvm_mmu_memory_cache page_header_cache; +}; +struct kvm_vcpu_arch {/* * rip and regs accesses must go through
@@ -681,10 +688,7 @@ struct kvm_vcpu_arch {*/ struct kvm_mmu *walk_mmu; -struct kvm_mmu_memory_cache mmu_pte_list_desc_cache; -struct kvm_mmu_memory_cache mmu_shadow_page_cache; -struct kvm_mmu_memory_cache mmu_gfn_array_cache; -struct kvm_mmu_memory_cache mmu_page_header_cache; +struct kvm_mmu_memory_caches mmu_caches;/* * QEMU userspace and the guest each have their own FPU state.
arch/x86/kvm/mmu/mmu.c +39 -20
109 lines not on this page · raw message
arch/x86/kvm/mmu/tdp_mmu.c +5 -2
@@ -175,10 +175,13 @@ static union kvm_mmu_page_role page_role_for_level(struct kvm_vcpu *vcpu,static struct kvm_mmu_page *alloc_tdp_mmu_page (struct kvm_vcpu *vcpu,gfn_t gfn,int level) { +struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - sp =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_page_header_cache); - sp->spt =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_shadow_page_cache); + mmu_caches = &vcpu->arch.mmu_caches; + + sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); + sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp); sp->role.word =page_role_for_level (vcpu, level).word;
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 05/15] KVM: x86/mmu: Abstract mmu caches out to a separate struct
Quoted 7 lines · David Matlack
Move the
kvm_mmu_memory_cachestructs into a separate wrapper struct. This is in preparation for eagerly splitting all large pages during VM-ioctls (i.e. not in the vCPU fault path) which will require addingkvm_mmu_memory_cachestructs to structkvm_arch.Signed-off-by David Matlack <[email protected]>
I don't think this patch creates any functional change. If that's the intent, it'd be worth noting.
Quoted 176 lines
--- arch/x86/include/asm/kvm_host.h | 12 ++++--- arch/x86/kvm/mmu/mmu.c | 59 ++++++++++++++++++++++----------- arch/x86/kvm/mmu/tdp_mmu.c | 7 ++-- 3 files changed, 52 insertions(+), 26 deletions(-)arch/x86/include/asm/kvm_host.h +8
-4@@ -612,6 +612,13 @@ struct kvm_vcpu_xen {u64 runstate_times[4 ]; }; +struct kvm_mmu_memory_caches { +struct kvm_mmu_memory_cache pte_list_desc_cache; +struct kvm_mmu_memory_cache shadow_page_cache; +struct kvm_mmu_memory_cache gfn_array_cache; +struct kvm_mmu_memory_cache page_header_cache; +}; +struct kvm_vcpu_arch {/* * rip and regs accesses must go through @@ -681,10 +688,7 @@ struct kvm_vcpu_arch {*/ struct kvm_mmu *walk_mmu; -struct kvm_mmu_memory_cache mmu_pte_list_desc_cache; -struct kvm_mmu_memory_cache mmu_shadow_page_cache; -struct kvm_mmu_memory_cache mmu_gfn_array_cache; -struct kvm_mmu_memory_cache mmu_page_header_cache; +struct kvm_mmu_memory_caches mmu_caches;/* * QEMU userspace and the guest each have their own FPU state. arch/x86/kvm/mmu/mmu.c +39
-20@@ -732,38 +732,60 @@ static void walk_shadow_page_lockless_end(struct kvm_vcpu *vcpu)static int mmu_topup_memory_caches (struct kvm_vcpu *vcpu,bool maybe_indirect) { +struct kvm_mmu_memory_caches *mmu_caches;int r; + mmu_caches = &vcpu->arch.mmu_caches; +/* 1 rmap, 1 parent PTE per level, and the prefetched rmaps. */ - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_pte_list_desc_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->pte_list_desc_cache,1 +PT64_ROOT_MAX_LEVEL +PTE_PREFETCH_NUM );if (r)return r; - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_shadow_page_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->shadow_page_cache,PT64_ROOT_MAX_LEVEL );if (r)return r;if (maybe_indirect) { - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_gfn_array_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->gfn_array_cache,PT64_ROOT_MAX_LEVEL );if (r)return r; } -return kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_page_header_cache, +return kvm_mmu_topup_memory_cache (&mmu_caches->page_header_cache,PT64_ROOT_MAX_LEVEL ); }static void mmu_free_memory_caches (struct kvm_vcpu *vcpu) { -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_pte_list_desc_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_shadow_page_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_gfn_array_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_page_header_cache); +struct kvm_mmu_memory_caches *mmu_caches; + + mmu_caches = &vcpu->arch.mmu_caches; + +kvm_mmu_free_memory_cache (&mmu_caches->pte_list_desc_cache); +kvm_mmu_free_memory_cache (&mmu_caches->shadow_page_cache); +kvm_mmu_free_memory_cache (&mmu_caches->gfn_array_cache); +kvm_mmu_free_memory_cache (&mmu_caches->page_header_cache); +} + +static void mmu_init_memory_caches (struct kvm_mmu_memory_caches *caches) +{ + caches->pte_list_desc_cache.kmem_cache = pte_list_desc_cache; + caches->pte_list_desc_cache.gfp_zero = __GFP_ZERO; + + caches->page_header_cache.kmem_cache = mmu_page_header_cache; + caches->page_header_cache.gfp_zero = __GFP_ZERO; + + caches->shadow_page_cache.gfp_zero = __GFP_ZERO; }static struct pte_list_desc *mmu_alloc_pte_list_desc (struct kvm_vcpu *vcpu) { -return kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_pte_list_desc_cache); +struct kvm_mmu_memory_caches *mmu_caches; + + mmu_caches = &vcpu->arch.mmu_caches; + +return kvm_mmu_memory_cache_alloc (&mmu_caches->pte_list_desc_cache); }static void mmu_free_pte_list_desc (struct pte_list_desc *pte_list_desc)@@ -1071,7 +1093,7 @@ static bool rmap_can_add(struct kvm_vcpu *vcpu) {struct kvm_mmu_memory_cache *mc; - mc = &vcpu->arch.mmu_pte_list_desc_cache; + mc = &vcpu->arch.mmu_caches.pte_list_desc_cache;return kvm_mmu_memory_cache_nr_free_objects (mc); }@@ -1742,12 +1764,15 @@ static void drop_parent_pte(struct kvm_mmu_page *sp,static struct kvm_mmu_page *kvm_mmu_alloc_page (struct kvm_vcpu *vcpu,int direct) { +struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - sp =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_page_header_cache); - sp->spt =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_shadow_page_cache); + mmu_caches = &vcpu->arch.mmu_caches; + + sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); + sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);if (!direct) - sp->gfns =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_gfn_array_cache); + sp->gfns =kvm_mmu_memory_cache_alloc (&mmu_caches->gfn_array_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp);/* @@ -5544,13 +5569,7 @@ int kvm_mmu_create(struct kvm_vcpu *vcpu) {int ret; - vcpu->arch.mmu_pte_list_desc_cache.kmem_cache = pte_list_desc_cache; - vcpu->arch.mmu_pte_list_desc_cache.gfp_zero = __GFP_ZERO; - - vcpu->arch.mmu_page_header_cache.kmem_cache = mmu_page_header_cache; - vcpu->arch.mmu_page_header_cache.gfp_zero = __GFP_ZERO; - - vcpu->arch.mmu_shadow_page_cache.gfp_zero = __GFP_ZERO; +mmu_init_memory_caches (&vcpu->arch.mmu_caches); vcpu->arch.mmu = &vcpu->arch.root_mmu; vcpu->arch.walk_mmu = &vcpu->arch.root_mmu;arch/x86/kvm/mmu/tdp_mmu.c +5
-3@@ -175,10 +175,13 @@ static union kvm_mmu_page_role page_role_for_level(struct kvm_vcpu *vcpu,static struct kvm_mmu_page *alloc_tdp_mmu_page (struct kvm_vcpu *vcpu,gfn_t gfn,int level) { +struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - sp =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_page_header_cache); - sp->spt =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_shadow_page_cache); + mmu_caches = &vcpu->arch.mmu_caches; + + sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); + sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp); sp->role.word =page_role_for_level (vcpu, level).word; --2.34.0.rc2.393.gf8c9666880-goog
Ben Gardon
Reviewed-byRe: [RFC PATCH 05/15] KVM: x86/mmu: Abstract mmu caches out to a separate struct
Quoted 11 lines · Ben Gardon
Quoted 7 lines · David Matlack
Move the
kvm_mmu_memory_cachestructs into a separate wrapper struct. This is in preparation for eagerly splitting all large pages during VM-ioctls (i.e. not in the vCPU fault path) which will require addingkvm_mmu_memory_cachestructs to structkvm_arch.Signed-off-by David Matlack <[email protected]>Reviewed-by Ben Gardon
Woops
Quoted 181 lines
I don't think this patch creates any functional change. If that's the intent, it'd be worth noting.
Quoted 176 lines
--- arch/x86/include/asm/kvm_host.h | 12 ++++--- arch/x86/kvm/mmu/mmu.c | 59 ++++++++++++++++++++++----------- arch/x86/kvm/mmu/tdp_mmu.c | 7 ++-- 3 files changed, 52 insertions(+), 26 deletions(-)arch/x86/include/asm/kvm_host.h +8
-4@@ -612,6 +612,13 @@ struct kvm_vcpu_xen {u64 runstate_times[4 ]; }; +struct kvm_mmu_memory_caches { +struct kvm_mmu_memory_cache pte_list_desc_cache; +struct kvm_mmu_memory_cache shadow_page_cache; +struct kvm_mmu_memory_cache gfn_array_cache; +struct kvm_mmu_memory_cache page_header_cache; +}; +struct kvm_vcpu_arch {/* * rip and regs accesses must go through @@ -681,10 +688,7 @@ struct kvm_vcpu_arch {*/ struct kvm_mmu *walk_mmu; -struct kvm_mmu_memory_cache mmu_pte_list_desc_cache; -struct kvm_mmu_memory_cache mmu_shadow_page_cache; -struct kvm_mmu_memory_cache mmu_gfn_array_cache; -struct kvm_mmu_memory_cache mmu_page_header_cache; +struct kvm_mmu_memory_caches mmu_caches;/* * QEMU userspace and the guest each have their own FPU state. arch/x86/kvm/mmu/mmu.c +39
-20@@ -732,38 +732,60 @@ static void walk_shadow_page_lockless_end(struct kvm_vcpu *vcpu)static int mmu_topup_memory_caches (struct kvm_vcpu *vcpu,bool maybe_indirect) { +struct kvm_mmu_memory_caches *mmu_caches;int r; + mmu_caches = &vcpu->arch.mmu_caches; +/* 1 rmap, 1 parent PTE per level, and the prefetched rmaps. */ - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_pte_list_desc_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->pte_list_desc_cache,1 +PT64_ROOT_MAX_LEVEL +PTE_PREFETCH_NUM );if (r)return r; - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_shadow_page_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->shadow_page_cache,PT64_ROOT_MAX_LEVEL );if (r)return r;if (maybe_indirect) { - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_gfn_array_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->gfn_array_cache,PT64_ROOT_MAX_LEVEL );if (r)return r; } -return kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_page_header_cache, +return kvm_mmu_topup_memory_cache (&mmu_caches->page_header_cache,PT64_ROOT_MAX_LEVEL ); }static void mmu_free_memory_caches (struct kvm_vcpu *vcpu) { -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_pte_list_desc_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_shadow_page_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_gfn_array_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_page_header_cache); +struct kvm_mmu_memory_caches *mmu_caches; + + mmu_caches = &vcpu->arch.mmu_caches; + +kvm_mmu_free_memory_cache (&mmu_caches->pte_list_desc_cache); +kvm_mmu_free_memory_cache (&mmu_caches->shadow_page_cache); +kvm_mmu_free_memory_cache (&mmu_caches->gfn_array_cache); +kvm_mmu_free_memory_cache (&mmu_caches->page_header_cache); +} + +static void mmu_init_memory_caches (struct kvm_mmu_memory_caches *caches) +{ + caches->pte_list_desc_cache.kmem_cache = pte_list_desc_cache; + caches->pte_list_desc_cache.gfp_zero = __GFP_ZERO; + + caches->page_header_cache.kmem_cache = mmu_page_header_cache; + caches->page_header_cache.gfp_zero = __GFP_ZERO; + + caches->shadow_page_cache.gfp_zero = __GFP_ZERO; }static struct pte_list_desc *mmu_alloc_pte_list_desc (struct kvm_vcpu *vcpu) { -return kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_pte_list_desc_cache); +struct kvm_mmu_memory_caches *mmu_caches; + + mmu_caches = &vcpu->arch.mmu_caches; + +return kvm_mmu_memory_cache_alloc (&mmu_caches->pte_list_desc_cache); }static void mmu_free_pte_list_desc (struct pte_list_desc *pte_list_desc)@@ -1071,7 +1093,7 @@ static bool rmap_can_add(struct kvm_vcpu *vcpu) {struct kvm_mmu_memory_cache *mc; - mc = &vcpu->arch.mmu_pte_list_desc_cache; + mc = &vcpu->arch.mmu_caches.pte_list_desc_cache;return kvm_mmu_memory_cache_nr_free_objects (mc); }@@ -1742,12 +1764,15 @@ static void drop_parent_pte(struct kvm_mmu_page *sp,static struct kvm_mmu_page *kvm_mmu_alloc_page (struct kvm_vcpu *vcpu,int direct) { +struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - sp =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_page_header_cache); - sp->spt =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_shadow_page_cache); + mmu_caches = &vcpu->arch.mmu_caches; + + sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); + sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);if (!direct) - sp->gfns =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_gfn_array_cache); + sp->gfns =kvm_mmu_memory_cache_alloc (&mmu_caches->gfn_array_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp);/* @@ -5544,13 +5569,7 @@ int kvm_mmu_create(struct kvm_vcpu *vcpu) {int ret; - vcpu->arch.mmu_pte_list_desc_cache.kmem_cache = pte_list_desc_cache; - vcpu->arch.mmu_pte_list_desc_cache.gfp_zero = __GFP_ZERO; - - vcpu->arch.mmu_page_header_cache.kmem_cache = mmu_page_header_cache; - vcpu->arch.mmu_page_header_cache.gfp_zero = __GFP_ZERO; - - vcpu->arch.mmu_shadow_page_cache.gfp_zero = __GFP_ZERO; +mmu_init_memory_caches (&vcpu->arch.mmu_caches); vcpu->arch.mmu = &vcpu->arch.root_mmu; vcpu->arch.walk_mmu = &vcpu->arch.root_mmu;arch/x86/kvm/mmu/tdp_mmu.c +5
-3@@ -175,10 +175,13 @@ static union kvm_mmu_page_role page_role_for_level(struct kvm_vcpu *vcpu,static struct kvm_mmu_page *alloc_tdp_mmu_page (struct kvm_vcpu *vcpu,gfn_t gfn,int level) { +struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - sp =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_page_header_cache); - sp->spt =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_shadow_page_cache); + mmu_caches = &vcpu->arch.mmu_caches; + + sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); + sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp); sp->role.word =page_role_for_level (vcpu, level).word; --2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 05/15] KVM: x86/mmu: Abstract mmu caches out to a separate struct
In reply to Ben GardonQuoted 8 lines · Ben Gardon
Quoted 6 lines · David Matlack
Move the
kvm_mmu_memory_cachestructs into a separate wrapper struct. This is in preparation for eagerly splitting all large pages during VM-ioctls (i.e. not in the vCPU fault path) which will require addingkvm_mmu_memory_cachestructs to structkvm_arch.
Quoted 6 lines
Quoted 1 line
Signed-off-by David Matlack <[email protected]>Reviewed-by Ben GardonI don't think this patch creates any functional change. If that's the intent, it'd be worth noting.
Will do!
Quoted 178 lines
Quoted 178 lines
--- arch/x86/include/asm/kvm_host.h | 12 ++++--- arch/x86/kvm/mmu/mmu.c | 59 ++++++++++++++++++++++----------- arch/x86/kvm/mmu/tdp_mmu.c | 7 ++-- 3 files changed, 52 insertions(+), 26 deletions(-)arch/x86/include/asm/kvm_host.h +8
-4@@ -612,6 +612,13 @@ struct kvm_vcpu_xen {u64 runstate_times[4 ]; }; +struct kvm_mmu_memory_caches { +struct kvm_mmu_memory_cache pte_list_desc_cache; +struct kvm_mmu_memory_cache shadow_page_cache; +struct kvm_mmu_memory_cache gfn_array_cache; +struct kvm_mmu_memory_cache page_header_cache; +}; +struct kvm_vcpu_arch {/* * rip and regs accesses must go through @@ -681,10 +688,7 @@ struct kvm_vcpu_arch {*/ struct kvm_mmu *walk_mmu; -struct kvm_mmu_memory_cache mmu_pte_list_desc_cache; -struct kvm_mmu_memory_cache mmu_shadow_page_cache; -struct kvm_mmu_memory_cache mmu_gfn_array_cache; -struct kvm_mmu_memory_cache mmu_page_header_cache; +struct kvm_mmu_memory_caches mmu_caches;/* * QEMU userspace and the guest each have their own FPU state. arch/x86/kvm/mmu/mmu.c +39
-20@@ -732,38 +732,60 @@ static void walk_shadow_page_lockless_end(struct kvm_vcpu *vcpu)static int mmu_topup_memory_caches (struct kvm_vcpu *vcpu,bool maybe_indirect) { +struct kvm_mmu_memory_caches *mmu_caches;int r; + mmu_caches = &vcpu->arch.mmu_caches; +/* 1 rmap, 1 parent PTE per level, and the prefetched rmaps. */ - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_pte_list_desc_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->pte_list_desc_cache,1 +PT64_ROOT_MAX_LEVEL +PTE_PREFETCH_NUM );if (r)return r; - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_shadow_page_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->shadow_page_cache,PT64_ROOT_MAX_LEVEL );if (r)return r;if (maybe_indirect) { - r =kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_gfn_array_cache, + r =kvm_mmu_topup_memory_cache (&mmu_caches->gfn_array_cache,PT64_ROOT_MAX_LEVEL );if (r)return r; } -return kvm_mmu_topup_memory_cache (&vcpu->arch.mmu_page_header_cache, +return kvm_mmu_topup_memory_cache (&mmu_caches->page_header_cache,PT64_ROOT_MAX_LEVEL ); }static void mmu_free_memory_caches (struct kvm_vcpu *vcpu) { -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_pte_list_desc_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_shadow_page_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_gfn_array_cache); -kvm_mmu_free_memory_cache (&vcpu->arch.mmu_page_header_cache); +struct kvm_mmu_memory_caches *mmu_caches; + + mmu_caches = &vcpu->arch.mmu_caches; + +kvm_mmu_free_memory_cache (&mmu_caches->pte_list_desc_cache); +kvm_mmu_free_memory_cache (&mmu_caches->shadow_page_cache); +kvm_mmu_free_memory_cache (&mmu_caches->gfn_array_cache); +kvm_mmu_free_memory_cache (&mmu_caches->page_header_cache); +} + +static void mmu_init_memory_caches (struct kvm_mmu_memory_caches *caches) +{ + caches->pte_list_desc_cache.kmem_cache = pte_list_desc_cache; + caches->pte_list_desc_cache.gfp_zero = __GFP_ZERO; + + caches->page_header_cache.kmem_cache = mmu_page_header_cache; + caches->page_header_cache.gfp_zero = __GFP_ZERO; + + caches->shadow_page_cache.gfp_zero = __GFP_ZERO; }static struct pte_list_desc *mmu_alloc_pte_list_desc (struct kvm_vcpu *vcpu) { -return kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_pte_list_desc_cache); +struct kvm_mmu_memory_caches *mmu_caches; + + mmu_caches = &vcpu->arch.mmu_caches; + +return kvm_mmu_memory_cache_alloc (&mmu_caches->pte_list_desc_cache); }static void mmu_free_pte_list_desc (struct pte_list_desc *pte_list_desc)@@ -1071,7 +1093,7 @@ static bool rmap_can_add(struct kvm_vcpu *vcpu) {struct kvm_mmu_memory_cache *mc; - mc = &vcpu->arch.mmu_pte_list_desc_cache; + mc = &vcpu->arch.mmu_caches.pte_list_desc_cache;return kvm_mmu_memory_cache_nr_free_objects (mc); }@@ -1742,12 +1764,15 @@ static void drop_parent_pte(struct kvm_mmu_page *sp,static struct kvm_mmu_page *kvm_mmu_alloc_page (struct kvm_vcpu *vcpu,int direct) { +struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - sp =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_page_header_cache); - sp->spt =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_shadow_page_cache); + mmu_caches = &vcpu->arch.mmu_caches; + + sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); + sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);if (!direct) - sp->gfns =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_gfn_array_cache); + sp->gfns =kvm_mmu_memory_cache_alloc (&mmu_caches->gfn_array_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp);/* @@ -5544,13 +5569,7 @@ int kvm_mmu_create(struct kvm_vcpu *vcpu) {int ret; - vcpu->arch.mmu_pte_list_desc_cache.kmem_cache = pte_list_desc_cache; - vcpu->arch.mmu_pte_list_desc_cache.gfp_zero = __GFP_ZERO; - - vcpu->arch.mmu_page_header_cache.kmem_cache = mmu_page_header_cache; - vcpu->arch.mmu_page_header_cache.gfp_zero = __GFP_ZERO; - - vcpu->arch.mmu_shadow_page_cache.gfp_zero = __GFP_ZERO; +mmu_init_memory_caches (&vcpu->arch.mmu_caches); vcpu->arch.mmu = &vcpu->arch.root_mmu; vcpu->arch.walk_mmu = &vcpu->arch.root_mmu;arch/x86/kvm/mmu/tdp_mmu.c +5
-3@@ -175,10 +175,13 @@ static union kvm_mmu_page_role page_role_for_level(struct kvm_vcpu *vcpu,static struct kvm_mmu_page *alloc_tdp_mmu_page (struct kvm_vcpu *vcpu,gfn_t gfn,int level) { +struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - sp =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_page_header_cache); - sp->spt =kvm_mmu_memory_cache_alloc (&vcpu->arch.mmu_shadow_page_cache); + mmu_caches = &vcpu->arch.mmu_caches; + + sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); + sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp); sp->role.word =page_role_for_level (vcpu, level).word; --2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 6/15 KVM: x86/mmu: Derive page role from parent
In reply to David MatlackDerive the page role from the parent shadow page, since the only thing that changes is the level. This is in preparation for eagerly splitting large pages during VM-ioctls which does not have access to the vCPU MMU context.
No functional change intended.
--- arch/x86/kvm/mmu/tdp_mmu.c | 43 ++++++++++++++++++++------------------ 1 file changed, 23 insertions(+), 20 deletions(-)
arch/x86/kvm/mmu/tdp_mmu.c +23 -20
@@ -157,23 +157,8 @@ static struct kvm_mmu_page *tdp_mmu_next_root(struct kvm *kvm,if (kvm_mmu_page_as_id (_root) != _as_id) { \ }else -static union kvm_mmu_page_role page_role_for_level(struct kvm_vcpu *vcpu, -int level) -{ -union kvm_mmu_page_role role; - - role = vcpu->arch.mmu->mmu_role.base; - role.level = level; - role.direct = true; - role.gpte_is_8_bytes = true; - role.access =ACC_ALL ; - role.ad_disabled = !shadow_accessed_mask; - -return role; -} - static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, -int level) +union kvm_mmu_page_role role) {struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp;
@@ -184,7 +169,7 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp); - sp->role.word =page_role_for_level (vcpu, level).word; + sp->role = role; sp->gfn = gfn; sp->tdp_mmu_page = true;
@@ -193,6 +178,19 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn,return sp; } +static struct kvm_mmu_page *alloc_child_tdp_mmu_page (struct kvm_vcpu *vcpu,struct tdp_iter *iter) +{ +struct kvm_mmu_page *parent_sp; +union kvm_mmu_page_role role; + + parent_sp =sptep_to_sp (rcu_dereference (iter->sptep)); + + role = parent_sp->role; + role.level--; + +return alloc_tdp_mmu_page (vcpu, iter->gfn, role); +} +hpa_t kvm_tdp_mmu_get_vcpu_root_hpa (struct kvm_vcpu *vcpu) {union kvm_mmu_page_role role;
@@ -201,7 +199,12 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu)lockdep_assert_held_write (&kvm->mmu_lock); - role =page_role_for_level (vcpu, vcpu->arch.mmu->shadow_root_level); + role = vcpu->arch.mmu->mmu_role.base; + role.level = vcpu->arch.mmu->shadow_root_level; + role.direct = true; + role.gpte_is_8_bytes = true; + role.access =ACC_ALL ; + role.ad_disabled = !shadow_accessed_mask;/* Check for an existing root before allocating a new one. */ for_each_tdp_mmu_root (kvm, root,kvm_mmu_role_as_id (role)) {
@@ -210,7 +213,7 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu) goto out; } - root =alloc_tdp_mmu_page (vcpu,0 , vcpu->arch.mmu->shadow_root_level); + root =alloc_tdp_mmu_page (vcpu,0 , role);refcount_set (&root->tdp_mmu_root_count,1 );spin_lock (&kvm->arch.tdp_mmu_pages_lock);
@@ -1028,7 +1031,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)if (is_removed_spte (iter.old_spte))break ; - sp =alloc_tdp_mmu_page (vcpu, iter.gfn, iter.level -1 ); + sp =alloc_child_tdp_mmu_page (vcpu, &iter);if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; }
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Paolo Bonzini
maintainerRe: [RFC PATCH 06/15] KVM: x86/mmu: Derive page role from parent
Quoted 71 lines · David Matlack
Derive the page role from the parent shadow page, since the only thing that changes is the level. This is in preparation for eagerly splitting large pages during VM-ioctls which does not have access to the vCPU MMU context.
No functional change intended.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 43 ++++++++++++++++++++------------------ 1 file changed, 23 insertions(+), 20 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +15
-17@@ -157,23 +157,8 @@ static struct kvm_mmu_page *tdp_mmu_next_root(struct kvm *kvm,if (kvm_mmu_page_as_id (_root) != _as_id) { \ }else -static union kvm_mmu_page_role page_role_for_level(struct kvm_vcpu *vcpu, -int level) -{ -union kvm_mmu_page_role role; - - role = vcpu->arch.mmu->mmu_role.base; - role.level = level; - role.direct = true; - role.gpte_is_8_bytes = true; - role.access =ACC_ALL ; - role.ad_disabled = !shadow_accessed_mask; - -return role; -} - static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, -int level) +union kvm_mmu_page_role role) {struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp;@@ -184,7 +169,7 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp); - sp->role.word =page_role_for_level (vcpu, level).word; + sp->role = role; sp->gfn = gfn; sp->tdp_mmu_page = true;@@ -193,6 +178,19 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn,return sp; } +static struct kvm_mmu_page *alloc_child_tdp_mmu_page (struct kvm_vcpu *vcpu,struct tdp_iter *iter) +{ +struct kvm_mmu_page *parent_sp; +union kvm_mmu_page_role role; + + parent_sp =sptep_to_sp (rcu_dereference (iter->sptep)); + + role = parent_sp->role; + role.level--; + +return alloc_tdp_mmu_page (vcpu, iter->gfn, role); +} +hpa_t kvm_tdp_mmu_get_vcpu_root_hpa (struct kvm_vcpu *vcpu) {union kvm_mmu_page_role role;
arch/x86/kvm/mmu/tdp_mmu.c hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu) · line 207
Quoted 10 lines
arch/x86/kvm/mmu/tdp_mmu.c +6
-1@@ -201,7 +199,12 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu)lockdep_assert_held_write (&kvm->mmu_lock); - role =page_role_for_level (vcpu, vcpu->arch.mmu->shadow_root_level); + role = vcpu->arch.mmu->mmu_role.base; + role.level = vcpu->arch.mmu->shadow_root_level; + role.direct = true; + role.gpte_is_8_bytes = true; + role.access =ACC_ALL ; + role.ad_disabled = !shadow_accessed_mask;
I have a similar patch for the old MMU, but it was also replacing shadow_root_level with shadow_root_role. I'll see if I can adapt it to the TDP MMU, since the shadow_root_role is obviously the same for both.
Paolo
Quoted 21 lines
arch/x86/kvm/mmu/tdp_mmu.c +2
-2/* Check for an existing root before allocating a new one. */ for_each_tdp_mmu_root (kvm, root,kvm_mmu_role_as_id (role)) {@@ -210,7 +213,7 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu) goto out; } - root =alloc_tdp_mmu_page (vcpu,0 , vcpu->arch.mmu->shadow_root_level); + root =alloc_tdp_mmu_page (vcpu,0 , role);refcount_set (&root->tdp_mmu_root_count,1 );spin_lock (&kvm->arch.tdp_mmu_pages_lock);@@ -1028,7 +1031,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)if (is_removed_spte (iter.old_spte))break ; - sp =alloc_tdp_mmu_page (vcpu, iter.gfn, iter.level -1 ); + sp =alloc_child_tdp_mmu_page (vcpu, &iter);if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; }
Re: [RFC PATCH 06/15] KVM: x86/mmu: Derive page role from parent
Quoted 5 lines · Paolo Bonzini
I have a similar patch for the old MMU, but it was also replacing
shadow_root_levelwithshadow_root_role. I'll see if I can adapt it to the TDP MMU, since theshadow_root_roleis obviously the same for both.
Hello, Paolo
I'm sorry to ask something unrelated to this patchset, but related to my pending work.
I will still continue to do something on shadow_root_level. But I would like to wait until your shadow_root_role work is queued. And is it a part of work splitting the struct kvm_mmu?
Thanks
Lai
Paolo Bonzini
maintainerRe: [RFC PATCH 06/15] KVM: x86/mmu: Derive page role from parent
Quoted 8 lines · Lai Jiangshan
Quoted 5 lines · Paolo Bonzini
I have a similar patch for the old MMU, but it was also replacing
shadow_root_levelwithshadow_root_role. I'll see if I can adapt it to the TDP MMU, since theshadow_root_roleis obviously the same for both.
Quoted 8 lines
Hello, Paolo
I'm sorry to ask something unrelated to this patchset, but related to my pending work.
I will still continue to do something on
shadow_root_level. But I would like to wait until yourshadow_root_rolework is queued. And is it a part of work splitting the structkvm_mmu?
Yes, more or less. I'm basically splitting the "CPU role" (the basic and extended role from the processor registers) used for emulation, from the "MMU role" (the basic role used for the root shadow page tables). Then shadow_root_level/root_level become respectively mmu_role->level and cpu_role->base.level.
Paolo
Re: [RFC PATCH 06/15] KVM: x86/mmu: Derive page role from parent
In reply to Paolo BonziniQuoted 76 lines · Paolo Bonzini
Quoted 74 lines · David Matlack
Derive the page role from the parent shadow page, since the only thing that changes is the level. This is in preparation for eagerly splitting large pages during VM-ioctls which does not have access to the vCPU MMU context.
No functional change intended.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 43 ++++++++++++++++++++------------------ 1 file changed, 23 insertions(+), 20 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +15
-17@@ -157,23 +157,8 @@ static struct kvm_mmu_page *tdp_mmu_next_root(struct kvm *kvm,if (kvm_mmu_page_as_id (_root) != _as_id) { \ }else -static union kvm_mmu_page_role page_role_for_level(struct kvm_vcpu *vcpu, -int level) -{ -union kvm_mmu_page_role role; - - role = vcpu->arch.mmu->mmu_role.base; - role.level = level; - role.direct = true; - role.gpte_is_8_bytes = true; - role.access =ACC_ALL ; - role.ad_disabled = !shadow_accessed_mask; - -return role; -} - static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, -int level) +union kvm_mmu_page_role role) {struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp;@@ -184,7 +169,7 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp); - sp->role.word =page_role_for_level (vcpu, level).word; + sp->role = role; sp->gfn = gfn; sp->tdp_mmu_page = true;@@ -193,6 +178,19 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn,return sp; } +static struct kvm_mmu_page *alloc_child_tdp_mmu_page (struct kvm_vcpu *vcpu,struct tdp_iter *iter) +{ +struct kvm_mmu_page *parent_sp; +union kvm_mmu_page_role role; + + parent_sp =sptep_to_sp (rcu_dereference (iter->sptep)); + + role = parent_sp->role; + role.level--; + +return alloc_tdp_mmu_page (vcpu, iter->gfn, role); +} +hpa_t kvm_tdp_mmu_get_vcpu_root_hpa (struct kvm_vcpu *vcpu) {union kvm_mmu_page_role role;@@ -201,7 +199,12 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu)lockdep_assert_held_write (&kvm->mmu_lock);
Quoted 11 lines
arch/x86/kvm/mmu/tdp_mmu.c hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu) · line 207
Quoted 7 lines
arch/x86/kvm/mmu/tdp_mmu.c +6
-1- role =page_role_for_level (vcpu, vcpu->arch.mmu->shadow_root_level); + role = vcpu->arch.mmu->mmu_role.base; + role.level = vcpu->arch.mmu->shadow_root_level; + role.direct = true; + role.gpte_is_8_bytes = true; + role.access =ACC_ALL ; + role.ad_disabled = !shadow_accessed_mask;I have a similar patch for the old MMU, but it was also replacing
shadow_root_levelwithshadow_root_role. I'll see if I can adapt it to the TDP MMU, since theshadow_root_roleis obviously the same for both.
While I was writing this patch it got me wondering if we can do an even more general refactor and replace root_hpa and shadow_root_level with a pointer to the root kvm_mmu_page struct. But I didn't get a chance to look into it further.
Quoted 24 lines
Paolo
Quoted 21 lines
arch/x86/kvm/mmu/tdp_mmu.c +2
-2/* Check for an existing root before allocating a new one. */ for_each_tdp_mmu_root (kvm, root,kvm_mmu_role_as_id (role)) {@@ -210,7 +213,7 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu) goto out; } - root =alloc_tdp_mmu_page (vcpu,0 , vcpu->arch.mmu->shadow_root_level); + root =alloc_tdp_mmu_page (vcpu,0 , role);refcount_set (&root->tdp_mmu_root_count,1 );spin_lock (&kvm->arch.tdp_mmu_pages_lock);@@ -1028,7 +1031,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)if (is_removed_spte (iter.old_spte))break ; - sp =alloc_tdp_mmu_page (vcpu, iter.gfn, iter.level -1 ); + sp =alloc_child_tdp_mmu_page (vcpu, &iter);if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; }
Sean Christopherson
maintainerRe: [RFC PATCH 06/15] KVM: x86/mmu: Derive page role from parent
Quoted 8 lines · David Matlack
Quoted 3 lines
I have a similar patch for the old MMU, but it was also replacing
shadow_root_levelwithshadow_root_role. I'll see if I can adapt it to the TDP MMU, since theshadow_root_roleis obviously the same for both.While I was writing this patch it got me wondering if we can do an even more general refactor and replace
root_hpaandshadow_root_levelwith a pointer to the rootkvm_mmu_pagestruct. But I didn't get a chance to look into it further.
For TDP MUU, yes, as root_hpa == __pa(sp->spt) in all cases. For the legacy/full MMU, not without additional refactoring since root_hpa doesn't point at a kvm_mmu_page when KVM shadows a non-paging guest with PAE paging (uses pae_root), or when KVM shadows nested NPT and the guest is using fewer paging levels that the host (uses pml5_root or pml4_root).
if (mmu->shadow_root_level == PT64_ROOT_5LEVEL) mmu->root_hpa = __pa(mmu->pml5_root); else if (mmu->shadow_root_level == PT64_ROOT_4LEVEL) mmu->root_hpa = __pa(mmu->pml4_root); else mmu->root_hpa = __pa(mmu->pae_root);
That's definitely a solvable problem, e.g. it wouldn't be a problem to burn a few kvm_mmu_page for the special root. The biggest issue is probably the sheer amount of code that would need to be updated. I do think it would be a good change, but I think we'd want to do it in a release that isn't expected to have many other MMU changes.
shadow_root_level can also be replaced by mmu_role.base.level. I've never bothered to do the replacement because there's zero memory savings and it would undoubtedly take me some time to retrain my brain :-)
Re: [RFC PATCH 06/15] KVM: x86/mmu: Derive page role from parent
Quoted 24 lines · Sean Christopherson
Quoted 8 lines · David Matlack
Quoted 3 lines
I have a similar patch for the old MMU, but it was also replacing
shadow_root_levelwithshadow_root_role. I'll see if I can adapt it to the TDP MMU, since theshadow_root_roleis obviously the same for both.While I was writing this patch it got me wondering if we can do an even more general refactor and replace
root_hpaandshadow_root_levelwith a pointer to the rootkvm_mmu_pagestruct. But I didn't get a chance to look into it further.For TDP MUU, yes, as
root_hpa==__pa(sp->spt)in all cases. For the legacy/full MMU, not without additional refactoring sinceroot_hpadoesn't point at akvm_mmu_pagewhen KVM shadows a non-paging guest with PAE paging (usespae_root), or when KVM shadows nested NPT and the guest is using fewer paging levels that the host (usespml5_rootorpml4_root).if (mmu->shadow_root_level == PT64_ROOT_5LEVEL) mmu->root_hpa = __pa(mmu->pml5_root); else if (mmu->shadow_root_level == PT64_ROOT_4LEVEL) mmu->root_hpa = __pa(mmu->pml4_root); else mmu->root_hpa = __pa(mmu->pae_root);
Quoted 5 lines
That's definitely a solvable problem, e.g. it wouldn't be a problem to burn a few
kvm_mmu_pagefor the special root. The biggest issue is probably the sheer amount of code that would need to be updated. I do think it would be a good change, but I think we'd want to do it in a release that isn't expected to have many other MMU changes.
Thanks for the explanation! I had a feeling this refactor would start getting hairy when I ventured outside of the TDP MMU.
Quoted 4 lines
shadow_root_levelcan also be replaced by mmu_role.base.level. I've never bothered to do the replacement because there's zero memory savings and it would undoubtedly take me some time to retrain my brain :-)
RFC PATCH 7/15 KVM: x86/mmu: Pass in vcpu->arch.mmu_caches instead of vcpu
In reply to David MatlackPass in vcpu->arch.mmu_caches to alloc_{,_child}_tdp_mmu_page() instead of the vcpu. This is in preparation for eagerly splitting large pages during VM-ioctls which does not have access to the vCPU mmu_caches.
No functional change intended.
--- arch/x86/kvm/mmu/tdp_mmu.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-)
arch/x86/kvm/mmu/tdp_mmu.c +7 -9
@@ -157,14 +157,11 @@ static struct kvm_mmu_page *tdp_mmu_next_root(struct kvm *kvm,if (kvm_mmu_page_as_id (_root) != _as_id) { \ }else -static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, -union kvm_mmu_page_role role) +static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_mmu_memory_caches *mmu_caches, +gfn_t gfn,union kvm_mmu_page_role role) { -struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - mmu_caches = &vcpu->arch.mmu_caches; - sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp);
@@ -178,7 +175,8 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn,return sp; } -static struct kvm_mmu_page *alloc_child_tdp_mmu_page (struct kvm_vcpu *vcpu,struct tdp_iter *iter) +static struct kvm_mmu_page *alloc_child_tdp_mmu_page (struct kvm_mmu_memory_caches *mmu_caches, +struct tdp_iter *iter) {struct kvm_mmu_page *parent_sp;union kvm_mmu_page_role role;
@@ -188,7 +186,7 @@ static struct kvm_mmu_page *alloc_child_tdp_mmu_page(struct kvm_vcpu *vcpu, stru role = parent_sp->role; role.level--; -return alloc_tdp_mmu_page (vcpu, iter->gfn, role); +return alloc_tdp_mmu_page (mmu_caches, iter->gfn, role); }hpa_t kvm_tdp_mmu_get_vcpu_root_hpa (struct kvm_vcpu *vcpu)
@@ -213,7 +211,7 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu) goto out; } - root =alloc_tdp_mmu_page (vcpu,0 , role); + root =alloc_tdp_mmu_page (&vcpu->arch.mmu_caches,0 , role);refcount_set (&root->tdp_mmu_root_count,1 );spin_lock (&kvm->arch.tdp_mmu_pages_lock);
@@ -1031,7 +1029,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)if (is_removed_spte (iter.old_spte))break ; - sp =alloc_child_tdp_mmu_page (vcpu, &iter); + sp =alloc_child_tdp_mmu_page (&vcpu->arch.mmu_caches, &iter);if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; }
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 07/15] KVM: x86/mmu: Pass in vcpu->arch.mmu_caches instead of vcpu
Quoted 8 lines · David Matlack
Pass in
vcpu->arch.mmu_cachesto alloc_{,_child}_tdp_mmu_page() instead of the vcpu. This is in preparation for eagerly splitting large pages during VM-ioctls which does not have access to the vCPUmmu_caches.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Quoted 65 lines
--- arch/x86/kvm/mmu/tdp_mmu.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +7
-10@@ -157,14 +157,11 @@ static struct kvm_mmu_page *tdp_mmu_next_root(struct kvm *kvm,if (kvm_mmu_page_as_id (_root) != _as_id) { \ }else -static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn, -union kvm_mmu_page_role role) +static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_mmu_memory_caches *mmu_caches, +gfn_t gfn,union kvm_mmu_page_role role) { -struct kvm_mmu_memory_caches *mmu_caches;struct kvm_mmu_page *sp; - mmu_caches = &vcpu->arch.mmu_caches; - sp =kvm_mmu_memory_cache_alloc (&mmu_caches->page_header_cache); sp->spt =kvm_mmu_memory_cache_alloc (&mmu_caches->shadow_page_cache);set_page_private (virt_to_page (sp->spt), (unsigned long )sp);@@ -178,7 +175,8 @@ static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn,return sp; } -static struct kvm_mmu_page *alloc_child_tdp_mmu_page (struct kvm_vcpu *vcpu,struct tdp_iter *iter) +static struct kvm_mmu_page *alloc_child_tdp_mmu_page (struct kvm_mmu_memory_caches *mmu_caches, +struct tdp_iter *iter) {struct kvm_mmu_page *parent_sp;union kvm_mmu_page_role role;@@ -188,7 +186,7 @@ static struct kvm_mmu_page *alloc_child_tdp_mmu_page(struct kvm_vcpu *vcpu, stru role = parent_sp->role; role.level--; -return alloc_tdp_mmu_page (vcpu, iter->gfn, role); +return alloc_tdp_mmu_page (mmu_caches, iter->gfn, role); }hpa_t kvm_tdp_mmu_get_vcpu_root_hpa (struct kvm_vcpu *vcpu)@@ -213,7 +211,7 @@ hpa_t kvm_tdp_mmu_get_vcpu_root_hpa(struct kvm_vcpu *vcpu) goto out; } - root =alloc_tdp_mmu_page (vcpu,0 , role); + root =alloc_tdp_mmu_page (&vcpu->arch.mmu_caches,0 , role);refcount_set (&root->tdp_mmu_root_count,1 );spin_lock (&kvm->arch.tdp_mmu_pages_lock);@@ -1031,7 +1029,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)if (is_removed_spte (iter.old_spte))break ; - sp =alloc_child_tdp_mmu_page (vcpu, &iter); + sp =alloc_child_tdp_mmu_page (&vcpu->arch.mmu_caches, &iter);if (!tdp_mmu_install_sp_atomic (vcpu->kvm, &iter, sp, account_nx))break ; } --2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 8/15 KVM: x86/mmu: Helper method to check for large and present sptes
In reply to David MatlackConsolidate is_large_pte and is_present_pte into a single helper. This will be used in a follow-up commit to check for present large-pages during Eager Page Splitting.
No functional change intended.
--- arch/x86/kvm/mmu/spte.h | 5 +++++ arch/x86/kvm/mmu/tdp_mmu.c | 3 +-- 2 files changed, 6 insertions(+), 2 deletions(-)
arch/x86/kvm/mmu/spte.h +5 -0
@@ -257,6 +257,11 @@ static inline bool is_large_pte(u64 pte)return pte &PT_PAGE_SIZE_MASK ; } +static inline bool is_large_present_pte (u64 pte) +{ +return is_shadow_present_pte (pte) &&is_large_pte (pte); +} +static inline bool is_last_spte (u64 pte,int level) {return (level ==PG_LEVEL_4K ) ||is_large_pte (pte);
arch/x86/kvm/mmu/tdp_mmu.c +1 -2
@@ -1011,8 +1011,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)* than the target, that SPTE must be cleared and replaced * with a non-leaf SPTE. */ -if (is_shadow_present_pte (iter.old_spte) && -is_large_pte (iter.old_spte)) { +if (is_large_present_pte (iter.old_spte)) {if (!tdp_mmu_zap_spte_atomic (vcpu->kvm, &iter))break ; }
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 08/15] KVM: x86/mmu: Helper method to check for large and present sptes
Quoted 8 lines · David Matlack
Consolidate
is_large_pteandis_present_pteinto a single helper. This will be used in a follow-up commit to check for present large-pages during Eager Page Splitting.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Quoted 26 lines
--- arch/x86/kvm/mmu/spte.h | 5 +++++ arch/x86/kvm/mmu/tdp_mmu.c | 3 +-- 2 files changed, 6 insertions(+), 2 deletions(-)arch/x86/kvm/mmu/spte.h +5
-0@@ -257,6 +257,11 @@ static inline bool is_large_pte(u64 pte)return pte &PT_PAGE_SIZE_MASK ; } +static inline bool is_large_present_pte (u64 pte) +{ +return is_shadow_present_pte (pte) &&is_large_pte (pte); +} +static inline bool is_last_spte (u64 pte,int level) {return (level ==PG_LEVEL_4K ) ||is_large_pte (pte);arch/x86/kvm/mmu/tdp_mmu.c +0
-0
arch/x86/kvm/mmu/tdp_mmu.c int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) · line 1014
Quoted 6 lines
arch/x86/kvm/mmu/tdp_mmu.c +1
-2@@ -1011,8 +1011,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)* than the target, that SPTE must be cleared and replaced * with a non-leaf SPTE. */ -if (is_shadow_present_pte (iter.old_spte) && -is_large_pte (iter.old_spte)) { +if (is_large_present_pte (iter.old_spte)) {
I'm amazed there's only one instance of a check for present and large.
Quoted 6 lines
arch/x86/kvm/mmu/tdp_mmu.c +0
-1if (!tdp_mmu_zap_spte_atomic (vcpu->kvm, &iter))break ; } --2.34.0.rc2.393.gf8c9666880-goog
Sean Christopherson
maintainerRe: [RFC PATCH 08/15] KVM: x86/mmu: Helper method to check for large and present sptes
In reply to David MatlackQuoted 33 lines · David Matlack
Consolidate
is_large_pteandis_present_pteinto a single helper. This will be used in a follow-up commit to check for present large-pages during Eager Page Splitting.No functional change intended.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/spte.h | 5 +++++ arch/x86/kvm/mmu/tdp_mmu.c | 3 +-- 2 files changed, 6 insertions(+), 2 deletions(-)arch/x86/kvm/mmu/spte.h +5
-0@@ -257,6 +257,11 @@ static inline bool is_large_pte(u64 pte)return pte &PT_PAGE_SIZE_MASK ; } +static inline bool is_large_present_pte (u64 pte) +{ +return is_shadow_present_pte (pte) &&is_large_pte (pte); +} +static inline bool is_last_spte (u64 pte,int level) {return (level ==PG_LEVEL_4K ) ||is_large_pte (pte);arch/x86/kvm/mmu/tdp_mmu.c +0
-0
arch/x86/kvm/mmu/tdp_mmu.c int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) · line 1014
Quoted 6 lines
arch/x86/kvm/mmu/tdp_mmu.c +1
-2@@ -1011,8 +1011,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)* than the target, that SPTE must be cleared and replaced * with a non-leaf SPTE. */ -if (is_shadow_present_pte (iter.old_spte) && -is_large_pte (iter.old_spte)) { +if (is_large_present_pte (iter.old_spte)) {
I strongly object to this helper. PRESENT in hardware and shadow-present are two very different things, the name is_large_present_pte() doesn't capture that detail. Yeah, we could name it is_large_shadow_present_pte(), but for me at least that requires more effort to read, and it's not like this is replacing 10s of instances.
Quoted 6 lines
arch/x86/kvm/mmu/tdp_mmu.c +0
-0if (!tdp_mmu_zap_spte_atomic (vcpu->kvm, &iter))break ; }Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 08/15] KVM: x86/mmu: Helper method to check for large and present sptes
Quoted 38 lines · Sean Christopherson
Quoted 36 lines · David Matlack
Consolidate
is_large_pteandis_present_pteinto a single helper. This will be used in a follow-up commit to check for present large-pages during Eager Page Splitting.No functional change intended.
Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/spte.h | 5 +++++ arch/x86/kvm/mmu/tdp_mmu.c | 3 +-- 2 files changed, 6 insertions(+), 2 deletions(-)arch/x86/kvm/mmu/spte.h +5
-0@@ -257,6 +257,11 @@ static inline bool is_large_pte(u64 pte)return pte &PT_PAGE_SIZE_MASK ; } +static inline bool is_large_present_pte (u64 pte) +{ +return is_shadow_present_pte (pte) &&is_large_pte (pte); +} +static inline bool is_last_spte (u64 pte,int level) {return (level ==PG_LEVEL_4K ) ||is_large_pte (pte);arch/x86/kvm/mmu/tdp_mmu.c +0
-0@@ -1011,8 +1011,7 @@ int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault)* than the target, that SPTE must be cleared and replaced * with a non-leaf SPTE. */
Quoted 8 lines
arch/x86/kvm/mmu/tdp_mmu.c int kvm_tdp_mmu_map(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault) · line 1014
Quoted 3 lines
arch/x86/kvm/mmu/tdp_mmu.c +1
-2-if (is_shadow_present_pte (iter.old_spte) && -is_large_pte (iter.old_spte)) { +if (is_large_present_pte (iter.old_spte)) {I strongly object to this helper. PRESENT in hardware and shadow-present are two very different things, the name
is_large_present_pte()doesn't capture that detail. Yeah, we could name itis_large_shadow_present_pte(), but for me at least that requires more effort to read, and it's not like this is replacing 10s of instances.
Ok I'll drop it in v1.
Quoted 7 lines
Quoted 7 lines
arch/x86/kvm/mmu/tdp_mmu.c +0
-1if (!tdp_mmu_zap_spte_atomic (vcpu->kvm, &iter))break ; } --2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 9/15 KVM: x86/mmu: Move restore_acc_track_spte to spte.c
In reply to David Matlackrestore_acc_track_spte is purely an SPTE manipulation, making it a good fit for spte.c. It is also needed in spte.c in a follow-up commit so we can construct child SPTEs during large page splitting.
No functional change intended.
--- arch/x86/kvm/mmu/mmu.c | 18 ------------------ arch/x86/kvm/mmu/spte.c | 18 ++++++++++++++++++ arch/x86/kvm/mmu/spte.h | 1 + 3 files changed, 19 insertions(+), 18 deletions(-)
arch/x86/kvm/mmu/mmu.c +0 -18
@@ -652,24 +652,6 @@ static u64 mmu_spte_get_lockless(u64 *sptep)return __get_spte_lockless (sptep); } -/* Restore an acc-track PTE back to a regular PTE */ -static u64 restore_acc_track_spte (u64 spte) -{ -u64 new_spte = spte; -u64 saved_bits = (spte >>SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ) - &SHADOW_ACC_TRACK_SAVED_BITS_MASK ; - -WARN_ON_ONCE (spte_ad_enabled (spte)); -WARN_ON_ONCE (!is_access_track_spte (spte)); - - new_spte &= ~shadow_acc_track_mask; - new_spte &= ~(SHADOW_ACC_TRACK_SAVED_BITS_MASK << -SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ); - new_spte |= saved_bits; - -return new_spte; -} -/* Returns the Accessed status of the PTE and resets it at the same time. */ static bool mmu_spte_age (u64 *sptep) {
arch/x86/kvm/mmu/spte.c +18 -0
@@ -268,6 +268,24 @@ u64 mark_spte_for_access_track(u64 spte)return spte; } +/* Restore an acc-track PTE back to a regular PTE */ +u64 restore_acc_track_spte (u64 spte) +{ +u64 new_spte = spte; +u64 saved_bits = (spte >>SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ) + &SHADOW_ACC_TRACK_SAVED_BITS_MASK ; + +WARN_ON_ONCE (spte_ad_enabled (spte)); +WARN_ON_ONCE (!is_access_track_spte (spte)); + + new_spte &= ~shadow_acc_track_mask; + new_spte &= ~(SHADOW_ACC_TRACK_SAVED_BITS_MASK << +SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ); + new_spte |= saved_bits; + +return new_spte; +} +void kvm_mmu_set_mmio_spte_mask (u64 mmio_value,u64 mmio_mask,u64 access_mask) {BUG_ON ((u64 )(unsigned )access_mask != access_mask);
arch/x86/kvm/mmu/spte.h +1 -0
@@ -342,6 +342,7 @@ bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp,u64 make_nonleaf_spte (u64 *child_pt,bool ad_disabled);u64 make_mmio_spte (struct kvm_vcpu *vcpu,u64 gfn,unsigned int access);u64 mark_spte_for_access_track (u64 spte); +u64 restore_acc_track_spte (u64 spte);u64 kvm_mmu_changed_pte_notifier_make_spte (u64 old_spte,kvm_pfn_t new_pfn);void kvm_mmu_reset_all_pte_masks (void );
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 09/15] KVM: x86/mmu: Move restore_acc_track_spte to spte.c
Quoted 8 lines · David Matlack
restore_acc_track_spteis purely an SPTE manipulation, making it a good fit forspte.c. It is also needed inspte.cin a follow-up commit so we can construct child SPTEs during large page splitting.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Love it.
Quoted 79 lines
--- arch/x86/kvm/mmu/mmu.c | 18 ------------------ arch/x86/kvm/mmu/spte.c | 18 ++++++++++++++++++ arch/x86/kvm/mmu/spte.h | 1 + 3 files changed, 19 insertions(+), 18 deletions(-)arch/x86/kvm/mmu/mmu.c +0
-18@@ -652,24 +652,6 @@ static u64 mmu_spte_get_lockless(u64 *sptep)return __get_spte_lockless (sptep); } -/* Restore an acc-track PTE back to a regular PTE */ -static u64 restore_acc_track_spte (u64 spte) -{ -u64 new_spte = spte; -u64 saved_bits = (spte >>SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ) - &SHADOW_ACC_TRACK_SAVED_BITS_MASK ; - -WARN_ON_ONCE (spte_ad_enabled (spte)); -WARN_ON_ONCE (!is_access_track_spte (spte)); - - new_spte &= ~shadow_acc_track_mask; - new_spte &= ~(SHADOW_ACC_TRACK_SAVED_BITS_MASK << -SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ); - new_spte |= saved_bits; - -return new_spte; -} -/* Returns the Accessed status of the PTE and resets it at the same time. */ static bool mmu_spte_age (u64 *sptep) {arch/x86/kvm/mmu/spte.c +18
-0@@ -268,6 +268,24 @@ u64 mark_spte_for_access_track(u64 spte)return spte; } +/* Restore an acc-track PTE back to a regular PTE */ +u64 restore_acc_track_spte (u64 spte) +{ +u64 new_spte = spte; +u64 saved_bits = (spte >>SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ) + &SHADOW_ACC_TRACK_SAVED_BITS_MASK ; + +WARN_ON_ONCE (spte_ad_enabled (spte)); +WARN_ON_ONCE (!is_access_track_spte (spte)); + + new_spte &= ~shadow_acc_track_mask; + new_spte &= ~(SHADOW_ACC_TRACK_SAVED_BITS_MASK << +SHADOW_ACC_TRACK_SAVED_BITS_SHIFT ); + new_spte |= saved_bits; + +return new_spte; +} +void kvm_mmu_set_mmio_spte_mask (u64 mmio_value,u64 mmio_mask,u64 access_mask) {BUG_ON ((u64 )(unsigned )access_mask != access_mask);arch/x86/kvm/mmu/spte.h +1
-1@@ -342,6 +342,7 @@ bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp,u64 make_nonleaf_spte (u64 *child_pt,bool ad_disabled);u64 make_mmio_spte (struct kvm_vcpu *vcpu,u64 gfn,unsigned int access);u64 mark_spte_for_access_track (u64 spte); +u64 restore_acc_track_spte (u64 spte);u64 kvm_mmu_changed_pte_notifier_make_spte (u64 old_spte,kvm_pfn_t new_pfn);void kvm_mmu_reset_all_pte_masks (void ); --2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 10/15 KVM: x86/mmu: Abstract need_resched logic from tdp_mmu_iter_cond_resched
In reply to David MatlackAbstract out the logic that checks whether or not we should reschedule (including the extra check that ensures we make forward progress) to a helper method. This will be used in a follow-up commit to reschedule during large page splitting.
No functional change intended.
--- arch/x86/kvm/mmu/tdp_mmu.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)
arch/x86/kvm/mmu/tdp_mmu.c +10 -5
@@ -645,6 +645,15 @@ static inline void tdp_mmu_set_spte_no_dirty_log(struct kvm *kvm,for_each_tdp_pte (_iter,__va (_mmu->root_hpa), \ _mmu->shadow_root_level, _start, _end) +static inline bool tdp_mmu_iter_need_resched (struct kvm *kvm,struct tdp_iter *iter) +{ +/* Ensure forward progress has been made before yielding. */ +if (iter->next_last_level_gfn == iter->yielded_gfn) +return false; + +return need_resched () ||rwlock_needbreak (&kvm->mmu_lock); +} +/* * Yield if the MMU lock is contended or this thread needs to return control * to the scheduler.
@@ -664,11 +673,7 @@ static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm, struct tdp_iter *iter, bool flush, bool shared) { - /* Ensure forward progress has been made before yielding. */ - if (iter->next_last_level_gfn == iter->yielded_gfn) - return false; - - if (need_resched() || rwlock_needbreak(&kvm->mmu_lock)) { + if (tdp_mmu_iter_need_resched(kvm, iter)) {rcu_read_unlock ();if (flush)
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 10/15] KVM: x86/mmu: Abstract need_resched logic from tdp_mmu_iter_cond_resched
Quoted 9 lines · David Matlack
Abstract out the logic that checks whether or not we should reschedule (including the extra check that ensures we make forward progress) to a helper method. This will be used in a follow-up commit to reschedule during large page splitting.
No functional change intended.
Signed-off-by David Matlack <[email protected]>
Quoted 40 lines
--- arch/x86/kvm/mmu/tdp_mmu.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)arch/x86/kvm/mmu/tdp_mmu.c +10
-6@@ -645,6 +645,15 @@ static inline void tdp_mmu_set_spte_no_dirty_log(struct kvm *kvm,for_each_tdp_pte (_iter,__va (_mmu->root_hpa), \ _mmu->shadow_root_level, _start, _end) +static inline bool tdp_mmu_iter_need_resched (struct kvm *kvm,struct tdp_iter *iter) +{ +/* Ensure forward progress has been made before yielding. */ +if (iter->next_last_level_gfn == iter->yielded_gfn) +return false; + +return need_resched () ||rwlock_needbreak (&kvm->mmu_lock); +} +/* * Yield if the MMU lock is contended or this thread needs to return control * to the scheduler. @@ -664,11 +673,7 @@ static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm, struct tdp_iter *iter, bool flush, bool shared) { - /* Ensure forward progress has been made before yielding. */ - if (iter->next_last_level_gfn == iter->yielded_gfn) - return false; - - if (need_resched() || rwlock_needbreak(&kvm->mmu_lock)) { + if (tdp_mmu_iter_need_resched(kvm, iter)) {rcu_read_unlock ();if (flush) --2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 11/15 KVM: x86/mmu: Refactor tdp_mmu iterators to take kvm_mmu_page root
In reply to David MatlackInstead of passing a pointer to the root page table and the root level seperately, pass in a pointer to the kvm_mmu_page that backs the root. This reduces the number of arguments by 1, cutting down on line lengths.
No functional change intended.
--- arch/x86/kvm/mmu/tdp_iter.c | 5 ++++- arch/x86/kvm/mmu/tdp_iter.h | 10 +++++----- arch/x86/kvm/mmu/tdp_mmu.c | 14 +++++--------- 3 files changed, 14 insertions(+), 15 deletions(-)
arch/x86/kvm/mmu/tdp_iter.c +4 -1
@@ -39,9 +39,12 @@ void tdp_iter_restart(struct tdp_iter *iter)* Sets a TDP iterator to walk a pre-order traversal of the paging structure * rooted at root_pt, starting with the walk to translate next_last_level_gfn. */ -void tdp_iter_start (struct tdp_iter *iter,u64 *root_pt,int root_level, +void tdp_iter_start (struct tdp_iter *iter,struct kvm_mmu_page *root,int min_level,gfn_t next_last_level_gfn) { +u64 *root_pt = root->spt; +int root_level = root->role.level; +WARN_ON (root_level <1 );WARN_ON (root_level >PT64_ROOT_MAX_LEVEL );
arch/x86/kvm/mmu/tdp_iter.h +5 -5
@@ -51,17 +51,17 @@ struct tdp_iter {* Iterates over every SPTE mapping the GFN range [start, end) in a * preorder traversal. */ -#define for_each_tdp_pte_min_level (iter, root, root_level, min_level, start, end) \ - for (tdp_iter_start(&iter, root, root_level, min_level, start); \ +#define for_each_tdp_pte_min_level (iter, root, min_level, start, end) \ + for (tdp_iter_start(&iter, root, min_level, start); \ iter.valid && iter.gfn < end; \ tdp_iter_next(&iter)) -#define for_each_tdp_pte (iter, root, root_level, start, end) \ - for_each_tdp_pte_min_level(iter, root, root_level, PG_LEVEL_4K, start, end) +#define for_each_tdp_pte (iter, root, start, end) \ + for_each_tdp_pte_min_level(iter, root, PG_LEVEL_4K, start, end)tdp_ptep_t spte_to_child_pt (u64 pte,int level); -void tdp_iter_start (struct tdp_iter *iter,u64 *root_pt,int root_level, +void tdp_iter_start (struct tdp_iter *iter,struct kvm_mmu_page *root,int min_level,gfn_t next_last_level_gfn);void tdp_iter_next (struct tdp_iter *iter);void tdp_iter_restart (struct tdp_iter *iter);
arch/x86/kvm/mmu/tdp_mmu.c +5 -9
@@ -632,7 +632,7 @@ static inline void tdp_mmu_set_spte_no_dirty_log(struct kvm *kvm, }#define tdp_root_for_each_pte (_iter, _root, _start, _end) \ - for_each_tdp_pte(_iter, _root->spt, _root->role.level, _start, _end) + for_each_tdp_pte(_iter, _root, _start, _end)#define tdp_root_for_each_leaf_pte (_iter, _root, _start, _end) \ tdp_root_for_each_pte(_iter, _root, _start, _end) \
@@ -642,8 +642,7 @@ static inline void tdp_mmu_set_spte_no_dirty_log(struct kvm *kvm, else#define tdp_mmu_for_each_pte (_iter, _mmu, _start, _end) \ - for_each_tdp_pte(_iter, __va(_mmu->root_hpa), \ - _mmu->shadow_root_level, _start, _end) + for_each_tdp_pte(_iter, to_shadow_page(_mmu->root_hpa), _start, _end)static inline bool tdp_mmu_iter_need_resched (struct kvm *kvm,struct tdp_iter *iter) {
@@ -738,8 +737,7 @@ static bool zap_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,rcu_read_lock (); -for_each_tdp_pte_min_level (iter, root->spt, root->role.level, - min_level, start, end) { +for_each_tdp_pte_min_level (iter, root, min_level, start, end) { retry:if (can_yield &&tdp_mmu_iter_cond_resched (kvm, &iter, flush, shared)) {
@@ -1201,8 +1199,7 @@ static bool wrprot_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,BUG_ON (min_level >KVM_MAX_HUGEPAGE_LEVEL ); -for_each_tdp_pte_min_level (iter, root->spt, root->role.level, - min_level, start, end) { +for_each_tdp_pte_min_level (iter, root, min_level, start, end) { retry:if (tdp_mmu_iter_cond_resched (kvm, &iter, false, true))continue ;
@@ -1450,8 +1447,7 @@ static bool write_protect_gfn(struct kvm *kvm, struct kvm_mmu_page *root,rcu_read_lock (); -for_each_tdp_pte_min_level (iter, root->spt, root->role.level, - min_level, gfn, gfn +1 ) { +for_each_tdp_pte_min_level (iter, root, min_level, gfn, gfn +1 ) {if (!is_shadow_present_pte (iter.old_spte) || !is_last_spte (iter.old_spte, iter.level))continue ;
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 11/15] KVM: x86/mmu: Refactor tdp_mmu iterators to take kvm_mmu_page root
Quoted 8 lines · David Matlack
Instead of passing a pointer to the root page table and the root level seperately, pass in a pointer to the
kvm_mmu_pagethat backs the root. This reduces the number of arguments by 1, cutting down on line lengths.No functional change intended.
Signed-off-by David Matlack <[email protected]>
Quoted 11 lines
--- arch/x86/kvm/mmu/tdp_iter.c | 5 ++++- arch/x86/kvm/mmu/tdp_iter.h | 10 +++++----- arch/x86/kvm/mmu/tdp_mmu.c | 14 +++++--------- 3 files changed, 14 insertions(+), 15 deletions(-)arch/x86/kvm/mmu/tdp_iter.c +0
-0
arch/x86/kvm/mmu/tdp_iter.c void tdp_iter_restart(struct tdp_iter *iter) · line 42
Quoted 5 lines
arch/x86/kvm/mmu/tdp_iter.c +1
-1@@ -39,9 +39,12 @@ void tdp_iter_restart(struct tdp_iter *iter)* Sets a TDP iterator to walk a pre-order traversal of the paging structure * rooted at root_pt, starting with the walk to translate next_last_level_gfn. */ -void tdp_iter_start(struct tdp_iter *iter, u64 *root_pt, int root_level, +void tdp_iter_start(struct tdp_iter *iter, struct kvm_mmu_page *root,
I think this is an artifact of the days when I thought we could avoid allocating struct kvm_mmu_pages for the TDP MMU.
Trying to do that turned out to be a huge pain though and the memory savings weren't great.
Happy to see this cleaned up.
Quoted 91 lines
arch/x86/kvm/mmu/tdp_iter.c +3
-0int min_level, gfn_t next_last_level_gfn) { +u64 *root_pt = root->spt; +int root_level = root->role.level; +WARN_ON (root_level <1 );WARN_ON (root_level >PT64_ROOT_MAX_LEVEL );arch/x86/kvm/mmu/tdp_iter.h +5
-5@@ -51,17 +51,17 @@ struct tdp_iter {* Iterates over every SPTE mapping the GFN range [start, end) in a * preorder traversal. */ -#define for_each_tdp_pte_min_level (iter, root, root_level, min_level, start, end) \ - for (tdp_iter_start(&iter, root, root_level, min_level, start); \ +#define for_each_tdp_pte_min_level (iter, root, min_level, start, end) \ + for (tdp_iter_start(&iter, root, min_level, start); \ iter.valid && iter.gfn < end; \ tdp_iter_next(&iter)) -#define for_each_tdp_pte (iter, root, root_level, start, end) \ - for_each_tdp_pte_min_level(iter, root, root_level, PG_LEVEL_4K, start, end) +#define for_each_tdp_pte (iter, root, start, end) \ + for_each_tdp_pte_min_level(iter, root, PG_LEVEL_4K, start, end)tdp_ptep_t spte_to_child_pt (u64 pte,int level); -void tdp_iter_start (struct tdp_iter *iter,u64 *root_pt,int root_level, +void tdp_iter_start (struct tdp_iter *iter,struct kvm_mmu_page *root,int min_level,gfn_t next_last_level_gfn);void tdp_iter_next (struct tdp_iter *iter);void tdp_iter_restart (struct tdp_iter *iter);arch/x86/kvm/mmu/tdp_mmu.c +5
-10@@ -632,7 +632,7 @@ static inline void tdp_mmu_set_spte_no_dirty_log(struct kvm *kvm, }#define tdp_root_for_each_pte (_iter, _root, _start, _end) \ - for_each_tdp_pte(_iter, _root->spt, _root->role.level, _start, _end) + for_each_tdp_pte(_iter, _root, _start, _end)#define tdp_root_for_each_leaf_pte (_iter, _root, _start, _end) \ tdp_root_for_each_pte(_iter, _root, _start, _end) \@@ -642,8 +642,7 @@ static inline void tdp_mmu_set_spte_no_dirty_log(struct kvm *kvm, else#define tdp_mmu_for_each_pte (_iter, _mmu, _start, _end) \ - for_each_tdp_pte(_iter, __va(_mmu->root_hpa), \ - _mmu->shadow_root_level, _start, _end) + for_each_tdp_pte(_iter, to_shadow_page(_mmu->root_hpa), _start, _end)static inline bool tdp_mmu_iter_need_resched (struct kvm *kvm,struct tdp_iter *iter) {@@ -738,8 +737,7 @@ static bool zap_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,rcu_read_lock (); -for_each_tdp_pte_min_level (iter, root->spt, root->role.level, - min_level, start, end) { +for_each_tdp_pte_min_level (iter, root, min_level, start, end) { retry:if (can_yield &&tdp_mmu_iter_cond_resched (kvm, &iter, flush, shared)) {@@ -1201,8 +1199,7 @@ static bool wrprot_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,BUG_ON (min_level >KVM_MAX_HUGEPAGE_LEVEL ); -for_each_tdp_pte_min_level (iter, root->spt, root->role.level, - min_level, start, end) { +for_each_tdp_pte_min_level (iter, root, min_level, start, end) { retry:if (tdp_mmu_iter_cond_resched (kvm, &iter, false, true))continue ;@@ -1450,8 +1447,7 @@ static bool write_protect_gfn(struct kvm *kvm, struct kvm_mmu_page *root,rcu_read_lock (); -for_each_tdp_pte_min_level (iter, root->spt, root->role.level, - min_level, gfn, gfn +1 ) { +for_each_tdp_pte_min_level (iter, root, min_level, gfn, gfn +1 ) {if (!is_shadow_present_pte (iter.old_spte) || !is_last_spte (iter.old_spte, iter.level))continue ; --2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 12/15 KVM: x86/mmu: Split large pages when dirty logging is enabled
In reply to David MatlackWhen dirty logging is enabled without initially-all-set, attempt to split all large pages in the memslot down to 4KB pages so that vCPUs do not have to take expensive write-protection faults to split large pages.
Large page splitting is best-effort only. This commit only adds the support for the TDP MMU, and even there splitting may fail due to out of memory conditions. Failures to split a large page is fine from a correctness standpoint because we still always follow it up by write- protecting any remaining large pages.
--- arch/x86/include/asm/kvm_host.h | 6 ++ arch/x86/kvm/mmu/mmu.c | 83 +++++++++++++++++++++ arch/x86/kvm/mmu/mmu_internal.h | 3 + arch/x86/kvm/mmu/spte.c | 46 ++++++++++++ arch/x86/kvm/mmu/spte.h | 1 + arch/x86/kvm/mmu/tdp_mmu.c | 123 ++++++++++++++++++++++++++++++++ arch/x86/kvm/mmu/tdp_mmu.h | 5 ++ arch/x86/kvm/x86.c | 6 ++ 8 files changed, 273 insertions(+)
arch/x86/include/asm/kvm_host.h +6 -0
@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches; };struct kvm_vm_stat {
@@ -1588,6 +1591,9 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu);void kvm_mmu_slot_remove_write_access (struct kvm *kvm,const struct kvm_memory_slot *memslot,int start_level); +void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +int target_level);void kvm_mmu_zap_collapsible_sptes (struct kvm *kvm,const struct kvm_memory_slot *memslot); void kvm_mmu_slot_leaf_clear_dirty(struct kvm *kvm,
arch/x86/kvm/mmu/mmu.c +83 -0
101 lines not on this page · raw message
arch/x86/kvm/mmu/mmu_internal.h +3 -0
@@ -161,4 +161,7 @@ void *mmu_memory_cache_alloc(struct kvm_mmu_memory_cache *mc);void account_huge_nx_page (struct kvm *kvm,struct kvm_mmu_page *sp);void unaccount_huge_nx_page (struct kvm *kvm,struct kvm_mmu_page *sp); +int mmu_topup_split_caches (struct kvm *kvm); +bool mmu_split_caches_need_topup (struct kvm *kvm); +#endif /* __KVM_X86_MMU_INTERNAL_H */
arch/x86/kvm/mmu/spte.c +46 -0
52 lines not on this page · raw message
arch/x86/kvm/mmu/spte.h +1 -0
@@ -339,6 +339,7 @@ bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, unsigned int pte_access, gfn_t gfn, kvm_pfn_t pfn, u64 old_spte, bool prefetch, bool can_unsync, bool host_writable, u64 *new_spte); +u64 make_large_page_split_spte (u64 large_spte,int level,int index,unsigned int access);u64 make_nonleaf_spte (u64 *child_pt,bool ad_disabled);u64 make_mmio_spte (struct kvm_vcpu *vcpu,u64 gfn,unsigned int access);u64 mark_spte_for_access_track (u64 spte);
arch/x86/kvm/mmu/tdp_mmu.c +123 -0
135 lines not on this page · raw message
arch/x86/kvm/mmu/tdp_mmu.h +5 -0
@@ -72,6 +72,11 @@ bool kvm_tdp_mmu_write_protect_gfn(struct kvm *kvm, struct kvm_memory_slot *slot, gfn_t gfn, int min_level); +void kvm_tdp_mmu_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *slot, +gfn_t start,gfn_t end, +int target_level); +static inline void kvm_tdp_mmu_walk_lockless_begin (void ) {rcu_read_lock ();
arch/x86/kvm/x86.c +6 -0
@@ -11735,6 +11735,12 @@ static void kvm_mmu_slot_apply_flags(struct kvm *kvm,if (kvm_dirty_log_manual_protect_and_init_set (kvm))return ; +/* +* Attempt to split all large pages into 4K pages so that vCPUs +* do not have to take write-protection faults. +*/ +kvm_mmu_slot_try_split_large_pages (kvm, new,PG_LEVEL_4K ); +if (kvm_x86_ops.cpu_dirty_log_size) {kvm_mmu_slot_leaf_clear_dirty (kvm, new);kvm_mmu_slot_remove_write_access (kvm, new,PG_LEVEL_2M );
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 30 lines · David Matlack
When dirty logging is enabled without initially-all-set, attempt to split all large pages in the memslot down to 4KB pages so that vCPUs do not have to take expensive write-protection faults to split large pages.
Large page splitting is best-effort only. This commit only adds the support for the TDP MMU, and even there splitting may fail due to out of memory conditions. Failures to split a large page is fine from a correctness standpoint because we still always follow it up by write- protecting any remaining large pages.
Signed-off-by David Matlack <[email protected]>arch/x86/kvm/mmu/mmu.c +17
-0+int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r; + +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out; + +return 0 ; +
arch/x86/kvm/mmu/mmu.c static int mmu_topup_memory_caches(struct kvm_vcpu *vcpu, bool maybe_indirect) · line 784
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +10
-0+out: +pr_warn ("Failed to top-up split caches. Will not split large pages.\n" ); +return r; +} + +static void mmu_free_split_caches (struct kvm *kvm) +{ +assert_split_caches_invariants (kvm); + +kvm_mmu_free_memory_cache (&kvm->arch.split_caches.pte_list_desc_cache);
^^^^^^^^^^^^^^
I believe this should be page_header_cache.
Review
Quoted 2 lines
(quoted diff) +2
-0+ kvm_mmu_free_memory_cache(&kvm->arch.split_caches.shadow_page_cache); +}
Regards
Nikunj
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 45 lines · Nikunj A. Dadhania
Quoted 30 lines · David Matlack
When dirty logging is enabled without initially-all-set, attempt to split all large pages in the memslot down to 4KB pages so that vCPUs do not have to take expensive write-protection faults to split large pages.
Large page splitting is best-effort only. This commit only adds the support for the TDP MMU, and even there splitting may fail due to out of memory conditions. Failures to split a large page is fine from a correctness standpoint because we still always follow it up by write- protecting any remaining large pages.
Signed-off-by David Matlack <[email protected]>arch/x86/kvm/mmu/mmu.c +17
-0+int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r; + +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out; + +return 0 ; +arch/x86/kvm/mmu/mmu.c static int mmu_topup_memory_caches(struct kvm_vcpu *vcpu, bool maybe_indirect) · line 784
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +10
-0+out: +pr_warn ("Failed to top-up split caches. Will not split large pages.\n" ); +return r; +} + +static void mmu_free_split_caches (struct kvm *kvm) +{ +assert_split_caches_invariants (kvm); + +kvm_mmu_free_memory_cache (&kvm->arch.split_caches.pte_list_desc_cache);^^^^^^^^^^^^^^
Quoted 1 line
I believe this should be
page_header_cache.
Oh wow, thanks for catching that. You are correct. Will fix in v1.
Quoted 7 lines
Review
Quoted 3 lines
(quoted diff) +2
-0+ kvm_mmu_free_memory_cache(&kvm->arch.split_caches.shadow_page_cache); +}Regards
Nikunj
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
In reply to David MatlackQuoted 188 lines · David Matlack
When dirty logging is enabled without initially-all-set, attempt to split all large pages in the memslot down to 4KB pages so that vCPUs do not have to take expensive write-protection faults to split large pages.
Large page splitting is best-effort only. This commit only adds the support for the TDP MMU, and even there splitting may fail due to out of memory conditions. Failures to split a large page is fine from a correctness standpoint because we still always follow it up by write- protecting any remaining large pages.
Signed-off-by David Matlack <[email protected]>--- arch/x86/include/asm/kvm_host.h | 6 ++ arch/x86/kvm/mmu/mmu.c | 83 +++++++++++++++++++++ arch/x86/kvm/mmu/mmu_internal.h | 3 + arch/x86/kvm/mmu/spte.c | 46 ++++++++++++ arch/x86/kvm/mmu/spte.h | 1 + arch/x86/kvm/mmu/tdp_mmu.c | 123 ++++++++++++++++++++++++++++++++ arch/x86/kvm/mmu/tdp_mmu.h | 5 ++ arch/x86/kvm/x86.c | 6 ++ 8 files changed, 273 insertions(+)arch/x86/include/asm/kvm_host.h +6
-0@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches; };struct kvm_vm_stat {@@ -1588,6 +1591,9 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu);void kvm_mmu_slot_remove_write_access (struct kvm *kvm,const struct kvm_memory_slot *memslot,int start_level); +void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +int target_level);void kvm_mmu_zap_collapsible_sptes (struct kvm *kvm,const struct kvm_memory_slot *memslot); void kvm_mmu_slot_leaf_clear_dirty(struct kvm *kvm,arch/x86/kvm/mmu/mmu.c +83
-0@@ -738,6 +738,66 @@ static int mmu_topup_memory_caches(struct kvm_vcpu *vcpu, bool maybe_indirect) PT64_ROOT_MAX_LEVEL); } +static inline void assert_split_caches_invariants (struct kvm *kvm) +{ +/* +* The split caches must only be modified while holding the slots_lock, +* since it is only used during memslot VM-ioctls. +*/ +lockdep_assert_held (&kvm->slots_lock); + +/* +* Only the TDP MMU supports large page splitting using +* kvm->arch.split_caches, which is why we only have to allocate +* page_header_cache and shadow_page_cache. Assert that the TDP +* MMU is at least enabled when the split cache is allocated. +*/ +BUG_ON (!is_tdp_mmu_enabled (kvm)); +} + +int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r; + +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out; + +return 0 ; + +out: +pr_warn ("Failed to top-up split caches. Will not split large pages.\n" ); +return r; +} + +static void mmu_free_split_caches (struct kvm *kvm) +{ +assert_split_caches_invariants (kvm); + +kvm_mmu_free_memory_cache (&kvm->arch.split_caches.pte_list_desc_cache); +kvm_mmu_free_memory_cache (&kvm->arch.split_caches.shadow_page_cache); +} + +bool mmu_split_caches_need_topup (struct kvm *kvm) +{ +assert_split_caches_invariants (kvm); + +if (kvm->arch.split_caches.page_header_cache.nobjs ==0 ) +return true; + +if (kvm->arch.split_caches.shadow_page_cache.nobjs ==0 ) +return true; + +return false; +} +static void mmu_free_memory_caches (struct kvm_vcpu *vcpu) {struct kvm_mmu_memory_caches *mmu_caches;@@ -5696,6 +5756,7 @@ void kvm_mmu_init_vm(struct kvm *kvm)spin_lock_init (&kvm->arch.mmu_unsync_pages_lock); +mmu_init_memory_caches (&kvm->arch.split_caches);kvm_mmu_init_tdp_mmu (kvm); node->track_write = kvm_mmu_pte_write;@@ -5819,6 +5880,28 @@ void kvm_mmu_slot_remove_write_access(struct kvm *kvm,kvm_arch_flush_remote_tlbs_memslot (kvm, memslot); } +void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +int target_level) +{ +u64 start, end; + +if (!is_tdp_mmu_enabled (kvm)) +return ; + +if (mmu_topup_split_caches (kvm)) +return ; + + start = memslot->base_gfn; + end = start + memslot->npages; + +read_lock (&kvm->mmu_lock); +kvm_tdp_mmu_try_split_large_pages (kvm, memslot, start, end, target_level); +read_unlock (&kvm->mmu_lock); + +mmu_free_split_caches (kvm); +} +static bool kvm_mmu_zap_collapsible_spte (struct kvm *kvm,struct kvm_rmap_head *rmap_head,const struct kvm_memory_slot *slot)arch/x86/kvm/mmu/mmu_internal.h +3
-0@@ -161,4 +161,7 @@ void *mmu_memory_cache_alloc(struct kvm_mmu_memory_cache *mc);void account_huge_nx_page (struct kvm *kvm,struct kvm_mmu_page *sp);void unaccount_huge_nx_page (struct kvm *kvm,struct kvm_mmu_page *sp); +int mmu_topup_split_caches (struct kvm *kvm); +bool mmu_split_caches_need_topup (struct kvm *kvm); +#endif /* __KVM_X86_MMU_INTERNAL_H */ arch/x86/kvm/mmu/spte.c +12
-0@@ -191,6 +191,52 @@ bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp,return wrprot; } +static u64 mark_spte_executable (u64 spte) +{ +bool is_access_track =is_access_track_spte (spte); + +if (is_access_track) + spte =restore_acc_track_spte (spte); + + spte &= ~shadow_nx_mask; + spte |= shadow_x_mask; + +if (is_access_track) + spte =mark_spte_for_access_track (spte);
arch/x86/kvm/mmu/spte.c bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, · line 215
Quoted 10 lines
arch/x86/kvm/mmu/spte.c +10
-0+ +return spte; +} + +/* +* Construct an SPTE that maps a sub-page of the given large SPTE. This is +* used during large page splitting, to build the SPTEs that make up the new +* page table. +*/ +u64 make_large_page_split_spte (u64 large_spte,int level,int index,unsigned int access)
Just because this always trips me up reading code, I'd suggest naming the argument large_spte_level or something.
Avoiding a variable called "level" in this function makes it much more explicit.
arch/x86/kvm/mmu/spte.c bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, · line 221
Quoted 6 lines
arch/x86/kvm/mmu/spte.c +6
-0+{ +u64 child_spte; +int child_level; + +BUG_ON (is_mmio_spte (large_spte)); +BUG_ON (!is_large_present_pte (large_spte));
In the interest of not crashing the host, I think it would be safe to WARN and return 0 here.
BUG is fine too if that's preferred.
arch/x86/kvm/mmu/spte.c bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, · line 226
Quoted 5 lines
arch/x86/kvm/mmu/spte.c +5
-0+ + child_spte = large_spte; + child_level = level -1 ; + + child_spte += (index *KVM_PAGES_PER_HPAGE (child_level)) <<PAGE_SHIFT ;
This += makes me nervous. It at least merits a comment explaining what's going on.
I'd find a |= more readable to make it more explicit and since sptes aren't numbers.
You could probably also be really explicit about extracting the PFN and adding to it, clearing the PFN bits and then putting it back in and I bet the compiler would optimize out the extra bit fiddling.
Quoted 37 lines
arch/x86/kvm/mmu/spte.c +13
-0+ +if (child_level ==PG_LEVEL_4K ) { + child_spte &= ~PT_PAGE_SIZE_MASK ; + +/* Allow execution for 4K pages if it was disabled for NX HugePages. */ +if (is_nx_huge_page_enabled () && access &ACC_EXEC_MASK ) + child_spte =mark_spte_executable (child_spte); + } + +return child_spte; +} + +u64 make_nonleaf_spte (u64 *child_pt,bool ad_disabled) {u64 spte =SPTE_MMU_PRESENT_MASK ;arch/x86/kvm/mmu/spte.h +1
-0@@ -339,6 +339,7 @@ bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, unsigned int pte_access, gfn_t gfn, kvm_pfn_t pfn, u64 old_spte, bool prefetch, bool can_unsync, bool host_writable, u64 *new_spte); +u64 make_large_page_split_spte (u64 large_spte,int level,int index,unsigned int access);u64 make_nonleaf_spte (u64 *child_pt,bool ad_disabled);u64 make_mmio_spte (struct kvm_vcpu *vcpu,u64 gfn,unsigned int access);u64 mark_spte_for_access_track (u64 spte);arch/x86/kvm/mmu/tdp_mmu.c +1
-0@@ -695,6 +695,39 @@ static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm,return false; } +static inline bool
arch/x86/kvm/mmu/tdp_mmu.c static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm, · line 708
Quoted 10 lines
arch/x86/kvm/mmu/tdp_mmu.c +10
-0+tdp_mmu_need_split_caches_topup_or_resched(struct kvm *kvm, struct tdp_iter *iter) +{ + if (mmu_split_caches_need_topup(kvm)) + return true; + +return tdp_mmu_iter_need_resched (kvm, iter); +} + +static inline int +tdp_mmu_topup_split_caches_resched (struct kvm *kvm,struct tdp_iter *iter,bool flush)
This functionality could be shoe-horned into tdp_mmu_iter_cond_resched, reducing code duplication.
I don't know if the extra parameters / complexity on that function would be worth it, but I'm slightly inclined in that direction.
arch/x86/kvm/mmu/tdp_mmu.c static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm, · line 720
Quoted 12 lines
arch/x86/kvm/mmu/tdp_mmu.c +12
-0+{ +int r; + +rcu_read_unlock (); + +if (flush) +kvm_flush_remote_tlbs (kvm); + +read_unlock (&kvm->mmu_lock); + +cond_resched (); + r =mmu_topup_split_caches (kvm);
Ah, right. I was confused by this for a second, but it's safe because the caches are protected by the slots lock.
Quoted 16 lines
arch/x86/kvm/mmu/tdp_mmu.c +10
-0+ +read_lock (&kvm->mmu_lock); + +rcu_read_lock (); +WARN_ON (iter->gfn > iter->next_last_level_gfn); +tdp_iter_restart (iter); + +return r; +} +/* * Tears down the mappings for the range of gfns, [start, end), and frees the * non-root pages mapping GFNs strictly within that range. Returns true if @@ -1241,6 +1274,96 @@ bool kvm_tdp_mmu_wrprot_slot(struct kvm *kvm,return spte_set; }
arch/x86/kvm/mmu/tdp_mmu.c bool kvm_tdp_mmu_wrprot_slot(struct kvm *kvm, · line 1285
Quoted 10 lines
arch/x86/kvm/mmu/tdp_mmu.c +9
-0+static bool tdp_mmu_split_large_page_atomic (struct kvm *kvm,struct tdp_iter *iter) +{ +const u64 large_spte = iter->old_spte; +const int level = iter->level; +struct kvm_mmu_page *child_sp; +u64 child_spte; +int i; + +BUG_ON (mmu_split_caches_need_topup (kvm));
I think it would be safe to just WARN and return here as well.
arch/x86/kvm/mmu/tdp_mmu.c bool kvm_tdp_mmu_wrprot_slot(struct kvm *kvm, · line 1290
Quoted 5 lines
arch/x86/kvm/mmu/tdp_mmu.c +5
-0+ + child_sp =alloc_child_tdp_mmu_page (&kvm->arch.split_caches, iter); + +for (i =0 ; i <PT64_ENT_PER_PAGE ; i++) { + child_spte =make_large_page_split_spte (large_spte, level, i,ACC_ALL );
Relating to my other comment above on make_large_page_split_spte, you could also iterate through the range of PFNs here and pass that as an argument to the helper function.
Quoted 100 lines
arch/x86/kvm/mmu/tdp_mmu.c +76
-0+ +/* +* No need for atomics since child_sp has not been installed +* in the table yet and thus is not reachable by any other +* thread. +*/ + child_sp->spt[i] = child_spte; + } + +return tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false); +} + +static void tdp_mmu_split_large_pages_root (struct kvm *kvm,struct kvm_mmu_page *root, +gfn_t start,gfn_t end,int target_level) +{ +struct tdp_iter iter; +bool flush = false; +int r; + +rcu_read_lock (); + +/* +* Traverse the page table splitting all large pages above the target +* level into one lower level. For example, if we encounter a 1GB page +* we split it into 512 2MB pages. +* +* Since the TDP iterator uses a pre-order traversal, we are guaranteed +* to visit an SPTE before ever visiting its children, which means we +* will correctly recursively split large pages that are more than one +* level above the target level (e.g. splitting 1GB to 2MB to 4KB). +*/ +for_each_tdp_pte_min_level (iter, root, target_level +1 , start, end) { +retry: +if (tdp_mmu_need_split_caches_topup_or_resched (kvm, &iter)) { + r =tdp_mmu_topup_split_caches_resched (kvm, &iter, flush); + flush = false; + +/* +* If topping up the split caches failed, we can't split +* any more pages. Bail out of the loop. +*/ +if (r) +break ; + +continue ; + } + +if (!is_large_present_pte (iter.old_spte)) +continue ; + +if (!tdp_mmu_split_large_page_atomic (kvm, &iter)) + goto retry; + + flush = true; + } + +rcu_read_unlock (); + +if (flush) +kvm_flush_remote_tlbs (kvm); +} + +void kvm_tdp_mmu_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *slot, +gfn_t start,gfn_t end, +int target_level) +{ +struct kvm_mmu_page *root; + +lockdep_assert_held_read (&kvm->mmu_lock); + +for_each_tdp_mmu_root_yield_safe (kvm, root, slot->as_id, true) +tdp_mmu_split_large_pages_root (kvm, root, start, end, target_level); + +} +/* * Clear the dirty status of all the SPTEs mapping GFNs in the memslot. If * AD bits are enabled, this will involve clearing the dirty bit on each SPTE. arch/x86/kvm/mmu/tdp_mmu.h +5
-0@@ -72,6 +72,11 @@ bool kvm_tdp_mmu_write_protect_gfn(struct kvm *kvm, struct kvm_memory_slot *slot, gfn_t gfn, int min_level); +void kvm_tdp_mmu_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *slot, +gfn_t start,gfn_t end, +int target_level); +static inline void kvm_tdp_mmu_walk_lockless_begin (void ) {rcu_read_lock ();arch/x86/kvm/x86.c +0
-0
arch/x86/kvm/x86.c static void kvm_mmu_slot_apply_flags(struct kvm *kvm, · line 11742
Quoted 8 lines
arch/x86/kvm/x86.c +5
-0@@ -11735,6 +11735,12 @@ static void kvm_mmu_slot_apply_flags(struct kvm *kvm,if (kvm_dirty_log_manual_protect_and_init_set (kvm))return ; +/* +* Attempt to split all large pages into 4K pages so that vCPUs +* do not have to take write-protection faults. +*/ +kvm_mmu_slot_try_split_large_pages (kvm, new,PG_LEVEL_4K );
Thank you for parameterizing the target level here. I'm working on a proof of concept for 2M dirty tracking right now (still in exploratory phase) and this parameter will help future-proof the splitting algorithm if we ever decide we don't want to split everything to 4k for dirty logging.
Quoted 7 lines
arch/x86/kvm/x86.c +1
-1+if (kvm_x86_ops.cpu_dirty_log_size) {kvm_mmu_slot_leaf_clear_dirty (kvm, new);kvm_mmu_slot_remove_write_access (kvm, new,PG_LEVEL_2M ); --2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 196 lines · Ben Gardon
Quoted 194 lines · David Matlack
When dirty logging is enabled without initially-all-set, attempt to split all large pages in the memslot down to 4KB pages so that vCPUs do not have to take expensive write-protection faults to split large pages.
Large page splitting is best-effort only. This commit only adds the support for the TDP MMU, and even there splitting may fail due to out of memory conditions. Failures to split a large page is fine from a correctness standpoint because we still always follow it up by write- protecting any remaining large pages.
Signed-off-by David Matlack <[email protected]>--- arch/x86/include/asm/kvm_host.h | 6 ++ arch/x86/kvm/mmu/mmu.c | 83 +++++++++++++++++++++ arch/x86/kvm/mmu/mmu_internal.h | 3 + arch/x86/kvm/mmu/spte.c | 46 ++++++++++++ arch/x86/kvm/mmu/spte.h | 1 + arch/x86/kvm/mmu/tdp_mmu.c | 123 ++++++++++++++++++++++++++++++++ arch/x86/kvm/mmu/tdp_mmu.h | 5 ++ arch/x86/kvm/x86.c | 6 ++ 8 files changed, 273 insertions(+)arch/x86/include/asm/kvm_host.h +6
-0@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches; };struct kvm_vm_stat {@@ -1588,6 +1591,9 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu);void kvm_mmu_slot_remove_write_access (struct kvm *kvm,const struct kvm_memory_slot *memslot,int start_level); +void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +int target_level);void kvm_mmu_zap_collapsible_sptes (struct kvm *kvm,const struct kvm_memory_slot *memslot); void kvm_mmu_slot_leaf_clear_dirty(struct kvm *kvm,arch/x86/kvm/mmu/mmu.c +83
-0@@ -738,6 +738,66 @@ static int mmu_topup_memory_caches(struct kvm_vcpu *vcpu, bool maybe_indirect) PT64_ROOT_MAX_LEVEL); } +static inline void assert_split_caches_invariants (struct kvm *kvm) +{ +/* +* The split caches must only be modified while holding the slots_lock, +* since it is only used during memslot VM-ioctls. +*/ +lockdep_assert_held (&kvm->slots_lock); + +/* +* Only the TDP MMU supports large page splitting using +* kvm->arch.split_caches, which is why we only have to allocate +* page_header_cache and shadow_page_cache. Assert that the TDP +* MMU is at least enabled when the split cache is allocated. +*/ +BUG_ON (!is_tdp_mmu_enabled (kvm)); +} + +int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r; + +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out; + +return 0 ; + +out: +pr_warn ("Failed to top-up split caches. Will not split large pages.\n" ); +return r; +} + +static void mmu_free_split_caches (struct kvm *kvm) +{ +assert_split_caches_invariants (kvm); + +kvm_mmu_free_memory_cache (&kvm->arch.split_caches.pte_list_desc_cache); +kvm_mmu_free_memory_cache (&kvm->arch.split_caches.shadow_page_cache); +} + +bool mmu_split_caches_need_topup (struct kvm *kvm) +{ +assert_split_caches_invariants (kvm); + +if (kvm->arch.split_caches.page_header_cache.nobjs ==0 ) +return true; + +if (kvm->arch.split_caches.shadow_page_cache.nobjs ==0 ) +return true; + +return false; +} +static void mmu_free_memory_caches (struct kvm_vcpu *vcpu) {struct kvm_mmu_memory_caches *mmu_caches;@@ -5696,6 +5756,7 @@ void kvm_mmu_init_vm(struct kvm *kvm)spin_lock_init (&kvm->arch.mmu_unsync_pages_lock); +mmu_init_memory_caches (&kvm->arch.split_caches);kvm_mmu_init_tdp_mmu (kvm); node->track_write = kvm_mmu_pte_write;@@ -5819,6 +5880,28 @@ void kvm_mmu_slot_remove_write_access(struct kvm *kvm,kvm_arch_flush_remote_tlbs_memslot (kvm, memslot); } +void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +int target_level) +{ +u64 start, end; + +if (!is_tdp_mmu_enabled (kvm)) +return ; + +if (mmu_topup_split_caches (kvm)) +return ; + + start = memslot->base_gfn; + end = start + memslot->npages; + +read_lock (&kvm->mmu_lock); +kvm_tdp_mmu_try_split_large_pages (kvm, memslot, start, end, target_level); +read_unlock (&kvm->mmu_lock); + +mmu_free_split_caches (kvm); +} +static bool kvm_mmu_zap_collapsible_spte (struct kvm *kvm,struct kvm_rmap_head *rmap_head,const struct kvm_memory_slot *slot)arch/x86/kvm/mmu/mmu_internal.h +3
-0@@ -161,4 +161,7 @@ void *mmu_memory_cache_alloc(struct kvm_mmu_memory_cache *mc);void account_huge_nx_page (struct kvm *kvm,struct kvm_mmu_page *sp);void unaccount_huge_nx_page (struct kvm *kvm,struct kvm_mmu_page *sp); +int mmu_topup_split_caches (struct kvm *kvm); +bool mmu_split_caches_need_topup (struct kvm *kvm); +#endif /* __KVM_X86_MMU_INTERNAL_H */ arch/x86/kvm/mmu/spte.c +18
-0@@ -191,6 +191,52 @@ bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp,return wrprot; } +static u64 mark_spte_executable (u64 spte) +{ +bool is_access_track =is_access_track_spte (spte); + +if (is_access_track) + spte =restore_acc_track_spte (spte); + + spte &= ~shadow_nx_mask; + spte |= shadow_x_mask; + +if (is_access_track) + spte =mark_spte_for_access_track (spte); + +return spte; +} + +/* +* Construct an SPTE that maps a sub-page of the given large SPTE. This is
Quoted 8 lines
arch/x86/kvm/mmu/spte.c bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, · line 215
Quoted 4 lines
arch/x86/kvm/mmu/spte.c +4
-0+* used during large page splitting, to build the SPTEs that make up the new +* page table. +*/ +u64 make_large_page_split_spte (u64 large_spte,int level,int index,unsigned int access)Just because this always trips me up reading code, I'd suggest naming the argument
large_spte_levelor something.
Avoiding a variable called "level" in this function makes it much more explicit.
Will do.
Quoted 11 lines
arch/x86/kvm/mmu/spte.c bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, · line 221
Quoted 7 lines
arch/x86/kvm/mmu/spte.c +6
-0+{ +u64 child_spte; +int child_level; + +BUG_ON (is_mmio_spte (large_spte)); +BUG_ON (!is_large_present_pte (large_spte));In the interest of not crashing the host, I think it would be safe to WARN and return 0 here.
BUG is fine too if that's preferred.
Ack. I'll take a look and see if I can avoid the BUG_ONs. They're optional sanity checks anyway.
Quoted 14 lines
arch/x86/kvm/mmu/spte.c bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, · line 226
Quoted 6 lines
arch/x86/kvm/mmu/spte.c +5
-0+ + child_spte = large_spte; + child_level = level -1 ; + + child_spte += (index *KVM_PAGES_PER_HPAGE (child_level)) <<PAGE_SHIFT ;This += makes me nervous. It at least merits a comment explaining what's going on.
I'd find a |= more readable to make it more explicit and since sptes aren't numbers.
You could probably also be really explicit about extracting the PFN and adding to it, clearing the PFN bits and then putting it back in and I bet the compiler would optimize out the extra bit fiddling.
I can change it to |= and add a comment. I prefer not to extra the PFN and replace it since there's really no reason to. One of the nice things about this function in general is that we don't have to construct the child SPTE from scratch, we just have to slightly adjust the parent SPTE. For the address, the address in the large SPTE is already there, we just need to add in the offset to the lower-level page.
Quoted 37 lines
Quoted 37 lines
arch/x86/kvm/mmu/spte.c +13
-0+ +if (child_level ==PG_LEVEL_4K ) { + child_spte &= ~PT_PAGE_SIZE_MASK ; + +/* Allow execution for 4K pages if it was disabled for NX HugePages. */ +if (is_nx_huge_page_enabled () && access &ACC_EXEC_MASK ) + child_spte =mark_spte_executable (child_spte); + } + +return child_spte; +} + +u64 make_nonleaf_spte (u64 *child_pt,bool ad_disabled) {u64 spte =SPTE_MMU_PRESENT_MASK ;arch/x86/kvm/mmu/spte.h +1
-0@@ -339,6 +339,7 @@ bool make_spte(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp, unsigned int pte_access, gfn_t gfn, kvm_pfn_t pfn, u64 old_spte, bool prefetch, bool can_unsync, bool host_writable, u64 *new_spte); +u64 make_large_page_split_spte (u64 large_spte,int level,int index,unsigned int access);u64 make_nonleaf_spte (u64 *child_pt,bool ad_disabled);u64 make_mmio_spte (struct kvm_vcpu *vcpu,u64 gfn,unsigned int access);u64 mark_spte_for_access_track (u64 spte);arch/x86/kvm/mmu/tdp_mmu.c +0
-0@@ -695,6 +695,39 @@ static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm,return false; }
Quoted 16 lines
arch/x86/kvm/mmu/tdp_mmu.c static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm, · line 708
Quoted 11 lines
arch/x86/kvm/mmu/tdp_mmu.c +11
-0+static inline bool +tdp_mmu_need_split_caches_topup_or_resched (struct kvm *kvm,struct tdp_iter *iter) +{ +if (mmu_split_caches_need_topup (kvm)) +return true; + +return tdp_mmu_iter_need_resched (kvm, iter); +} + +static inline int +tdp_mmu_topup_split_caches_resched (struct kvm *kvm,struct tdp_iter *iter,bool flush)This functionality could be shoe-horned into
tdp_mmu_iter_cond_resched, reducing code duplication.
I don't know if the extra parameters / complexity on that function would be worth it, but I'm slightly inclined in that direction.
Ok I'll take a look and see if I can combine them in a nice way.
Quoted 159 lines
arch/x86/kvm/mmu/tdp_mmu.c static inline bool tdp_mmu_iter_cond_resched(struct kvm *kvm, · line 720
Quoted 13 lines
arch/x86/kvm/mmu/tdp_mmu.c +12
-0+{ +int r; + +rcu_read_unlock (); + +if (flush) +kvm_flush_remote_tlbs (kvm); + +read_unlock (&kvm->mmu_lock); + +cond_resched (); + r =mmu_topup_split_caches (kvm);Ah, right. I was confused by this for a second, but it's safe because the caches are protected by the slots lock.
Quoted 16 lines
arch/x86/kvm/mmu/tdp_mmu.c +10
-0+ +read_lock (&kvm->mmu_lock); + +rcu_read_lock (); +WARN_ON (iter->gfn > iter->next_last_level_gfn); +tdp_iter_restart (iter); + +return r; +} +/* * Tears down the mappings for the range of gfns, [start, end), and frees the * non-root pages mapping GFNs strictly within that range. Returns true if @@ -1241,6 +1274,96 @@ bool kvm_tdp_mmu_wrprot_slot(struct kvm *kvm,return spte_set; }arch/x86/kvm/mmu/tdp_mmu.c bool kvm_tdp_mmu_wrprot_slot(struct kvm *kvm, · line 1285
Quoted 10 lines
arch/x86/kvm/mmu/tdp_mmu.c +9
-0+static bool tdp_mmu_split_large_page_atomic (struct kvm *kvm,struct tdp_iter *iter) +{ +const u64 large_spte = iter->old_spte; +const int level = iter->level; +struct kvm_mmu_page *child_sp; +u64 child_spte; +int i; + +BUG_ON (mmu_split_caches_need_topup (kvm));I think it would be safe to just WARN and return here as well.
arch/x86/kvm/mmu/tdp_mmu.c bool kvm_tdp_mmu_wrprot_slot(struct kvm *kvm, · line 1290
Quoted 5 lines
arch/x86/kvm/mmu/tdp_mmu.c +5
-0+ + child_sp =alloc_child_tdp_mmu_page (&kvm->arch.split_caches, iter); + +for (i =0 ; i <PT64_ENT_PER_PAGE ; i++) { + child_spte =make_large_page_split_spte (large_spte, level, i,ACC_ALL );Relating to my other comment above on
make_large_page_split_spte, you could also iterate through the range of PFNs here and pass that as an argument to the helper function.Quoted 103 lines
arch/x86/kvm/mmu/tdp_mmu.c +76
-0+ +/* +* No need for atomics since child_sp has not been installed +* in the table yet and thus is not reachable by any other +* thread. +*/ + child_sp->spt[i] = child_spte; + } + +return tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false); +} + +static void tdp_mmu_split_large_pages_root (struct kvm *kvm,struct kvm_mmu_page *root, +gfn_t start,gfn_t end,int target_level) +{ +struct tdp_iter iter; +bool flush = false; +int r; + +rcu_read_lock (); + +/* +* Traverse the page table splitting all large pages above the target +* level into one lower level. For example, if we encounter a 1GB page +* we split it into 512 2MB pages. +* +* Since the TDP iterator uses a pre-order traversal, we are guaranteed +* to visit an SPTE before ever visiting its children, which means we +* will correctly recursively split large pages that are more than one +* level above the target level (e.g. splitting 1GB to 2MB to 4KB). +*/ +for_each_tdp_pte_min_level (iter, root, target_level +1 , start, end) { +retry: +if (tdp_mmu_need_split_caches_topup_or_resched (kvm, &iter)) { + r =tdp_mmu_topup_split_caches_resched (kvm, &iter, flush); + flush = false; + +/* +* If topping up the split caches failed, we can't split +* any more pages. Bail out of the loop. +*/ +if (r) +break ; + +continue ; + } + +if (!is_large_present_pte (iter.old_spte)) +continue ; + +if (!tdp_mmu_split_large_page_atomic (kvm, &iter)) + goto retry; + + flush = true; + } + +rcu_read_unlock (); + +if (flush) +kvm_flush_remote_tlbs (kvm); +} + +void kvm_tdp_mmu_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *slot, +gfn_t start,gfn_t end, +int target_level) +{ +struct kvm_mmu_page *root; + +lockdep_assert_held_read (&kvm->mmu_lock); + +for_each_tdp_mmu_root_yield_safe (kvm, root, slot->as_id, true) +tdp_mmu_split_large_pages_root (kvm, root, start, end, target_level); + +} +/* * Clear the dirty status of all the SPTEs mapping GFNs in the memslot. If * AD bits are enabled, this will involve clearing the dirty bit on each SPTE. arch/x86/kvm/mmu/tdp_mmu.h +5
-0@@ -72,6 +72,11 @@ bool kvm_tdp_mmu_write_protect_gfn(struct kvm *kvm, struct kvm_memory_slot *slot, gfn_t gfn, int min_level); +void kvm_tdp_mmu_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *slot, +gfn_t start,gfn_t end, +int target_level); +static inline void kvm_tdp_mmu_walk_lockless_begin (void ) {rcu_read_lock ();arch/x86/kvm/x86.c +0
-0@@ -11735,6 +11735,12 @@ static void kvm_mmu_slot_apply_flags(struct kvm *kvm,if (kvm_dirty_log_manual_protect_and_init_set (kvm))return ;
Quoted 11 lines
arch/x86/kvm/x86.c static void kvm_mmu_slot_apply_flags(struct kvm *kvm, · line 11742
Quoted 5 lines
arch/x86/kvm/x86.c +5
-0+/* +* Attempt to split all large pages into 4K pages so that vCPUs +* do not have to take write-protection faults. +*/ +kvm_mmu_slot_try_split_large_pages (kvm, new,PG_LEVEL_4K );Thank you for parameterizing the target level here. I'm working on a proof of concept for 2M dirty tracking right now (still in exploratory phase) and this parameter will help future-proof the splitting algorithm if we ever decide we don't want to split everything to 4k for dirty logging.
Exactly my thinking as well! :)
Quoted 8 lines
Quoted 8 lines
arch/x86/kvm/x86.c +1
-1+if (kvm_x86_ops.cpu_dirty_log_size) {kvm_mmu_slot_leaf_clear_dirty (kvm, new);kvm_mmu_slot_remove_write_access (kvm, new,PG_LEVEL_2M ); --2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
In reply to David MatlackHi, David,
arch/x86/include/asm/kvm_host.h struct kvm_arch { · line 1237
Quoted 11 lines · David Matlack
arch/x86/include/asm/kvm_host.h +3
-0@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches;
Are mmu_gfn_array_cache and mmu_pte_list_desc_cache wasted here? I saw that "struct kvm_mmu_memory_cache" still takes up quite a few hundreds of bytes, just want to make sure we won't waste them in vain.
[...]
Quoted 4 lines
arch/x86/include/asm/kvm_host.h +4
-0+int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r;
arch/x86/include/asm/kvm_host.h struct kvm_arch {
Quoted 10 lines
arch/x86/include/asm/kvm_host.h +10
-0+ +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out;
Is it intended to only top-up with one cache object? IIUC this means we'll try to proactively yield the cpu for each of the huge page split right after the object is consumed.
Wondering whether it be more efficient to make it a slightly larger number, so we don't overload the memory but also make the loop a bit more efficient.
arch/x86/include/asm/kvm_host.h
Quoted 7 lines
arch/x86/include/asm/kvm_host.h +7
-0+ +return 0 ; + +out: +pr_warn ("Failed to top-up split caches. Will not split large pages.\n" ); +return r; +}
Thanks,
Signature · 1 line
Peter Xu
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 4 lines · Peter Xu
Hi, David,
On Fri, Nov 19, 2021 at 11:57:56PM +0000, David Matlack wrote:
Quoted 15 lines
arch/x86/include/asm/kvm_host.h struct kvm_arch { · line 1237
Quoted 11 lines
arch/x86/include/asm/kvm_host.h +3
-0@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches;Are
mmu_gfn_array_cacheandmmu_pte_list_desc_cachewasted here? I saw that "structkvm_mmu_memory_cache" still takes up quite a few hundreds of bytes, just want to make sure we won't waste them in vain.
Yes they are wasted right now. But there's a couple of things to keep in mind:
1. They are also wasted in every vCPU (in the per-vCPU caches) that does not use the shadow MMU.
2. They will (I think) be used eventually when I add Eager Page Splitting support to the shadow MMU.
3. split_caches is per-VM so it's only a few hundred bytes per VM.
If we really want to save the memory the right way forward might be to make each kvm_mmu_memory_cache a pointer instead of an embedded struct. Then we can allocate each dynamically only as needed. I can add that to my TODO list but I don't think it'd be worth blocking this on it given the points above.
Quoted 22 lines
[...]
Quoted 4 lines
arch/x86/include/asm/kvm_host.h +4
-0+int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r;arch/x86/include/asm/kvm_host.h
Quoted 10 lines
arch/x86/include/asm/kvm_host.h +10
-0+ +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out;Is it intended to only top-up with one cache object? IIUC this means we'll try to proactively yield the cpu for each of the huge page split right after the object is consumed.
Quoted 2 lines
Wondering whether it be more efficient to make it a slightly larger number, so we don't overload the memory but also make the loop a bit more efficient.
IIUC, 1 here is just the min needed for kvm_mmu_topup_memory_cache to return success. I chose 1 for each because it's the minimum necessary to make forward progress (split one large page).
No matter what you pass for min kvm_mmu_topup_memory_cache() will still always try to allocate KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE objects.
Quoted 14 lines
arch/x86/include/asm/kvm_host.h
Quoted 8 lines
arch/x86/include/asm/kvm_host.h +7
-0+ +return 0 ; + +out: +pr_warn ("Failed to top-up split caches. Will not split large pages.\n" ); +return r; +}Thanks,
--
Peter Xu
Sean Christopherson
maintainerRe: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 57 lines · David Matlack
Quoted 4 lines · Peter Xu
Hi, David,
On Fri, Nov 19, 2021 at 11:57:56PM +0000, David Matlack wrote:
Quoted 15 lines
arch/x86/include/asm/kvm_host.h struct kvm_arch { · line 1237
Quoted 11 lines
arch/x86/include/asm/kvm_host.h +3
-0@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches;Are
mmu_gfn_array_cacheandmmu_pte_list_desc_cachewasted here? I saw that "structkvm_mmu_memory_cache" still takes up quite a few hundreds of bytes, just want to make sure we won't waste them in vain.Yes they are wasted right now. But there's a couple of things to keep in mind:
1. They are also wasted in every vCPU (in the per-vCPU caches) that does not use the shadow MMU.
2. They will (I think) be used eventually when I add Eager Page Splitting support to the shadow MMU.
3.split_cachesis per-VM so it's only a few hundred bytes per VM.If we really want to save the memory the right way forward might be to make each
kvm_mmu_memory_cachea pointer instead of an embedded struct. Then we can allocate each dynamically only as needed. I can add that to my TODO list but I don't think it'd be worth blocking this on it given the points above.Quoted 22 lines
[...]
Quoted 4 lines
arch/x86/include/asm/kvm_host.h +4
-0+int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r;arch/x86/include/asm/kvm_host.h
Quoted 10 lines
arch/x86/include/asm/kvm_host.h +10
-0+ +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out;Is it intended to only top-up with one cache object? IIUC this means we'll try to proactively yield the cpu for each of the huge page split right after the object is consumed.
Quoted 6 lines
Quoted 2 lines
Wondering whether it be more efficient to make it a slightly larger number, so we don't overload the memory but also make the loop a bit more efficient.
IIUC, 1 here is just the min needed for
kvm_mmu_topup_memory_cacheto return success. I chose 1 for each because it's the minimum necessary to make forward progress (split one large page).
The @min parameter is minimum number of pages that _must_ be available in the cache, i.e. it's the maximum number of pages that can theoretically be used by whatever upcoming operation is going to be consuming pages from the cache.
So '1' is technically correct, but I think it's the wrong choice given the behavior of this code. E.g. if there's 1 object in the cache, the initial top-up will do nothing, and then tdp_mmu_split_large_pages_root() will almost immediately drop mmu_lock to topup the cache. Since the in-loop usage explicitly checks for an empty cache, i.e. any non-zero @min will have identical behavior, I think it makes sense to use KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE _and_ add a comment explaining why.
Quoted 3 lines
No matter what you pass for min
kvm_mmu_topup_memory_cache()will still always try to allocateKVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects.
No, it will try to allocate KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE if and only if there are fewer than @min objects in the cache.
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 66 lines · Sean Christopherson
Quoted 57 lines · David Matlack
Quoted 4 lines · Peter Xu
Hi, David,
On Fri, Nov 19, 2021 at 11:57:56PM +0000, David Matlack wrote:
Quoted 15 lines
arch/x86/include/asm/kvm_host.h struct kvm_arch { · line 1237
Quoted 11 lines
arch/x86/include/asm/kvm_host.h +3
-0@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches;Are
mmu_gfn_array_cacheandmmu_pte_list_desc_cachewasted here? I saw that "structkvm_mmu_memory_cache" still takes up quite a few hundreds of bytes, just want to make sure we won't waste them in vain.Yes they are wasted right now. But there's a couple of things to keep in mind:
1. They are also wasted in every vCPU (in the per-vCPU caches) that does not use the shadow MMU.
2. They will (I think) be used eventually when I add Eager Page Splitting support to the shadow MMU.
3.split_cachesis per-VM so it's only a few hundred bytes per VM.If we really want to save the memory the right way forward might be to make each
kvm_mmu_memory_cachea pointer instead of an embedded struct. Then we can allocate each dynamically only as needed. I can add that to my TODO list but I don't think it'd be worth blocking this on it given the points above.Quoted 22 lines
[...]
Quoted 4 lines
arch/x86/include/asm/kvm_host.h +4
-0+int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r;arch/x86/include/asm/kvm_host.h
Quoted 10 lines
arch/x86/include/asm/kvm_host.h +10
-0+ +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out;Is it intended to only top-up with one cache object? IIUC this means we'll try to proactively yield the cpu for each of the huge page split right after the object is consumed.
Quoted 6 lines
Quoted 2 lines
Wondering whether it be more efficient to make it a slightly larger number, so we don't overload the memory but also make the loop a bit more efficient.
IIUC, 1 here is just the min needed for
kvm_mmu_topup_memory_cacheto return success. I chose 1 for each because it's the minimum necessary to make forward progress (split one large page).
Quoted 7 lines
The @min parameter is minimum number of pages that _must_ be available in the cache, i.e. it's the maximum number of pages that can theoretically be used by whatever upcoming operation is going to be consuming pages from the cache.
So '1' is technically correct, but I think it's the wrong choice given the behavior of this code. E.g. if there's 1 object in the cache, the initial top-up will do nothing,
This scenario will not happen though, since we free the caches after splitting. So, the next time userspace enables dirty logging on a memslot and we go to do the initial top-up the caches will have 0 objects.
Quoted 4 lines
and then
tdp_mmu_split_large_pages_root()will almost immediately dropmmu_lockto topup the cache. Since the in-loop usage explicitly checks for an empty cache, i.e. any non-zero @min will have identical behavior, I think it makes sense to useKVM_ARCH_NR_OBJS_PER_MEMORY_CACHE_and_ add a comment explaining why.
If we set the min to KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE, kvm_mmu_topup_memory_cache will return ENOMEM if it can't allocate at least KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE objects, even though we really only need 1 to make forward progress.
It's a total edge case but there could be a scenario where userspace sets the cgroup memory limits so tight that we can't allocate KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE objects when splitting the last few pages and in the end we only needed 1 or 2 objects to finish splitting. In this case we'd end up with a spurious pr_warn and may not split the last few pages depending on which cache failed to get topped up.
Quoted 7 lines
Quoted 4 lines
No matter what you pass for min
kvm_mmu_topup_memory_cache()will still always try to allocateKVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects.No, it will try to allocate
KVM_ARCH_NR_OBJS_PER_MEMORY_CACHEif and only if there are fewer than @min objects in the cache.
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 32 lines · David Matlack
Quoted 31 lines · Sean Christopherson
Quoted 29 lines · David Matlack
Quoted 4 lines · Peter Xu
Hi, David,
On Fri, Nov 19, 2021 at 11:57:56PM +0000, David Matlack wrote:
Quoted 15 lines
arch/x86/include/asm/kvm_host.h struct kvm_arch { · line 1237
Quoted 11 lines
arch/x86/include/asm/kvm_host.h +3
-0@@ -1232,6 +1232,9 @@ struct kvm_arch {hpa_t hv_root_tdp;spinlock_t hv_root_tdp_lock;#endif + +/* MMU caches used when splitting large pages during VM-ioctls. */ +struct kvm_mmu_memory_caches split_caches;Are
mmu_gfn_array_cacheandmmu_pte_list_desc_cachewasted here? I saw that "structkvm_mmu_memory_cache" still takes up quite a few hundreds of bytes, just want to make sure we won't waste them in vain.Yes they are wasted right now. But there's a couple of things to keep in mind:
1. They are also wasted in every vCPU (in the per-vCPU caches) that does not use the shadow MMU.
2. They will (I think) be used eventually when I add Eager Page Splitting support to the shadow MMU.
3.split_cachesis per-VM so it's only a few hundred bytes per VM.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
If we really want to save the memory the right way forward might be to make each
kvm_mmu_memory_cachea pointer instead of an embedded struct. Then we can allocate each dynamically only as needed. I can add that to my TODO list but I don't think it'd be worth blocking this on it given the points above.
Yeah I never meant to block this series just for this. :)
If there's plan to move forward with shadow mmu support and they'll be needed at last, then it's good to me to keep it as is. Maybe before adding the shadow mmu support we add a comment above the structure? Depending on whether the shadow mmu support is in schedule or not, I think.
Quoted 53 lines
Quoted 30 lines
Quoted 23 lines
Quoted 23 lines
[...]
Quoted 4 lines
arch/x86/include/asm/kvm_host.h +4
-0+int mmu_topup_split_caches (struct kvm *kvm) +{ +struct kvm_mmu_memory_caches *split_caches = &kvm->arch.split_caches; +int r;arch/x86/include/asm/kvm_host.h
Quoted 10 lines
arch/x86/include/asm/kvm_host.h +10
-0+ +assert_split_caches_invariants (kvm); + + r =kvm_mmu_topup_memory_cache (&split_caches->page_header_cache,1 ); +if (r) + goto out; + + r =kvm_mmu_topup_memory_cache (&split_caches->shadow_page_cache,1 ); +if (r) + goto out;Is it intended to only top-up with one cache object? IIUC this means we'll try to proactively yield the cpu for each of the huge page split right after the object is consumed.
Quoted 6 lines
Quoted 2 lines
Wondering whether it be more efficient to make it a slightly larger number, so we don't overload the memory but also make the loop a bit more efficient.
IIUC, 1 here is just the min needed for
kvm_mmu_topup_memory_cacheto return success. I chose 1 for each because it's the minimum necessary to make forward progress (split one large page).Quoted 7 lines
The @min parameter is minimum number of pages that _must_ be available in the cache, i.e. it's the maximum number of pages that can theoretically be used by whatever upcoming operation is going to be consuming pages from the cache.
So '1' is technically correct, but I think it's the wrong choice given the behavior of this code. E.g. if there's 1 object in the cache, the initial top-up will do nothing,
This scenario will not happen though, since we free the caches after splitting. So, the next time userspace enables dirty logging on a memslot and we go to do the initial top-up the caches will have 0 objects.
Quoted 4 lines
and then
tdp_mmu_split_large_pages_root()will almost immediately dropmmu_lockto topup the cache. Since the in-loop usage explicitly checks for an empty cache, i.e. any non-zero @min will have identical behavior, I think it makes sense to useKVM_ARCH_NR_OBJS_PER_MEMORY_CACHE_and_ add a comment explaining why.If we set the min to
KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE,kvm_mmu_topup_memory_cachewill return ENOMEM if it can't allocate at leastKVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects, even though we really only need 1 to make forward progress.
Quoted 7 lines
It's a total edge case but there could be a scenario where userspace sets the cgroup memory limits so tight that we can't allocate
KVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects when splitting the last few pages and in the end we only needed 1 or 2 objects to finish splitting. In this case we'd end up with a spuriouspr_warnand may not split the last few pages depending on which cache failed to get topped up.
IMHO when -ENOMEM happens, instead of keep trying with 1 shadow sp we should just bail out even earlier.
Say, if we only have 10 (<40) pages left for shadow sp's use, we'd better make good use of them lazily to be consumed in follow up page faults when the guest accessed any of the huge pages, rather than we take them all over to split the next continuous huge pages assuming it'll be helpful..
From that POV I have a slight preference over Sean's suggestion because that'll make us fail earlier. But I agree it shouldn't be a big deal.
Thanks,
Signature · 1 line
Peter Xu
Sean Christopherson
maintainerRe: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 10 lines · Peter Xu
Quoted 9 lines · David Matlack
Quoted 3 lines · Sean Christopherson
So '1' is technically correct, but I think it's the wrong choice given the behavior of this code. E.g. if there's 1 object in the cache, the initial top-up will do nothing,
This scenario will not happen though, since we free the caches after splitting. So, the next time userspace enables dirty logging on a memslot and we go to do the initial top-up the caches will have 0 objects.
Ah.
Quoted 21 lines
Quoted 10 lines
Quoted 4 lines
and then
tdp_mmu_split_large_pages_root()will almost immediately dropmmu_lockto topup the cache. Since the in-loop usage explicitly checks for an empty cache, i.e. any non-zero @min will have identical behavior, I think it makes sense to useKVM_ARCH_NR_OBJS_PER_MEMORY_CACHE_and_ add a comment explaining why.If we set the min to
KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE,kvm_mmu_topup_memory_cachewill return ENOMEM if it can't allocate at leastKVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects, even though we really only need 1 to make forward progress.Quoted 7 lines
It's a total edge case but there could be a scenario where userspace sets the cgroup memory limits so tight that we can't allocate
KVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects when splitting the last few pages and in the end we only needed 1 or 2 objects to finish splitting. In this case we'd end up with a spuriouspr_warnand may not split the last few pages depending on which cache failed to get topped up.IMHO when
-ENOMEMhappens, instead of keep trying with 1 shadow sp we should just bail out even earlier.
Quoted 7 lines
Say, if we only have 10 (<40) pages left for shadow sp's use, we'd better make good use of them lazily to be consumed in follow up page faults when the guest accessed any of the huge pages, rather than we take them all over to split the next continuous huge pages assuming it'll be helpful..
From that POV I have a slight preference over Sean's suggestion because that'll make us fail earlier. But I agree it shouldn't be a big deal.
Hmm, in this particular case, I think using the caches is the wrong approach. The behavior of pre-filling the caches makes sense for vCPUs because faults may need multiple objects and filling the cache ensures the entire fault can be handled without dropping mmu_lock. And any extra/unused objects can be used by future faults. For page splitting, neither of those really holds true. If there are a lot of pages to split, KVM will have to drop mmu_lock to refill the cache. And if there are few pages to split, or the caches are refilled toward the end of the walk, KVM may end up with a pile of unused objects it needs to free.
Since this code already needs to handle failure, and more importantly, it's a best-effort optimization, I think trying to use the caches is a square peg, round hole scenario.
Rather than use the caches, we could do allocation 100% on-demand and never drop mmu_lock to do allocation. The one caveat is that direct reclaim would need to be disallowed so that the allocation won't sleep. That would mean that eager splitting would fail under heavy memory pressure when it otherwise might succeed by reclaiming. That would mean vCPUs get penalized as they'd need to do the splitting on fault and potentially do direct reclaim as well. It's not obvious that that would be a problem in practice, e.g. the vCPU is probably already seeing a fair amount of disruption due to memory pressure, and slowing down vCPUs might alleviate some of that pressure.
Not using the cache would also reduce the extra complexity, e.g. no need for special mmu_cache handling or a variant of tdp_mmu_iter_cond_resched().
I'm thinking something like this (very incomplete):
static void init_tdp_mmu_page(struct kvm_mmu_page *sp, u64 *spt, gfn_t gfn,
union kvm_mmu_page_role role)
{
sp->spt = spt;
set_page_private(virt_to_page(sp->spt), (unsigned long)sp);
sp->role = role;
sp->gfn = gfn;
sp->tdp_mmu_page = true;
trace_kvm_mmu_get_page(sp, true);
}static struct kvm_mmu_page *alloc_tdp_mmu_page(struct kvm_vcpu *vcpu, gfn_t gfn,
union kvm_mmu_page_role role)
{
struct kvm_mmu_page *sp;
u64 *spt;
sp = kvm_mmu_memory_cache_alloc(&vcpu->arch.mmu_page_header_cache);
spt = kvm_mmu_memory_cache_alloc(&vcpu->arch.mmu_shadow_page_cache);
init_tdp_mmu_page(sp, spt, gfn, role);
}static union kvm_mmu_page_role get_child_page_role(struct tdp_iter *iter)
{
struct kvm_mmu_page *parent = sptep_to_sp(rcu_dereference(iter->sptep));
union kvm_mmu_page_role role = parent->role;
role.level--;
return role;
}static bool tdp_mmu_install_sp_atomic(struct kvm *kvm,
struct tdp_iter *iter, struct kvm_mmu_page *sp, bool account_nx)
{
u64 spte;
spte = make_nonleaf_spte(sp->spt, !shadow_accessed_mask);
if (tdp_mmu_set_spte_atomic(kvm, iter, spte)) {
tdp_mmu_link_page(kvm, sp, account_nx);
return true;
}
return false;
}static void tdp_mmu_split_large_pages_root(struct kvm *kvm, struct kvm_mmu_page *root,
gfn_t start, gfn_t end, int target_level)
{
/*
* Disallow direct reclaim, allocations will be made while holding
* mmu_lock and must not sleep.
*/
gfp_t gfp = (GFP_KERNEL_ACCOUNT | __GFP_ZERO) & ~__GFP_DIRECT_RECLAIM;
struct kvm_mmu_page *sp = NULL;
struct tdp_iter iter;
bool flush = false;
u64 *spt = NULL;
int r;
rcu_read_lock();
/*
* Traverse the page table splitting all large pages above the target
* level into one lower level. For example, if we encounter a 1GB page
* we split it into 512 2MB pages.
*
* Since the TDP iterator uses a pre-order traversal, we are guaranteed
* to visit an SPTE before ever visiting its children, which means we
* will correctly recursively split large pages that are more than one
* level above the target level (e.g. splitting 1GB to 2MB to 4KB).
*/
for_each_tdp_pte_min_level(iter, root, target_level + 1, start, end) {
retry:
if (tdp_mmu_iter_cond_resched(kvm, &iter, flush, true))
continue;
if (!is_shadow_present_pte(iter.old_spte || !is_large_pte(pte))
continue;
if (!sp) {
sp = kmem_cache_alloc(mmu_page_header_cache, gfp);
if (!sp)
break;
spt = (void *)__get_free_page(gfp);
if (!spt)
break;
}
init_tdp_mmu_page(sp, spt, iter->gfn,
get_child_page_role(&iter));
if (!tdp_mmu_split_large_page(kvm, &iter, sp))
goto retry;
sp = NULL;
spt = NULL;
}
free_page((unsigned long)spt);
kmem_cache_free(mmu_page_header_cache, sp);
rcu_read_unlock();
if (flush)
kvm_flush_remote_tlbs(kvm);
}Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 57 lines · Sean Christopherson
Quoted 10 lines · Peter Xu
Quoted 9 lines · David Matlack
Quoted 3 lines · Sean Christopherson
So '1' is technically correct, but I think it's the wrong choice given the behavior of this code. E.g. if there's 1 object in the cache, the initial top-up will do nothing,
This scenario will not happen though, since we free the caches after splitting. So, the next time userspace enables dirty logging on a memslot and we go to do the initial top-up the caches will have 0 objects.
Ah.
Quoted 21 lines
Quoted 10 lines
Quoted 4 lines
and then
tdp_mmu_split_large_pages_root()will almost immediately dropmmu_lockto topup the cache. Since the in-loop usage explicitly checks for an empty cache, i.e. any non-zero @min will have identical behavior, I think it makes sense to useKVM_ARCH_NR_OBJS_PER_MEMORY_CACHE_and_ add a comment explaining why.If we set the min to
KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE,kvm_mmu_topup_memory_cachewill return ENOMEM if it can't allocate at leastKVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects, even though we really only need 1 to make forward progress.Quoted 7 lines
It's a total edge case but there could be a scenario where userspace sets the cgroup memory limits so tight that we can't allocate
KVM_ARCH_NR_OBJS_PER_MEMORY_CACHEobjects when splitting the last few pages and in the end we only needed 1 or 2 objects to finish splitting. In this case we'd end up with a spuriouspr_warnand may not split the last few pages depending on which cache failed to get topped up.IMHO when
-ENOMEMhappens, instead of keep trying with 1 shadow sp we should just bail out even earlier.Quoted 7 lines
Say, if we only have 10 (<40) pages left for shadow sp's use, we'd better make good use of them lazily to be consumed in follow up page faults when the guest accessed any of the huge pages, rather than we take them all over to split the next continuous huge pages assuming it'll be helpful..
From that POV I have a slight preference over Sean's suggestion because that'll make us fail earlier. But I agree it shouldn't be a big deal.
Hmm, in this particular case, I think using the caches is the wrong approach. The behavior of pre-filling the caches makes sense for vCPUs because faults may need multiple objects and filling the cache ensures the entire fault can be handled without dropping
mmu_lock. And any extra/unused objects can be used by future faults. For page splitting, neither of those really holds true. If there are a lot of pages to split, KVM will have to dropmmu_lockto refill the cache. And if there are few pages to split, or the caches are refilled toward the end of the walk, KVM may end up with a pile of unused objects it needs to free.Since this code already needs to handle failure, and more importantly, it's a best-effort optimization, I think trying to use the caches is a square peg, round hole scenario.
Quoted 8 lines
Rather than use the caches, we could do allocation 100% on-demand and never drop
mmu_lockto do allocation. The one caveat is that direct reclaim would need to be disallowed so that the allocation won't sleep. That would mean that eager splitting would fail under heavy memory pressure when it otherwise might succeed by reclaiming. That would mean vCPUs get penalized as they'd need to do the splitting on fault and potentially do direct reclaim as well. It's not obvious that that would be a problem in practice, e.g. the vCPU is probably already seeing a fair amount of disruption due to memory pressure, and slowing down vCPUs might alleviate some of that pressure.
Not necessarily. The vCPUs might be running just fine in the VM being split because they are in their steady state and not faulting in any new memory. (Memory pressure might be coming from another VM landing on the host.)
IMO, if we have an opportunity to avoid doing direct reclaim in the critical path of customer execution we should take it.
The on-demand approach will also increase the amount of time we have to hold the MMU lock to page splitting. This is not too terrible for the TDP MMU since we are holding the MMU lock in read mode, but is going to become a problem when we add page splitting support for the shadow MMU.
I do agree that the caches approach, as implemented, will inevitably end up with a pile of unused objects at the end that need to be freed. I'd be happy to take a look and see if there's anyway to reduce the amount of unused objects at the end with a bit smarter top-up logic.
Quoted 117 lines
Not using the cache would also reduce the extra complexity, e.g. no need for special
mmu_cachehandling or a variant oftdp_mmu_iter_cond_resched().I'm thinking something like this (very incomplete):
static void init_tdp_mmu_page(struct
kvm_mmu_page*sp, u64 *spt,gfn_tgfn,
unionkvm_mmu_page_rolerole){ sp->spt = spt; set_page_private(virt_to_page(sp->spt), (unsigned long)sp); sp->role = role; sp->gfn = gfn; sp->tdp_mmu_page = true; trace_kvm_mmu_get_page(sp, true); }static struct
kvm_mmu_page*alloc_tdp_mmu_page(structkvm_vcpu*vcpu,gfn_tgfn,
unionkvm_mmu_page_rolerole){ struct kvm_mmu_page *sp; u64 *spt; sp = kvm_mmu_memory_cache_alloc(&vcpu->arch.mmu_page_header_cache); spt = kvm_mmu_memory_cache_alloc(&vcpu->arch.mmu_shadow_page_cache); init_tdp_mmu_page(sp, spt, gfn, role); }static union
kvm_mmu_page_roleget_child_page_role(struct tdp_iter *iter){ struct kvm_mmu_page *parent = sptep_to_sp(rcu_dereference(iter->sptep)); union kvm_mmu_page_role role = parent->role; role.level--; return role; }static bool tdp_mmu_install_sp_atomic(struct kvm *kvm,
structtdp_iter*iter, structkvm_mmu_page*sp, boolaccount_nx){ u64 spte; spte = make_nonleaf_spte(sp->spt, !shadow_accessed_mask); if (tdp_mmu_set_spte_atomic(kvm, iter, spte)) { tdp_mmu_link_page(kvm, sp, account_nx); return true; } return false; }static void tdp_mmu_split_large_pages_root(struct kvm *kvm, struct
kvm_mmu_page*root,
gfn_tstart,gfn_tend, inttarget_level){ /* * Disallow direct reclaim, allocations will be made while holding * mmu_lock and must not sleep. */ gfp_t gfp = (GFP_KERNEL_ACCOUNT | __GFP_ZERO) & ~__GFP_DIRECT_RECLAIM; struct kvm_mmu_page *sp = NULL; struct tdp_iter iter; bool flush = false; u64 *spt = NULL; int r; rcu_read_lock(); /* * Traverse the page table splitting all large pages above the target * level into one lower level. For example, if we encounter a 1GB page * we split it into 512 2MB pages. * * Since the TDP iterator uses a pre-order traversal, we are guaranteed * to visit an SPTE before ever visiting its children, which means we * will correctly recursively split large pages that are more than one * level above the target level (e.g. splitting 1GB to 2MB to 4KB). */ for_each_tdp_pte_min_level(iter, root, target_level + 1, start, end) { retry: if (tdp_mmu_iter_cond_resched(kvm, &iter, flush, true)) continue; if (!is_shadow_present_pte(iter.old_spte || !is_large_pte(pte)) continue; if (!sp) { sp = kmem_cache_alloc(mmu_page_header_cache, gfp); if (!sp) break; spt = (void *)__get_free_page(gfp); if (!spt) break; } init_tdp_mmu_page(sp, spt, iter->gfn, get_child_page_role(&iter)); if (!tdp_mmu_split_large_page(kvm, &iter, sp)) goto retry; sp = NULL; spt = NULL; } free_page((unsigned long)spt); kmem_cache_free(mmu_page_header_cache, sp); rcu_read_unlock(); if (flush) kvm_flush_remote_tlbs(kvm); }
Sean Christopherson
maintainerRe: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 23 lines · David Matlack
Quoted 13 lines · Sean Christopherson
Hmm, in this particular case, I think using the caches is the wrong approach. The behavior of pre-filling the caches makes sense for vCPUs because faults may need multiple objects and filling the cache ensures the entire fault can be handled without dropping
mmu_lock. And any extra/unused objects can be used by future faults. For page splitting, neither of those really holds true. If there are a lot of pages to split, KVM will have to dropmmu_lockto refill the cache. And if there are few pages to split, or the caches are refilled toward the end of the walk, KVM may end up with a pile of unused objects it needs to free.Since this code already needs to handle failure, and more importantly, it's a best-effort optimization, I think trying to use the caches is a square peg, round hole scenario.
Quoted 8 lines
Rather than use the caches, we could do allocation 100% on-demand and never drop
mmu_lockto do allocation. The one caveat is that direct reclaim would need to be disallowed so that the allocation won't sleep. That would mean that eager splitting would fail under heavy memory pressure when it otherwise might succeed by reclaiming. That would mean vCPUs get penalized as they'd need to do the splitting on fault and potentially do direct reclaim as well. It's not obvious that that would be a problem in practice, e.g. the vCPU is probably already seeing a fair amount of disruption due to memory pressure, and slowing down vCPUs might alleviate some of that pressure.
Quoted 4 lines
Not necessarily. The vCPUs might be running just fine in the VM being split because they are in their steady state and not faulting in any new memory. (Memory pressure might be coming from another VM landing on the host.)
Hrm, true.
Quoted 10 lines
IMO, if we have an opportunity to avoid doing direct reclaim in the critical path of customer execution we should take it.
The on-demand approach will also increase the amount of time we have to hold the MMU lock to page splitting. This is not too terrible for the TDP MMU since we are holding the MMU lock in read mode, but is going to become a problem when we add page splitting support for the shadow MMU.
Quoted 4 lines
I do agree that the caches approach, as implemented, will inevitably end up with a pile of unused objects at the end that need to be freed. I'd be happy to take a look and see if there's anyway to reduce the amount of unused objects at the end with a bit smarter top-up logic.
It's not just the extra objects, it's the overall complexity that bothers me. Complexity isn't really the correct word, it's more that as written, the logic is spread over several files and is disingenuous from the perspective that the split_cache is in kvm->arch, which implies persistence, but the cache are completely torn down after evey memslot split.
I suspect part of the problem is that the code is trying to plan for a future where nested MMUs also support splitting large pages. Usually I'm all for that sort of thing, but in this case it creates a lot of APIs that should not exist, either because the function is not needed at all, or because it's a helper buried in tdp_mmu.c. E.g. assert_split_caches_invariants() is overkill.
That's solvable by refactoring and shuffling code, but using kvm_mmu_memory_cache still feels wrong. The caches don't fully solve the might_sleep() problem since the loop still has to drop mmu_lock purely because it needs to allocate memory, and at the same time the caches are too agressive because we can theoretically get false positives on OOM scenarios, e.g. a topup could fail when trying to allocate 25 objects, when only 1 is needed. We could enhance the cache code, which is pretty rudimentary, but it still feels forced.
One thing we can take advantage of is that remote TLB flushes can be deferred until after all roots are done, and don't need to be serviced if mmu_lock is dropped. Changes from a hugepage to a collection of smaller pages is atomic, no memory is freed, and there are no changes in gfn=>pfn made by the split. If something else comes along and modifies the newly created sp or its children, then it will flush accordingly. Similar to write-protecting the page, the only requirement is that all vCPUs see the small pages before the ioctl() returns, i.e. before userspace can query the dirty log. Never needing to flush is one less reason to use a variant of tdp_mmu_iter_cond_resched().
So, what if we do something like this? Try to allocate on-demand without dropping mmu_lock. In the happy case, it will succeed and there's no need to drop mmu_lock. If allocation fails, drop RCU and mmu_lock and retry with direct relcaim allowed.
Some ugly gotos to reduce indentation, there's probably a better way to dress this up. Comments obviously needed. This also doesn't track whether or not a flush is needed, that will sadly need to be an in/out param, assuming we want to return success/failure.
static struct kvm_mmu_page *tdp_mmu_alloc_sp(gfp_t allow_direct_reclaim)
{
gfp_t gfp = GFP_KERNEL_ACCOUNT | __GFP_ZERO | allow_direct_reclaim;
struct kvm_mmu_page *sp;
u64 *spt;
spt = (void *)__get_free_page(gfp);
if (!spt)
return NULL;
sp = kmem_cache_alloc(mmu_page_header_cache, gfp);
if (!sp) {
free_page((unsigned long)spt);
return NULL;
}
sp->spt = spt;
return sp;
}static int tdp_mmu_split_large_pages(struct kvm *kvm, struct kvm_mmu_page *root,
gfn_t start, gfn_t end, int target_level)
{
struct kvm_mmu_page *sp = NULL;
struct tdp_iter iter;
rcu_read_lock();
for_each_tdp_pte_min_level(iter, root, target_level + 1, start, end) {
retry:
if (tdp_mmu_iter_cond_resched(kvm, &iter, false, true))
continue;
if (!is_shadow_present_pte(iter.old_spte || !is_large_pte(pte))
continue;
if (likely(sp))
goto do_split;
sp = tdp_mmu_alloc_sp(0);
if (!sp) {
rcu_read_unlock();
read_unlock(&kvm->mmu_lock);
sp = tdp_mmu_alloc_sp(__GFP_DIRECT_RECLAIM);
read_lock(&kvm->mmu_lock);
if (!sp)
return -ENOMEM;
rcu_read_lock();
tdp_iter_restart(iter);
continue;
}do_split:
init_tdp_mmu_page(sp, iter->gfn, get_child_page_role(&iter)); if (!tdp_mmu_split_large_page(kvm, &iter, sp)) goto retry; sp = NULL; } rcu_read_unlock(); return 0; }
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 59 lines · Sean Christopherson
Quoted 23 lines · David Matlack
Quoted 13 lines · Sean Christopherson
Hmm, in this particular case, I think using the caches is the wrong approach. The behavior of pre-filling the caches makes sense for vCPUs because faults may need multiple objects and filling the cache ensures the entire fault can be handled without dropping
mmu_lock. And any extra/unused objects can be used by future faults. For page splitting, neither of those really holds true. If there are a lot of pages to split, KVM will have to dropmmu_lockto refill the cache. And if there are few pages to split, or the caches are refilled toward the end of the walk, KVM may end up with a pile of unused objects it needs to free.Since this code already needs to handle failure, and more importantly, it's a best-effort optimization, I think trying to use the caches is a square peg, round hole scenario.
Quoted 8 lines
Rather than use the caches, we could do allocation 100% on-demand and never drop
mmu_lockto do allocation. The one caveat is that direct reclaim would need to be disallowed so that the allocation won't sleep. That would mean that eager splitting would fail under heavy memory pressure when it otherwise might succeed by reclaiming. That would mean vCPUs get penalized as they'd need to do the splitting on fault and potentially do direct reclaim as well. It's not obvious that that would be a problem in practice, e.g. the vCPU is probably already seeing a fair amount of disruption due to memory pressure, and slowing down vCPUs might alleviate some of that pressure.Quoted 4 lines
Not necessarily. The vCPUs might be running just fine in the VM being split because they are in their steady state and not faulting in any new memory. (Memory pressure might be coming from another VM landing on the host.)
Hrm, true.
Quoted 10 lines
IMO, if we have an opportunity to avoid doing direct reclaim in the critical path of customer execution we should take it.
The on-demand approach will also increase the amount of time we have to hold the MMU lock to page splitting. This is not too terrible for the TDP MMU since we are holding the MMU lock in read mode, but is going to become a problem when we add page splitting support for the shadow MMU.
Quoted 4 lines
I do agree that the caches approach, as implemented, will inevitably end up with a pile of unused objects at the end that need to be freed. I'd be happy to take a look and see if there's anyway to reduce the amount of unused objects at the end with a bit smarter top-up logic.
It's not just the extra objects, it's the overall complexity that bothers me. Complexity isn't really the correct word, it's more that as written, the logic is spread over several files and is disingenuous from the perspective that the
split_cacheis inkvm->arch, which implies persistence, but the cache are completely torn down after evey memslot split.I suspect part of the problem is that the code is trying to plan for a future where nested MMUs also support splitting large pages. Usually I'm all for that sort of thing, but in this case it creates a lot of APIs that should not exist, either because the function is not needed at all, or because it's a helper buried in
tdp_mmu.c. E.g.assert_split_caches_invariants()is overkill.
Quoted 3 lines
That's solvable by refactoring and shuffling code, but using
kvm_mmu_memory_cachestill feels wrong. The caches don't fully solve themight_sleep()problem since the loop still has to dropmmu_lockpurely because it needs to allocate memory,
I thought dropping the lock to allocate memory was a good thing. It reduces the length of time we hold the RCU read lock and mmu_lock in read mode. Plus it avoids the retry-with-reclaim and lets us reuse the existing sp allocation code.
Eager page splitting itself does not need to be that performant since it's not on the critical path of vCPU execution. But holding the MMU lock can negatively affect vCPU performance.
But your preference is to allocate without dropping the lock when possible. Why?
Quoted 3 lines
and at the same time the caches are too agressive because we can theoretically get false positives on OOM scenarios, e.g. a topup could fail when trying to allocate 25 objects, when only 1 is needed.
This is why I picked a min of 1 for the cache top-up. But this would be true if we increased the min beyond 1.
Quoted 6 lines
We could enhance the cache code, which is
pretty rudimentary, but it still feels forced.One thing we can take advantage of is that remote TLB flushes can be deferred until after all roots are done, and don't need to be serviced if
mmu_lockis dropped.
Good point. I'll revise the TLB flushing in v1 regardless.
Quoted 88 lines
Changes from a hugepage to a collection of smaller pages is atomic, no memory is freed, and there are no changes in gfn=>pfn made by the split. If something else comes along and modifies the newly created sp or its children, then it will flush accordingly. Similar to write-protecting the page, the only requirement is that all vCPUs see the small pages before the
ioctl()returns, i.e. before userspace can query the dirty log. Never needing to flush is one less reason to use a variant oftdp_mmu_iter_cond_resched().So, what if we do something like this? Try to allocate on-demand without dropping
mmu_lock. In the happy case, it will succeed and there's no need to dropmmu_lock. If allocation fails, drop RCU andmmu_lockand retry with direct relcaim allowed.Some ugly gotos to reduce indentation, there's probably a better way to dress this up. Comments obviously needed. This also doesn't track whether or not a flush is needed, that will sadly need to be an in/out param, assuming we want to return success/failure.
static struct
kvm_mmu_page*tdp_mmu_alloc_sp(gfp_tallow_direct_reclaim){ gfp_t gfp = GFP_KERNEL_ACCOUNT | __GFP_ZERO | allow_direct_reclaim; struct kvm_mmu_page *sp; u64 *spt; spt = (void *)__get_free_page(gfp); if (!spt) return NULL; sp = kmem_cache_alloc(mmu_page_header_cache, gfp); if (!sp) { free_page((unsigned long)spt); return NULL; } sp->spt = spt; return sp; }static int tdp_mmu_split_large_pages(struct kvm *kvm, struct
kvm_mmu_page*root,
gfn_tstart,gfn_tend, inttarget_level){ struct kvm_mmu_page *sp = NULL; struct tdp_iter iter; rcu_read_lock(); for_each_tdp_pte_min_level(iter, root, target_level + 1, start, end) { retry: if (tdp_mmu_iter_cond_resched(kvm, &iter, false, true)) continue; if (!is_shadow_present_pte(iter.old_spte || !is_large_pte(pte)) continue; if (likely(sp)) goto do_split; sp = tdp_mmu_alloc_sp(0); if (!sp) { rcu_read_unlock(); read_unlock(&kvm->mmu_lock); sp = tdp_mmu_alloc_sp(__GFP_DIRECT_RECLAIM); read_lock(&kvm->mmu_lock); if (!sp) return -ENOMEM; rcu_read_lock(); tdp_iter_restart(iter); continue; }
do_split:init_tdp_mmu_page(sp, iter->gfn, get_child_page_role(&iter)); if (!tdp_mmu_split_large_page(kvm, &iter, sp)) goto retry; sp = NULL; } rcu_read_unlock(); return 0; }
Sean Christopherson
maintainerRe: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 13 lines · David Matlack
Quoted 12 lines · Sean Christopherson
It's not just the extra objects, it's the overall complexity that bothers me. Complexity isn't really the correct word, it's more that as written, the logic is spread over several files and is disingenuous from the perspective that the
split_cacheis inkvm->arch, which implies persistence, but the cache are completely torn down after evey memslot split.I suspect part of the problem is that the code is trying to plan for a future where nested MMUs also support splitting large pages. Usually I'm all for that sort of thing, but in this case it creates a lot of APIs that should not exist, either because the function is not needed at all, or because it's a helper buried in
tdp_mmu.c. E.g.assert_split_caches_invariants()is overkill.
Quoted 8 lines
Quoted 3 lines
That's solvable by refactoring and shuffling code, but using
kvm_mmu_memory_cachestill feels wrong. The caches don't fully solve themight_sleep()problem since the loop still has to dropmmu_lockpurely because it needs to allocate memory,I thought dropping the lock to allocate memory was a good thing. It reduces the length of time we hold the RCU read lock and
mmu_lockin read mode. Plus it avoids the retry-with-reclaim and lets us reuse the existing sp allocation code.
It's not a simple reuse though, e.g. it needs new logic to detect when the caches are empty, requires a variant of tdp_mmu_iter_cond_resched(), needs its own instance of caches and thus initialization/destruction of the caches, etc...
Quoted 5 lines
Eager page splitting itself does not need to be that performant since it's not on the critical path of vCPU execution. But holding the MMU lock can negatively affect vCPU performance.
But your preference is to allocate without dropping the lock when possible. Why?
Because they're two different things. Lock contention is already handled by tdp_mmu_iter_cond_resched(). If mmu_lock is not contended, holding it for a long duration is a complete non-issue.
Dropping mmu_lock means restarting the walk at the root because a different task may have zapped/changed upper level entries. If every allocation is dropping mmu_lock, that adds up to a lot of extra memory accesses, especially when using 5-level paging.
Batching allocations via mmu_caches mostly works around that problem, but IMO it's more complex overall than the retry-on-failure approach because it bleeds core details into several locations, e.g. the split logic needs to know intimate details of kvm_mmu_memory_cache, and we end up with two (or one complex) versions of tdp_mmu_iter_cond_resched().
In general, I also dislike relying on magic numbers (the capacity of the cache) for performance. At best, we have to justify the magic number, now and in the future. At worst, someone will have a use case that doesn't play nice with KVM's chosen magic number and then we have to do more tuning, e.g. see the PTE prefetch stuff where the magic number of '8' (well, 7) ran out of gas for modern usage. I don't actually think tuning will be problematic for this case, but I'd rather avoid the discussion entirely if possible.
I'm not completely opposed to using kvm_mmu_memory_cache to batch allocations, but I think we should do so if and only if batching has measurably better performance for things we care about. E.g. if eager splitting takes n% longer under heavy memory pressure, but vCPUs aren't impacted, do we care?
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 32 lines · Sean Christopherson
Quoted 13 lines · David Matlack
Quoted 12 lines · Sean Christopherson
It's not just the extra objects, it's the overall complexity that bothers me. Complexity isn't really the correct word, it's more that as written, the logic is spread over several files and is disingenuous from the perspective that the
split_cacheis inkvm->arch, which implies persistence, but the cache are completely torn down after evey memslot split.kmem_cache_alloc
I suspect part of the problem is that the code is trying to plan for a future where nested MMUs also support splitting large pages. Usually I'm all for that sort of thing, but in this case it creates a lot of APIs that should not exist, either because the function is not needed at all, or because it's a helper buried intdp_mmu.c. E.g.assert_split_caches_invariants()is overkill.Quoted 8 lines
Quoted 3 lines
That's solvable by refactoring and shuffling code, but using
kvm_mmu_memory_cachestill feels wrong. The caches don't fully solve themight_sleep()problem since the loop still has to dropmmu_lockpurely because it needs to allocate memory,I thought dropping the lock to allocate memory was a good thing. It reduces the length of time we hold the RCU read lock and
mmu_lockin read mode. Plus it avoids the retry-with-reclaim and lets us reuse the existing sp allocation code.It's not a simple reuse though, e.g. it needs new logic to detect when the caches are empty, requires a variant of
tdp_mmu_iter_cond_resched(), needs its own instance of caches and thus initialization/destruction of the caches, etc...Quoted 4 lines
Eager page splitting itself does not need to be that performant since it's not on the critical path of vCPU execution. But holding the MMU lock can negatively affect vCPU performance.
Quoted 5 lines
Quoted 1 line
But your preference is to allocate without dropping the lock when possible. Why?
Because they're two different things. Lock contention is already handled by
tdp_mmu_iter_cond_resched(). Ifmmu_lockis not contended, holding it for a long duration is a complete non-issue.
So I think you are positing that disabling reclaim will make the allocations fast enough that the time between tdp_mmu_iter_cond_resched checks will be acceptable. Is there really no risk of long tail latency in kmem_cache_alloc() or __get_free_page()? Even if it's rare, they will be common at scale.
This is why I'm being so hesitant, and prefer to avoid the problem entirely by doing all allocations outside the lock. But I'm honestly more than happy to be convinced otherwise and go with your approach.
Quoted 24 lines
Dropping
mmu_lockmeans restarting the walk at the root because a different task may have zapped/changed upper level entries. If every allocation is droppingmmu_lock, that adds up to a lot of extra memory accesses, especially when using 5-level paging.Batching allocations via
mmu_cachesmostly works around that problem, but IMO it's more complex overall than the retry-on-failure approach because it bleeds core details into several locations, e.g. the split logic needs to know intimate details ofkvm_mmu_memory_cache, and we end up with two (or one complex) versions oftdp_mmu_iter_cond_resched().In general, I also dislike relying on magic numbers (the capacity of the cache) for performance. At best, we have to justify the magic number, now and in the future. At worst, someone will have a use case that doesn't play nice with KVM's chosen magic number and then we have to do more tuning, e.g. see the PTE prefetch stuff where the magic number of '8' (well, 7) ran out of gas for modern usage. I don't actually think tuning will be problematic for this case, but I'd rather avoid the discussion entirely if possible.
I'm not completely opposed to using
kvm_mmu_memory_cacheto batch allocations, but I think we should do so if and only if batching has measurably better performance for things we care about. E.g. if eager splitting takes n% longer under heavy memory pressure, but vCPUs aren't impacted, do we care?
Sean Christopherson
maintainerRe: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 8 lines · David Matlack
Quoted 3 lines · Sean Christopherson
Because they're two different things. Lock contention is already handled by
tdp_mmu_iter_cond_resched(). Ifmmu_lockis not contended, holding it for a long duration is a complete non-issue.So I think you are positing that disabling reclaim will make the allocations fast enough that the time between
tdp_mmu_iter_cond_reschedchecks will be acceptable.
Yep.
Quoted 2 lines
Is there really no risk of long tail latency in
kmem_cache_alloc()or__get_free_page()? Even if it's rare, they will be common at scale.
If there is a potentially long latency in __get_free_page(), then we're hosed no matter what because per alloc_pages(), it's allowed in any context, including NMI, IRQ, and Soft-IRQ. I've no idea how often those contexts allocate, but I assume it's not _that_ rare given the amount of stuff that networking does in Soft-IRQ context, e.g. see the stack trace from commit 2620fe268e80, the use of PF_MEMALLOC, the use of GFP_ATOMIC in napi_alloc_skb, etc... Anb it's not just direct allocations, e.g. anything that uses a radix tree or XArray will potentially trigger allocation on insertion.
But I would be very, very surprised if alloc_pages() without GFP_DIRECT_RECLAIM has a long tail latency, otherwise allocating from any atomic context would be doomed.
Quoted 3 lines
This is why I'm being so hesitant, and prefer to avoid the problem entirely by doing all allocations outside the lock. But I'm honestly more than happy to be convinced otherwise and go with your approach.
Re: [RFC PATCH 12/15] KVM: x86/mmu: Split large pages when dirty logging is enabled
Quoted 14 lines · Sean Christopherson
Quoted 2 lines · David Matlack
Is there really no risk of long tail latency in
kmem_cache_alloc()or__get_free_page()? Even if it's rare, they will be common at scale.If there is a potentially long latency in
__get_free_page(), then we're hosed no matter what because peralloc_pages(), it's allowed in any context, including NMI, IRQ, and Soft-IRQ. I've no idea how often those contexts allocate, but I assume it's not _that_ rare given the amount of stuff that networking does in Soft-IRQ context, e.g. see the stack trace from commit2620fe268e80, the use ofPF_MEMALLOC, the use ofGFP_ATOMICinnapi_alloc_skb, etc... Anb it's not just direct allocations, e.g. anything that uses a radix tree or XArray will potentially trigger allocation on insertion.
Quoted 3 lines
But I would be very, very surprised if
alloc_pages()withoutGFP_DIRECT_RECLAIMhas a long tail latency, otherwise allocating from any atomic context would be doomed.
In that case I agree your approach should not introduce any more MMU lock contention than the split_caches approach in practice, and will require a lot less new code. I'll attempt to do some testing to confirm, but assuming that goes fine I'll go with your approach in v1.
Thanks!
RFC PATCH 13/15 KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
In reply to David MatlackWhen using initially-all-set, large pages are not write-protected when dirty logging is enabled on the memslot. Instead they are write-protected once userspace invoked CLEAR_DIRTY_LOG for the first time, and only for the specific sub-region of the memslot that userspace whishes to clear.
Enhance CLEAR_DIRTY_LOG to also try to split large pages prior to write-protecting to avoid causing write-protection faults on vCPU threads. This also allows userspace to smear the cost of large page splitting across multiple ioctls rather than splitting the entire memslot when not using initially-all-set.
--- arch/x86/include/asm/kvm_host.h | 4 ++++ arch/x86/kvm/mmu/mmu.c | 30 ++++++++++++++++++++++-------- 2 files changed, 26 insertions(+), 8 deletions(-)
arch/x86/include/asm/kvm_host.h +4 -0
@@ -1591,6 +1591,10 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu);void kvm_mmu_slot_remove_write_access (struct kvm *kvm,const struct kvm_memory_slot *memslot,int start_level); +void kvm_mmu_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +u64 start,u64 end, +int target_level);void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm,const struct kvm_memory_slot *memslot,int target_level);
arch/x86/kvm/mmu/mmu.c +22 -8
@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask); +/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K ); +kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */
@@ -5880,21 +5886,17 @@ void kvm_mmu_slot_remove_write_access(struct kvm *kvm,kvm_arch_flush_remote_tlbs_memslot (kvm, memslot); } -void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm, -const struct kvm_memory_slot *memslot, -int target_level) +void kvm_mmu_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +u64 start,u64 end, +int target_level) { -u64 start, end; -if (!is_tdp_mmu_enabled (kvm))return ;if (mmu_topup_split_caches (kvm))return ; - start = memslot->base_gfn; - end = start + memslot->npages; -read_lock (&kvm->mmu_lock);kvm_tdp_mmu_try_split_large_pages (kvm, memslot, start, end, target_level);read_unlock (&kvm->mmu_lock);
@@ -5902,6 +5904,18 @@ void kvm_mmu_slot_try_split_large_pages(struct kvm *kvm,mmu_free_split_caches (kvm); } +void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm, +const struct kvm_memory_slot *memslot, +int target_level) +{ +u64 start, end; + + start = memslot->base_gfn; + end = start + memslot->npages; + +kvm_mmu_try_split_large_pages (kvm, memslot, start, end, target_level); +} +static bool kvm_mmu_zap_collapsible_spte (struct kvm *kvm,struct kvm_rmap_head *rmap_head,const struct kvm_memory_slot *slot)
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 7 lines · David Matlack
arch/x86/kvm/mmu/mmu.c +0
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask);
arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1459
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +6
-0+/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K ); +kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */
Is it intended to try split every time even if we could have split it already? As I remember Paolo mentioned that we can skip split if it's not the 1st CLEAR_LOG on the same range, and IIUC that makes sense.
But indeed I don't see a trivial way to know whether this is the first clear of this range. Maybe we can maintain "how many huge pages are there under current kvm_mmu_page node" somehow? Then if root sp has the counter==0, then we can skip it. Just a wild idea..
Or maybe it's intended to try split unconditionally for some reason? If so it'll be great to mention that either in the commit message or in comments.
Thanks,
Signature · 1 line
Peter Xu
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 24 lines · Peter Xu
Quoted 7 lines · David Matlack
arch/x86/kvm/mmu/mmu.c +0
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask);arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1459
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +6
-0+/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K ); +kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */ Is it intended to try split every time even if we could have split it already? As I remember Paolo mentioned that we can skip split if it's not the 1st
CLEAR_LOGon the same range, and IIUC that makes sense.
Quoted 7 lines
But indeed I don't see a trivial way to know whether this is the first clear of this range. Maybe we can maintain "how many huge pages are there under current
kvm_mmu_pagenode" somehow? Then if root sp has the counter==0, then we can skip it. Just a wild idea..Or maybe it's intended to try split unconditionally for some reason? If so it'll be great to mention that either in the commit message or in comments.
Thanks for calling this out. Could the same be said about the existing code that unconditionally tries to write-protect 2M+ pages? I aimed to keep parity with the write-protection calls (always try to split before write-protecting) but I agree there might be opportunities available to skip altogether.
By the way, looking at this code again I think I see some potential bugs:
- I don't think I ever free split_caches in the initially-all-set case.
- What happens if splitting fails the CLEAR_LOG but succeeds theCLEAR_LOG? We would end up propagating the write-protection on the 2M page down to the 4K page. This might cause issues if using PML.
Quoted 6 lines
Thanks,
--
Peter Xu
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 40 lines · David Matlack
Quoted 24 lines · Peter Xu
Quoted 7 lines · David Matlack
arch/x86/kvm/mmu/mmu.c +0
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask);arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1459
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +6
-0+/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K ); +kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */ Is it intended to try split every time even if we could have split it already? As I remember Paolo mentioned that we can skip split if it's not the 1st
CLEAR_LOGon the same range, and IIUC that makes sense.Quoted 7 lines
But indeed I don't see a trivial way to know whether this is the first clear of this range. Maybe we can maintain "how many huge pages are there under current
kvm_mmu_pagenode" somehow? Then if root sp has the counter==0, then we can skip it. Just a wild idea..Or maybe it's intended to try split unconditionally for some reason? If so it'll be great to mention that either in the commit message or in comments.
Thanks for calling this out. Could the same be said about the existing code that unconditionally tries to write-protect 2M+ pages? I aimed to keep parity with the write-protection calls (always try to split before write-protecting) but I agree there might be opportunities available to skip altogether.
Quoted 4 lines
By the way, looking at this code again I think I see some potential bugs:
- I don't think I ever freesplit_cachesin the initially-all-set case.
- What happens if splitting fails theCLEAR_LOGbut succeeds theCLEAR_LOG?
Gah, meant to say "first CLEAR_LOG" and "second CLEAR_LOG" here.
Quoted 9 lines
We would end up propagating the write-protection on the 2M page down to the 4K page. This might cause issues if using PML.
Quoted 6 lines
Thanks,
--
Peter Xu
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 32 lines · David Matlack
Quoted 31 lines · David Matlack
Quoted 29 lines · Peter Xu
Quoted 7 lines · David Matlack
arch/x86/kvm/mmu/mmu.c +0
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask);arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1459
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +6
-0+/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K ); +kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */ Is it intended to try split every time even if we could have split it already? As I remember Paolo mentioned that we can skip split if it's not the 1st
CLEAR_LOGon the same range, and IIUC that makes sense.But indeed I don't see a trivial way to know whether this is the first clear of this range. Maybe we can maintain "how many huge pages are there under current
kvm_mmu_pagenode" somehow? Then if root sp has the counter==0, then we can skip it. Just a wild idea..
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Or maybe it's intended to try split unconditionally for some reason? If so it'll be great to mention that either in the commit message or in comments.
Thanks for calling this out. Could the same be said about the existing code that unconditionally tries to write-protect 2M+ pages?
They're different because wr-protect can be restored (to be not-wr-protected) when vcpu threads write to the pages, so they need to be always done.
For huge page split - when it happened during dirty tracking it'll not be recovered anymore, so it's a one-time thing.
Quoted 3 lines
Quoted 3 lines
I aimed to keep parity with the write-protection calls (always try to split before write-protecting) but I agree there might be opportunities available to skip altogether.
So IMHO it's not about parity but it could be about how easy can it be implemented, and whether it'll be worth it to add that complexity.
Besides the above accounting idea per-sp, we can have other ways to do this too, e.g., keeping a bitmap showing which range has been split: that bitmap will be 2M in granule for x86 because that'll be enough. We init-all-ones for the bitmap when start logging for a memslot.
But again maybe it turns out we don't really want that complexity.
IMHO a good start could be the perf numbers (which I asked in the cover letter) comparing the overhead of 2nd+ iterations of CLEAR_LOG with/without eager page split.
Quoted 3 lines
Quoted 3 lines
By the way, looking at this code again I think I see some potential bugs:
- I don't think I ever freesplit_cachesin the initially-all-set case.
I saw that it's freed in kvm_mmu_try_split_large_pages(), no?
Quoted 7 lines
Quoted 2 lines
- What happens if splitting fails the
CLEAR_LOGbut succeeds theCLEAR_LOG?Gah, meant to say "first
CLEAR_LOG" and "secondCLEAR_LOG" here.Quoted 2 lines
We would end up propagating the write-protection on the 2M page down to the 4K page. This might cause issues if using PML.
Hmm looks correct.. I'm wondering what will happen with that.
Firstly this should be rare as the 1st split should in 99% cases succeed.
Then if split failed at the 1st attempt, we wr-protected sptes even during pml during the split. When written, we'll go the fast page fault and record the writes too, I think, as we'll apply dirty bit to the new spte so I think it'll just skip pml. Looks like we'll be using a mixture of pml+wp but all dirty will still be captured as exptected?..
There could be leftover wp when stopping dirty logging, but that seems not directly harmful too. It'll make things a bit messed up, at least.
Signature · 1 line
Peter Xu
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 34 lines · Peter Xu
Quoted 32 lines · David Matlack
Quoted 31 lines · David Matlack
Quoted 29 lines · Peter Xu
Quoted 7 lines · David Matlack
arch/x86/kvm/mmu/mmu.c +0
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask);arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1459
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c +6
-0+/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K ); +kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */ Is it intended to try split every time even if we could have split it already? As I remember Paolo mentioned that we can skip split if it's not the 1st
CLEAR_LOGon the same range, and IIUC that makes sense.But indeed I don't see a trivial way to know whether this is the first clear of this range. Maybe we can maintain "how many huge pages are there under current
kvm_mmu_pagenode" somehow? Then if root sp has the counter==0, then we can skip it. Just a wild idea..
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Or maybe it's intended to try split unconditionally for some reason? If so it'll be great to mention that either in the commit message or in comments.
Thanks for calling this out. Could the same be said about the existing code that unconditionally tries to write-protect 2M+ pages?
They're different because wr-protect can be restored (to be not-wr-protected) when vcpu threads write to the pages, so they need to be always done.
That's true for 4K pages, but not for write-protecting 2M+ pages (which is what we're discussing here). Once KVM write-protects a 2M+ page, it should never need to write-protect it again, but we always try to here. Same goes with splitting.
Quoted 10 lines
For huge page split - when it happened during dirty tracking it'll not be recovered anymore, so it's a one-time thing.
Quoted 3 lines
Quoted 3 lines
I aimed to keep parity with the write-protection calls (always try to split before write-protecting) but I agree there might be opportunities available to skip altogether.
So IMHO it's not about parity but it could be about how easy can it be implemented, and whether it'll be worth it to add that complexity.
Agreed.
Quoted 11 lines
Besides the above accounting idea per-sp, we can have other ways to do this too, e.g., keeping a bitmap showing which range has been split: that bitmap will be 2M in granule for x86 because that'll be enough. We init-all-ones for the bitmap when start logging for a memslot.
But again maybe it turns out we don't really want that complexity.
IMHO a good start could be the perf numbers (which I asked in the cover letter) comparing the overhead of 2nd+ iterations of
CLEAR_LOGwith/without eager page split.
Ack. I'll be sure to include these in v1!
Quoted 6 lines
Quoted 4 lines
Quoted 4 lines
By the way, looking at this code again I think I see some potential bugs:
- I don't think I ever freesplit_cachesin the initially-all-set case.I saw that it's freed in
kvm_mmu_try_split_large_pages(), no?
Ah yes you are right. I misremembered how I implemented it and thought we kept the split_caches around across calls to CLEAR_LOG. (We probably should TBH. The current implementation is quite wasteful.)
Quoted 11 lines
Quoted 8 lines
Quoted 3 lines
- What happens if splitting fails the
CLEAR_LOGbut succeeds theCLEAR_LOG?Gah, meant to say "first
CLEAR_LOG" and "secondCLEAR_LOG" here.Quoted 2 lines
We would end up propagating the write-protection on the 2M page down to the 4K page. This might cause issues if using PML.
Hmm looks correct.. I'm wondering what will happen with that.
Quoted 7 lines
Firstly this should be rare as the 1st split should in 99% cases succeed.
Then if split failed at the 1st attempt, we wr-protected sptes even during pml during the split. When written, we'll go the fast page fault and record the writes too, I think, as we'll apply dirty bit to the new spte so I think it'll just skip pml. Looks like we'll be using a mixture of pml+wp but all dirty will still be captured as exptected?..
That's what I was hoping for. I'll double check for v1.
Quoted 7 lines
There could be leftover wp when stopping dirty logging, but that seems not directly harmful too. It'll make things a bit messed up, at least.
--
Peter Xu
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 10 lines · David Matlack
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
Thanks for calling this out. Could the same be said about the existing code that unconditionally tries to write-protect 2M+ pages?
They're different because wr-protect can be restored (to be not-wr-protected) when vcpu threads write to the pages, so they need to be always done.
That's true for 4K pages, but not for write-protecting 2M+ pages (which is what we're discussing here). Once KVM write-protects a 2M+ page, it should never need to write-protect it again, but we always try to here. Same goes with splitting.
Ah I see, that's fair point. :)
Yeah let's see how it goes with the numbers, I'd hope it's trivial to do both wr-protect 2m and the split unconditionally, because for CLEAR_LOG the major overhead should be walking the small pages instead, afaiu.
Signature · 1 line
Peter Xu
Sean Christopherson
maintainerRe: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
In reply to David MatlackQuoted 23 lines · David Matlack
When using initially-all-set, large pages are not write-protected when dirty logging is enabled on the memslot. Instead they are write-protected once userspace invoked
CLEAR_DIRTY_LOGfor the first time, and only for the specific sub-region of the memslot that userspace whishes to clear.Enhance
CLEAR_DIRTY_LOGto also try to split large pages prior to write-protecting to avoid causing write-protection faults on vCPU threads. This also allows userspace to smear the cost of large page splitting across multiple ioctls rather than splitting the entire memslot when not using initially-all-set.Signed-off-by David Matlack <[email protected]>--- arch/x86/include/asm/kvm_host.h | 4 ++++ arch/x86/kvm/mmu/mmu.c | 30 ++++++++++++++++++++++-------- 2 files changed, 26 insertions(+), 8 deletions(-)arch/x86/include/asm/kvm_host.h +0
-0
arch/x86/include/asm/kvm_host.h void kvm_mmu_reset_context(struct kvm_vcpu *vcpu); · line 1594
Quoted 4 lines
arch/x86/include/asm/kvm_host.h +1
-0@@ -1591,6 +1591,10 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu);void kvm_mmu_slot_remove_write_access (struct kvm *kvm,const struct kvm_memory_slot *memslot,int start_level); +void kvm_mmu_try_split_large_pages(struct kvm *kvm,
I would prefer we use hugepage when possible, mostly because that's the terminology used by the kernel. KVM is comically inconsistent, but if we make an effort to use hugepage when adding new code, hopefully someday we'll have enough inertia to commit fully to hugepage.
Quoted 11 lines
arch/x86/include/asm/kvm_host.h +3
-0+const struct kvm_memory_slot *memslot, + u64 start, u64 end, + int target_level);void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm,const struct kvm_memory_slot *memslot,int target_level);arch/x86/kvm/mmu/mmu.c +0
-0
arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1455
Quoted 8 lines
arch/x86/kvm/mmu/mmu.c +5
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask); +/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K );
This should return a value. If splitting succeeds, there should be no hugepages and so walking the page tables to write-protect 2M is unnecessary. Same for the previous patch, although skipping the write-protect path is a little less straightforward in that case.
Quoted 4 lines
arch/x86/kvm/mmu/mmu.c +1
-0+kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 20 lines · Sean Christopherson
Quoted 18 lines · David Matlack
When using initially-all-set, large pages are not write-protected when dirty logging is enabled on the memslot. Instead they are write-protected once userspace invoked
CLEAR_DIRTY_LOGfor the first time, and only for the specific sub-region of the memslot that userspace whishes to clear.Enhance
CLEAR_DIRTY_LOGto also try to split large pages prior to write-protecting to avoid causing write-protection faults on vCPU threads. This also allows userspace to smear the cost of large page splitting across multiple ioctls rather than splitting the entire memslot when not using initially-all-set.Signed-off-by David Matlack <[email protected]>--- arch/x86/include/asm/kvm_host.h | 4 ++++ arch/x86/kvm/mmu/mmu.c | 30 ++++++++++++++++++++++-------- 2 files changed, 26 insertions(+), 8 deletions(-)
Quoted 14 lines
arch/x86/include/asm/kvm_host.h void kvm_mmu_reset_context(struct kvm_vcpu *vcpu); · line 1594
Quoted 9 lines
arch/x86/include/asm/kvm_host.h +1
-0@@ -1591,6 +1591,10 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu);void kvm_mmu_slot_remove_write_access (struct kvm *kvm,const struct kvm_memory_slot *memslot,int start_level); +void kvm_mmu_try_split_large_pages(struct kvm *kvm,I would prefer we use hugepage when possible, mostly because that's the terminology used by the kernel. KVM is comically inconsistent, but if we make an effort to use hugepage when adding new code, hopefully someday we'll have enough inertia to commit fully to hugepage.
In my mind "huge page" implies 2M and "large page" is generic to 2m and 1g. (IDK if we settled on a name for 1G pages)
I've definitely been guilty of reinforcing this inconsistent terminology. (Though it was consistent in my head, of course.) If we want to pick one and use it everywhere, I'm happy to get onboard with a standard terminology.
Quoted 30 lines
Quoted 12 lines
arch/x86/include/asm/kvm_host.h +3
-0+const struct kvm_memory_slot *memslot, + u64 start, u64 end, + int target_level);void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm,const struct kvm_memory_slot *memslot,int target_level);arch/x86/kvm/mmu/mmu.c +0
-0arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1455
Quoted 8 lines
arch/x86/kvm/mmu/mmu.c +5
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask); +/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K );This should return a value. If splitting succeeds, there should be no hugepages and so walking the page tables to write-protect 2M is unnecessary. Same for the previous patch, although skipping the write-protect path is a little less straightforward in that case.
Quoted 4 lines
arch/x86/kvm/mmu/mmu.c +1
-0+kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */
Sean Christopherson
maintainerRe: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 8 lines · Ben Gardon
Quoted 4 lines · Sean Christopherson
I would prefer we use hugepage when possible, mostly because that's the terminology used by the kernel. KVM is comically inconsistent, but if we make an effort to use hugepage when adding new code, hopefully someday we'll have enough inertia to commit fully to hugepage.
In my mind "huge page" implies 2M and "large page" is generic to 2m and 1g. (IDK if we settled on a name for 1G pages)
What about 4m PSE pages? :-)
I'm mostly joking, but it does raise the point that trying to provide unique names for each size is a bit of a fools errand, especially on non-x86 architectures that support a broader variety of hugepage sizes. IMO, the least ambiguous way to refer to hugepages is to say that everything that isn't a 4k page (or whatever PAGE_SIZE is on the architecture) is a hugepage, and then explicitly state the size of the page if it matters.
Quoted 4 lines
I've definitely been guilty of reinforcing this inconsistent terminology. (Though it was consistent in my head, of course.) If we want to pick one and use it everywhere, I'm happy to get onboard with a standard terminology.
I hear you on using "large page", I've had to undo a solid decade of "large page" terminology from my pre-Linux days. But for better or worse, the kernel uses hugepage, e.g. hugetlbfs supports 1gb and 2mb pages. I think we should follow the kernel, especially since we have aspirations of unifying more of KVM's MMU across multiple architectures.
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
Quoted 25 lines · Sean Christopherson
Quoted 8 lines · Ben Gardon
Quoted 4 lines · Sean Christopherson
I would prefer we use hugepage when possible, mostly because that's the terminology used by the kernel. KVM is comically inconsistent, but if we make an effort to use hugepage when adding new code, hopefully someday we'll have enough inertia to commit fully to hugepage.
In my mind "huge page" implies 2M and "large page" is generic to 2m and 1g. (IDK if we settled on a name for 1G pages)
What about 4m PSE pages? :-)
I'm mostly joking, but it does raise the point that trying to provide unique names for each size is a bit of a fools errand, especially on non-x86 architectures that support a broader variety of hugepage sizes. IMO, the least ambiguous way to refer to hugepages is to say that everything that isn't a 4k page (or whatever
PAGE_SIZEis on the architecture) is a hugepage, and then explicitly state the size of the page if it matters.Quoted 4 lines
I've definitely been guilty of reinforcing this inconsistent terminology. (Though it was consistent in my head, of course.) If we want to pick one and use it everywhere, I'm happy to get onboard with a standard terminology.
Quoted 5 lines
I hear you on using "large page", I've had to undo a solid decade of "large page" terminology from my pre-Linux days. But for better or worse, the kernel uses hugepage, e.g. hugetlbfs supports 1gb and 2mb pages. I think we should follow the kernel, especially since we have aspirations of unifying more of KVM's MMU across multiple architectures.
Sounds good to me. I'll keep that in mind in future patches. I'm happy to call them anything as long as we all use the same terms.
Re: [RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG
In reply to Sean ChristophersonQuoted 20 lines · Sean Christopherson
Quoted 18 lines · David Matlack
When using initially-all-set, large pages are not write-protected when dirty logging is enabled on the memslot. Instead they are write-protected once userspace invoked
CLEAR_DIRTY_LOGfor the first time, and only for the specific sub-region of the memslot that userspace whishes to clear.Enhance
CLEAR_DIRTY_LOGto also try to split large pages prior to write-protecting to avoid causing write-protection faults on vCPU threads. This also allows userspace to smear the cost of large page splitting across multiple ioctls rather than splitting the entire memslot when not using initially-all-set.Signed-off-by David Matlack <[email protected]>--- arch/x86/include/asm/kvm_host.h | 4 ++++ arch/x86/kvm/mmu/mmu.c | 30 ++++++++++++++++++++++-------- 2 files changed, 26 insertions(+), 8 deletions(-)
Quoted 14 lines
arch/x86/include/asm/kvm_host.h void kvm_mmu_reset_context(struct kvm_vcpu *vcpu); · line 1594
Quoted 9 lines
arch/x86/include/asm/kvm_host.h +1
-0@@ -1591,6 +1591,10 @@ void kvm_mmu_reset_context(struct kvm_vcpu *vcpu);void kvm_mmu_slot_remove_write_access (struct kvm *kvm,const struct kvm_memory_slot *memslot,int start_level); +void kvm_mmu_try_split_large_pages(struct kvm *kvm,I would prefer we use hugepage when possible, mostly because that's the terminology used by the kernel. KVM is comically inconsistent, but if we make an effort to use hugepage when adding new code, hopefully someday we'll have enough inertia to commit fully to hugepage.
Will do.
Quoted 15 lines
Quoted 15 lines
arch/x86/include/asm/kvm_host.h +3
-0+const struct kvm_memory_slot *memslot, + u64 start, u64 end, + int target_level);void kvm_mmu_slot_try_split_large_pages (struct kvm *kvm,const struct kvm_memory_slot *memslot,int target_level);arch/x86/kvm/mmu/mmu.c +0
-0@@ -1448,6 +1448,12 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,gfn_t start = slot->base_gfn + gfn_offset +__ffs (mask);gfn_t end = slot->base_gfn + gfn_offset +__fls (mask);
Quoted 10 lines
arch/x86/kvm/mmu/mmu.c void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, · line 1455
Quoted 5 lines
arch/x86/kvm/mmu/mmu.c +5
-0+/* +* Try to proactively split any large pages down to 4KB so that +* vCPUs don't have to take write-protection faults. +*/ +kvm_mmu_try_split_large_pages (kvm, slot, start, end,PG_LEVEL_4K );This should return a value. If splitting succeeds, there should be no hugepages and so walking the page tables to write-protect 2M is unnecessary. Same for the previous patch, although skipping the write-protect path is a little less straightforward in that case.
Great idea! Will do.
Quoted 5 lines
Quoted 5 lines
arch/x86/kvm/mmu/mmu.c +1
-0+kvm_mmu_slot_gfn_write_protect (kvm, slot, start,PG_LEVEL_2M );/* Cross two large pages? */
kernel test robot
build bot[KVM] d3750a0923: WARNING:possible_circular_locking_dependency_detected
In reply to David MatlackFYI, we noticed the following commit (built with gcc-9):
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: d3750a09232a9af1e8c6bb3b06a6609d921eb506 ("[RFC PATCH 13/15] KVM: x86/mmu: Split large pages during CLEAR_DIRTY_LOG")
url: https://github.com/0day-ci/linux/commits/David-Matlack/KVM-x86-mmu-Eager-Page-Splitting-for-the-TDP-MMU/20211120-080051
base: https://git.kernel.org/cgit/virt/kvm/kvm.git queue
patch link: https://lore.kernel.org/kvm/20211119235759.1304274-14-dmatlack(a)google.com
in testcase: kernel-selftests
version: kernel-selftests-x86_64-a21458fc-1_20211128 with following parameters:
group: kvm ucode: 0xe2
test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
on test machine: 8 threads Intel(R) Core(TM) i7-6770HQ CPU @ 2.60GHz with 32G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
[ 280.691224][T10825] WARNING: possible circular locking dependency detected
[ 280.698458][T10825] 5.15.0-12443-gd3750a09232a #1 Tainted: G I
[ 280.705780][T10825] ------------------------------------------------------
[ 280.712843][T10825] dirty_log_test/10825 is trying to acquire lock:
[280.719317][T10825] ffffffff859d97c0 (fs_reclaim){+.+.}-{0:0}, at: kmem_cache_alloc (include/linux/sched/mm.h:228 mm/slab.h:492 mm/slub.c:3148 mm/slub.c:3242 mm/slub.c:3247)
[ 280.728159][T10825]
[ 280.728159][T10825] but task is already holding lock:
[280.735565][T10825] ffffc90009b61018 (&(kvm)->mmu_lock){++++}-{2:2}, at: kvm_clear_dirty_log_protect (arch/x86/kvm/../../../virt/kvm/kvm_main.c:2176)
[ 280.745919][T10825]
[ 280.745919][T10825] which lock already depends on the new lock.
[ 280.745919][T10825]
[ 280.756398][T10825]
[ 280.756398][T10825] the existing dependency chain (in reverse order) is:
[ 280.765486][T10825]
[ 280.765486][T10825] -> #2 (&(kvm)->mmu_lock){++++}-{2:2}:
[280.773296][T10825] lock_acquire (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5639 kernel/locking/lockdep.c:5602)
[280.778318][T10825] _raw_write_lock (include/linux/rwlock_api_smp.h:209 kernel/locking/spinlock.c:300)
[280.783422][T10825] kvm_mmu_notifier_invalidate_range_start (arch/x86/kvm/../../../virt/kvm/kvm_main.c:576 arch/x86/kvm/../../../virt/kvm/kvm_main.c:714)
[280.790879][T10825] __mmu_notifier_invalidate_range_start (mm/mmu_notifier.c:494 mm/mmu_notifier.c:548)
[280.798089][T10825] wp_page_copy (include/linux/mmu_notifier.h:459 mm/memory.c:3017)
[280.803304][T10825] __handle_mm_fault (mm/memory.c:4569 mm/memory.c:4686)
[280.808964][T10825] handle_mm_fault (mm/memory.c:4784)
[280.814276][T10825] do_user_addr_fault (arch/x86/mm/fault.c:1397)
[280.819805][T10825] exc_page_fault (arch/x86/include/asm/irqflags.h:29 arch/x86/include/asm/irqflags.h:70 arch/x86/include/asm/irqflags.h:132 arch/x86/mm/fault.c:1493 arch/x86/mm/fault.c:1541)
[280.824952][T10825] asm_exc_page_fault (arch/x86/include/asm/idtentry.h:568)
[ 280.830336][T10825]
[ 280.830336][T10825] -> #1 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:
[280.839807][T10825] lock_acquire (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5639 kernel/locking/lockdep.c:5602)
[280.844868][T10825] fs_reclaim_acquire (mm/page_alloc.c:4552)
[280.850354][T10825] __kmalloc_node (include/linux/sched/mm.h:228 mm/slab.h:492 mm/slub.c:3148 mm/slub.c:4467)
[280.855538][T10825] alloc_cpumask_var_node (lib/cpumask.c:115)
[280.861284][T10825] native_smp_prepare_cpus (arch/x86/kernel/smpboot.c:1373)
[280.867316][T10825] kernel_init_freeable (include/linux/compiler.h:252 include/linux/init.h:124 init/main.c:1414 init/main.c:1599)
[280.873070][T10825] kernel_init (init/main.c:1501)
[280.877992][T10825] ret_from_fork (arch/x86/entry/entry_64.S:301)
[ 280.882914][T10825]
[ 280.882914][T10825] -> #0 (fs_reclaim){+.+.}-{0:0}:
[280.890200][T10825] check_prev_add (kernel/locking/lockdep.c:3064)
[280.895486][T10825] __lock_acquire (kernel/locking/lockdep.c:3187 kernel/locking/lockdep.c:3801 kernel/locking/lockdep.c:5027)
[280.900838][T10825] lock_acquire (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5639 kernel/locking/lockdep.c:5602)
[280.905873][T10825] fs_reclaim_acquire (mm/page_alloc.c:4536 mm/page_alloc.c:4549)
[280.911412][T10825] kmem_cache_alloc (include/linux/sched/mm.h:228 mm/slab.h:492 mm/slub.c:3148 mm/slub.c:3242 mm/slub.c:3247)
[280.916733][T10825] kvm_mmu_topup_memory_cache (arch/x86/kvm/../../../virt/kvm/kvm_main.c:383)
[280.922982][T10825] mmu_topup_split_caches (arch/x86/kvm/mmu/mmu.c:765)
[280.928842][T10825] kvm_mmu_try_split_large_pages (arch/x86/kvm/mmu/mmu.c:5897)
[280.935333][T10825] kvm_arch_mmu_enable_log_dirty_pt_masked (arch/x86/kvm/mmu/mmu.c:1457)
[280.942762][T10825] kvm_clear_dirty_log_protect (arch/x86/kvm/../../../virt/kvm/kvm_main.c:2193)
[280.949182][T10825] kvm_vm_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:2215 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4511)
[280.954337][T10825] __x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:874 fs/ioctl.c:860 fs/ioctl.c:860)
[280.959633][T10825] do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80)
[280.964580][T10825] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:113)
[ 280.971044][T10825]
[ 280.971044][T10825] other info that might help us debug this:
[ 280.971044][T10825]
[ 280.981447][T10825] Chain exists of:
[ 280.981447][T10825] fs_reclaim --> mmu_notifier_invalidate_range_start --> &(kvm)->mmu_lock
[ 280.981447][T10825]
[ 280.996135][T10825] Possible unsafe locking scenario:
[ 280.996135][T10825]
[ 281.003699][T10825] CPU0 CPU1
[ 281.009067][T10825] ---- ----
[ 281.014443][T10825] lock(&(kvm)->mmu_lock);
[ 281.018989][T10825] lock(mmu_notifier_invalidate_range_start);
[ 281.027803][T10825] lock(&(kvm)->mmu_lock);
[ 281.034897][T10825] lock(fs_reclaim);
[ 281.038853][T10825]
[ 281.038853][T10825] *** DEADLOCK ***
[ 281.038853][T10825]
[ 281.047128][T10825] 2 locks held by dirty_log_test/10825:
[281.052687][T10825] #0: ffffc90009b610a8 (&kvm->slots_lock){+.+.}-{3:3}, at: kvm_vm_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:2213 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4511)
[281.062371][T10825] #1: ffffc90009b61018 (&(kvm)->mmu_lock){++++}-{2:2}, at: kvm_clear_dirty_log_protect (arch/x86/kvm/../../../virt/kvm/kvm_main.c:2176)
[ 281.073672][T10825]
[ 281.073672][T10825] stack backtrace:
[ 281.079747][T10825] CPU: 5 PID: 10825 Comm: dirty_log_test Tainted: G I 5.15.0-12443-gd3750a09232a #1
[ 281.090909][T10825] Hardware name: /NUC6i7KYB, BIOS KYSKLi70.86A.0041.2016.0817.1130 08/17/2016
[ 281.099876][T10825] Call Trace:
[ 281.103142][T10825] <TASK>
[281.106036][T10825] dump_stack_lvl (lib/dump_stack.c:107)
[281.110529][T10825] check_noncircular (kernel/locking/lockdep.c:2143)
[281.115472][T10825] ? print_circular_bug+0x480/0x480
[281.121341][T10825] ? mark_lock_irq (kernel/locking/lockdep.c:4564)
[281.126269][T10825] ? is_bpf_text_address (kernel/bpf/core.c:713)
[281.131478][T10825] ? mark_lock+0xca/0x1400
[281.136540][T10825] ? mark_lock+0xca/0x1400
[281.141578][T10825] check_prev_add (kernel/locking/lockdep.c:3064)
[281.146353][T10825] __lock_acquire (kernel/locking/lockdep.c:3187 kernel/locking/lockdep.c:3801 kernel/locking/lockdep.c:5027)
[281.151214][T10825] ? lock_is_held_type (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5681)
[281.156272][T10825] ? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4885)
[281.162278][T10825] ? lock_is_held_type (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5681)
[281.167324][T10825] ? rcu_read_lock_sched_held (include/linux/lockdep.h:283 kernel/rcu/update.c:125)
[281.173091][T10825] lock_acquire (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5639 kernel/locking/lockdep.c:5602)
[281.177732][T10825] ? kmem_cache_alloc (include/linux/sched/mm.h:228 mm/slab.h:492 mm/slub.c:3148 mm/slub.c:3242 mm/slub.c:3247)
[281.182856][T10825] ? rcu_read_unlock (include/linux/rcupdate.h:717 (discriminator 5))
[281.187846][T10825] ? lock_is_held_type (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5681)
[281.193099][T10825] ? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4885)
[281.199356][T10825] ? lock_is_held_type (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5681)
[281.204642][T10825] fs_reclaim_acquire (mm/page_alloc.c:4536 mm/page_alloc.c:4549)
[281.209675][T10825] ? kmem_cache_alloc (include/linux/sched/mm.h:228 mm/slab.h:492 mm/slub.c:3148 mm/slub.c:3242 mm/slub.c:3247)
[281.214625][T10825] ? kvm_mmu_topup_memory_cache (arch/x86/kvm/../../../virt/kvm/kvm_main.c:383)
[281.220440][T10825] kmem_cache_alloc (include/linux/sched/mm.h:228 mm/slab.h:492 mm/slub.c:3148 mm/slub.c:3242 mm/slub.c:3247)
[281.225225][T10825] ? lock_acquire (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5639 kernel/locking/lockdep.c:5602)
[281.230012][T10825] kvm_mmu_topup_memory_cache (arch/x86/kvm/../../../virt/kvm/kvm_main.c:383)
[281.235876][T10825] ? lock_is_held_type (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5681)
[281.241148][T10825] mmu_topup_split_caches (arch/x86/kvm/mmu/mmu.c:765)
[281.246492][T10825] kvm_mmu_try_split_large_pages (arch/x86/kvm/mmu/mmu.c:5897)
[281.252407][T10825] kvm_arch_mmu_enable_log_dirty_pt_masked (arch/x86/kvm/mmu/mmu.c:1457)
[281.259324][T10825] kvm_clear_dirty_log_protect (arch/x86/kvm/../../../virt/kvm/kvm_main.c:2193)
[281.265165][T10825] kvm_vm_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:2215 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4511)
[281.269769][T10825] ? __lock_acquire (arch/x86/include/asm/bitops.h:214 (discriminator 9) include/asm-generic/bitops/instrumented-non-atomic.h:135 (discriminator 9) kernel/locking/lockdep.c:199 (discriminator 9) kernel/locking/lockdep.c:5024 (discriminator 9))
[281.274716][T10825] ? kvm_unregister_device_ops (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4464)
[281.280453][T10825] ? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4885)
[281.286752][T10825] ? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:4885)
[281.292869][T10825] ? lock_is_held_type (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5681)
[281.297878][T10825] ? fiemap_prep (fs/ioctl.c:778)
[281.302467][T10825] ? rcu_read_lock_sched_held (include/linux/lockdep.h:283 kernel/rcu/update.c:125)
[281.308131][T10825] ? rcu_read_lock_bh_held (kernel/rcu/update.c:120)
[281.313458][T10825] ? lock_acquire (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5639 kernel/locking/lockdep.c:5602)
[281.318131][T10825] ? find_held_lock (kernel/locking/lockdep.c:5130)
[281.322907][T10825] ? lock_release (kernel/locking/lockdep.c:438 kernel/locking/lockdep.c:5659)
[281.327606][T10825] ? lock_downgrade (kernel/locking/lockdep.c:5645)
[281.332467][T10825] ? rcu_read_lock_sched_held (kernel/rcu/update.c:306)
[281.338192][T10825] ? __fget_files (fs/file.c:865)
[281.342877][T10825] __x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:874 fs/ioctl.c:860 fs/ioctl.c:860)
[281.347634][T10825] do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80)
[281.352016][T10825] ? irqentry_exit_to_user_mode (kernel/entry/common.c:127 kernel/entry/common.c:315)
[281.357667][T10825] ? asm_exc_page_fault (arch/x86/include/asm/idtentry.h:568)
[281.362599][T10825] ? rcu_read_lock_sched_held (include/linux/lockdep.h:283 kernel/rcu/update.c:125)
[281.368259][T10825] ? rcu_read_lock_bh_held (kernel/rcu/update.c:120)
[281.373557][T10825] ? asm_exc_page_fault (arch/x86/include/asm/idtentry.h:568)
[281.378614][T10825] ? asm_exc_page_fault (arch/x86/include/asm/idtentry.h:568)
[281.383562][T10825] ? lockdep_hardirqs_on (kernel/locking/lockdep.c:4356)
[281.388772][T10825] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:113)
[ 281.394893][T10825] RIP: 0033:0x7f9d40646427
[ 281.399484][T10825] Code: 00 00 90 48 8b 05 69 aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 39 aa 0c 00 f7 d8 64 89 01 48All code
========
0: 00 00 add %al,(%rax)
2: 90 nop
3: 48 8b 05 69 aa 0c 00 mov 0xcaa69(%rip),%rax # 0xcaa73 a: 64 c7 00 26 00 00 00 movl $0x26,%fs:(%rax) 11: 48 c7 c0 ff ff ff ff mov $0xffffffffffffffff,%rax
18: c3 retq
19: 66 2e 0f 1f 84 00 00 nopw %cs:0x0(%rax,%rax,1)
20: 00 00 00
23: b8 10 00 00 00 mov $0x10,%eax
28: 0f 05 syscall
2a:* 48 3d 01 f0 ff ff cmp $0xfffffffffffff001,%rax <-- trapping instruction
30: 73 01 jae 0x33
32: c3 retq
33: 48 8b 0d 39 aa 0c 00 mov 0xcaa39(%rip),%rcx # 0xcaa73
3a: f7 d8 neg %eax
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
sudo bin/lkp install job.yaml # job file is attached in this email
bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run sudo bin/lkp run generated-yaml-file
# if come across any failure that blocks the test, # please remove ~/.lkp and /lkp dir to run from a clean state.
---
0DAY/LKP+ Test Infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/[email protected] Intel Corporation
Thanks,
Oliver Sang
#
# Automatically generated file; DO NOT EDIT. # Linux/x86_64 5.15.0 Kernel Configuration
#CONFIG_CC_VERSION_TEXT="gcc-9 (Debian 9.3.0-22) 9.3.0" CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=90300 CONFIG_CLANG_VERSION=0CONFIG_AS_IS_GNU=yCONFIG_AS_VERSION=23502CONFIG_LD_IS_BFD=yCONFIG_LD_VERSION=23502CONFIG_LLD_VERSION=0CONFIG_CC_CAN_LINK=y CONFIG_CC_CAN_LINK_STATIC=y CONFIG_CC_HAS_ASM_GOTO=y CONFIG_CC_HAS_ASM_INLINE=y CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y CONFIG_CONSTRUCTORS=yCONFIG_IRQ_WORK=y CONFIG_BUILDTIME_TABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
# CONFIG_WERROR is not setCONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_BUILD_SALT=""CONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_XZ=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_HAVE_KERNEL_LZ4=yCONFIG_HAVE_KERNEL_ZSTD=yCONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
# CONFIG_KERNEL_ZSTD is not setCONFIG_DEFAULT_INIT=""CONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=y
# CONFIG_WATCH_QUEUE is not setCONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_USELIB is not setCONFIG_AUDIT=yCONFIG_HAVE_ARCH_AUDITSYSCALL=yCONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=yCONFIG_GENERIC_PENDING_IRQ=yCONFIG_GENERIC_IRQ_MIGRATION=yCONFIG_GENERIC_IRQ_INJECTION=yCONFIG_HARDIRQS_SW_RESEND=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_SIM=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_IRQ_MSI_IOMMU=yCONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=yCONFIG_GENERIC_IRQ_RESERVATION_MODE=yCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem
CONFIG_CLOCKSOURCE_WATCHDOG=yCONFIG_ARCH_CLOCKSOURCE_INIT=yCONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=yCONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=yCONFIG_GENERIC_CMOS_UPDATE=yCONFIG_HAVE_POSIX_CPU_TIMERS_TASK_WORK=yCONFIG_POSIX_CPU_TIMERS_TASK_WORK=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
# CONFIG_NO_HZ_IDLE is not setCONFIG_NO_HZ_FULL=yCONFIG_CONTEXT_TRACKING=y
# CONFIG_CONTEXT_TRACKING_FORCE is not setCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
CONFIG_BPF=yCONFIG_HAVE_EBPF_JIT=yCONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y
#
# BPF subsystem
#CONFIG_BPF_SYSCALL=yCONFIG_BPF_JIT=yCONFIG_BPF_JIT_ALWAYS_ON=yCONFIG_BPF_JIT_DEFAULT_ON=yCONFIG_BPF_UNPRIV_DEFAULT_OFF=y
# CONFIG_BPF_PRELOAD is not set
# CONFIG_BPF_LSM is not set
# end of BPF subsystem
CONFIG_PREEMPT_NONE_BEHAVIOUR=y
# CONFIG_PREEMPT_VOLUNTARY_BEHAVIOUR is not set
# CONFIG_PREEMPT_BEHAVIOUR is not setCONFIG_PREEMPT=yCONFIG_PREEMPT_COUNT=yCONFIG_PREEMPTION=yCONFIG_PREEMPT_DYNAMIC=y
# CONFIG_SCHED_CORE is not set
#
# CPU/Task time and stats accounting
#CONFIG_VIRT_CPU_ACCOUNTING=yCONFIG_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_SCHED_AVG_IRQ=yCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#CONFIG_TREE_RCU=yCONFIG_PREEMPT_RCU=y
# CONFIG_RCU_EXPERT is not setCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU_GENERIC=yCONFIG_TASKS_RCU=yCONFIG_TASKS_RUDE_RCU=yCONFIG_TASKS_TRACE_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_NOCB_CPU=y
# end of RCU Subsystem
CONFIG_BUILD_BIN2C=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS is not setCONFIG_LOG_BUF_SHIFT=20CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
# CONFIG_PRINTK_INDEX is not setCONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=yCONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=yCONFIG_CC_HAS_INT128=yCONFIG_ARCH_SUPPORTS_INT128=yCONFIG_NUMA_BALANCING=yCONFIG_NUMA_BALANCING_DEFAULT_ENABLED=yCONFIG_CGROUPS=yCONFIG_PAGE_COUNTER=yCONFIG_MEMCG=yCONFIG_MEMCG_SWAP=yCONFIG_MEMCG_KMEM=yCONFIG_BLK_CGROUP=yCONFIG_CGROUP_WRITEBACK=yCONFIG_CGROUP_SCHED=yCONFIG_FAIR_GROUP_SCHED=yCONFIG_CFS_BANDWIDTH=yCONFIG_RT_GROUP_SCHED=yCONFIG_CGROUP_PIDS=yCONFIG_CGROUP_RDMA=yCONFIG_CGROUP_FREEZER=yCONFIG_CGROUP_HUGETLB=yCONFIG_CPUSETS=yCONFIG_PROC_PID_CPUSET=yCONFIG_CGROUP_DEVICE=yCONFIG_CGROUP_CPUACCT=yCONFIG_CGROUP_PERF=yCONFIG_CGROUP_BPF=y
# CONFIG_CGROUP_MISC is not set
# CONFIG_CGROUP_DEBUG is not setCONFIG_SOCK_CGROUP_DATA=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_TIME_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=yCONFIG_CHECKPOINT_RESTORE=yCONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not setCONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_XZ=yCONFIG_RD_LZO=yCONFIG_RD_LZ4=yCONFIG_RD_ZSTD=y
# CONFIG_BOOT_CONFIG is not setCONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_LD_ORPHAN_WARN=yCONFIG_SYSCTL=yCONFIG_HAVE_UID16=yCONFIG_SYSCTL_EXCEPTION_TRACE=yCONFIG_HAVE_PCSPKR_PLATFORM=yCONFIG_EXPERT=yCONFIG_UID16=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=yCONFIG_SYSFS_SYSCALL=yCONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_FUTEX_PI=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_IO_URING=yCONFIG_ADVISE_SYSCALLS=yCONFIG_HAVE_ARCH_USERFAULTFD_WP=yCONFIG_HAVE_ARCH_USERFAULTFD_MINOR=yCONFIG_MEMBARRIER=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=yCONFIG_KALLSYMS_ABSOLUTE_PERCPU=yCONFIG_KALLSYMS_BASE_RELATIVE=yCONFIG_USERFAULTFD=yCONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=yCONFIG_KCMP=yCONFIG_RSEQ=y
# CONFIG_DEBUG_RSEQ is not setCONFIG_EMBEDDED=yCONFIG_HAVE_PERF_EVENTS=y
# CONFIG_PC104 is not set
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters
CONFIG_VM_EVENT_COUNTERS=yCONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_SLAB_MERGE_DEFAULT=yCONFIG_SLAB_FREELIST_RANDOM=yCONFIG_SLAB_FREELIST_HARDENED=yCONFIG_SHUFFLE_PAGE_ALLOCATOR=yCONFIG_SLUB_CPU_PARTIAL=yCONFIG_SYSTEM_DATA_VERIFICATION=yCONFIG_PROFILING=yCONFIG_TRACEPOINTS=y
# end of General setup
CONFIG_64BIT=yCONFIG_X86_64=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=yCONFIG_OUTPUT_FORMAT="elf64-x86-64"CONFIG_LOCKDEP_SUPPORT=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_MMU=yCONFIG_ARCH_MMAP_RND_BITS_MIN=28CONFIG_ARCH_MMAP_RND_BITS_MAX=32CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16CONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_BUG=yCONFIG_GENERIC_BUG_RELATIVE_POINTERS=yCONFIG_ARCH_MAY_HAVE_PC_FDC=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_ARCH_HAS_CPU_RELAX=yCONFIG_ARCH_HAS_FILTER_PGPROT=yCONFIG_HAVE_SETUP_PER_CPU_AREA=yCONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=yCONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=yCONFIG_ARCH_HIBERNATION_POSSIBLE=yCONFIG_ARCH_NR_GPIO=1024CONFIG_ARCH_SUSPEND_POSSIBLE=yCONFIG_ARCH_WANT_GENERAL_HUGETLB=yCONFIG_AUDIT_ARCH=yCONFIG_KASAN_SHADOW_OFFSET=0xdffffc0000000000CONFIG_HAVE_INTEL_TXT=yCONFIG_X86_64_SMP=yCONFIG_ARCH_SUPPORTS_UPROBES=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_PGTABLE_LEVELS=5CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
#
# Processor type and features
#CONFIG_SMP=yCONFIG_X86_FEATURE_NAMES=yCONFIG_X86_X2APIC=yCONFIG_X86_MPPARSE=y
# CONFIG_GOLDFISH is not setCONFIG_RETPOLINE=yCONFIG_X86_CPU_RESCTRL=yCONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_NUMACHIP is not set
# CONFIG_X86_VSMP is not setCONFIG_X86_UV=y
# CONFIG_X86_GOLDFISH is not set
# CONFIG_X86_INTEL_MID is not setCONFIG_X86_INTEL_LPSS=y
# CONFIG_X86_AMD_PLATFORM_DEVICE is not setCONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not setCONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not setCONFIG_HYPERVISOR_GUEST=yCONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_DEBUG is not setCONFIG_PARAVIRT_SPINLOCKS=yCONFIG_X86_HV_CALLBACK_VECTOR=y
# CONFIG_XEN is not setCONFIG_KVM_GUEST=yCONFIG_ARCH_CPUIDLE_HALTPOLL=y
# CONFIG_PVH is not setCONFIG_PARAVIRT_TIME_ACCOUNTING=yCONFIG_PARAVIRT_CLOCK=y
# CONFIG_JAILHOUSE_GUEST is not set
# CONFIG_ACRN_GUEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not setCONFIG_GENERIC_CPU=yCONFIG_X86_INTERNODE_CACHE_SHIFT=6CONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_TSC=yCONFIG_X86_CMPXCHG64=yCONFIG_X86_CMOV=yCONFIG_X86_MINIMUM_CPU_FAMILY=64CONFIG_X86_DEBUGCTLMSR=yCONFIG_IA32_FEAT_CTL=yCONFIG_X86_VMX_FEATURE_NAMES=y
# CONFIG_PROCESSOR_SELECT is not setCONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_AMD=yCONFIG_CPU_SUP_HYGON=yCONFIG_CPU_SUP_CENTAUR=yCONFIG_CPU_SUP_ZHAOXIN=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=y
# CONFIG_GART_IOMMU is not setCONFIG_MAXSMP=yCONFIG_NR_CPUS_RANGE_BEGIN=8192CONFIG_NR_CPUS_RANGE_END=8192CONFIG_NR_CPUS_DEFAULT=8192CONFIG_NR_CPUS=8192CONFIG_SCHED_CLUSTER=yCONFIG_SCHED_SMT=yCONFIG_SCHED_MC=yCONFIG_SCHED_MC_PRIO=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=yCONFIG_X86_MCE=yCONFIG_X86_MCELOG_LEGACY=yCONFIG_X86_MCE_INTEL=yCONFIG_X86_MCE_AMD=yCONFIG_X86_MCE_THRESHOLD=yCONFIG_X86_MCE_INJECT=m
#
# Performance monitoring
#CONFIG_PERF_EVENTS_INTEL_UNCORE=mCONFIG_PERF_EVENTS_INTEL_RAPL=mCONFIG_PERF_EVENTS_INTEL_CSTATE=m
# CONFIG_PERF_EVENTS_AMD_POWER is not setCONFIG_PERF_EVENTS_AMD_UNCORE=y
# end of Performance monitoring
CONFIG_X86_16BIT=yCONFIG_X86_ESPFIX64=y CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_X86_IOPL_IOPERM=yCONFIG_I8K=mCONFIG_MICROCODE=yCONFIG_MICROCODE_INTEL=yCONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=yCONFIG_X86_CPUID=yCONFIG_X86_5LEVEL=yCONFIG_X86_DIRECT_GBPAGES=y
# CONFIG_X86_CPA_STATISTICS is not set
# CONFIG_AMD_MEM_ENCRYPT is not set CONFIG_NUMA=y
# CONFIG_AMD_NUMA is not set CONFIG_X86_64_ACPI_NUMA=yCONFIG_NUMA_EMU=yCONFIG_NODES_SHIFT=10 CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y
# CONFIG_ARCH_MEMORY_PROBE is not set CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_X86_PMEM_LEGACY_DEVICE=y CONFIG_X86_PMEM_LEGACY=m CONFIG_X86_CHECK_BIOS_CORRUPTION=y
# CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set CONFIG_MTRR=yCONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=yCONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=yCONFIG_X86_SMAP=yCONFIG_X86_UMIP=y CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y CONFIG_X86_INTEL_TSX_MODE_OFF=y
# CONFIG_X86_INTEL_TSX_MODE_ON is not set
# CONFIG_X86_INTEL_TSX_MODE_AUTO is not set CONFIG_X86_SGX=yCONFIG_EFI=yCONFIG_EFI_STUB=yCONFIG_EFI_MIXED=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not setCONFIG_HZ_1000=yCONFIG_HZ=1000CONFIG_SCHED_HRTICK=yCONFIG_KEXEC=yCONFIG_KEXEC_FILE=y CONFIG_ARCH_HAS_KEXEC_PURGATORY=y
# CONFIG_KEXEC_SIG is not set CONFIG_CRASH_DUMP=yCONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=yCONFIG_RANDOMIZE_BASE=yCONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_DYNAMIC_MEMORY_LAYOUT=y CONFIG_RANDOMIZE_MEMORY=y CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0xa CONFIG_HOTPLUG_CPU=y CONFIG_BOOTPARAM_HOTPLUG_CPU0=y
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y
# CONFIG_LEGACY_VSYSCALL_XONLY is not set
# CONFIG_LEGACY_VSYSCALL_NONE is not set
# CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y
# CONFIG_STRICT_SIGALTSTACK_SIZE is not set CONFIG_HAVE_LIVEPATCH=yCONFIG_LIVEPATCH=y
# end of Processor type and features
CONFIG_ARCH_HAS_ADD_PAGES=yCONFIG_ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE=yCONFIG_USE_PERCPU_NUMA_NODE_ID=y
#
# Power management and ACPI options
#CONFIG_ARCH_HIBERNATION_HEADER=yCONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not setCONFIG_HIBERNATE_CALLBACKS=yCONFIG_HIBERNATION=yCONFIG_HIBERNATION_SNAPSHOT_DEV=yCONFIG_PM_STD_PARTITION=""CONFIG_PM_SLEEP=yCONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not setCONFIG_PM=yCONFIG_PM_DEBUG=y
# CONFIG_PM_ADVANCED_DEBUG is not set
# CONFIG_PM_TEST_SUSPEND is not setCONFIG_PM_SLEEP_DEBUG=y
# CONFIG_DPM_WATCHDOG is not set
# CONFIG_PM_TRACE_RTC is not setCONFIG_PM_CLK=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
# CONFIG_ENERGY_MODEL is not setCONFIG_ARCH_SUPPORTS_ACPI=yCONFIG_ACPI=yCONFIG_ACPI_LEGACY_TABLES_LOOKUP=yCONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=yCONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
# CONFIG_ACPI_DEBUGGER is not setCONFIG_ACPI_SPCR_TABLE=y
# CONFIG_ACPI_FPDT is not setCONFIG_ACPI_LPIT=yCONFIG_ACPI_SLEEP=yCONFIG_ACPI_REV_OVERRIDE_POSSIBLE=yCONFIG_ACPI_EC_DEBUGFS=mCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=mCONFIG_ACPI_FAN=yCONFIG_ACPI_TAD=mCONFIG_ACPI_DOCK=yCONFIG_ACPI_CPU_FREQ_PSS=yCONFIG_ACPI_PROCESSOR_CSTATE=yCONFIG_ACPI_PROCESSOR_IDLE=yCONFIG_ACPI_CPPC_LIB=yCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_IPMI=mCONFIG_ACPI_HOTPLUG_CPU=yCONFIG_ACPI_PROCESSOR_AGGREGATOR=mCONFIG_ACPI_THERMAL=yCONFIG_ACPI_PLATFORM_PROFILE=mCONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=yCONFIG_ACPI_TABLE_UPGRADE=y
# CONFIG_ACPI_DEBUG is not setCONFIG_ACPI_PCI_SLOT=yCONFIG_ACPI_CONTAINER=yCONFIG_ACPI_HOTPLUG_MEMORY=yCONFIG_ACPI_HOTPLUG_IOAPIC=yCONFIG_ACPI_SBS=mCONFIG_ACPI_HED=y
# CONFIG_ACPI_CUSTOM_METHOD is not setCONFIG_ACPI_BGRT=y
# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not setCONFIG_ACPI_NFIT=m
# CONFIG_NFIT_SECURITY_DEBUG is not setCONFIG_ACPI_NUMA=y
# CONFIG_ACPI_HMAT is not setCONFIG_HAVE_ACPI_APEI=yCONFIG_HAVE_ACPI_APEI_NMI=yCONFIG_ACPI_APEI=yCONFIG_ACPI_APEI_GHES=yCONFIG_ACPI_APEI_PCIEAER=yCONFIG_ACPI_APEI_MEMORY_FAILURE=yCONFIG_ACPI_APEI_EINJ=m
# CONFIG_ACPI_APEI_ERST_DEBUG is not set
# CONFIG_ACPI_DPTF is not setCONFIG_ACPI_WATCHDOG=yCONFIG_ACPI_EXTLOG=mCONFIG_ACPI_ADXL=y
# CONFIG_ACPI_CONFIGFS is not setCONFIG_PMIC_OPREGION=yCONFIG_X86_PM_TIMER=yCONFIG_ACPI_PRMT=y
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
#
# CPU frequency scaling drivers
#CONFIG_X86_INTEL_PSTATE=y
# CONFIG_X86_PCC_CPUFREQ is not setCONFIG_X86_ACPI_CPUFREQ=mCONFIG_X86_ACPI_CPUFREQ_CPB=yCONFIG_X86_POWERNOW_K8=m
# CONFIG_X86_AMD_FREQ_SENSITIVITY is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not setCONFIG_X86_P4_CLOCKMOD=m
#
# shared options # CONFIG_X86_SPEEDSTEP_LIB=m # end of CPU Frequency scaling
#
# CPU Idle
#CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not setCONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
# CONFIG_CPU_IDLE_GOV_HALTPOLL is not setCONFIG_HALTPOLL_CPUIDLE=y
# end of CPU Idle
CONFIG_INTEL_IDLE=y
# end of Power management and ACPI options
#
# Bus options (PCI etc.)
#CONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_MMCONF_FAM10H=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
# CONFIG_ISA_BUS is not setCONFIG_ISA_DMA_API=yCONFIG_AMD_NB=y
# end of Bus options (PCI etc.)
#
# Binary Emulations
#CONFIG_IA32_EMULATION=y
# CONFIG_X86_X32 is not setCONFIG_COMPAT_32=yCONFIG_COMPAT=yCONFIG_COMPAT_FOR_U64_ALIGNMENT=yCONFIG_SYSVIPC_COMPAT=y
# end of Binary Emulations
CONFIG_HAVE_KVM=yCONFIG_HAVE_KVM_IRQCHIP=yCONFIG_HAVE_KVM_IRQFD=yCONFIG_HAVE_KVM_IRQ_ROUTING=yCONFIG_HAVE_KVM_EVENTFD=yCONFIG_KVM_MMIO=yCONFIG_KVM_ASYNC_PF=yCONFIG_HAVE_KVM_MSI=yCONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=yCONFIG_KVM_VFIO=yCONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=yCONFIG_KVM_COMPAT=yCONFIG_HAVE_KVM_IRQ_BYPASS=yCONFIG_HAVE_KVM_NO_POLL=yCONFIG_KVM_XFER_TO_GUEST_WORK=yCONFIG_HAVE_KVM_PM_NOTIFIER=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=y
# CONFIG_KVM_WERROR is not setCONFIG_KVM_INTEL=y
# CONFIG_X86_SGX_KVM is not set
# CONFIG_KVM_AMD is not set
# CONFIG_KVM_XEN is not setCONFIG_KVM_MMU_AUDIT=yCONFIG_AS_AVX512=yCONFIG_AS_SHA1_NI=yCONFIG_AS_SHA256_NI=yCONFIG_AS_TPAUSE=y
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_HOTPLUG_SMT=yCONFIG_GENERIC_ENTRY=yCONFIG_KPROBES=yCONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_STATIC_CALL_SELFTEST is not setCONFIG_OPTPROBES=yCONFIG_KPROBES_ON_FTRACE=yCONFIG_UPROBES=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_ARCH_USE_BUILTIN_BSWAP=yCONFIG_KRETPROBES=yCONFIG_USER_RETURN_NOTIFIER=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_KPROBES_ON_FTRACE=yCONFIG_ARCH_CORRECT_STACKTRACE_ON_KRETPROBE=yCONFIG_HAVE_FUNCTION_ERROR_INJECTION=yCONFIG_HAVE_NMI=yCONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_CONTIGUOUS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_ARCH_HAS_FORTIFY_SOURCE=yCONFIG_ARCH_HAS_SET_MEMORY=yCONFIG_ARCH_HAS_SET_DIRECT_MAP=yCONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=yCONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=yCONFIG_ARCH_WANTS_NO_INSTR=yCONFIG_HAVE_ASM_MODVERSIONS=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_RSEQ=yCONFIG_HAVE_FUNCTION_ARG_ACCESS_API=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_MIXED_BREAKPOINTS_REGS=yCONFIG_HAVE_USER_RETURN_NOTIFIER=yCONFIG_HAVE_PERF_EVENTS_NMI=yCONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=yCONFIG_HAVE_PERF_REGS=yCONFIG_HAVE_PERF_USER_STACK_DUMP=yCONFIG_HAVE_ARCH_JUMP_LABEL=yCONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=yCONFIG_MMU_GATHER_TABLE_FREE=yCONFIG_MMU_GATHER_RCU_TABLE_FREE=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_HAVE_ALIGNED_STRUCT_PAGE=yCONFIG_HAVE_CMPXCHG_LOCAL=yCONFIG_HAVE_CMPXCHG_DOUBLE=yCONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=yCONFIG_ARCH_WANT_OLD_COMPAT_IPC=yCONFIG_HAVE_ARCH_SECCOMP=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=yCONFIG_SECCOMP=yCONFIG_SECCOMP_FILTER=y
# CONFIG_SECCOMP_CACHE_DEBUG is not setCONFIG_HAVE_ARCH_STACKLEAK=yCONFIG_HAVE_STACKPROTECTOR=yCONFIG_STACKPROTECTOR=yCONFIG_STACKPROTECTOR_STRONG=yCONFIG_ARCH_SUPPORTS_LTO_CLANG=yCONFIG_ARCH_SUPPORTS_LTO_CLANG_THIN=yCONFIG_LTO_NONE=yCONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=yCONFIG_HAVE_CONTEXT_TRACKING=yCONFIG_HAVE_CONTEXT_TRACKING_OFFSTACK=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_HAVE_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_MOVE_PUD=yCONFIG_HAVE_MOVE_PMD=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=yCONFIG_HAVE_ARCH_HUGE_VMAP=yCONFIG_ARCH_WANT_HUGE_PMD_SHARE=yCONFIG_HAVE_ARCH_SOFT_DIRTY=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_RELA=yCONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=yCONFIG_HAVE_SOFTIRQ_ON_OWN_STACK=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_ARCH_MMAP_RND_BITS=28CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=yCONFIG_ARCH_MMAP_RND_COMPAT_BITS=8CONFIG_HAVE_ARCH_COMPAT_MMAP_BASES=yCONFIG_HAVE_STACK_VALIDATION=yCONFIG_HAVE_RELIABLE_STACKTRACE=yCONFIG_OLD_SIGSUSPEND3=yCONFIG_COMPAT_OLD_SIGACTION=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_HAVE_ARCH_VMAP_STACK=yCONFIG_VMAP_STACK=yCONFIG_HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET=yCONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT=yCONFIG_ARCH_HAS_STRICT_KERNEL_RWX=yCONFIG_STRICT_KERNEL_RWX=yCONFIG_ARCH_HAS_STRICT_MODULE_RWX=yCONFIG_STRICT_MODULE_RWX=yCONFIG_HAVE_ARCH_PREL32_RELOCATIONS=yCONFIG_ARCH_USE_MEMREMAP_PROT=y
# CONFIG_LOCK_EVENT_COUNTS is not setCONFIG_ARCH_HAS_MEM_ENCRYPT=yCONFIG_HAVE_STATIC_CALL=yCONFIG_HAVE_STATIC_CALL_INLINE=yCONFIG_HAVE_PREEMPT_DYNAMIC=yCONFIG_ARCH_WANT_LD_ORPHAN_WARN=yCONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=yCONFIG_ARCH_HAS_ELFCORE_COMPAT=yCONFIG_ARCH_HAS_PARANOID_L1D_FLUSH=yCONFIG_DYNAMIC_SIGFRAME=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not setCONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_HAVE_GCC_PLUGINS=y
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULE_SIG_FORMAT=yCONFIG_MODULES=yCONFIG_MODULE_FORCE_LOAD=yCONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set CONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set CONFIG_MODULE_SIG_HASH="sha256" CONFIG_MODULE_COMPRESS_NONE=y
# CONFIG_MODULE_COMPRESS_GZIP is not set
# CONFIG_MODULE_COMPRESS_XZ is not set
# CONFIG_MODULE_COMPRESS_ZSTD is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set CONFIG_MODPROBE_PATH="/sbin/modprobe"
# CONFIG_TRIM_UNUSED_KSYMS is not set CONFIG_MODULES_TREE_LOOKUP=yCONFIG_BLOCK=yCONFIG_BLK_CGROUP_RWSTAT=y CONFIG_BLK_DEV_BSG_COMMON=y CONFIG_BLK_DEV_BSGLIB=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLK_DEV_INTEGRITY_T10=m
# CONFIG_BLK_DEV_ZONED is not set CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set CONFIG_BLK_WBT=yCONFIG_BLK_WBT_MQ=y
# CONFIG_BLK_CGROUP_IOLATENCY is not set
# CONFIG_BLK_CGROUP_FC_APPID is not set
# CONFIG_BLK_CGROUP_IOCOST is not set
# CONFIG_BLK_CGROUP_IOPRIO is not set CONFIG_BLK_DEBUG_FS=y
# CONFIG_BLK_SED_OPAL is not set
# CONFIG_BLK_INLINE_ENCRYPTION is not set
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not setCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not setCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not setCONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not setCONFIG_SUN_PARTITION=yCONFIG_KARMA_PARTITION=yCONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set
# end of Partition Types
CONFIG_BLOCK_COMPAT=yCONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLK_PM=yCONFIG_BLOCK_HOLDER_DEPRECATED=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=yCONFIG_MQ_IOSCHED_KYBER=yCONFIG_IOSCHED_BFQ=yCONFIG_BFQ_GROUP_IOSCHED=y
# CONFIG_BFQ_CGROUP_DEBUG is not set
# end of IO Schedulers
CONFIG_PREEMPT_NOTIFIERS=yCONFIG_PADATA=yCONFIG_ASN1=yCONFIG_UNINLINE_SPIN_UNLOCK=yCONFIG_ARCH_SUPPORTS_ATOMIC_RMW=yCONFIG_MUTEX_SPIN_ON_OWNER=yCONFIG_RWSEM_SPIN_ON_OWNER=yCONFIG_LOCK_SPIN_ON_OWNER=yCONFIG_ARCH_USE_QUEUED_SPINLOCKS=yCONFIG_QUEUED_SPINLOCKS=yCONFIG_ARCH_USE_QUEUED_RWLOCKS=yCONFIG_QUEUED_RWLOCKS=yCONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=yCONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=yCONFIG_ARCH_HAS_SYSCALL_WRAPPER=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_COMPAT_BINFMT_ELF=yCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_BINFMT_MISC=mCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_FAST_GUP=y CONFIG_NUMA_KEEP_MEMINFO=y CONFIG_MEMORY_ISOLATION=y CONFIG_EXCLUSIVE_SYSTEM_RAM=y CONFIG_HAVE_BOOTMEM_INFO_NODE=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_MEMORY_HOTPLUG=y
# CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not set CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y CONFIG_MEMORY_HOTREMOVE=y CONFIG_MHP_MEMMAP_ON_MEMORY=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y CONFIG_MEMORY_BALLOON=y CONFIG_BALLOON_COMPACTION=y CONFIG_COMPACTION=yCONFIG_PAGE_REPORTING=yCONFIG_MIGRATION=y CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y CONFIG_ARCH_ENABLE_THP_MIGRATION=y CONFIG_CONTIG_ALLOC=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_VIRT_TO_BUS=yCONFIG_MMU_NOTIFIER=yCONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y CONFIG_MEMORY_FAILURE=y CONFIG_HWPOISON_INJECT=m CONFIG_TRANSPARENT_HUGEPAGE=y CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not set CONFIG_ARCH_WANTS_THP_SWAP=y CONFIG_THP_SWAP=yCONFIG_CLEANCACHE=yCONFIG_FRONTSWAP=y
# CONFIG_CMA is not set
# CONFIG_MEM_SOFT_DIRTY is not set CONFIG_ZSWAP=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4 is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC is not set # CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD is not set CONFIG_ZSWAP_COMPRESSOR_DEFAULT="lzo" CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=y
# CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD is not set # CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC is not set CONFIG_ZSWAP_ZPOOL_DEFAULT="zbud"
# CONFIG_ZSWAP_DEFAULT_ON is not set CONFIG_ZPOOL=yCONFIG_ZBUD=y
# CONFIG_Z3FOLD is not setCONFIG_ZSMALLOC=yCONFIG_ZSMALLOC_STAT=y CONFIG_GENERIC_EARLY_IOREMAP=y CONFIG_DEFERRED_STRUCT_PAGE_INIT=y CONFIG_PAGE_IDLE_FLAG=y CONFIG_IDLE_PAGE_TRACKING=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_PTE_DEVMAP=y CONFIG_ARCH_HAS_ZONE_DMA_SET=y CONFIG_ZONE_DMA=yCONFIG_ZONE_DMA32=yCONFIG_ZONE_DEVICE=y CONFIG_DEV_PAGEMAP_OPS=yCONFIG_HMM_MIRROR=yCONFIG_DEVICE_PRIVATE=yCONFIG_VMAP_PFN=y CONFIG_ARCH_USES_HIGH_VMA_FLAGS=y CONFIG_ARCH_HAS_PKEYS=y
# CONFIG_PERCPU_STATS is not set CONFIG_GUP_TEST=y
# CONFIG_READ_ONLY_THP_FOR_FS is not set CONFIG_ARCH_HAS_PTE_SPECIAL=y
#
# Data Access Monitoring
#
# CONFIG_DAMON is not set
# end of Data Access Monitoring # end of Memory Management options
CONFIG_NET=yCONFIG_NET_INGRESS=yCONFIG_NET_EGRESS=yCONFIG_NET_REDIRECT=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_PACKET_DIAG=mCONFIG_UNIX=yCONFIG_UNIX_SCM=yCONFIG_AF_UNIX_OOB=yCONFIG_UNIX_DIAG=mCONFIG_TLS=mCONFIG_TLS_DEVICE=y
# CONFIG_TLS_TOE is not setCONFIG_XFRM=yCONFIG_XFRM_OFFLOAD=yCONFIG_XFRM_ALGO=yCONFIG_XFRM_USER=y
# CONFIG_XFRM_USER_COMPAT is not set
# CONFIG_XFRM_INTERFACE is not setCONFIG_XFRM_SUB_POLICY=yCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_AH=mCONFIG_XFRM_ESP=mCONFIG_XFRM_IPCOMP=mCONFIG_NET_KEY=mCONFIG_NET_KEY_MIGRATE=yCONFIG_XDP_SOCKETS=y
# CONFIG_XDP_SOCKETS_DIAG is not setCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_FIB_TRIE_STATS=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_IP_ROUTE_CLASSID=yCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not setCONFIG_NET_IPIP=yCONFIG_NET_IPGRE_DEMUX=yCONFIG_NET_IP_TUNNEL=yCONFIG_NET_IPGRE=yCONFIG_NET_IPGRE_BROADCAST=yCONFIG_IP_MROUTE_COMMON=yCONFIG_IP_MROUTE=yCONFIG_IP_MROUTE_MULTIPLE_TABLES=yCONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=yCONFIG_SYN_COOKIES=yCONFIG_NET_IPVTI=mCONFIG_NET_UDP_TUNNEL=yCONFIG_NET_FOU=yCONFIG_NET_FOU_IP_TUNNELS=yCONFIG_INET_AH=mCONFIG_INET_ESP=mCONFIG_INET_ESP_OFFLOAD=m
# CONFIG_INET_ESPINTCP is not setCONFIG_INET_IPCOMP=mCONFIG_INET_XFRM_TUNNEL=mCONFIG_INET_TUNNEL=yCONFIG_INET_DIAG=mCONFIG_INET_TCP_DIAG=mCONFIG_INET_UDP_DIAG=mCONFIG_INET_RAW_DIAG=m
# CONFIG_INET_DIAG_DESTROY is not setCONFIG_TCP_CONG_ADVANCED=yCONFIG_TCP_CONG_BIC=mCONFIG_TCP_CONG_CUBIC=yCONFIG_TCP_CONG_WESTWOOD=mCONFIG_TCP_CONG_HTCP=mCONFIG_TCP_CONG_HSTCP=mCONFIG_TCP_CONG_HYBLA=mCONFIG_TCP_CONG_VEGAS=mCONFIG_TCP_CONG_NV=mCONFIG_TCP_CONG_SCALABLE=mCONFIG_TCP_CONG_LP=mCONFIG_TCP_CONG_VENO=mCONFIG_TCP_CONG_YEAH=mCONFIG_TCP_CONG_ILLINOIS=mCONFIG_TCP_CONG_DCTCP=m
# CONFIG_TCP_CONG_CDG is not setCONFIG_TCP_CONG_BBR=mCONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not setCONFIG_DEFAULT_TCP_CONG="cubic"CONFIG_TCP_MD5SIG=yCONFIG_IPV6=yCONFIG_IPV6_ROUTER_PREF=yCONFIG_IPV6_ROUTE_INFO=yCONFIG_IPV6_OPTIMISTIC_DAD=yCONFIG_INET6_AH=mCONFIG_INET6_ESP=mCONFIG_INET6_ESP_OFFLOAD=m
# CONFIG_INET6_ESPINTCP is not setCONFIG_INET6_IPCOMP=mCONFIG_IPV6_MIP6=m
# CONFIG_IPV6_ILA is not setCONFIG_INET6_XFRM_TUNNEL=mCONFIG_INET6_TUNNEL=yCONFIG_IPV6_VTI=mCONFIG_IPV6_SIT=mCONFIG_IPV6_SIT_6RD=yCONFIG_IPV6_NDISC_NODETYPE=yCONFIG_IPV6_TUNNEL=yCONFIG_IPV6_GRE=yCONFIG_IPV6_FOU=yCONFIG_IPV6_FOU_TUNNEL=yCONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not setCONFIG_IPV6_MROUTE=yCONFIG_IPV6_MROUTE_MULTIPLE_TABLES=yCONFIG_IPV6_PIMSM_V2=yCONFIG_IPV6_SEG6_LWTUNNEL=y
# CONFIG_IPV6_SEG6_HMAC is not setCONFIG_IPV6_SEG6_BPF=y
# CONFIG_IPV6_RPL_LWTUNNEL is not set
# CONFIG_IPV6_IOAM6_LWTUNNEL is not setCONFIG_NETLABEL=yCONFIG_MPTCP=yCONFIG_INET_MPTCP_DIAG=mCONFIG_MPTCP_IPV6=yCONFIG_NETWORK_SECMARK=yCONFIG_NET_PTP_CLASSIFY=yCONFIG_NETWORK_PHY_TIMESTAMPING=yCONFIG_NETFILTER=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=m
#
# Core Netfilter Configuration
#CONFIG_NETFILTER_INGRESS=yCONFIG_NETFILTER_EGRESS=yCONFIG_NETFILTER_SKIP_EGRESS=yCONFIG_NETFILTER_NETLINK=mCONFIG_NETFILTER_FAMILY_BRIDGE=yCONFIG_NETFILTER_FAMILY_ARP=y
# CONFIG_NETFILTER_NETLINK_HOOK is not set
# CONFIG_NETFILTER_NETLINK_ACCT is not setCONFIG_NETFILTER_NETLINK_QUEUE=mCONFIG_NETFILTER_NETLINK_LOG=mCONFIG_NETFILTER_NETLINK_OSF=mCONFIG_NF_CONNTRACK=mCONFIG_NF_LOG_SYSLOG=mCONFIG_NETFILTER_CONNCOUNT=mCONFIG_NF_CONNTRACK_MARK=yCONFIG_NF_CONNTRACK_SECMARK=yCONFIG_NF_CONNTRACK_ZONES=yCONFIG_NF_CONNTRACK_PROCFS=yCONFIG_NF_CONNTRACK_EVENTS=yCONFIG_NF_CONNTRACK_TIMEOUT=yCONFIG_NF_CONNTRACK_TIMESTAMP=yCONFIG_NF_CONNTRACK_LABELS=yCONFIG_NF_CT_PROTO_DCCP=yCONFIG_NF_CT_PROTO_GRE=yCONFIG_NF_CT_PROTO_SCTP=yCONFIG_NF_CT_PROTO_UDPLITE=yCONFIG_NF_CONNTRACK_AMANDA=mCONFIG_NF_CONNTRACK_FTP=mCONFIG_NF_CONNTRACK_H323=mCONFIG_NF_CONNTRACK_IRC=mCONFIG_NF_CONNTRACK_BROADCAST=mCONFIG_NF_CONNTRACK_NETBIOS_NS=mCONFIG_NF_CONNTRACK_SNMP=mCONFIG_NF_CONNTRACK_PPTP=mCONFIG_NF_CONNTRACK_SANE=mCONFIG_NF_CONNTRACK_SIP=mCONFIG_NF_CONNTRACK_TFTP=mCONFIG_NF_CT_NETLINK=mCONFIG_NF_CT_NETLINK_TIMEOUT=mCONFIG_NF_CT_NETLINK_HELPER=mCONFIG_NETFILTER_NETLINK_GLUE_CT=yCONFIG_NF_NAT=mCONFIG_NF_NAT_AMANDA=mCONFIG_NF_NAT_FTP=mCONFIG_NF_NAT_IRC=mCONFIG_NF_NAT_SIP=mCONFIG_NF_NAT_TFTP=mCONFIG_NF_NAT_REDIRECT=yCONFIG_NF_NAT_MASQUERADE=yCONFIG_NETFILTER_SYNPROXY=mCONFIG_NF_TABLES=mCONFIG_NF_TABLES_INET=yCONFIG_NF_TABLES_NETDEV=yCONFIG_NFT_NUMGEN=mCONFIG_NFT_CT=mCONFIG_NFT_FLOW_OFFLOAD=mCONFIG_NFT_COUNTER=mCONFIG_NFT_CONNLIMIT=mCONFIG_NFT_LOG=mCONFIG_NFT_LIMIT=mCONFIG_NFT_MASQ=mCONFIG_NFT_REDIR=mCONFIG_NFT_NAT=m
# CONFIG_NFT_TUNNEL is not setCONFIG_NFT_OBJREF=mCONFIG_NFT_QUEUE=mCONFIG_NFT_QUOTA=mCONFIG_NFT_REJECT=mCONFIG_NFT_REJECT_INET=mCONFIG_NFT_COMPAT=mCONFIG_NFT_HASH=mCONFIG_NFT_FIB=mCONFIG_NFT_FIB_INET=m
# CONFIG_NFT_XFRM is not setCONFIG_NFT_SOCKET=m
# CONFIG_NFT_OSF is not set
# CONFIG_NFT_TPROXY is not set
# CONFIG_NFT_SYNPROXY is not setCONFIG_NF_DUP_NETDEV=mCONFIG_NFT_DUP_NETDEV=mCONFIG_NFT_FWD_NETDEV=mCONFIG_NFT_FIB_NETDEV=m
# CONFIG_NFT_REJECT_NETDEV is not setCONFIG_NF_FLOW_TABLE_INET=mCONFIG_NF_FLOW_TABLE=mCONFIG_NETFILTER_XTABLES=yCONFIG_NETFILTER_XTABLES_COMPAT=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=mCONFIG_NETFILTER_XT_CONNMARK=mCONFIG_NETFILTER_XT_SET=m
#
# Xtables targets
#CONFIG_NETFILTER_XT_TARGET_AUDIT=mCONFIG_NETFILTER_XT_TARGET_CHECKSUM=mCONFIG_NETFILTER_XT_TARGET_CLASSIFY=mCONFIG_NETFILTER_XT_TARGET_CONNMARK=mCONFIG_NETFILTER_XT_TARGET_CONNSECMARK=mCONFIG_NETFILTER_XT_TARGET_CT=mCONFIG_NETFILTER_XT_TARGET_DSCP=mCONFIG_NETFILTER_XT_TARGET_HL=mCONFIG_NETFILTER_XT_TARGET_HMARK=mCONFIG_NETFILTER_XT_TARGET_IDLETIMER=m
# CONFIG_NETFILTER_XT_TARGET_LED is not setCONFIG_NETFILTER_XT_TARGET_LOG=mCONFIG_NETFILTER_XT_TARGET_MARK=mCONFIG_NETFILTER_XT_NAT=mCONFIG_NETFILTER_XT_TARGET_NETMAP=mCONFIG_NETFILTER_XT_TARGET_NFLOG=mCONFIG_NETFILTER_XT_TARGET_NFQUEUE=mCONFIG_NETFILTER_XT_TARGET_NOTRACK=mCONFIG_NETFILTER_XT_TARGET_RATEEST=mCONFIG_NETFILTER_XT_TARGET_REDIRECT=mCONFIG_NETFILTER_XT_TARGET_MASQUERADE=mCONFIG_NETFILTER_XT_TARGET_TEE=mCONFIG_NETFILTER_XT_TARGET_TPROXY=mCONFIG_NETFILTER_XT_TARGET_TRACE=mCONFIG_NETFILTER_XT_TARGET_SECMARK=mCONFIG_NETFILTER_XT_TARGET_TCPMSS=mCONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=mCONFIG_NETFILTER_XT_MATCH_BPF=mCONFIG_NETFILTER_XT_MATCH_CGROUP=mCONFIG_NETFILTER_XT_MATCH_CLUSTER=mCONFIG_NETFILTER_XT_MATCH_COMMENT=mCONFIG_NETFILTER_XT_MATCH_CONNBYTES=mCONFIG_NETFILTER_XT_MATCH_CONNLABEL=mCONFIG_NETFILTER_XT_MATCH_CONNLIMIT=mCONFIG_NETFILTER_XT_MATCH_CONNMARK=mCONFIG_NETFILTER_XT_MATCH_CONNTRACK=mCONFIG_NETFILTER_XT_MATCH_CPU=mCONFIG_NETFILTER_XT_MATCH_DCCP=mCONFIG_NETFILTER_XT_MATCH_DEVGROUP=mCONFIG_NETFILTER_XT_MATCH_DSCP=mCONFIG_NETFILTER_XT_MATCH_ECN=mCONFIG_NETFILTER_XT_MATCH_ESP=mCONFIG_NETFILTER_XT_MATCH_HASHLIMIT=mCONFIG_NETFILTER_XT_MATCH_HELPER=mCONFIG_NETFILTER_XT_MATCH_HL=m
# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not setCONFIG_NETFILTER_XT_MATCH_IPRANGE=mCONFIG_NETFILTER_XT_MATCH_IPVS=m
# CONFIG_NETFILTER_XT_MATCH_L2TP is not setCONFIG_NETFILTER_XT_MATCH_LENGTH=mCONFIG_NETFILTER_XT_MATCH_LIMIT=mCONFIG_NETFILTER_XT_MATCH_MAC=mCONFIG_NETFILTER_XT_MATCH_MARK=mCONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
# CONFIG_NETFILTER_XT_MATCH_NFACCT is not setCONFIG_NETFILTER_XT_MATCH_OSF=mCONFIG_NETFILTER_XT_MATCH_OWNER=mCONFIG_NETFILTER_XT_MATCH_POLICY=mCONFIG_NETFILTER_XT_MATCH_PHYSDEV=mCONFIG_NETFILTER_XT_MATCH_PKTTYPE=mCONFIG_NETFILTER_XT_MATCH_QUOTA=mCONFIG_NETFILTER_XT_MATCH_RATEEST=mCONFIG_NETFILTER_XT_MATCH_REALM=mCONFIG_NETFILTER_XT_MATCH_RECENT=mCONFIG_NETFILTER_XT_MATCH_SCTP=mCONFIG_NETFILTER_XT_MATCH_SOCKET=mCONFIG_NETFILTER_XT_MATCH_STATE=mCONFIG_NETFILTER_XT_MATCH_STATISTIC=mCONFIG_NETFILTER_XT_MATCH_STRING=mCONFIG_NETFILTER_XT_MATCH_TCPMSS=m
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# end of Core Netfilter Configuration
CONFIG_IP_SET=mCONFIG_IP_SET_MAX=256CONFIG_IP_SET_BITMAP_IP=mCONFIG_IP_SET_BITMAP_IPMAC=mCONFIG_IP_SET_BITMAP_PORT=mCONFIG_IP_SET_HASH_IP=mCONFIG_IP_SET_HASH_IPMARK=mCONFIG_IP_SET_HASH_IPPORT=mCONFIG_IP_SET_HASH_IPPORTIP=mCONFIG_IP_SET_HASH_IPPORTNET=mCONFIG_IP_SET_HASH_IPMAC=mCONFIG_IP_SET_HASH_MAC=mCONFIG_IP_SET_HASH_NETPORTNET=mCONFIG_IP_SET_HASH_NET=mCONFIG_IP_SET_HASH_NETNET=mCONFIG_IP_SET_HASH_NETPORT=mCONFIG_IP_SET_HASH_NETIFACE=mCONFIG_IP_SET_LIST_SET=mCONFIG_IP_VS=mCONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not setCONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#CONFIG_IP_VS_PROTO_TCP=yCONFIG_IP_VS_PROTO_UDP=yCONFIG_IP_VS_PROTO_AH_ESP=yCONFIG_IP_VS_PROTO_ESP=yCONFIG_IP_VS_PROTO_AH=yCONFIG_IP_VS_PROTO_SCTP=y
#
# IPVS scheduler
#CONFIG_IP_VS_RR=mCONFIG_IP_VS_WRR=mCONFIG_IP_VS_LC=mCONFIG_IP_VS_WLC=mCONFIG_IP_VS_FO=mCONFIG_IP_VS_OVF=mCONFIG_IP_VS_LBLC=mCONFIG_IP_VS_LBLCR=mCONFIG_IP_VS_DH=mCONFIG_IP_VS_SH=m
# CONFIG_IP_VS_MH is not setCONFIG_IP_VS_SED=mCONFIG_IP_VS_NQ=m
# CONFIG_IP_VS_TWOS is not set
#
# IPVS SH scheduler
#CONFIG_IP_VS_SH_TAB_BITS=8
#
# IPVS MH scheduler
#CONFIG_IP_VS_MH_TAB_INDEX=12
#
# IPVS application helper
#CONFIG_IP_VS_FTP=mCONFIG_IP_VS_NFCT=yCONFIG_IP_VS_PE_SIP=m
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=mCONFIG_NF_SOCKET_IPV4=mCONFIG_NF_TPROXY_IPV4=mCONFIG_NF_TABLES_IPV4=yCONFIG_NFT_REJECT_IPV4=mCONFIG_NFT_DUP_IPV4=mCONFIG_NFT_FIB_IPV4=mCONFIG_NF_TABLES_ARP=yCONFIG_NF_FLOW_TABLE_IPV4=mCONFIG_NF_DUP_IPV4=mCONFIG_NF_LOG_ARP=mCONFIG_NF_LOG_IPV4=mCONFIG_NF_REJECT_IPV4=mCONFIG_NF_NAT_SNMP_BASIC=mCONFIG_NF_NAT_PPTP=mCONFIG_NF_NAT_H323=mCONFIG_IP_NF_IPTABLES=mCONFIG_IP_NF_MATCH_AH=mCONFIG_IP_NF_MATCH_ECN=mCONFIG_IP_NF_MATCH_RPFILTER=mCONFIG_IP_NF_MATCH_TTL=mCONFIG_IP_NF_FILTER=mCONFIG_IP_NF_TARGET_REJECT=mCONFIG_IP_NF_TARGET_SYNPROXY=mCONFIG_IP_NF_NAT=mCONFIG_IP_NF_TARGET_MASQUERADE=mCONFIG_IP_NF_TARGET_NETMAP=mCONFIG_IP_NF_TARGET_REDIRECT=mCONFIG_IP_NF_MANGLE=m
# CONFIG_IP_NF_TARGET_CLUSTERIP is not setCONFIG_IP_NF_TARGET_ECN=mCONFIG_IP_NF_TARGET_TTL=mCONFIG_IP_NF_RAW=mCONFIG_IP_NF_SECURITY=mCONFIG_IP_NF_ARPTABLES=mCONFIG_IP_NF_ARPFILTER=mCONFIG_IP_NF_ARP_MANGLE=m
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#CONFIG_NF_SOCKET_IPV6=mCONFIG_NF_TPROXY_IPV6=mCONFIG_NF_TABLES_IPV6=yCONFIG_NFT_REJECT_IPV6=mCONFIG_NFT_DUP_IPV6=mCONFIG_NFT_FIB_IPV6=mCONFIG_NF_FLOW_TABLE_IPV6=mCONFIG_NF_DUP_IPV6=mCONFIG_NF_REJECT_IPV6=mCONFIG_NF_LOG_IPV6=mCONFIG_IP6_NF_IPTABLES=mCONFIG_IP6_NF_MATCH_AH=mCONFIG_IP6_NF_MATCH_EUI64=mCONFIG_IP6_NF_MATCH_FRAG=mCONFIG_IP6_NF_MATCH_OPTS=mCONFIG_IP6_NF_MATCH_HL=mCONFIG_IP6_NF_MATCH_IPV6HEADER=mCONFIG_IP6_NF_MATCH_MH=mCONFIG_IP6_NF_MATCH_RPFILTER=mCONFIG_IP6_NF_MATCH_RT=m
# CONFIG_IP6_NF_MATCH_SRH is not set
# CONFIG_IP6_NF_TARGET_HL is not setCONFIG_IP6_NF_FILTER=mCONFIG_IP6_NF_TARGET_REJECT=mCONFIG_IP6_NF_TARGET_SYNPROXY=mCONFIG_IP6_NF_MANGLE=mCONFIG_IP6_NF_RAW=mCONFIG_IP6_NF_SECURITY=mCONFIG_IP6_NF_NAT=mCONFIG_IP6_NF_TARGET_MASQUERADE=mCONFIG_IP6_NF_TARGET_NPT=m
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=m CONFIG_NF_TABLES_BRIDGE=m
# CONFIG_NFT_BRIDGE_META is not set CONFIG_NFT_BRIDGE_REJECT=m
# CONFIG_NF_CONNTRACK_BRIDGE is not set CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_NFLOG=m
# CONFIG_BPFILTER is not set
# CONFIG_IP_DCCP is not setCONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5 is not set CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set CONFIG_SCTP_COOKIE_HMAC_MD5=y CONFIG_SCTP_COOKIE_HMAC_SHA1=y CONFIG_INET_SCTP_DIAG=m
# CONFIG_RDS is not setCONFIG_TIPC=mCONFIG_TIPC_MEDIA_UDP=yCONFIG_TIPC_CRYPTO=yCONFIG_TIPC_DIAG=mCONFIG_ATM=mCONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_L2TP=mCONFIG_L2TP_DEBUGFS=mCONFIG_L2TP_V3=yCONFIG_L2TP_IP=mCONFIG_L2TP_ETH=mCONFIG_STP=yCONFIG_GARP=yCONFIG_MRP=yCONFIG_BRIDGE=y CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_BRIDGE_VLAN_FILTERING=y
# CONFIG_BRIDGE_MRP is not set
# CONFIG_BRIDGE_CFM is not set
# CONFIG_NET_DSA is not set CONFIG_VLAN_8021Q=yCONFIG_VLAN_8021Q_GVRP=y CONFIG_VLAN_8021Q_MVRP=y
# CONFIG_DECNET is not setCONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not setCONFIG_6LOWPAN=m
# CONFIG_6LOWPAN_DEBUGFS is not set
# CONFIG_6LOWPAN_NHC is not set CONFIG_IEEE802154=m
# CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set CONFIG_IEEE802154_SOCKET=m CONFIG_IEEE802154_6LOWPAN=m CONFIG_MAC802154=mCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#CONFIG_NET_SCH_CBQ=mCONFIG_NET_SCH_HTB=mCONFIG_NET_SCH_HFSC=mCONFIG_NET_SCH_ATM=mCONFIG_NET_SCH_PRIO=mCONFIG_NET_SCH_MULTIQ=mCONFIG_NET_SCH_RED=mCONFIG_NET_SCH_SFB=mCONFIG_NET_SCH_SFQ=mCONFIG_NET_SCH_TEQL=mCONFIG_NET_SCH_TBF=m
# CONFIG_NET_SCH_CBS is not setCONFIG_NET_SCH_ETF=m
# CONFIG_NET_SCH_TAPRIO is not setCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=mCONFIG_NET_SCH_NETEM=yCONFIG_NET_SCH_DRR=mCONFIG_NET_SCH_MQPRIO=m
# CONFIG_NET_SCH_SKBPRIO is not setCONFIG_NET_SCH_CHOKE=mCONFIG_NET_SCH_QFQ=mCONFIG_NET_SCH_CODEL=mCONFIG_NET_SCH_FQ_CODEL=y
# CONFIG_NET_SCH_CAKE is not setCONFIG_NET_SCH_FQ=mCONFIG_NET_SCH_HHF=mCONFIG_NET_SCH_PIE=mCONFIG_NET_SCH_FQ_PIE=mCONFIG_NET_SCH_INGRESS=yCONFIG_NET_SCH_PLUG=mCONFIG_NET_SCH_ETS=mCONFIG_NET_SCH_DEFAULT=y
# CONFIG_DEFAULT_FQ is not set
# CONFIG_DEFAULT_CODEL is not setCONFIG_DEFAULT_FQ_CODEL=y
# CONFIG_DEFAULT_FQ_PIE is not set
# CONFIG_DEFAULT_SFQ is not set
# CONFIG_DEFAULT_PFIFO_FAST is not setCONFIG_DEFAULT_NET_SCH="fq_codel"
#
# Classification
#CONFIG_NET_CLS=yCONFIG_NET_CLS_BASIC=mCONFIG_NET_CLS_TCINDEX=mCONFIG_NET_CLS_ROUTE4=mCONFIG_NET_CLS_FW=mCONFIG_NET_CLS_U32=mCONFIG_CLS_U32_PERF=yCONFIG_CLS_U32_MARK=yCONFIG_NET_CLS_RSVP=mCONFIG_NET_CLS_RSVP6=mCONFIG_NET_CLS_FLOW=mCONFIG_NET_CLS_CGROUP=yCONFIG_NET_CLS_BPF=mCONFIG_NET_CLS_FLOWER=mCONFIG_NET_CLS_MATCHALL=mCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32CONFIG_NET_EMATCH_CMP=mCONFIG_NET_EMATCH_NBYTE=mCONFIG_NET_EMATCH_U32=mCONFIG_NET_EMATCH_META=mCONFIG_NET_EMATCH_TEXT=mCONFIG_NET_EMATCH_CANID=mCONFIG_NET_EMATCH_IPSET=mCONFIG_NET_EMATCH_IPT=mCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=mCONFIG_NET_ACT_GACT=mCONFIG_GACT_PROB=yCONFIG_NET_ACT_MIRRED=mCONFIG_NET_ACT_SAMPLE=mCONFIG_NET_ACT_IPT=mCONFIG_NET_ACT_NAT=mCONFIG_NET_ACT_PEDIT=mCONFIG_NET_ACT_SIMP=mCONFIG_NET_ACT_SKBEDIT=mCONFIG_NET_ACT_CSUM=mCONFIG_NET_ACT_MPLS=mCONFIG_NET_ACT_VLAN=mCONFIG_NET_ACT_BPF=mCONFIG_NET_ACT_CONNMARK=mCONFIG_NET_ACT_CTINFO=mCONFIG_NET_ACT_SKBMOD=mCONFIG_NET_ACT_IFE=mCONFIG_NET_ACT_TUNNEL_KEY=mCONFIG_NET_ACT_CT=m
# CONFIG_NET_ACT_GATE is not setCONFIG_NET_IFE_SKBMARK=mCONFIG_NET_IFE_SKBPRIO=mCONFIG_NET_IFE_SKBTCINDEX=m
# CONFIG_NET_TC_SKB_EXT is not setCONFIG_NET_SCH_FIFO=yCONFIG_DCB=yCONFIG_DNS_RESOLVER=m
# CONFIG_BATMAN_ADV is not setCONFIG_OPENVSWITCH=mCONFIG_OPENVSWITCH_GRE=mCONFIG_OPENVSWITCH_VXLAN=mCONFIG_OPENVSWITCH_GENEVE=mCONFIG_VSOCKETS=mCONFIG_VSOCKETS_DIAG=mCONFIG_VSOCKETS_LOOPBACK=mCONFIG_VMWARE_VMCI_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS_COMMON=mCONFIG_HYPERV_VSOCKETS=mCONFIG_NETLINK_DIAG=mCONFIG_MPLS=yCONFIG_NET_MPLS_GSO=mCONFIG_MPLS_ROUTING=mCONFIG_MPLS_IPTUNNEL=mCONFIG_NET_NSH=y
# CONFIG_HSR is not setCONFIG_NET_SWITCHDEV=yCONFIG_NET_L3_MASTER_DEV=y
# CONFIG_QRTR is not set
# CONFIG_NET_NCSI is not setCONFIG_PCPU_DEV_REFCNT=yCONFIG_RPS=yCONFIG_RFS_ACCEL=yCONFIG_SOCK_RX_QUEUE_MAPPING=yCONFIG_XPS=yCONFIG_CGROUP_NET_PRIO=yCONFIG_CGROUP_NET_CLASSID=yCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=yCONFIG_BPF_STREAM_PARSER=yCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#CONFIG_NET_PKTGEN=mCONFIG_NET_DROP_MONITOR=y
# end of Network testing # end of Networking options
# CONFIG_HAMRADIO is not setCONFIG_CAN=mCONFIG_CAN_RAW=mCONFIG_CAN_BCM=mCONFIG_CAN_GW=m
# CONFIG_CAN_J1939 is not set
# CONFIG_CAN_ISOTP is not set
#
# CAN Device Drivers
#CONFIG_CAN_VCAN=m
# CONFIG_CAN_VXCAN is not setCONFIG_CAN_SLCAN=mCONFIG_CAN_DEV=mCONFIG_CAN_CALC_BITTIMING=y
# CONFIG_CAN_KVASER_PCIEFD is not setCONFIG_CAN_C_CAN=mCONFIG_CAN_C_CAN_PLATFORM=mCONFIG_CAN_C_CAN_PCI=mCONFIG_CAN_CC770=m
# CONFIG_CAN_CC770_ISA is not setCONFIG_CAN_CC770_PLATFORM=m
# CONFIG_CAN_IFI_CANFD is not set
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_PEAK_PCIEFD is not setCONFIG_CAN_SJA1000=mCONFIG_CAN_EMS_PCI=m
# CONFIG_CAN_F81601 is not setCONFIG_CAN_KVASER_PCI=mCONFIG_CAN_PEAK_PCI=mCONFIG_CAN_PEAK_PCIEC=yCONFIG_CAN_PLX_PCI=m
# CONFIG_CAN_SJA1000_ISA is not setCONFIG_CAN_SJA1000_PLATFORM=mCONFIG_CAN_SOFTING=m
#
# CAN SPI interfaces
#
# CONFIG_CAN_HI311X is not set
# CONFIG_CAN_MCP251X is not set
# CONFIG_CAN_MCP251XFD is not set
# end of CAN SPI interfaces
#
# CAN USB interfaces
#
# CONFIG_CAN_8DEV_USB is not set
# CONFIG_CAN_EMS_USB is not set
# CONFIG_CAN_ESD_USB2 is not set
# CONFIG_CAN_ETAS_ES58X is not set
# CONFIG_CAN_GS_USB is not set
# CONFIG_CAN_KVASER_USB is not set
# CONFIG_CAN_MCBA_USB is not set
# CONFIG_CAN_PEAK_USB is not set
# CONFIG_CAN_UCAN is not set
# end of CAN USB interfaces
# CONFIG_CAN_DEBUG_DEVICES is not set
# end of CAN Device Drivers
CONFIG_BT=mCONFIG_BT_BREDR=yCONFIG_BT_RFCOMM=mCONFIG_BT_RFCOMM_TTY=yCONFIG_BT_BNEP=mCONFIG_BT_BNEP_MC_FILTER=yCONFIG_BT_BNEP_PROTO_FILTER=yCONFIG_BT_HIDP=mCONFIG_BT_HS=yCONFIG_BT_LE=y
# CONFIG_BT_6LOWPAN is not set
# CONFIG_BT_LEDS is not set
# CONFIG_BT_MSFTEXT is not set
# CONFIG_BT_AOSPEXT is not setCONFIG_BT_DEBUGFS=y
# CONFIG_BT_SELFTEST is not set
#
# Bluetooth device drivers
#
# CONFIG_BT_HCIBTUSB is not set
# CONFIG_BT_HCIBTSDIO is not setCONFIG_BT_HCIUART=mCONFIG_BT_HCIUART_H4=yCONFIG_BT_HCIUART_BCSP=yCONFIG_BT_HCIUART_ATH3K=y
# CONFIG_BT_HCIUART_INTEL is not set
# CONFIG_BT_HCIUART_AG6XX is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not setCONFIG_BT_HCIVHCI=mCONFIG_BT_MRVL=m
# CONFIG_BT_MRVL_SDIO is not set
# CONFIG_BT_MTKSDIO is not set
# CONFIG_BT_VIRTIO is not set
# end of Bluetooth device drivers
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not setCONFIG_STREAM_PARSER=y
# CONFIG_MCTP is not setCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not setCONFIG_CFG80211_REQUIRE_SIGNED_REGDB=yCONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=yCONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not setCONFIG_CFG80211_CRDA_SUPPORT=y
# CONFIG_CFG80211_WEXT is not setCONFIG_MAC80211=mCONFIG_MAC80211_HAS_RC=yCONFIG_MAC80211_RC_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not setCONFIG_MAC80211_LEDS=yCONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not setCONFIG_MAC80211_STA_HASH_MAX_SIZE=0CONFIG_RFKILL=mCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not setCONFIG_NET_9P=yCONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_DEBUG is not set
# CONFIG_CAIF is not setCONFIG_CEPH_LIB=m
# CONFIG_CEPH_LIB_PRETTYDEBUG is not setCONFIG_CEPH_LIB_USE_DNS_RESOLVER=yCONFIG_NFC=m
# CONFIG_NFC_DIGITAL is not setCONFIG_NFC_NCI=m
# CONFIG_NFC_NCI_SPI is not set
# CONFIG_NFC_NCI_UART is not set
# CONFIG_NFC_HCI is not set
#
# Near Field Communication (NFC) devices
#CONFIG_NFC_VIRTUAL_NCI=m
# CONFIG_NFC_FDP is not set
# CONFIG_NFC_PN533_USB is not set
# CONFIG_NFC_PN533_I2C is not set
# CONFIG_NFC_MRVL_USB is not set
# CONFIG_NFC_ST_NCI_I2C is not set
# CONFIG_NFC_ST_NCI_SPI is not set
# CONFIG_NFC_NXP_NCI is not set
# CONFIG_NFC_S3FWRN5_I2C is not set
# end of Near Field Communication (NFC) devices
CONFIG_PSAMPLE=mCONFIG_NET_IFE=mCONFIG_LWTUNNEL=yCONFIG_LWTUNNEL_BPF=yCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_SOCK_VALIDATE_XMIT=yCONFIG_NET_SELFTESTS=yCONFIG_NET_SOCK_MSG=yCONFIG_NET_DEVLINK=yCONFIG_FAILOVER=mCONFIG_ETHTOOL_NETLINK=y
#
# Device Drivers
#CONFIG_HAVE_EISA=y
# CONFIG_EISA is not setCONFIG_HAVE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=yCONFIG_PCIEPORTBUS=yCONFIG_HOTPLUG_PCI_PCIE=yCONFIG_PCIEAER=yCONFIG_PCIEAER_INJECT=mCONFIG_PCIE_ECRC=yCONFIG_PCIEASPM=yCONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not setCONFIG_PCIE_PME=yCONFIG_PCIE_DPC=y
# CONFIG_PCIE_PTM is not set
# CONFIG_PCIE_EDR is not setCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not setCONFIG_PCI_STUB=yCONFIG_PCI_PF_STUB=mCONFIG_PCI_ATS=yCONFIG_PCI_LOCKLESS_CONFIG=yCONFIG_PCI_IOV=yCONFIG_PCI_PRI=yCONFIG_PCI_PASID=y
# CONFIG_PCI_P2PDMA is not setCONFIG_PCI_LABEL=yCONFIG_PCI_HYPERV=m
# CONFIG_PCIE_BUS_TUNE_OFF is not setCONFIG_PCIE_BUS_DEFAULT=y
# CONFIG_PCIE_BUS_SAFE is not set
# CONFIG_PCIE_BUS_PERFORMANCE is not set
# CONFIG_PCIE_BUS_PEER2PEER is not setCONFIG_HOTPLUG_PCI=yCONFIG_HOTPLUG_PCI_ACPI=yCONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not setCONFIG_HOTPLUG_PCI_SHPC=y
#
# PCI controller drivers
#CONFIG_VMD=yCONFIG_PCI_HYPERV_INTERFACE=m
#
# DesignWare PCI Core Support
#
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCI_MESON is not set
# end of DesignWare PCI Core Support
#
# Mobiveil PCIe Core Support
#
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#
# end of Cadence PCIe controllers support # end of PCI controller drivers
#
# PCI Endpoint
#
# CONFIG_PCI_ENDPOINT is not set
# end of PCI Endpoint
#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers
# CONFIG_CXL_BUS is not set
# CONFIG_PCCARD is not set
# CONFIG_RAPIDIO is not set
#
# Generic Driver Options
#CONFIG_AUXILIARY_BUS=y
# CONFIG_UEVENT_HELPER is not setCONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=y CONFIG_FW_LOADER_PAGED_BUF=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set # CONFIG_FW_LOADER_COMPRESS is not set CONFIG_FW_CACHE=y
# end of Firmware loader
CONFIG_ALLOW_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not setCONFIG_GENERIC_CPU_AUTOPROBE=yCONFIG_GENERIC_CPU_VULNERABILITIES=yCONFIG_REGMAP=yCONFIG_REGMAP_I2C=mCONFIG_REGMAP_SPI=mCONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set
# end of Generic Driver Options
#
# Bus devices
#
# CONFIG_MHI_BUS is not set
# end of Bus devices
CONFIG_CONNECTOR=yCONFIG_PROC_EVENTS=y
#
# Firmware Drivers
#
#
# ARM System Control and Management Interface Protocol #
# end of ARM System Control and Management Interface Protocol
CONFIG_EDD=m
# CONFIG_EDD_OFF is not setCONFIG_FIRMWARE_MEMMAP=yCONFIG_DMIID=yCONFIG_DMI_SYSFS=yCONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
# CONFIG_ISCSI_IBFT is not setCONFIG_FW_CFG_SYSFS=y
# CONFIG_FW_CFG_SYSFS_CMDLINE is not setCONFIG_SYSFB=y
# CONFIG_SYSFB_SIMPLEFB is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# EFI (Extensible Firmware Interface) Support
#CONFIG_EFI_VARS=yCONFIG_EFI_ESRT=yCONFIG_EFI_VARS_PSTORE=yCONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=yCONFIG_EFI_RUNTIME_MAP=y
# CONFIG_EFI_FAKE_MEMMAP is not setCONFIG_EFI_RUNTIME_WRAPPERS=yCONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER=y
# CONFIG_EFI_BOOTLOADER_CONTROL is not set
# CONFIG_EFI_CAPSULE_LOADER is not set
# CONFIG_EFI_TEST is not setCONFIG_APPLE_PROPERTIES=y
# CONFIG_RESET_ATTACK_MITIGATION is not set
# CONFIG_EFI_RCI2_TABLE is not set
# CONFIG_EFI_DISABLE_PCI_DMA is not set
# end of EFI (Extensible Firmware Interface) Support
CONFIG_UEFI_CPER=yCONFIG_UEFI_CPER_X86=yCONFIG_EFI_DEV_PATH_PARSER=yCONFIG_EFI_EARLYCON=yCONFIG_EFI_CUSTOM_SSDT_OVERLAYS=y
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
# CONFIG_GNSS is not set
# CONFIG_MTD is not set
# CONFIG_OF is not setCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=mCONFIG_PARPORT_PC=mCONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AX88796 is not setCONFIG_PARPORT_1284=yCONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set
#
# Protocols
#CONFIG_PNPACPI=yCONFIG_BLK_DEV=yCONFIG_BLK_DEV_NULL_BLK=m
# CONFIG_BLK_DEV_FD is not setCONFIG_CDROM=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not setCONFIG_ZRAM=mCONFIG_ZRAM_DEF_COMP_LZORLE=y
# CONFIG_ZRAM_DEF_COMP_LZO is not setCONFIG_ZRAM_DEF_COMP="lzo-rle"CONFIG_ZRAM_WRITEBACK=y
# CONFIG_ZRAM_MEMORY_TRACKING is not setCONFIG_BLK_DEV_LOOP=mCONFIG_BLK_DEV_LOOP_MIN_COUNT=0
# CONFIG_BLK_DEV_DRBD is not setCONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not setCONFIG_BLK_DEV_RAM=mCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=16384CONFIG_CDROM_PKTCDVD=mCONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not setCONFIG_VIRTIO_BLK=mCONFIG_BLK_DEV_RBD=m
# CONFIG_BLK_DEV_RSXX is not set
#
# NVME Support
#CONFIG_NVME_CORE=mCONFIG_BLK_DEV_NVME=mCONFIG_NVME_MULTIPATH=y
# CONFIG_NVME_HWMON is not setCONFIG_NVME_FABRICS=mCONFIG_NVME_FC=m
# CONFIG_NVME_TCP is not setCONFIG_NVME_TARGET=m
# CONFIG_NVME_TARGET_PASSTHRU is not setCONFIG_NVME_TARGET_LOOP=mCONFIG_NVME_TARGET_FC=mCONFIG_NVME_TARGET_FCLOOP=m
# CONFIG_NVME_TARGET_TCP is not set
# end of NVME Support
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=m
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not setCONFIG_TIFM_CORE=mCONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not setCONFIG_ENCLOSURE_SERVICES=mCONFIG_SGI_XP=mCONFIG_HP_ILO=mCONFIG_SGI_GRU=m
# CONFIG_SGI_GRU_DEBUG is not setCONFIG_APDS9802ALS=mCONFIG_ISL29003=mCONFIG_ISL29020=mCONFIG_SENSORS_TSL2550=mCONFIG_SENSORS_BH1770=mCONFIG_SENSORS_APDS990X=m
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not setCONFIG_VMWARE_BALLOON=m
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_DW_XDATA_PCIE is not set
# CONFIG_PCI_ENDPOINT_TEST is not set
# CONFIG_XILINX_SDFEC is not setCONFIG_MISC_RTSX=m
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not setCONFIG_EEPROM_LEGACY=mCONFIG_EEPROM_MAX6875=mCONFIG_EEPROM_93CX6=m
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not setCONFIG_CB710_DEBUG_ASSUMPTIONS=y
#
# Texas Instruments shared transport line discipline #
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
CONFIG_SENSORS_LIS3_I2C=mCONFIG_ALTERA_STAPL=mCONFIG_INTEL_MEI=mCONFIG_INTEL_MEI_ME=m
# CONFIG_INTEL_MEI_TXE is not set
# CONFIG_INTEL_MEI_HDCP is not set
# CONFIG_INTEL_MEI_PXP is not setCONFIG_VMWARE_VMCI=m
# CONFIG_GENWQE is not set
# CONFIG_ECHO is not set
# CONFIG_BCM_VK is not set
# CONFIG_MISC_ALCOR_PCI is not setCONFIG_MISC_RTSX_PCI=m
# CONFIG_MISC_RTSX_USB is not set
# CONFIG_HABANA_AI is not set
# CONFIG_UACCE is not setCONFIG_PVPANIC=y
# CONFIG_PVPANIC_MMIO is not set
# CONFIG_PVPANIC_PCI is not set
# end of Misc devices
#
# SCSI device support
#CONFIG_SCSI_MOD=yCONFIG_RAID_ATTRS=mCONFIG_SCSI_COMMON=yCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=mCONFIG_CHR_DEV_ST=mCONFIG_BLK_DEV_SR=mCONFIG_CHR_DEV_SG=mCONFIG_BLK_DEV_BSG=yCONFIG_CHR_DEV_SCH=mCONFIG_SCSI_ENCLOSURE=mCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_LOGGING=yCONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=mCONFIG_SCSI_FC_ATTRS=mCONFIG_SCSI_ISCSI_ATTRS=mCONFIG_SCSI_SAS_ATTRS=mCONFIG_SCSI_SAS_LIBSAS=mCONFIG_SCSI_SAS_ATA=yCONFIG_SCSI_SAS_HOST_SMP=yCONFIG_SCSI_SRP_ATTRS=m
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not setCONFIG_SCSI_MPT3SAS=mCONFIG_SCSI_MPT2SAS_MAX_SGE=128CONFIG_SCSI_MPT3SAS_MAX_SGE=128
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_MPI3MR is not set
# CONFIG_SCSI_SMARTPQI is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_UFS_HWMON is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not set
# CONFIG_VMWARE_PVSCSI is not setCONFIG_HYPERV_STORAGE=m
# CONFIG_LIBFC is not set
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FDOMAIN_PCI is not setCONFIG_SCSI_ISCI=m
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_EFCT is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_WD719X is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_BFA_FC is not set
# CONFIG_SCSI_VIRTIO is not set
# CONFIG_SCSI_CHELSIO_FCOE is not setCONFIG_SCSI_DH=yCONFIG_SCSI_DH_RDAC=yCONFIG_SCSI_DH_HP_SW=yCONFIG_SCSI_DH_EMC=yCONFIG_SCSI_DH_ALUA=y
# end of SCSI device support
CONFIG_ATA=mCONFIG_SATA_HOST=yCONFIG_PATA_TIMINGS=yCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_FORCE=yCONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not setCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=mCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=m
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not setCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not setCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=m
# CONFIG_SATA_DWC is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set CONFIG_ATA_GENERIC=m
# CONFIG_PATA_LEGACY is not set CONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=mCONFIG_MD_RAID0=mCONFIG_MD_RAID1=mCONFIG_MD_RAID10=mCONFIG_MD_RAID456=m
# CONFIG_MD_MULTIPATH is not set CONFIG_MD_FAULTY=mCONFIG_MD_CLUSTER=m
# CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=mCONFIG_DM_DEBUG=yCONFIG_DM_BUFIO=m
# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set CONFIG_DM_BIO_PRISON=m CONFIG_DM_PERSISTENT_DATA=m
# CONFIG_DM_UNSTRIPED is not set CONFIG_DM_CRYPT=mCONFIG_DM_SNAPSHOT=m CONFIG_DM_THIN_PROVISIONING=m CONFIG_DM_CACHE=mCONFIG_DM_CACHE_SMQ=m CONFIG_DM_WRITECACHE=m
# CONFIG_DM_EBS is not setCONFIG_DM_ERA=m
# CONFIG_DM_CLONE is not set CONFIG_DM_MIRROR=m CONFIG_DM_LOG_USERSPACE=mCONFIG_DM_RAID=mCONFIG_DM_ZERO=mCONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=m
# CONFIG_DM_MULTIPATH_HST is not set
# CONFIG_DM_MULTIPATH_IOA is not set CONFIG_DM_DELAY=m
# CONFIG_DM_DUST is not set CONFIG_DM_UEVENT=yCONFIG_DM_FLAKEY=mCONFIG_DM_VERITY=m
# CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG is not set # CONFIG_DM_VERITY_FEC is not set CONFIG_DM_SWITCH=mCONFIG_DM_LOG_WRITES=m CONFIG_DM_INTEGRITY=mCONFIG_DM_AUDIT=yCONFIG_TARGET_CORE=mCONFIG_TCM_IBLOCK=mCONFIG_TCM_FILEIO=mCONFIG_TCM_PSCSI=mCONFIG_TCM_USER2=m CONFIG_LOOPBACK_TARGET=m CONFIG_ISCSI_TARGET=m
# CONFIG_SBP_TARGET is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=mCONFIG_FIREWIRE_OHCI=mCONFIG_FIREWIRE_SBP2=mCONFIG_FIREWIRE_NET=m
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support
CONFIG_MACINTOSH_DRIVERS=yCONFIG_MAC_EMUMOUSEBTN=yCONFIG_NETDEVICES=yCONFIG_MII=yCONFIG_NET_CORE=y
# CONFIG_BONDING is not setCONFIG_DUMMY=y
# CONFIG_WIREGUARD is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_FC is not setCONFIG_IFB=m
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_IPVLAN is not setCONFIG_VXLAN=yCONFIG_GENEVE=yCONFIG_BAREUDP=m
# CONFIG_GTP is not set
# CONFIG_AMT is not setCONFIG_MACSEC=yCONFIG_NETCONSOLE=mCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=yCONFIG_NET_POLL_CONTROLLER=yCONFIG_TUN=m
# CONFIG_TUN_VNET_CROSS_LE is not setCONFIG_VETH=yCONFIG_VIRTIO_NET=m
# CONFIG_NLMON is not setCONFIG_NET_VRF=y
# CONFIG_VSOCKMON is not set
# CONFIG_ARCNET is not setCONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
# CONFIG_ATM_TCP is not set
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
# CONFIG_ATM_FIRESTREAM is not set
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_NICSTAR is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
# CONFIG_ATM_FORE200E is not set
# CONFIG_ATM_HE is not set
# CONFIG_ATM_SOLOS is not setCONFIG_ETHERNET=yCONFIG_MDIO=y
# CONFIG_NET_VENDOR_3COM is not setCONFIG_NET_VENDOR_ADAPTEC=y
# CONFIG_ADAPTEC_STARFIRE is not setCONFIG_NET_VENDOR_AGERE=y
# CONFIG_ET131X is not setCONFIG_NET_VENDOR_ALACRITECH=y
# CONFIG_SLICOSS is not setCONFIG_NET_VENDOR_ALTEON=y
# CONFIG_ACENIC is not set
# CONFIG_ALTERA_TSE is not setCONFIG_NET_VENDOR_AMAZON=y
# CONFIG_ENA_ETHERNET is not setCONFIG_NET_VENDOR_AMD=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_PCNET32 is not set
# CONFIG_AMD_XGBE is not setCONFIG_NET_VENDOR_AQUANTIA=y
# CONFIG_AQTION is not setCONFIG_NET_VENDOR_ARC=yCONFIG_NET_VENDOR_ASIX=y
# CONFIG_SPI_AX88796C is not setCONFIG_NET_VENDOR_ATHEROS=y
# CONFIG_ATL2 is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_ALX is not setCONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BCMGENET is not set
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2X is not set
# CONFIG_SYSTEMPORT is not set
# CONFIG_BNXT is not setCONFIG_NET_VENDOR_BROCADE=y
# CONFIG_BNA is not setCONFIG_NET_VENDOR_CADENCE=y
# CONFIG_MACB is not setCONFIG_NET_VENDOR_CAVIUM=y
# CONFIG_THUNDER_NIC_PF is not set
# CONFIG_THUNDER_NIC_VF is not set
# CONFIG_THUNDER_NIC_BGX is not set
# CONFIG_THUNDER_NIC_RGX is not setCONFIG_CAVIUM_PTP=y
# CONFIG_LIQUIDIO is not set
# CONFIG_LIQUIDIO_VF is not setCONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_CHELSIO_T4 is not set
# CONFIG_CHELSIO_T4VF is not setCONFIG_NET_VENDOR_CISCO=y
# CONFIG_ENIC is not setCONFIG_NET_VENDOR_CORTINA=y
# CONFIG_CX_ECAT is not set
# CONFIG_DNET is not setCONFIG_NET_VENDOR_DEC=y
# CONFIG_NET_TULIP is not setCONFIG_NET_VENDOR_DLINK=y
# CONFIG_DL2K is not set
# CONFIG_SUNDANCE is not setCONFIG_NET_VENDOR_EMULEX=y
# CONFIG_BE2NET is not setCONFIG_NET_VENDOR_EZCHIP=yCONFIG_NET_VENDOR_GOOGLE=y
# CONFIG_GVE is not setCONFIG_NET_VENDOR_HUAWEI=y
# CONFIG_HINIC is not setCONFIG_NET_VENDOR_I825XX=yCONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not setCONFIG_E1000=yCONFIG_E1000E=yCONFIG_E1000E_HWTS=yCONFIG_IGB=yCONFIG_IGB_HWMON=y
# CONFIG_IGBVF is not set
# CONFIG_IXGB is not setCONFIG_IXGBE=yCONFIG_IXGBE_HWMON=y
# CONFIG_IXGBE_DCB is not setCONFIG_IXGBE_IPSEC=y
# CONFIG_IXGBEVF is not setCONFIG_I40E=y
# CONFIG_I40E_DCB is not set
# CONFIG_I40EVF is not set
# CONFIG_ICE is not set
# CONFIG_FM10K is not setCONFIG_IGC=yCONFIG_NET_VENDOR_MICROSOFT=y
# CONFIG_MICROSOFT_MANA is not set
# CONFIG_JME is not setCONFIG_NET_VENDOR_LITEX=yCONFIG_NET_VENDOR_MARVELL=y
# CONFIG_MVMDIO is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_PRESTERA is not setCONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLX4_EN is not set
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not setCONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8842 is not set
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not set
# CONFIG_KSZ884X_PCI is not setCONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_ENC28J60 is not set
# CONFIG_ENCX24J600 is not set
# CONFIG_LAN743X is not setCONFIG_NET_VENDOR_MICROSEMI=yCONFIG_NET_VENDOR_MYRI=y
# CONFIG_MYRI10GE is not set
# CONFIG_FEALNX is not setCONFIG_NET_VENDOR_NATSEMI=y
# CONFIG_NATSEMI is not set
# CONFIG_NS83820 is not setCONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not setCONFIG_NET_VENDOR_NETRONOME=y
# CONFIG_NFP is not setCONFIG_NET_VENDOR_NI=y
# CONFIG_NI_XGE_MANAGEMENT_ENET is not setCONFIG_NET_VENDOR_8390=y
# CONFIG_NE2K_PCI is not setCONFIG_NET_VENDOR_NVIDIA=y
# CONFIG_FORCEDETH is not setCONFIG_NET_VENDOR_OKI=y
# CONFIG_ETHOC is not setCONFIG_NET_VENDOR_PACKET_ENGINES=y
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not setCONFIG_NET_VENDOR_PENSANDO=y
# CONFIG_IONIC is not setCONFIG_NET_VENDOR_QLOGIC=y
# CONFIG_QLA3XXX is not set
# CONFIG_QLCNIC is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_QED is not setCONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not setCONFIG_NET_VENDOR_RDC=y
# CONFIG_R6040 is not setCONFIG_NET_VENDOR_REALTEK=y
# CONFIG_ATP is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not setCONFIG_R8169=yCONFIG_NET_VENDOR_RENESAS=yCONFIG_NET_VENDOR_ROCKER=y
# CONFIG_ROCKER is not setCONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not setCONFIG_NET_VENDOR_SEEQ=yCONFIG_NET_VENDOR_SOLARFLARE=y
# CONFIG_SFC is not set
# CONFIG_SFC_FALCON is not setCONFIG_NET_VENDOR_SILAN=y
# CONFIG_SC92031 is not setCONFIG_NET_VENDOR_SIS=y
# CONFIG_SIS900 is not set
# CONFIG_SIS190 is not setCONFIG_NET_VENDOR_SMSC=y
# CONFIG_EPIC100 is not set
# CONFIG_SMSC911X is not set
# CONFIG_SMSC9420 is not setCONFIG_NET_VENDOR_SOCIONEXT=yCONFIG_NET_VENDOR_STMICRO=y
# CONFIG_STMMAC_ETH is not setCONFIG_NET_VENDOR_SUN=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NIU is not setCONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not setCONFIG_NET_VENDOR_TEHUTI=y
# CONFIG_TEHUTI is not setCONFIG_NET_VENDOR_TI=y
# CONFIG_TI_CPSW_PHY_SEL is not set
# CONFIG_TLAN is not setCONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not setCONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not setCONFIG_NET_VENDOR_XILINX=y
# CONFIG_XILINX_EMACLITE is not set
# CONFIG_XILINX_AXI_EMAC is not set
# CONFIG_XILINX_LL_TEMAC is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not setCONFIG_PHYLIB=yCONFIG_SWPHY=y
# CONFIG_LED_TRIGGER_PHY is not setCONFIG_FIXED_PHY=y
#
# MII PHY device drivers
#
# CONFIG_AMD_PHY is not set
# CONFIG_ADIN_PHY is not set
# CONFIG_AQUANTIA_PHY is not setCONFIG_AX88796B_PHY=y
# CONFIG_BROADCOM_PHY is not set
# CONFIG_BCM54140_PHY is not set
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM84881_PHY is not set
# CONFIG_BCM87XX_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_CORTINA_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_INTEL_XWAY_PHY is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MARVELL_PHY is not set
# CONFIG_MARVELL_10G_PHY is not set
# CONFIG_MARVELL_88X2222_PHY is not set
# CONFIG_MAXLINEAR_GPHY is not set
# CONFIG_MEDIATEK_GE_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not set
# CONFIG_MOTORCOMM_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_NXP_C45_TJA11XX_PHY is not set
# CONFIG_NXP_TJA11XX_PHY is not set
# CONFIG_QSEMI_PHY is not setCONFIG_REALTEK_PHY=y
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_TERANETICS_PHY is not set
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not set
# CONFIG_DP83869_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not setCONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=yCONFIG_FWNODE_MDIO=yCONFIG_ACPI_MDIO=yCONFIG_MDIO_DEVRES=y
# CONFIG_MDIO_BITBANG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_MVUSB is not set
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_THUNDER is not set
#
# MDIO Multiplexers
#
#
# PCS device drivers
#
# CONFIG_PCS_XPCS is not set
# end of PCS device drivers
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not setCONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not setCONFIG_USB_RTL8152=y
# CONFIG_USB_LAN78XX is not setCONFIG_USB_USBNET=yCONFIG_USB_NET_AX8817X=yCONFIG_USB_NET_AX88179_178A=y
# CONFIG_USB_NET_CDCETHER is not set
# CONFIG_USB_NET_CDC_EEM is not set
# CONFIG_USB_NET_CDC_NCM is not set
# CONFIG_USB_NET_HUAWEI_CDC_NCM is not set
# CONFIG_USB_NET_CDC_MBIM is not set
# CONFIG_USB_NET_DM9601 is not set
# CONFIG_USB_NET_SR9700 is not set
# CONFIG_USB_NET_SR9800 is not set
# CONFIG_USB_NET_SMSC75XX is not set
# CONFIG_USB_NET_SMSC95XX is not set
# CONFIG_USB_NET_GL620A is not set
# CONFIG_USB_NET_NET1080 is not set
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
# CONFIG_USB_NET_CDC_SUBSET is not set
# CONFIG_USB_NET_ZAURUS is not set
# CONFIG_USB_NET_CX82310_ETH is not set
# CONFIG_USB_NET_KALMIA is not set
# CONFIG_USB_NET_QMI_WWAN is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_NET_INT51X1 is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_USB_SIERRA_NET is not set
# CONFIG_USB_NET_CH9200 is not set
# CONFIG_USB_NET_AQC111 is not setCONFIG_WLAN=yCONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not setCONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not set
# CONFIG_ATH9K is not set
# CONFIG_ATH9K_HTC is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_WIL6210 is not set
# CONFIG_ATH10K is not set
# CONFIG_WCN36XX is not set
# CONFIG_ATH11K is not setCONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not setCONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_BRCMSMAC is not set
# CONFIG_BRCMFMAC is not setCONFIG_WLAN_VENDOR_CISCO=y
# CONFIG_AIRO is not setCONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_IWLWIFI is not setCONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not setCONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_MWIFIEX is not set
# CONFIG_MWL8K is not set
# CONFIG_WLAN_VENDOR_MEDIATEK is not setCONFIG_WLAN_VENDOR_MICROCHIP=y
# CONFIG_WILC1000_SDIO is not set
# CONFIG_WILC1000_SPI is not setCONFIG_WLAN_VENDOR_RALINK=y
# CONFIG_RT2X00 is not setCONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not setCONFIG_RTL_CARDS=m
# CONFIG_RTL8192CE is not set
# CONFIG_RTL8192SE is not set
# CONFIG_RTL8192DE is not set
# CONFIG_RTL8723AE is not set
# CONFIG_RTL8723BE is not set
# CONFIG_RTL8188EE is not set
# CONFIG_RTL8192EE is not set
# CONFIG_RTL8821AE is not set
# CONFIG_RTL8192CU is not set
# CONFIG_RTL8XXXU is not set
# CONFIG_RTW88 is not set
# CONFIG_RTW89 is not setCONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not setCONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not setCONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not setCONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not setCONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_QTNFMAC_PCIE is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_VIRT_WIFI is not set
# CONFIG_WAN is not setCONFIG_IEEE802154_DRIVERS=m
# CONFIG_IEEE802154_FAKELB is not set
# CONFIG_IEEE802154_AT86RF230 is not set
# CONFIG_IEEE802154_MRF24J40 is not set
# CONFIG_IEEE802154_CC2520 is not set
# CONFIG_IEEE802154_ATUSB is not set
# CONFIG_IEEE802154_ADF7242 is not set
# CONFIG_IEEE802154_CA8210 is not set
# CONFIG_IEEE802154_MCR20A is not set
# CONFIG_IEEE802154_HWSIM is not set
#
# Wireless WAN
#
# CONFIG_WWAN is not set
# end of Wireless WAN
# CONFIG_VMXNET3 is not set
# CONFIG_FUJITSU_ES is not set
# CONFIG_HYPERV_NET is not setCONFIG_NETDEVSIM=mCONFIG_NET_FAILOVER=m
# CONFIG_ISDN is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=mCONFIG_INPUT_SPARSEKMAP=m
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not setCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=mCONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
# CONFIG_KEYBOARD_APPLESPI is not setCONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_XTKBD is not setCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_BYD=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=yCONFIG_MOUSE_PS2_CYPRESS=yCONFIG_MOUSE_PS2_LIFEBOOK=yCONFIG_MOUSE_PS2_TRACKPOINT=yCONFIG_MOUSE_PS2_ELANTECH=yCONFIG_MOUSE_PS2_ELANTECH_SMBUS=yCONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not setCONFIG_MOUSE_PS2_FOCALTECH=yCONFIG_MOUSE_PS2_VMMOUSE=yCONFIG_MOUSE_PS2_SMBUS=yCONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not setCONFIG_MOUSE_CYAPA=mCONFIG_MOUSE_ELAN_I2C=mCONFIG_MOUSE_ELAN_I2C_I2C=yCONFIG_MOUSE_ELAN_I2C_SMBUS=yCONFIG_MOUSE_VSXXXAA=m
# CONFIG_MOUSE_GPIO is not setCONFIG_MOUSE_SYNAPTICS_I2C=m
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not setCONFIG_RMI4_CORE=mCONFIG_RMI4_I2C=mCONFIG_RMI4_SPI=mCONFIG_RMI4_SMB=mCONFIG_RMI4_F03=yCONFIG_RMI4_F03_SERIO=mCONFIG_RMI4_2D_SENSOR=yCONFIG_RMI4_F11=yCONFIG_RMI4_F12=yCONFIG_RMI4_F30=yCONFIG_RMI4_F34=y
# CONFIG_RMI4_F3A is not set
# CONFIG_RMI4_F54 is not setCONFIG_RMI4_F55=y
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_ARCH_MIGHT_HAVE_PC_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=yCONFIG_SERIO_RAW=mCONFIG_SERIO_ALTERA_PS2=m
# CONFIG_SERIO_PS2MULT is not setCONFIG_SERIO_ARC_PS2=mCONFIG_HYPERV_KEYBOARD=m
# CONFIG_SERIO_GPIO_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_VT_CONSOLE_SLEEP=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not setCONFIG_LDISC_AUTOLOAD=y
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=y CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_16550A_VARIANTS is not set # CONFIG_SERIAL_8250_FINTEK is not set CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_DMA=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_EXAR=y CONFIG_SERIAL_8250_NR_UARTS=64 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_8250_DWLIB=y CONFIG_SERIAL_8250_DW=y
# CONFIG_SERIAL_8250_RT288X is not set CONFIG_SERIAL_8250_LPSS=y CONFIG_SERIAL_8250_MID=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not setCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_SERIAL_JSM=m
# CONFIG_SERIAL_LANTIQ is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_BCM63XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not setCONFIG_SERIAL_ARC=mCONFIG_SERIAL_ARC_NR_PORTS=1
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_SPRD is not set
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=yCONFIG_SERIAL_NONSTANDARD=y
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not setCONFIG_SYNCLINK_GT=mCONFIG_N_HDLC=mCONFIG_N_GSM=mCONFIG_NOZOMI=m
# CONFIG_NULL_TTY is not setCONFIG_HVC_DRIVER=y
# CONFIG_SERIAL_DEV_BUS is not set
# CONFIG_TTY_PRINTK is not setCONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not setCONFIG_PPDEV=mCONFIG_VIRTIO_CONSOLE=mCONFIG_IPMI_HANDLER=mCONFIG_IPMI_DMI_DECODE=yCONFIG_IPMI_PLAT_DATA=yCONFIG_IPMI_PANIC_EVENT=yCONFIG_IPMI_PANIC_STRING=yCONFIG_IPMI_DEVICE_INTERFACE=mCONFIG_IPMI_SI=mCONFIG_IPMI_SSIF=mCONFIG_IPMI_WATCHDOG=mCONFIG_IPMI_POWEROFF=mCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_TIMERIOMEM=mCONFIG_HW_RANDOM_INTEL=mCONFIG_HW_RANDOM_AMD=m
# CONFIG_HW_RANDOM_BA431 is not setCONFIG_HW_RANDOM_VIA=mCONFIG_HW_RANDOM_VIRTIO=y
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not setCONFIG_DEVMEM=yCONFIG_NVRAM=yCONFIG_DEVPORT=yCONFIG_HPET=yCONFIG_HPET_MMAP=y
# CONFIG_HPET_MMAP_DEFAULT is not setCONFIG_HANGCHECK_TIMER=mCONFIG_UV_MMTIMER=mCONFIG_TCG_TPM=yCONFIG_HW_RANDOM_TPM=yCONFIG_TCG_TIS_CORE=yCONFIG_TCG_TIS=y
# CONFIG_TCG_TIS_SPI is not set
# CONFIG_TCG_TIS_I2C_CR50 is not setCONFIG_TCG_TIS_I2C_ATMEL=mCONFIG_TCG_TIS_I2C_INFINEON=mCONFIG_TCG_TIS_I2C_NUVOTON=mCONFIG_TCG_NSC=mCONFIG_TCG_ATMEL=mCONFIG_TCG_INFINEON=mCONFIG_TCG_CRB=y
# CONFIG_TCG_VTPM_PROXY is not setCONFIG_TCG_TIS_ST33ZP24=mCONFIG_TCG_TIS_ST33ZP24_I2C=m
# CONFIG_TCG_TIS_ST33ZP24_SPI is not setCONFIG_TELCLOCK=m
# CONFIG_XILLYBUS is not set
# CONFIG_XILLYUSB is not set
# CONFIG_RANDOM_TRUST_CPU is not set
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
# end of Character devices
#
# I2C support
#CONFIG_I2C=yCONFIG_ACPI_I2C_OPREGION=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=yCONFIG_I2C_CHARDEV=mCONFIG_I2C_MUX=m
#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_REG is not setCONFIG_I2C_MUX_MLXCPLD=m
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=mCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not setCONFIG_I2C_AMD756=mCONFIG_I2C_AMD756_S4882=mCONFIG_I2C_AMD8111=m
# CONFIG_I2C_AMD_MP2 is not setCONFIG_I2C_I801=mCONFIG_I2C_ISCH=mCONFIG_I2C_ISMT=mCONFIG_I2C_PIIX4=mCONFIG_I2C_NFORCE2=mCONFIG_I2C_NFORCE2_S4985=m
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not setCONFIG_I2C_SIS96X=mCONFIG_I2C_VIA=mCONFIG_I2C_VIAPRO=m
#
# ACPI drivers
#CONFIG_I2C_SCMI=m
#
# I2C system bus drivers (mostly embedded / system-on-chip) #
# CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DESIGNWARE_CORE=m
# CONFIG_I2C_DESIGNWARE_SLAVE is not set CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_DESIGNWARE_BAYTRAIL=y
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set CONFIG_I2C_PCA_PLATFORM=mCONFIG_I2C_SIMTEC=m
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_CP2615 is not setCONFIG_I2C_PARPORT=m
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#CONFIG_I2C_MLXCPLD=m
# CONFIG_I2C_VIRTIO is not set
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=m
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not setCONFIG_SPI=y
# CONFIG_SPI_DEBUG is not setCONFIG_SPI_MASTER=y
# CONFIG_SPI_MEM is not set
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_NXP_FLEXSPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_LANTIQ_SSC is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
# CONFIG_SPI_AMD is not set
#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not setCONFIG_SPI_DYNAMIC=y
# CONFIG_SPMI is not set
# CONFIG_HSI is not setCONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not setCONFIG_PPS_CLIENT_LDISC=mCONFIG_PPS_CLIENT_PARPORT=mCONFIG_PPS_CLIENT_GPIO=m
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK=yCONFIG_PTP_1588_CLOCK_OPTIONAL=y
# CONFIG_DP83640_PHY is not set
# CONFIG_PTP_1588_CLOCK_INES is not setCONFIG_PTP_1588_CLOCK_KVM=m
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
# CONFIG_PTP_1588_CLOCK_VMW is not set
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_PINMUX=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not setCONFIG_PINCTRL_AMD=m
# CONFIG_PINCTRL_MCP23S08 is not set
# CONFIG_PINCTRL_SX150X is not set
#
# Intel pinctrl drivers
#CONFIG_PINCTRL_BAYTRAIL=y
# CONFIG_PINCTRL_CHERRYVIEW is not set
# CONFIG_PINCTRL_LYNXPOINT is not setCONFIG_PINCTRL_INTEL=y
# CONFIG_PINCTRL_ALDERLAKE is not setCONFIG_PINCTRL_BROXTON=mCONFIG_PINCTRL_CANNONLAKE=mCONFIG_PINCTRL_CEDARFORK=mCONFIG_PINCTRL_DENVERTON=m
# CONFIG_PINCTRL_ELKHARTLAKE is not set
# CONFIG_PINCTRL_EMMITSBURG is not setCONFIG_PINCTRL_GEMINILAKE=m
# CONFIG_PINCTRL_ICELAKE is not set
# CONFIG_PINCTRL_JASPERLAKE is not set
# CONFIG_PINCTRL_LAKEFIELD is not setCONFIG_PINCTRL_LEWISBURG=mCONFIG_PINCTRL_SUNRISEPOINT=m
# CONFIG_PINCTRL_TIGERLAKE is not set
# end of Intel pinctrl drivers
#
# Renesas pinctrl drivers
#
# end of Renesas pinctrl drivers
CONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_GPIO_ACPI=yCONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not setCONFIG_GPIO_SYSFS=yCONFIG_GPIO_CDEV=yCONFIG_GPIO_CDEV_V1=yCONFIG_GPIO_GENERIC=m
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_AMDPT=m
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_EXAR is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not setCONFIG_GPIO_ICH=m
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_VX855 is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# Port-mapped I/O GPIO drivers
#
# CONFIG_GPIO_F7188X is not set
# CONFIG_GPIO_IT87 is not set
# CONFIG_GPIO_SCH is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_WINBOND is not set
# CONFIG_GPIO_WS16C48 is not set
# end of Port-mapped I/O GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCA9570 is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders
#
# USB GPIO expanders
#
# end of USB GPIO expanders
#
# Virtual GPIO drivers
#
# CONFIG_GPIO_AGGREGATOR is not setCONFIG_GPIO_MOCKUP=m
# CONFIG_GPIO_VIRTIO is not set
# end of Virtual GPIO drivers
# CONFIG_W1 is not setCONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_RESTART is not setCONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not setCONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_CW2015 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_LTC4162L is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ2515X is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_BQ25980 is not set
# CONFIG_CHARGER_BQ256XX is not set
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_BATTERY_GOLDFISH is not set
# CONFIG_BATTERY_RT5033 is not set
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_BD99954 is not setCONFIG_HWMON=yCONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#CONFIG_SENSORS_ABITUGURU=mCONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not setCONFIG_SENSORS_AD7414=mCONFIG_SENSORS_AD7418=mCONFIG_SENSORS_ADM1021=mCONFIG_SENSORS_ADM1025=mCONFIG_SENSORS_ADM1026=mCONFIG_SENSORS_ADM1029=mCONFIG_SENSORS_ADM1031=m
# CONFIG_SENSORS_ADM1177 is not setCONFIG_SENSORS_ADM9240=mCONFIG_SENSORS_ADT7X10=m
# CONFIG_SENSORS_ADT7310 is not setCONFIG_SENSORS_ADT7410=mCONFIG_SENSORS_ADT7411=mCONFIG_SENSORS_ADT7462=mCONFIG_SENSORS_ADT7470=mCONFIG_SENSORS_ADT7475=m
# CONFIG_SENSORS_AHT10 is not set
# CONFIG_SENSORS_AQUACOMPUTER_D5NEXT is not set
# CONFIG_SENSORS_AS370 is not setCONFIG_SENSORS_ASC7621=m
# CONFIG_SENSORS_AXI_FAN_CONTROL is not setCONFIG_SENSORS_K8TEMP=mCONFIG_SENSORS_K10TEMP=mCONFIG_SENSORS_FAM15H_POWER=mCONFIG_SENSORS_APPLESMC=mCONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ASPEED is not setCONFIG_SENSORS_ATXP1=m
# CONFIG_SENSORS_CORSAIR_CPRO is not set
# CONFIG_SENSORS_CORSAIR_PSU is not set
# CONFIG_SENSORS_DRIVETEMP is not setCONFIG_SENSORS_DS620=mCONFIG_SENSORS_DS1621=mCONFIG_SENSORS_DELL_SMM=mCONFIG_SENSORS_I5K_AMB=mCONFIG_SENSORS_F71805F=mCONFIG_SENSORS_F71882FG=mCONFIG_SENSORS_F75375S=mCONFIG_SENSORS_FSCHMD=m
# CONFIG_SENSORS_FTSTEUTATES is not setCONFIG_SENSORS_GL518SM=mCONFIG_SENSORS_GL520SM=mCONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_HIH6130 is not setCONFIG_SENSORS_IBMAEM=mCONFIG_SENSORS_IBMPEX=mCONFIG_SENSORS_I5500=mCONFIG_SENSORS_CORETEMP=mCONFIG_SENSORS_IT87=mCONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not setCONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2947_SPI is not set
# CONFIG_SENSORS_LTC2990 is not set
# CONFIG_SENSORS_LTC2992 is not setCONFIG_SENSORS_LTC4151=mCONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not setCONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not setCONFIG_SENSORS_LTC4261=m
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX127 is not setCONFIG_SENSORS_MAX16065=mCONFIG_SENSORS_MAX1619=mCONFIG_SENSORS_MAX1668=mCONFIG_SENSORS_MAX197=m
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX31730 is not set
# CONFIG_SENSORS_MAX6620 is not set
# CONFIG_SENSORS_MAX6621 is not setCONFIG_SENSORS_MAX6639=mCONFIG_SENSORS_MAX6642=mCONFIG_SENSORS_MAX6650=mCONFIG_SENSORS_MAX6697=m
# CONFIG_SENSORS_MAX31790 is not setCONFIG_SENSORS_MCP3021=m
# CONFIG_SENSORS_MLXREG_FAN is not set
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_TPS23861 is not set
# CONFIG_SENSORS_MR75203 is not set
# CONFIG_SENSORS_ADCXX is not setCONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not setCONFIG_SENSORS_LM73=mCONFIG_SENSORS_LM75=mCONFIG_SENSORS_LM77=mCONFIG_SENSORS_LM78=mCONFIG_SENSORS_LM80=mCONFIG_SENSORS_LM83=mCONFIG_SENSORS_LM85=mCONFIG_SENSORS_LM87=mCONFIG_SENSORS_LM90=mCONFIG_SENSORS_LM92=mCONFIG_SENSORS_LM93=mCONFIG_SENSORS_LM95234=mCONFIG_SENSORS_LM95241=mCONFIG_SENSORS_LM95245=mCONFIG_SENSORS_PC87360=mCONFIG_SENSORS_PC87427=mCONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not setCONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not set
# CONFIG_SENSORS_NZXT_KRAKEN2 is not setCONFIG_SENSORS_PCF8591=mCONFIG_PMBUS=mCONFIG_SENSORS_PMBUS=m
# CONFIG_SENSORS_ADM1266 is not setCONFIG_SENSORS_ADM1275=m
# CONFIG_SENSORS_BEL_PFE is not set
# CONFIG_SENSORS_BPA_RS600 is not set
# CONFIG_SENSORS_FSP_3Y is not set
# CONFIG_SENSORS_IBM_CFFPS is not set
# CONFIG_SENSORS_DPS920AB is not set
# CONFIG_SENSORS_INSPUR_IPSPS is not set
# CONFIG_SENSORS_IR35221 is not set
# CONFIG_SENSORS_IR36021 is not set
# CONFIG_SENSORS_IR38064 is not set
# CONFIG_SENSORS_IRPS5401 is not set
# CONFIG_SENSORS_ISL68137 is not setCONFIG_SENSORS_LM25066=mCONFIG_SENSORS_LTC2978=m
# CONFIG_SENSORS_LTC3815 is not set
# CONFIG_SENSORS_MAX15301 is not setCONFIG_SENSORS_MAX16064=m
# CONFIG_SENSORS_MAX16601 is not set
# CONFIG_SENSORS_MAX20730 is not set
# CONFIG_SENSORS_MAX20751 is not set
# CONFIG_SENSORS_MAX31785 is not setCONFIG_SENSORS_MAX34440=mCONFIG_SENSORS_MAX8688=m
# CONFIG_SENSORS_MP2888 is not set
# CONFIG_SENSORS_MP2975 is not set
# CONFIG_SENSORS_PIM4328 is not set
# CONFIG_SENSORS_PM6764TR is not set
# CONFIG_SENSORS_PXE1610 is not set
# CONFIG_SENSORS_Q54SJ108A2 is not set
# CONFIG_SENSORS_STPDDC60 is not set
# CONFIG_SENSORS_TPS40422 is not set
# CONFIG_SENSORS_TPS53679 is not setCONFIG_SENSORS_UCD9000=mCONFIG_SENSORS_UCD9200=m
# CONFIG_SENSORS_XDPE122 is not setCONFIG_SENSORS_ZL6100=m
# CONFIG_SENSORS_SBTSI is not set
# CONFIG_SENSORS_SBRMI is not setCONFIG_SENSORS_SHT15=mCONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHT4x is not set
# CONFIG_SENSORS_SHTC1 is not setCONFIG_SENSORS_SIS5595=mCONFIG_SENSORS_DME1737=mCONFIG_SENSORS_EMC1403=m
# CONFIG_SENSORS_EMC2103 is not setCONFIG_SENSORS_EMC6W201=mCONFIG_SENSORS_SMSC47M1=mCONFIG_SENSORS_SMSC47M192=mCONFIG_SENSORS_SMSC47B397=mCONFIG_SENSORS_SCH56XX_COMMON=mCONFIG_SENSORS_SCH5627=mCONFIG_SENSORS_SCH5636=m
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not setCONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_ADS7871 is not setCONFIG_SENSORS_AMC6821=mCONFIG_SENSORS_INA209=mCONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not setCONFIG_SENSORS_THMC50=mCONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not setCONFIG_SENSORS_TMP401=mCONFIG_SENSORS_TMP421=m
# CONFIG_SENSORS_TMP513 is not setCONFIG_SENSORS_VIA_CPUTEMP=mCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_VT1211=mCONFIG_SENSORS_VT8231=m
# CONFIG_SENSORS_W83773G is not setCONFIG_SENSORS_W83781D=mCONFIG_SENSORS_W83791D=mCONFIG_SENSORS_W83792D=mCONFIG_SENSORS_W83793=mCONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not setCONFIG_SENSORS_W83L785TS=mCONFIG_SENSORS_W83L786NG=mCONFIG_SENSORS_W83627HF=mCONFIG_SENSORS_W83627EHF=m
# CONFIG_SENSORS_XGENE is not set
#
# ACPI drivers
#CONFIG_SENSORS_ACPI_POWER=m CONFIG_SENSORS_ATK0110=mCONFIG_THERMAL=y
# CONFIG_THERMAL_NETLINK is not set
# CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=y CONFIG_THERMAL_WRITABLE_TRIPS=y CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set CONFIG_THERMAL_GOV_FAIR_SHARE=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_THERMAL_EMULATION is not set
#
# Intel thermal drivers
#CONFIG_INTEL_POWERCLAMP=mCONFIG_X86_THERMAL_VECTOR=yCONFIG_X86_PKG_TEMP_THERMAL=mCONFIG_INTEL_SOC_DTS_IOSF_CORE=m
# CONFIG_INTEL_SOC_DTS_THERMAL is not set
#
# ACPI INT340X thermal drivers
#CONFIG_INT340X_THERMAL=mCONFIG_ACPI_THERMAL_REL=m
# CONFIG_INT3406_THERMAL is not setCONFIG_PROC_THERMAL_MMIO_RAPL=m
# end of ACPI INT340X thermal drivers
CONFIG_INTEL_PCH_THERMAL=m
# CONFIG_INTEL_TCC_COOLING is not set
# CONFIG_INTEL_MENLOW is not set
# end of Intel thermal drivers
CONFIG_WATCHDOG=yCONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not setCONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=yCONFIG_WATCHDOG_OPEN_TIMEOUT=0CONFIG_WATCHDOG_SYSFS=y
# CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT is not set
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#CONFIG_SOFT_WATCHDOG=mCONFIG_WDAT_WDT=m
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_MLX_WDT is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not setCONFIG_ALIM1535_WDT=mCONFIG_ALIM7101_WDT=m
# CONFIG_EBC_C384_WDT is not setCONFIG_F71808E_WDT=mCONFIG_SP5100_TCO=mCONFIG_SBC_FITPC2_WATCHDOG=m
# CONFIG_EUROTECH_WDT is not setCONFIG_IB700_WDT=mCONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not setCONFIG_I6300ESB_WDT=yCONFIG_IE6XX_WDT=mCONFIG_ITCO_WDT=yCONFIG_ITCO_VENDOR_SUPPORT=yCONFIG_IT8712F_WDT=mCONFIG_IT87_WDT=mCONFIG_HP_WATCHDOG=mCONFIG_HPWDT_NMI_DECODING=y
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not setCONFIG_NV_TCO=m
# CONFIG_60XX_WDT is not set
# CONFIG_CPU5_WDT is not setCONFIG_SMSC_SCH311X_WDT=m
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_TQMX86_WDT is not setCONFIG_VIA_WDT=mCONFIG_W83627HF_WDT=mCONFIG_W83877F_WDT=mCONFIG_W83977F_WDT=mCONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not setCONFIG_INTEL_MEI_WDT=m
# CONFIG_NI903X_WDT is not set
# CONFIG_NIC7018_WDT is not set
# CONFIG_MEN_A21_WDT is not set
#
# PCI-based Watchdog Cards
#CONFIG_PCIPCWATCHDOG=mCONFIG_WDTPCI=m
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not setCONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not setCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=mCONFIG_BCMA_HOST_PCI_POSSIBLE=yCONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not setCONFIG_BCMA_DRIVER_PCI=yCONFIG_BCMA_DRIVER_GMAC_CMN=yCONFIG_BCMA_DRIVER_GPIO=y
# CONFIG_BCMA_DEBUG is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=y
# CONFIG_MFD_AS3711 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_MP2629 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_INTEL_QUARK_I2C_GPIO is not setCONFIG_LPC_ICH=mCONFIG_LPC_SCH=m
# CONFIG_INTEL_SOC_PMIC_CHTDC_TI is not setCONFIG_MFD_INTEL_LPSS=yCONFIG_MFD_INTEL_LPSS_ACPI=yCONFIG_MFD_INTEL_LPSS_PCI=y
# CONFIG_MFD_INTEL_PMC_BXT is not set
# CONFIG_MFD_INTEL_PMT is not set
# CONFIG_MFD_IQS62X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6360 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT4831 is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_SI476X_CORE is not setCONFIG_MFD_SM501=mCONFIG_MFD_SM501_GPIO=y
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_SYSCON is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TQMX86 is not setCONFIG_MFD_VX855=m
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_ATC260X_I2C is not set
# CONFIG_MFD_INTEL_M10_BMC is not set
# end of Multifunction device drivers
# CONFIG_REGULATOR is not setCONFIG_RC_CORE=mCONFIG_RC_MAP=mCONFIG_LIRC=yCONFIG_RC_DECODERS=yCONFIG_IR_NEC_DECODER=mCONFIG_IR_RC5_DECODER=mCONFIG_IR_RC6_DECODER=mCONFIG_IR_JVC_DECODER=mCONFIG_IR_SONY_DECODER=mCONFIG_IR_SANYO_DECODER=mCONFIG_IR_SHARP_DECODER=mCONFIG_IR_MCE_KBD_DECODER=m
# CONFIG_IR_XMP_DECODER is not setCONFIG_IR_IMON_DECODER=m
# CONFIG_IR_RCMM_DECODER is not setCONFIG_RC_DEVICES=y
# CONFIG_RC_ATI_REMOTE is not setCONFIG_IR_ENE=m
# CONFIG_IR_IMON is not set
# CONFIG_IR_IMON_RAW is not set
# CONFIG_IR_MCEUSB is not setCONFIG_IR_ITE_CIR=mCONFIG_IR_FINTEK=mCONFIG_IR_NUVOTON=m
# CONFIG_IR_REDRAT3 is not set
# CONFIG_IR_STREAMZAP is not setCONFIG_IR_WINBOND_CIR=m
# CONFIG_IR_IGORPLUGUSB is not set
# CONFIG_IR_IGUANA is not set
# CONFIG_IR_TTUSBIR is not setCONFIG_RC_LOOPBACK=mCONFIG_IR_SERIAL=mCONFIG_IR_SERIAL_TRANSMITTER=y
# CONFIG_RC_XBOX_DVD is not set
# CONFIG_IR_TOY is not set
#
# CEC support
#CONFIG_MEDIA_CEC_SUPPORT=y
# CONFIG_CEC_CH7322 is not set
# CONFIG_CEC_GPIO is not set
# CONFIG_CEC_SECO is not set
# CONFIG_USB_PULSE8_CEC is not set
# CONFIG_USB_RAINSHADOW_CEC is not set
# end of CEC support
CONFIG_MEDIA_SUPPORT=m
# CONFIG_MEDIA_SUPPORT_FILTER is not set
# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
#
# Media device types
#CONFIG_MEDIA_CAMERA_SUPPORT=yCONFIG_MEDIA_ANALOG_TV_SUPPORT=yCONFIG_MEDIA_DIGITAL_TV_SUPPORT=yCONFIG_MEDIA_RADIO_SUPPORT=yCONFIG_MEDIA_SDR_SUPPORT=yCONFIG_MEDIA_PLATFORM_SUPPORT=yCONFIG_MEDIA_TEST_SUPPORT=y
# end of Media device types
#
# Media core support
#CONFIG_VIDEO_DEV=mCONFIG_MEDIA_CONTROLLER=yCONFIG_DVB_CORE=m
# end of Media core support
#
# Video4Linux options
#CONFIG_VIDEO_V4L2=mCONFIG_VIDEO_V4L2_I2C=yCONFIG_VIDEO_V4L2_SUBDEV_API=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
# end of Video4Linux options
#
# Media controller options
#
# CONFIG_MEDIA_CONTROLLER_DVB is not set
# end of Media controller options
#
# Digital TV options
#
# CONFIG_DVB_MMAP is not setCONFIG_DVB_NET=yCONFIG_DVB_MAX_ADAPTERS=16CONFIG_DVB_DYNAMIC_MINORS=y
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set
# end of Digital TV options
#
# Media drivers
#
# CONFIG_MEDIA_USB_SUPPORT is not set
# CONFIG_MEDIA_PCI_SUPPORT is not setCONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not setCONFIG_VIDEOBUF2_CORE=mCONFIG_VIDEOBUF2_V4L2=mCONFIG_VIDEOBUF2_MEMOPS=mCONFIG_VIDEOBUF2_VMALLOC=m
# CONFIG_V4L_PLATFORM_DRIVERS is not set
# CONFIG_V4L_MEM2MEM_DRIVERS is not set
# CONFIG_DVB_PLATFORM_DRIVERS is not set
# CONFIG_SDR_PLATFORM_DRIVERS is not set
#
# MMC/SDIO DVB adapters
#
# CONFIG_SMS_SDIO_DRV is not set
# CONFIG_V4L_TEST_DRIVERS is not set
# CONFIG_DVB_TEST_DRIVERS is not set
#
# FireWire (IEEE 1394) Adapters
#
# CONFIG_DVB_FIREDTV is not set
# end of Media drivers
#
# Media ancillary drivers
#CONFIG_MEDIA_ATTACH=yCONFIG_VIDEO_IR_I2C=m
#
# Audio decoders, processors and mixers
#
# CONFIG_VIDEO_TVAUDIO is not set
# CONFIG_VIDEO_TDA7432 is not set
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not set
# CONFIG_VIDEO_MSP3400 is not set
# CONFIG_VIDEO_CS3308 is not set
# CONFIG_VIDEO_CS5345 is not set
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_UDA1342 is not set
# CONFIG_VIDEO_WM8775 is not set
# CONFIG_VIDEO_WM8739 is not set
# CONFIG_VIDEO_VP27SMPX is not set
# CONFIG_VIDEO_SONY_BTF_MPX is not set
# end of Audio decoders, processors and mixers
#
# RDS decoders
#
# CONFIG_VIDEO_SAA6588 is not set
# end of RDS decoders
#
# Video decoders
#
# CONFIG_VIDEO_ADV7180 is not set
# CONFIG_VIDEO_ADV7183 is not set
# CONFIG_VIDEO_ADV7604 is not set
# CONFIG_VIDEO_ADV7842 is not set
# CONFIG_VIDEO_BT819 is not set
# CONFIG_VIDEO_BT856 is not set
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_KS0127 is not set
# CONFIG_VIDEO_ML86V7667 is not set
# CONFIG_VIDEO_SAA7110 is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_TC358743 is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set
# CONFIG_VIDEO_TVP7002 is not set
# CONFIG_VIDEO_TW2804 is not set
# CONFIG_VIDEO_TW9903 is not set
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_TW9910 is not set
# CONFIG_VIDEO_VPX3220 is not set
#
# Video and audio decoders
#
# CONFIG_VIDEO_SAA717X is not set
# CONFIG_VIDEO_CX25840 is not set
# end of Video decoders
#
# Video encoders
#
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_SAA7185 is not set
# CONFIG_VIDEO_ADV7170 is not set
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not set
# CONFIG_VIDEO_ADV7393 is not set
# CONFIG_VIDEO_ADV7511 is not set
# CONFIG_VIDEO_AD9389B is not set
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_THS8200 is not set
# end of Video encoders
#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set
# end of Video improvement chips
#
# Audio/Video compression chips
#
# CONFIG_VIDEO_SAA6752HS is not set
# end of Audio/Video compression chips
#
# SDR tuner chips
#
# CONFIG_SDR_MAX2175 is not set
# end of SDR tuner chips
#
# Miscellaneous helper chips
#
# CONFIG_VIDEO_THS7303 is not set
# CONFIG_VIDEO_M52790 is not set
# CONFIG_VIDEO_I2C is not set
# CONFIG_VIDEO_ST_MIPID02 is not set
# end of Miscellaneous helper chips
#
# Camera sensor devices
#
# CONFIG_VIDEO_HI556 is not set
# CONFIG_VIDEO_HI846 is not set
# CONFIG_VIDEO_IMX208 is not set
# CONFIG_VIDEO_IMX214 is not set
# CONFIG_VIDEO_IMX219 is not set
# CONFIG_VIDEO_IMX258 is not set
# CONFIG_VIDEO_IMX274 is not set
# CONFIG_VIDEO_IMX290 is not set
# CONFIG_VIDEO_IMX319 is not set
# CONFIG_VIDEO_IMX355 is not set
# CONFIG_VIDEO_OV02A10 is not set
# CONFIG_VIDEO_OV2640 is not set
# CONFIG_VIDEO_OV2659 is not set
# CONFIG_VIDEO_OV2680 is not set
# CONFIG_VIDEO_OV2685 is not set
# CONFIG_VIDEO_OV2740 is not set
# CONFIG_VIDEO_OV5647 is not set
# CONFIG_VIDEO_OV5648 is not set
# CONFIG_VIDEO_OV6650 is not set
# CONFIG_VIDEO_OV5670 is not set
# CONFIG_VIDEO_OV5675 is not set
# CONFIG_VIDEO_OV5695 is not set
# CONFIG_VIDEO_OV7251 is not set
# CONFIG_VIDEO_OV772X is not set
# CONFIG_VIDEO_OV7640 is not set
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV7740 is not set
# CONFIG_VIDEO_OV8856 is not set
# CONFIG_VIDEO_OV8865 is not set
# CONFIG_VIDEO_OV9640 is not set
# CONFIG_VIDEO_OV9650 is not set
# CONFIG_VIDEO_OV9734 is not set
# CONFIG_VIDEO_OV13858 is not set
# CONFIG_VIDEO_OV13B10 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M001 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9M111 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9T112 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_MT9V111 is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_RDACM20 is not set
# CONFIG_VIDEO_RDACM21 is not set
# CONFIG_VIDEO_RJ54N1 is not set
# CONFIG_VIDEO_S5K6AA is not set
# CONFIG_VIDEO_S5K6A3 is not set
# CONFIG_VIDEO_S5K4ECGX is not set
# CONFIG_VIDEO_S5K5BAF is not set
# CONFIG_VIDEO_CCS is not set
# CONFIG_VIDEO_ET8EK8 is not set
# CONFIG_VIDEO_S5C73M3 is not set
# end of Camera sensor devices
#
# Lens drivers
#
# CONFIG_VIDEO_AD5820 is not set
# CONFIG_VIDEO_AK7375 is not set
# CONFIG_VIDEO_DW9714 is not set
# CONFIG_VIDEO_DW9768 is not set
# CONFIG_VIDEO_DW9807_VCM is not set
# end of Lens drivers
#
# Flash devices
#
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set
# end of Flash devices
#
# SPI helper chips
#
# CONFIG_VIDEO_GS1662 is not set
# end of SPI helper chips
#
# Media SPI Adapters
#CONFIG_CXD2880_SPI_DRV=m
# end of Media SPI Adapters
CONFIG_MEDIA_TUNER=m
#
# Customize TV tuners
#CONFIG_MEDIA_TUNER_SIMPLE=mCONFIG_MEDIA_TUNER_TDA18250=mCONFIG_MEDIA_TUNER_TDA8290=mCONFIG_MEDIA_TUNER_TDA827X=mCONFIG_MEDIA_TUNER_TDA18271=mCONFIG_MEDIA_TUNER_TDA9887=mCONFIG_MEDIA_TUNER_TEA5761=mCONFIG_MEDIA_TUNER_TEA5767=mCONFIG_MEDIA_TUNER_MSI001=mCONFIG_MEDIA_TUNER_MT20XX=mCONFIG_MEDIA_TUNER_MT2060=mCONFIG_MEDIA_TUNER_MT2063=mCONFIG_MEDIA_TUNER_MT2266=mCONFIG_MEDIA_TUNER_MT2131=mCONFIG_MEDIA_TUNER_QT1010=mCONFIG_MEDIA_TUNER_XC2028=mCONFIG_MEDIA_TUNER_XC5000=mCONFIG_MEDIA_TUNER_XC4000=mCONFIG_MEDIA_TUNER_MXL5005S=mCONFIG_MEDIA_TUNER_MXL5007T=mCONFIG_MEDIA_TUNER_MC44S803=mCONFIG_MEDIA_TUNER_MAX2165=mCONFIG_MEDIA_TUNER_TDA18218=mCONFIG_MEDIA_TUNER_FC0011=mCONFIG_MEDIA_TUNER_FC0012=mCONFIG_MEDIA_TUNER_FC0013=mCONFIG_MEDIA_TUNER_TDA18212=mCONFIG_MEDIA_TUNER_E4000=mCONFIG_MEDIA_TUNER_FC2580=mCONFIG_MEDIA_TUNER_M88RS6000T=mCONFIG_MEDIA_TUNER_TUA9001=mCONFIG_MEDIA_TUNER_SI2157=mCONFIG_MEDIA_TUNER_IT913X=mCONFIG_MEDIA_TUNER_R820T=mCONFIG_MEDIA_TUNER_MXL301RF=mCONFIG_MEDIA_TUNER_QM1D1C0042=mCONFIG_MEDIA_TUNER_QM1D1B0004=m
# end of Customize TV tuners
#
# Customise DVB Frontends
#
#
# Multistandard (satellite) frontends
#CONFIG_DVB_STB0899=mCONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=mCONFIG_DVB_STV0910=m
CONFIG_DVB_STV6110x=mCONFIG_DVB_STV6111=mCONFIG_DVB_MXL5XX=mCONFIG_DVB_M88DS3103=m
#
# Multistandard (cable + terrestrial) frontends
#CONFIG_DVB_DRXK=mCONFIG_DVB_TDA18271C2DD=mCONFIG_DVB_SI2165=mCONFIG_DVB_MN88472=mCONFIG_DVB_MN88473=m
#
# DVB-S (satellite) frontends
#CONFIG_DVB_CX24110=mCONFIG_DVB_CX24123=mCONFIG_DVB_MT312=mCONFIG_DVB_ZL10036=mCONFIG_DVB_ZL10039=mCONFIG_DVB_S5H1420=mCONFIG_DVB_STV0288=mCONFIG_DVB_STB6000=mCONFIG_DVB_STV0299=mCONFIG_DVB_STV6110=mCONFIG_DVB_STV0900=mCONFIG_DVB_TDA8083=mCONFIG_DVB_TDA10086=mCONFIG_DVB_TDA8261=mCONFIG_DVB_VES1X93=mCONFIG_DVB_TUNER_ITD1000=mCONFIG_DVB_TUNER_CX24113=mCONFIG_DVB_TDA826X=mCONFIG_DVB_TUA6100=mCONFIG_DVB_CX24116=mCONFIG_DVB_CX24117=mCONFIG_DVB_CX24120=mCONFIG_DVB_SI21XX=mCONFIG_DVB_TS2020=mCONFIG_DVB_DS3000=mCONFIG_DVB_MB86A16=mCONFIG_DVB_TDA10071=m
#
# DVB-T (terrestrial) frontends
#CONFIG_DVB_SP887X=mCONFIG_DVB_CX22700=mCONFIG_DVB_CX22702=mCONFIG_DVB_S5H1432=mCONFIG_DVB_DRXD=mCONFIG_DVB_L64781=mCONFIG_DVB_TDA1004X=mCONFIG_DVB_NXT6000=mCONFIG_DVB_MT352=mCONFIG_DVB_ZL10353=mCONFIG_DVB_DIB3000MB=mCONFIG_DVB_DIB3000MC=mCONFIG_DVB_DIB7000M=mCONFIG_DVB_DIB7000P=mCONFIG_DVB_DIB9000=mCONFIG_DVB_TDA10048=mCONFIG_DVB_AF9013=mCONFIG_DVB_EC100=mCONFIG_DVB_STV0367=mCONFIG_DVB_CXD2820R=mCONFIG_DVB_CXD2841ER=mCONFIG_DVB_RTL2830=mCONFIG_DVB_RTL2832=mCONFIG_DVB_RTL2832_SDR=mCONFIG_DVB_SI2168=mCONFIG_DVB_ZD1301_DEMOD=mCONFIG_DVB_CXD2880=m
#
# DVB-C (cable) frontends
#CONFIG_DVB_VES1820=mCONFIG_DVB_TDA10021=mCONFIG_DVB_TDA10023=mCONFIG_DVB_STV0297=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #CONFIG_DVB_NXT200X=mCONFIG_DVB_OR51211=mCONFIG_DVB_OR51132=mCONFIG_DVB_BCM3510=mCONFIG_DVB_LGDT330X=mCONFIG_DVB_LGDT3305=mCONFIG_DVB_LGDT3306A=mCONFIG_DVB_LG2160=mCONFIG_DVB_S5H1409=mCONFIG_DVB_AU8522=mCONFIG_DVB_AU8522_DTV=mCONFIG_DVB_AU8522_V4L=mCONFIG_DVB_S5H1411=mCONFIG_DVB_MXL692=m
#
# ISDB-T (terrestrial) frontends
#CONFIG_DVB_S921=mCONFIG_DVB_DIB8000=mCONFIG_DVB_MB86A20S=m
#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends #CONFIG_DVB_TC90522=mCONFIG_DVB_MN88443X=m
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=mCONFIG_DVB_TUNER_DIB0070=mCONFIG_DVB_TUNER_DIB0090=m
#
# SEC control devices for DVB-S
#CONFIG_DVB_DRX39XYJ=mCONFIG_DVB_LNBH25=mCONFIG_DVB_LNBH29=mCONFIG_DVB_LNBP21=mCONFIG_DVB_LNBP22=mCONFIG_DVB_ISL6405=mCONFIG_DVB_ISL6421=mCONFIG_DVB_ISL6423=mCONFIG_DVB_A8293=mCONFIG_DVB_LGS8GL5=mCONFIG_DVB_LGS8GXX=mCONFIG_DVB_ATBM8830=m
CONFIG_DVB_TDA665x=mCONFIG_DVB_IX2505V=mCONFIG_DVB_M88RS2000=mCONFIG_DVB_AF9033=mCONFIG_DVB_HORUS3A=mCONFIG_DVB_ASCOT2E=mCONFIG_DVB_HELENE=m
#
# Common Interface (EN50221) controller drivers
#CONFIG_DVB_CXD2099=mCONFIG_DVB_SP2=m
# end of Customise DVB Frontends
#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set
# end of Media ancillary drivers
#
# Graphics support
#
# CONFIG_AGP is not setCONFIG_INTEL_GTT=mCONFIG_VGA_ARB=y CONFIG_VGA_ARB_MAX_GPUS=64 CONFIG_VGA_SWITCHEROO=yCONFIG_DRM=yCONFIG_DRM_MIPI_DSI=y CONFIG_DRM_DP_AUX_CHARDEV=y
# CONFIG_DRM_DEBUG_MM is not set CONFIG_DRM_DEBUG_SELFTEST=m CONFIG_DRM_KMS_HELPER=y
# CONFIG_DRM_DEBUG_DP_MST_TOPOLOGY_REFS is not set CONFIG_DRM_FBDEV_EMULATION=y CONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not set CONFIG_DRM_LOAD_EDID_FIRMWARE=y
# CONFIG_DRM_DP_CEC is not set CONFIG_DRM_TTM=mCONFIG_DRM_VRAM_HELPER=m CONFIG_DRM_TTM_HELPER=m CONFIG_DRM_GEM_SHMEM_HELPER=y
#
# I2C encoder or helper chips
#CONFIG_DRM_I2C_CH7006=mCONFIG_DRM_I2C_SIL164=m
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# end of I2C encoder or helper chips
#
# ARM devices
#
# end of ARM devices
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
# CONFIG_DRM_NOUVEAU is not setCONFIG_DRM_I915=mCONFIG_DRM_I915_FORCE_PROBE=""CONFIG_DRM_I915_CAPTURE_ERROR=yCONFIG_DRM_I915_COMPRESS_ERROR=yCONFIG_DRM_I915_USERPTR=yCONFIG_DRM_I915_GVT=y
# CONFIG_DRM_I915_GVT_KVMGT is not set
#
# drm/i915 Debugging # # CONFIG_DRM_I915_WERROR is not set # CONFIG_DRM_I915_DEBUG is not set # CONFIG_DRM_I915_DEBUG_MMIO is not set # CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set # CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set # CONFIG_DRM_I915_DEBUG_GUC is not set # CONFIG_DRM_I915_SELFTEST is not set # CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set # CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set # CONFIG_DRM_I915_DEBUG_RUNTIME_PM is not set # end of drm/i915 Debugging
#
# drm/i915 Profile Guided Optimisation # CONFIG_DRM_I915_REQUEST_TIMEOUT=20000 CONFIG_DRM_I915_FENCE_TIMEOUT=10000 CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250 CONFIG_DRM_I915_HEARTBEAT_INTERVAL=2500 CONFIG_DRM_I915_PREEMPT_TIMEOUT=640 CONFIG_DRM_I915_MAX_REQUEST_BUSYWAIT=8000 CONFIG_DRM_I915_STOP_TIMEOUT=100 CONFIG_DRM_I915_TIMESLICE_DURATION=1 # end of drm/i915 Profile Guided Optimisation
CONFIG_DRM_VGEM=y
# CONFIG_DRM_VKMS is not set
# CONFIG_DRM_VMWGFX is not setCONFIG_DRM_GMA500=m
# CONFIG_DRM_UDL is not setCONFIG_DRM_AST=mCONFIG_DRM_MGAG200=mCONFIG_DRM_QXL=mCONFIG_DRM_VIRTIO_GPU=mCONFIG_DRM_PANEL=y
#
# Display Panels
#
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set # CONFIG_DRM_PANEL_WIDECHIPS_WS2401 is not set
# end of Display Panels
CONFIG_DRM_BRIDGE=yCONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
# end of Display Interface Bridges
# CONFIG_DRM_ETNAVIV is not setCONFIG_DRM_BOCHS=mCONFIG_DRM_CIRRUS_QEMU=m
# CONFIG_DRM_GM12U320 is not set
# CONFIG_DRM_SIMPLEDRM is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
# CONFIG_TINYDRM_ILI9486 is not set
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_ST7586 is not set
# CONFIG_TINYDRM_ST7735R is not set
# CONFIG_DRM_VBOXVIDEO is not set
# CONFIG_DRM_GUD is not set
# CONFIG_DRM_HYPERV is not set
# CONFIG_DRM_LEGACY is not setCONFIG_DRM_EXPORT_FOR_TESTS=yCONFIG_DRM_PANEL_ORIENTATION_QUIRKS=yCONFIG_DRM_LIB_RANDOM=y
#
# Frame buffer Devices
#CONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not setCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_SYS_FILLRECT=yCONFIG_FB_SYS_COPYAREA=yCONFIG_FB_SYS_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not setCONFIG_FB_SYS_FOPS=yCONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_MODE_HELPERS is not setCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not setCONFIG_FB_VESA=yCONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SM501 is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not setCONFIG_FB_HYPERV=m
# CONFIG_FB_SIMPLE is not set
# CONFIG_FB_SSD1307 is not set
# CONFIG_FB_SM712 is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not setCONFIG_LCD_PLATFORM=m
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
# CONFIG_LCD_OTM3225A is not setCONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_KTD253 is not set
# CONFIG_BACKLIGHT_PWM is not setCONFIG_BACKLIGHT_APPLE=m
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not setCONFIG_BACKLIGHT_LP855X=m
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# end of Backlight & LCD device support
CONFIG_HDMI=y
#
# Console display driver support
#CONFIG_VGA_CONSOLE=yCONFIG_DUMMY_CONSOLE=y CONFIG_DUMMY_CONSOLE_COLUMNS=80 CONFIG_DUMMY_CONSOLE_ROWS=25 CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
# end of Console display driver support
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not setCONFIG_LOGO_LINUX_CLUT224=y
# end of Graphics support
# CONFIG_SOUND is not set
#
# HID support
#CONFIG_HID=yCONFIG_HID_BATTERY_STRENGTH=yCONFIG_HIDRAW=yCONFIG_UHID=mCONFIG_HID_GENERIC=y
#
# Special HID drivers
#CONFIG_HID_A4TECH=m
# CONFIG_HID_ACCUTOUCH is not setCONFIG_HID_ACRUX=m
# CONFIG_HID_ACRUX_FF is not setCONFIG_HID_APPLE=m
# CONFIG_HID_APPLEIR is not setCONFIG_HID_ASUS=mCONFIG_HID_AUREAL=mCONFIG_HID_BELKIN=m
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not setCONFIG_HID_CHERRY=mCONFIG_HID_CHICONY=m
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not setCONFIG_HID_CMEDIA=m
# CONFIG_HID_CP2112 is not set
# CONFIG_HID_CREATIVE_SB0540 is not setCONFIG_HID_CYPRESS=mCONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not setCONFIG_HID_ELECOM=m
# CONFIG_HID_ELO is not setCONFIG_HID_EZKEY=m
# CONFIG_HID_FT260 is not setCONFIG_HID_GEMBIRD=mCONFIG_HID_GFRM=m
# CONFIG_HID_GLORIOUS is not set
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_VIVALDI is not set
# CONFIG_HID_GT683R is not setCONFIG_HID_KEYTOUCH=mCONFIG_HID_KYE=m
# CONFIG_HID_UCLOGIC is not setCONFIG_HID_WALTOP=m
# CONFIG_HID_VIEWSONIC is not set
# CONFIG_HID_XIAOMI is not setCONFIG_HID_GYRATION=mCONFIG_HID_ICADE=mCONFIG_HID_ITE=mCONFIG_HID_JABRA=mCONFIG_HID_TWINHAN=mCONFIG_HID_KENSINGTON=mCONFIG_HID_LCPOWER=mCONFIG_HID_LED=mCONFIG_HID_LENOVO=mCONFIG_HID_LOGITECH=mCONFIG_HID_LOGITECH_DJ=mCONFIG_HID_LOGITECH_HIDPP=m
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not setCONFIG_HID_MAGICMOUSE=y
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not set
# CONFIG_HID_REDRAGON is not setCONFIG_HID_MICROSOFT=mCONFIG_HID_MONTEREY=mCONFIG_HID_MULTITOUCH=m
# CONFIG_HID_NINTENDO is not setCONFIG_HID_NTI=m
# CONFIG_HID_NTRIG is not setCONFIG_HID_ORTEK=mCONFIG_HID_PANTHERLORD=m
# CONFIG_PANTHERLORD_FF is not set
# CONFIG_HID_PENMOUNT is not setCONFIG_HID_PETALYNX=mCONFIG_HID_PICOLCD=mCONFIG_HID_PICOLCD_FB=yCONFIG_HID_PICOLCD_BACKLIGHT=yCONFIG_HID_PICOLCD_LCD=yCONFIG_HID_PICOLCD_LEDS=yCONFIG_HID_PICOLCD_CIR=yCONFIG_HID_PLANTRONICS=mCONFIG_HID_PRIMAX=m
# CONFIG_HID_RETRODE is not set
# CONFIG_HID_ROCCAT is not setCONFIG_HID_SAITEK=mCONFIG_HID_SAMSUNG=m
# CONFIG_HID_SEMITEK is not set
# CONFIG_HID_SONY is not setCONFIG_HID_SPEEDLINK=m
# CONFIG_HID_STEAM is not setCONFIG_HID_STEELSERIES=mCONFIG_HID_SUNPLUS=mCONFIG_HID_RMI=mCONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not setCONFIG_HID_HYPERV_MOUSE=mCONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not setCONFIG_HID_TIVO=mCONFIG_HID_TOPSEED=mCONFIG_HID_THINGM=mCONFIG_HID_THRUSTMASTER=m
# CONFIG_THRUSTMASTER_FF is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not set
# CONFIG_HID_WACOM is not setCONFIG_HID_WIIMOTE=mCONFIG_HID_XINMO=mCONFIG_HID_ZEROPLUS=m
# CONFIG_ZEROPLUS_FF is not setCONFIG_HID_ZYDACRON=mCONFIG_HID_SENSOR_HUB=yCONFIG_HID_SENSOR_CUSTOM_SENSOR=mCONFIG_HID_ALPS=m
# CONFIG_HID_MCP2221 is not set
# end of Special HID drivers
#
# USB HID support
#CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set
# end of USB HID support
#
# I2C HID support
#
# CONFIG_I2C_HID_ACPI is not set
# end of I2C HID support
#
# Intel ISH HID support
#CONFIG_INTEL_ISH_HID=m
# CONFIG_INTEL_ISH_FIRMWARE_DOWNLOADER is not set
# end of Intel ISH HID support
#
# AMD SFH HID Support
#
# CONFIG_AMD_SFH_HID is not set
# end of AMD SFH HID Support # end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_SUPPORT=yCONFIG_USB_COMMON=y
# CONFIG_USB_LED_TRIG is not set
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_CONN_GPIO is not setCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB=yCONFIG_USB_PCI=yCONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_FEW_INIT_RETRIES is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_PRODUCTLIST is not set
# CONFIG_USB_OTG_DISABLE_EXTERNAL_HUB is not setCONFIG_USB_LEDS_TRIGGER_USBPORT=yCONFIG_USB_AUTOSUSPEND_DELAY=2CONFIG_USB_MON=y
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not setCONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_DBGCAP is not setCONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PCI_RENESAS is not set
# CONFIG_USB_XHCI_PLATFORM is not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_EHCI_TT_NEWSCHED=yCONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not setCONFIG_USB_OHCI_HCD=yCONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not setCONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_TEST_MODE is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may #
#
# also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_REALTEK is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_STORAGE_ENE_UB6250 is not set # CONFIG_USB_UAS is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_USB_CDNS_SUPPORT is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
# CONFIG_USB_ISP1760 is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not setCONFIG_USB_SERIAL=mCONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_SIMPLE is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
# CONFIG_USB_SERIAL_BELKIN is not set
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP210X is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_F81232 is not set
# CONFIG_USB_SERIAL_F8153X is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_IUU is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_METRO is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_MXUPORT is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_QCAUX is not set
# CONFIG_USB_SERIAL_QUALCOMM is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_SYMBOL is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_OPTICON is not set
# CONFIG_USB_SERIAL_XSENS_MT is not set
# CONFIG_USB_SERIAL_WISHBONE is not set
# CONFIG_USB_SERIAL_SSU100 is not set
# CONFIG_USB_SERIAL_QT2 is not set
# CONFIG_USB_SERIAL_UPD78F0730 is not set
# CONFIG_USB_SERIAL_XR is not setCONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_APPLE_MFI_FASTCHARGE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
# CONFIG_USB_HUB_USB251XB is not set
# CONFIG_USB_HSIC_USB3503 is not set
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not set
# CONFIG_USB_ATM is not set
#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# end of USB Physical Layer drivers
# CONFIG_USB_GADGET is not setCONFIG_TYPEC=y
# CONFIG_TYPEC_TCPM is not setCONFIG_TYPEC_UCSI=y
# CONFIG_UCSI_CCG is not setCONFIG_UCSI_ACPI=y
# CONFIG_TYPEC_TPS6598X is not set
# CONFIG_TYPEC_STUSB160X is not set
#
# USB Type-C Multiplexer/DeMultiplexer Switch support #
# CONFIG_TYPEC_MUX_PI3USB30532 is not set
# end of USB Type-C Multiplexer/DeMultiplexer Switch support
#
# USB Type-C Alternate Mode drivers
#
# CONFIG_TYPEC_DP_ALTMODE is not set
# end of USB Type-C Alternate Mode drivers
# CONFIG_USB_ROLE_SWITCH is not setCONFIG_MMC=mCONFIG_MMC_BLOCK=mCONFIG_MMC_BLOCK_MINORS=8CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not setCONFIG_MMC_SDHCI=mCONFIG_MMC_SDHCI_IO_ACCESSORS=yCONFIG_MMC_SDHCI_PCI=mCONFIG_MMC_RICOH_MMC=yCONFIG_MMC_SDHCI_ACPI=mCONFIG_MMC_SDHCI_PLTFM=m
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SPI is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
# CONFIG_MMC_USDHI6ROL0 is not set
# CONFIG_MMC_REALTEK_PCI is not setCONFIG_MMC_CQHCI=m
# CONFIG_MMC_HSQ is not set
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MMC_SDHCI_XENON is not set
# CONFIG_MEMSTICK is not setCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
# CONFIG_LEDS_CLASS_MULTICOLOR is not set
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set
#
# LED drivers
#
# CONFIG_LEDS_APU is not setCONFIG_LEDS_LM3530=m
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not setCONFIG_LEDS_LP3944=m
# CONFIG_LEDS_LP3952 is not set
# CONFIG_LEDS_LP50XX is not setCONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_BD2802 is not setCONFIG_LEDS_INTEL_SS4200=mCONFIG_LEDS_LT3593=m
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #CONFIG_LEDS_BLINKM=mCONFIG_LEDS_MLXCPLD=m
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_NIC78BX is not set
# CONFIG_LEDS_TI_LMU_COMMON is not set
#
# Flash and Torch LED drivers
#
#
# LED Triggers
#CONFIG_LEDS_TRIGGERS=yCONFIG_LEDS_TRIGGER_TIMER=mCONFIG_LEDS_TRIGGER_ONESHOT=m
# CONFIG_LEDS_TRIGGER_DISK is not setCONFIG_LEDS_TRIGGER_HEARTBEAT=mCONFIG_LEDS_TRIGGER_BACKLIGHT=m
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not setCONFIG_LEDS_TRIGGER_GPIO=mCONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target) # CONFIG_LEDS_TRIGGER_TRANSIENT=m CONFIG_LEDS_TRIGGER_CAMERA=m # CONFIG_LEDS_TRIGGER_PANIC is not set # CONFIG_LEDS_TRIGGER_NETDEV is not set # CONFIG_LEDS_TRIGGER_PATTERN is not set CONFIG_LEDS_TRIGGER_AUDIO=m # CONFIG_LEDS_TRIGGER_TTY is not set # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set CONFIG_EDAC_ATOMIC_SCRUB=y CONFIG_EDAC_SUPPORT=y CONFIG_EDAC=y CONFIG_EDAC_LEGACY_SYSFS=y # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_DECODE_MCE=m CONFIG_EDAC_GHES=y CONFIG_EDAC_AMD64=m CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_I3200=m CONFIG_EDAC_IE31200=m CONFIG_EDAC_X38=m CONFIG_EDAC_I5400=m CONFIG_EDAC_I7CORE=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m CONFIG_EDAC_I7300=m CONFIG_EDAC_SBRIDGE=m CONFIG_EDAC_SKX=m # CONFIG_EDAC_I10NM is not set CONFIG_EDAC_PND2=m # CONFIG_EDAC_IGEN6 is not set CONFIG_RTC_LIB=y CONFIG_RTC_MC146818_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_SYSTOHC is not set # CONFIG_RTC_DEBUG is not set CONFIG_RTC_NVMEM=y
#
# RTC interfaces
#CONFIG_RTC_INTF_SYSFS=yCONFIG_RTC_INTF_PROC=yCONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABEOZ9 is not set
# CONFIG_RTC_DRV_ABX80X is not setCONFIG_RTC_DRV_DS1307=m
# CONFIG_RTC_DRV_DS1307_CENTURY is not setCONFIG_RTC_DRV_DS1374=m
# CONFIG_RTC_DRV_DS1374_WDT is not setCONFIG_RTC_DRV_DS1672=mCONFIG_RTC_DRV_MAX6900=mCONFIG_RTC_DRV_RS5C372=mCONFIG_RTC_DRV_ISL1208=mCONFIG_RTC_DRV_ISL12022=mCONFIG_RTC_DRV_X1205=mCONFIG_RTC_DRV_PCF8523=m
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF85363 is not setCONFIG_RTC_DRV_PCF8563=mCONFIG_RTC_DRV_PCF8583=mCONFIG_RTC_DRV_M41T80=mCONFIG_RTC_DRV_M41T80_WDT=yCONFIG_RTC_DRV_BQ32K=m
# CONFIG_RTC_DRV_S35390A is not setCONFIG_RTC_DRV_FM3130=m
# CONFIG_RTC_DRV_RX8010 is not setCONFIG_RTC_DRV_RX8581=mCONFIG_RTC_DRV_RX8025=mCONFIG_RTC_DRV_EM3027=m
# CONFIG_RTC_DRV_RV3028 is not set
# CONFIG_RTC_DRV_RV3032 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_SD3078 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not setCONFIG_RTC_DRV_RX4581=m
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not setCONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#CONFIG_RTC_DRV_DS3232=mCONFIG_RTC_DRV_DS3232_HWMON=y
# CONFIG_RTC_DRV_PCF2127 is not setCONFIG_RTC_DRV_RV3029C2=m
# CONFIG_RTC_DRV_RV3029_HWMON is not set
# CONFIG_RTC_DRV_RX6110 is not set
#
# Platform RTC drivers
#CONFIG_RTC_DRV_CMOS=yCONFIG_RTC_DRV_DS1286=mCONFIG_RTC_DRV_DS1511=mCONFIG_RTC_DRV_DS1553=m
# CONFIG_RTC_DRV_DS1685_FAMILY is not setCONFIG_RTC_DRV_DS1742=mCONFIG_RTC_DRV_DS2404=mCONFIG_RTC_DRV_STK17TA8=m
# CONFIG_RTC_DRV_M48T86 is not setCONFIG_RTC_DRV_M48T35=mCONFIG_RTC_DRV_M48T59=mCONFIG_RTC_DRV_MSM6242=mCONFIG_RTC_DRV_BQ4802=mCONFIG_RTC_DRV_RP5C01=mCONFIG_RTC_DRV_V3020=m
#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_FTRTC010 is not set
#
# HID Sensor RTC drivers
#
# CONFIG_RTC_DRV_GOLDFISH is not setCONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#CONFIG_DMA_ENGINE=yCONFIG_DMA_VIRTUAL_CHANNELS=yCONFIG_DMA_ACPI=y
# CONFIG_ALTERA_MSGDMA is not setCONFIG_INTEL_IDMA64=m
# CONFIG_INTEL_IDXD is not set
# CONFIG_INTEL_IDXD_COMPAT is not setCONFIG_INTEL_IOATDMA=m
# CONFIG_PLX_DMA is not set
# CONFIG_AMD_PTDMA is not set
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not setCONFIG_DW_DMAC_CORE=yCONFIG_DW_DMAC=mCONFIG_DW_DMAC_PCI=y
# CONFIG_DW_EDMA is not set
# CONFIG_DW_EDMA_PCIE is not setCONFIG_HSU_DMA=y
# CONFIG_SF_PDMA is not set
# CONFIG_INTEL_LDMA is not set
#
# DMA Clients
#CONFIG_ASYNC_TX_DMA=yCONFIG_DMATEST=mCONFIG_DMA_ENGINE_RAID=y
#
# DMABUF options
#CONFIG_SYNC_FILE=yCONFIG_SW_SYNC=yCONFIG_UDMABUF=y
# CONFIG_DMABUF_MOVE_NOTIFY is not set
# CONFIG_DMABUF_DEBUG is not set
# CONFIG_DMABUF_SELFTESTS is not setCONFIG_DMABUF_HEAPS=y
# CONFIG_DMABUF_SYSFS_STATS is not setCONFIG_DMABUF_HEAPS_SYSTEM=y
# end of DMABUF options
CONFIG_DCA=m
# CONFIG_AUXDISPLAY is not set
# CONFIG_PANEL is not setCONFIG_UIO=mCONFIG_UIO_CIF=mCONFIG_UIO_PDRV_GENIRQ=m
# CONFIG_UIO_DMEM_GENIRQ is not setCONFIG_UIO_AEC=mCONFIG_UIO_SERCOS3=mCONFIG_UIO_PCI_GENERIC=m
# CONFIG_UIO_NETX is not set
# CONFIG_UIO_PRUSS is not set
# CONFIG_UIO_MF624 is not setCONFIG_UIO_HV_GENERIC=mCONFIG_VFIO=mCONFIG_VFIO_IOMMU_TYPE1=mCONFIG_VFIO_VIRQFD=mCONFIG_VFIO_NOIOMMU=yCONFIG_VFIO_PCI_CORE=mCONFIG_VFIO_PCI_MMAP=yCONFIG_VFIO_PCI_INTX=yCONFIG_VFIO_PCI=m
# CONFIG_VFIO_PCI_VGA is not set
# CONFIG_VFIO_PCI_IGD is not setCONFIG_VFIO_MDEV=mCONFIG_IRQ_BYPASS_MANAGER=y
# CONFIG_VIRT_DRIVERS is not setCONFIG_VIRTIO=yCONFIG_VIRTIO_PCI_LIB=yCONFIG_VIRTIO_PCI_LIB_LEGACY=yCONFIG_VIRTIO_MENU=yCONFIG_VIRTIO_PCI=yCONFIG_VIRTIO_PCI_LEGACY=y
# CONFIG_VIRTIO_PMEM is not setCONFIG_VIRTIO_BALLOON=mCONFIG_VIRTIO_MEM=mCONFIG_VIRTIO_INPUT=m
# CONFIG_VIRTIO_MMIO is not setCONFIG_VIRTIO_DMA_SHARED_BUFFER=m
# CONFIG_VDPA is not setCONFIG_VHOST_IOTLB=mCONFIG_VHOST=mCONFIG_VHOST_MENU=yCONFIG_VHOST_NET=m
# CONFIG_VHOST_SCSI is not setCONFIG_VHOST_VSOCK=m
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
#
# Microsoft Hyper-V guest support
#CONFIG_HYPERV=mCONFIG_HYPERV_TIMER=yCONFIG_HYPERV_UTILS=mCONFIG_HYPERV_BALLOON=m
# end of Microsoft Hyper-V guest support
# CONFIG_GREYBUS is not set
# CONFIG_COMEDI is not setCONFIG_STAGING=y
# CONFIG_PRISM2_USB is not set
# CONFIG_RTL8192U is not set
# CONFIG_RTLLIB is not set
# CONFIG_RTL8723BS is not set
# CONFIG_R8712U is not set
# CONFIG_R8188EU is not set
# CONFIG_RTS5208 is not set
# CONFIG_VT6655 is not set
# CONFIG_VT6656 is not set
# CONFIG_FB_SM750 is not set
# CONFIG_STAGING_MEDIA is not set
#
# Android
#
# CONFIG_ASHMEM is not set
# end of Android
# CONFIG_LTE_GDM724X is not set
# CONFIG_FIREWIRE_SERIAL is not set
# CONFIG_GS_FPGABOOT is not set
# CONFIG_UNISYSSPAR is not set
# CONFIG_FB_TFT is not set
# CONFIG_KS7010 is not set
# CONFIG_PI433 is not set
# CONFIG_FIELDBUS_DEV is not set
# CONFIG_QLGE is not set
# CONFIG_WFX is not setCONFIG_X86_PLATFORM_DEVICES=yCONFIG_ACPI_WMI=mCONFIG_WMI_BMOF=m
# CONFIG_HUAWEI_WMI is not set
# CONFIG_UV_SYSFS is not setCONFIG_MXM_WMI=m
# CONFIG_PEAQ_WMI is not set
# CONFIG_NVIDIA_WMI_EC_BACKLIGHT is not set
# CONFIG_XIAOMI_WMI is not set
# CONFIG_GIGABYTE_WMI is not setCONFIG_ACERHDF=m
# CONFIG_ACER_WIRELESS is not setCONFIG_ACER_WMI=m
# CONFIG_AMD_PMC is not set
# CONFIG_ADV_SWBUTTON is not setCONFIG_APPLE_GMUX=mCONFIG_ASUS_LAPTOP=m
# CONFIG_ASUS_WIRELESS is not setCONFIG_ASUS_WMI=mCONFIG_ASUS_NB_WMI=m
# CONFIG_MERAKI_MX100 is not setCONFIG_EEEPC_LAPTOP=mCONFIG_EEEPC_WMI=m
# CONFIG_X86_PLATFORM_DRIVERS_DELL is not setCONFIG_AMILO_RFKILL=mCONFIG_FUJITSU_LAPTOP=mCONFIG_FUJITSU_TABLET=m
# CONFIG_GPD_POCKET_FAN is not setCONFIG_HP_ACCEL=m
# CONFIG_WIRELESS_HOTKEY is not setCONFIG_HP_WMI=m
# CONFIG_IBM_RTL is not setCONFIG_IDEAPAD_LAPTOP=mCONFIG_SENSORS_HDAPS=mCONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not setCONFIG_THINKPAD_ACPI_VIDEO=yCONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
# CONFIG_THINKPAD_LMI is not setCONFIG_X86_PLATFORM_DRIVERS_INTEL=y
# CONFIG_INTEL_ATOMISP2_PM is not set
# CONFIG_INTEL_SAR_INT1092 is not setCONFIG_INTEL_PMC_CORE=m
#
# Intel Speed Select Technology interface support
#
# CONFIG_INTEL_SPEED_SELECT_INTERFACE is not set
# end of Intel Speed Select Technology interface support
CONFIG_INTEL_WMI=y
# CONFIG_INTEL_WMI_SBL_FW_UPDATE is not setCONFIG_INTEL_WMI_THUNDERBOLT=mCONFIG_INTEL_HID_EVENT=mCONFIG_INTEL_VBTN=m
# CONFIG_INTEL_INT0002_VGPIO is not setCONFIG_INTEL_OAKTRAIL=m
# CONFIG_INTEL_ISHTP_ECLITE is not set
# CONFIG_INTEL_PUNIT_IPC is not setCONFIG_INTEL_RST=m
# CONFIG_INTEL_SMARTCONNECT is not setCONFIG_INTEL_TURBO_MAX_3=y
# CONFIG_INTEL_UNCORE_FREQ_CONTROL is not setCONFIG_MSI_LAPTOP=mCONFIG_MSI_WMI=m
# CONFIG_PCENGINES_APU2 is not set
# CONFIG_BARCO_P50_GPIO is not setCONFIG_SAMSUNG_LAPTOP=mCONFIG_SAMSUNG_Q10=mCONFIG_TOSHIBA_BT_RFKILL=m
# CONFIG_TOSHIBA_HAPS is not set
# CONFIG_TOSHIBA_WMI is not setCONFIG_ACPI_CMPC=mCONFIG_COMPAL_LAPTOP=m
# CONFIG_LG_LAPTOP is not setCONFIG_PANASONIC_LAPTOP=mCONFIG_SONY_LAPTOP=mCONFIG_SONYPI_COMPAT=y
# CONFIG_SYSTEM76_ACPI is not setCONFIG_TOPSTAR_LAPTOP=m
# CONFIG_I2C_MULTI_INSTANTIATE is not setCONFIG_MLX_PLATFORM=mCONFIG_INTEL_IPS=m
# CONFIG_INTEL_SCU_PCI is not set
# CONFIG_INTEL_SCU_PLATFORM is not setCONFIG_PMC_ATOM=y
# CONFIG_CHROME_PLATFORMS is not setCONFIG_MELLANOX_PLATFORM=yCONFIG_MLXREG_HOTPLUG=m
# CONFIG_MLXREG_IO is not set
# CONFIG_MLXREG_LC is not setCONFIG_SURFACE_PLATFORMS=y
# CONFIG_SURFACE3_WMI is not set
# CONFIG_SURFACE_3_POWER_OPREGION is not set
# CONFIG_SURFACE_GPE is not set
# CONFIG_SURFACE_HOTPLUG is not set
# CONFIG_SURFACE_PRO3_BUTTON is not setCONFIG_HAVE_CLK=yCONFIG_HAVE_CLK_PREPARE=yCONFIG_COMMON_CLK=y
# CONFIG_LMK04832 is not set
# CONFIG_COMMON_CLK_MAX9485 is not set
# CONFIG_COMMON_CLK_SI5341 is not set
# CONFIG_COMMON_CLK_SI5351 is not set
# CONFIG_COMMON_CLK_SI544 is not set
# CONFIG_COMMON_CLK_CDCE706 is not set
# CONFIG_COMMON_CLK_CS2000_CP is not set
# CONFIG_COMMON_CLK_PWM is not set
# CONFIG_XILINX_VCU is not setCONFIG_HWSPINLOCK=y
#
# Clock Source drivers
#CONFIG_CLKEVT_I8253=yCONFIG_I8253_LOCK=yCONFIG_CLKBLD_I8253=y
# end of Clock Source drivers
CONFIG_MAILBOX=yCONFIG_PCC=y
# CONFIG_ALTERA_MBOX is not setCONFIG_IOMMU_IOVA=yCONFIG_IOASID=yCONFIG_IOMMU_API=yCONFIG_IOMMU_SUPPORT=y
#
# Generic IOMMU Pagetable Support
#
# end of Generic IOMMU Pagetable Support
# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_IOMMU_DEFAULT_DMA_STRICT is not setCONFIG_IOMMU_DEFAULT_DMA_LAZY=y
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not setCONFIG_IOMMU_DMA=y
# CONFIG_AMD_IOMMU is not setCONFIG_DMAR_TABLE=yCONFIG_INTEL_IOMMU=y
# CONFIG_INTEL_IOMMU_SVM is not set
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not setCONFIG_INTEL_IOMMU_FLOPPY_WA=yCONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=yCONFIG_IRQ_REMAP=yCONFIG_HYPERV_IOMMU=y
# CONFIG_VIRTIO_IOMMU is not set
#
# Remoteproc drivers
#
# CONFIG_REMOTEPROC is not set
# end of Remoteproc drivers
#
# Rpmsg drivers
#
# CONFIG_RPMSG_QCOM_GLINK_RPM is not set
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers
# CONFIG_SOUNDWIRE is not set
#
# SOC (System On Chip) specific Drivers
#
#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers
#
# Broadcom SoC drivers
#
# end of Broadcom SoC drivers
#
# NXP/Freescale QorIQ SoC drivers
#
# end of NXP/Freescale QorIQ SoC drivers
#
# i.MX SoC drivers
#
# end of i.MX SoC drivers
#
# Enable LiteX SoC Builder specific drivers
#
# end of Enable LiteX SoC Builder specific drivers
#
# Qualcomm SoC drivers
#
# end of Qualcomm SoC drivers
# CONFIG_SOC_TI is not set
#
# Xilinx SoC drivers
#
# end of Xilinx SoC drivers # end of SOC (System On Chip) specific Drivers
# CONFIG_PM_DEVFREQ is not set
# CONFIG_EXTCON is not set
# CONFIG_MEMORY is not set
# CONFIG_IIO is not setCONFIG_NTB=m
# CONFIG_NTB_MSI is not set
# CONFIG_NTB_AMD is not set
# CONFIG_NTB_IDT is not set
# CONFIG_NTB_INTEL is not set
# CONFIG_NTB_EPF is not set
# CONFIG_NTB_SWITCHTEC is not set
# CONFIG_NTB_PINGPONG is not set
# CONFIG_NTB_TOOL is not set
# CONFIG_NTB_PERF is not set
# CONFIG_NTB_TRANSPORT is not set
# CONFIG_VME_BUS is not setCONFIG_PWM=yCONFIG_PWM_SYSFS=y
# CONFIG_PWM_DEBUG is not set
# CONFIG_PWM_DWC is not setCONFIG_PWM_LPSS=mCONFIG_PWM_LPSS_PCI=mCONFIG_PWM_LPSS_PLATFORM=m
# CONFIG_PWM_PCA9685 is not set
#
# IRQ chip support
#
# end of IRQ chip support
# CONFIG_IPACK_BUS is not set
# CONFIG_RESET_CONTROLLER is not set
#
# PHY Subsystem
#
# CONFIG_GENERIC_PHY is not set
# CONFIG_USB_LGM_PHY is not set
# CONFIG_PHY_CAN_TRANSCEIVER is not set
#
# PHY drivers for Broadcom platforms
#
# CONFIG_BCM_KONA_USB2_PHY is not set
# end of PHY drivers for Broadcom platforms
# CONFIG_PHY_PXA_28NM_HSIC is not set
# CONFIG_PHY_PXA_28NM_USB2 is not set
# CONFIG_PHY_INTEL_LGM_EMMC is not set
# end of PHY Subsystem
CONFIG_POWERCAP=yCONFIG_INTEL_RAPL_CORE=mCONFIG_INTEL_RAPL=m
# CONFIG_IDLE_INJECT is not set
# CONFIG_DTPM is not set
# CONFIG_MCB is not set
#
# Performance monitor support
#
# end of Performance monitor support
CONFIG_RAS=y
# CONFIG_RAS_CEC is not set
# CONFIG_USB4 is not set
#
# Android
#CONFIG_ANDROID=y
# CONFIG_ANDROID_BINDER_IPC is not set
# end of Android
CONFIG_LIBNVDIMM=mCONFIG_BLK_DEV_PMEM=mCONFIG_ND_BLK=mCONFIG_ND_CLAIM=yCONFIG_ND_BTT=mCONFIG_BTT=yCONFIG_ND_PFN=mCONFIG_NVDIMM_PFN=yCONFIG_NVDIMM_DAX=yCONFIG_NVDIMM_KEYS=yCONFIG_DAX_DRIVER=yCONFIG_DAX=yCONFIG_DEV_DAX=mCONFIG_DEV_DAX_PMEM=mCONFIG_DEV_DAX_KMEM=mCONFIG_DEV_DAX_PMEM_COMPAT=mCONFIG_NVMEM=yCONFIG_NVMEM_SYSFS=y
# CONFIG_NVMEM_RMEM is not set
#
# HW tracing support
#CONFIG_STM=m
# CONFIG_STM_PROTO_BASIC is not set
# CONFIG_STM_PROTO_SYS_T is not setCONFIG_STM_DUMMY=mCONFIG_STM_SOURCE_CONSOLE=mCONFIG_STM_SOURCE_HEARTBEAT=mCONFIG_STM_SOURCE_FTRACE=mCONFIG_INTEL_TH=mCONFIG_INTEL_TH_PCI=mCONFIG_INTEL_TH_ACPI=mCONFIG_INTEL_TH_GTH=mCONFIG_INTEL_TH_STH=mCONFIG_INTEL_TH_MSU=mCONFIG_INTEL_TH_PTI=m
# CONFIG_INTEL_TH_DEBUG is not set
# end of HW tracing support
# CONFIG_FPGA is not set
# CONFIG_TEE is not set
# CONFIG_UNISYS_VISORBUS is not set
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
# CONFIG_COUNTER is not set
# CONFIG_MOST is not set
# end of Device Drivers
#
# File systems
#CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_VALIDATE_FS_PARSER is not set CONFIG_FS_IOMAP=y
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not setCONFIG_EXT4_FS=yCONFIG_EXT4_USE_FOR_EXT2=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not setCONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not setCONFIG_XFS_FS=mCONFIG_XFS_SUPPORT_V4=yCONFIG_XFS_QUOTA=yCONFIG_XFS_POSIX_ACL=yCONFIG_XFS_RT=yCONFIG_XFS_ONLINE_SCRUB=y
# CONFIG_XFS_ONLINE_REPAIR is not set CONFIG_XFS_DEBUG=yCONFIG_XFS_ASSERT_FATAL=yCONFIG_GFS2_FS=mCONFIG_GFS2_FS_LOCKING_DLM=y CONFIG_OCFS2_FS=mCONFIG_OCFS2_FS_O2CB=m CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m CONFIG_OCFS2_FS_STATS=y CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set CONFIG_BTRFS_FS=mCONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set # CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set # CONFIG_BTRFS_DEBUG is not set
# CONFIG_BTRFS_ASSERT is not set
# CONFIG_BTRFS_FS_REF_VERIFY is not set
# CONFIG_NILFS2_FS is not set CONFIG_F2FS_FS=mCONFIG_F2FS_STAT_FS=yCONFIG_F2FS_FS_XATTR=y CONFIG_F2FS_FS_POSIX_ACL=y
# CONFIG_F2FS_FS_SECURITY is not set
# CONFIG_F2FS_CHECK_FS is not set
# CONFIG_F2FS_FAULT_INJECTION is not set
# CONFIG_F2FS_FS_COMPRESSION is not set CONFIG_F2FS_IOSTAT=yCONFIG_FS_DAX=yCONFIG_FS_DAX_PMD=yCONFIG_FS_POSIX_ACL=yCONFIG_EXPORTFS=yCONFIG_EXPORTFS_BLOCK_OPS=y CONFIG_FILE_LOCKING=yCONFIG_FS_ENCRYPTION=y CONFIG_FS_ENCRYPTION_ALGS=y
# CONFIG_FS_VERITY is not set CONFIG_FSNOTIFY=yCONFIG_DNOTIFY=yCONFIG_INOTIFY_USER=yCONFIG_FANOTIFY=y CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not set CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not setCONFIG_QFMT_V2=yCONFIG_QUOTACTL=yCONFIG_AUTOFS4_FS=yCONFIG_AUTOFS_FS=yCONFIG_FUSE_FS=mCONFIG_CUSE=m
# CONFIG_VIRTIO_FS is not set CONFIG_OVERLAY_FS=m
# CONFIG_OVERLAY_FS_REDIRECT_DIR is not set
# CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW is not set # CONFIG_OVERLAY_FS_INDEX is not set
# CONFIG_OVERLAY_FS_XINO_AUTO is not set
# CONFIG_OVERLAY_FS_METACOPY is not set
#
# Caches
#CONFIG_NETFS_SUPPORT=mCONFIG_NETFS_STATS=yCONFIG_FSCACHE=mCONFIG_FSCACHE_STATS=y
# CONFIG_FSCACHE_DEBUG is not setCONFIG_CACHEFILES=m
# CONFIG_CACHEFILES_DEBUG is not set
# end of Caches
#
# CD-ROM/DVD Filesystems
#CONFIG_ISO9660_FS=mCONFIG_JOLIET=yCONFIG_ZISOFS=yCONFIG_UDF_FS=m
# end of CD-ROM/DVD Filesystems
#
# DOS/FAT/EXFAT/NT Filesystems
#CONFIG_FAT_FS=mCONFIG_MSDOS_FS=mCONFIG_VFAT_FS=mCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_FAT_DEFAULT_UTF8 is not set
# CONFIG_EXFAT_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS3_FS is not set
# end of DOS/FAT/EXFAT/NT Filesystems
#
# Pseudo filesystems
#CONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_PROC_VMCORE=y CONFIG_PROC_VMCORE_DEVICE_DUMP=y CONFIG_PROC_SYSCTL=yCONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_CHILDREN=y CONFIG_PROC_PID_ARCH_STATUS=y CONFIG_PROC_CPU_RESCTRL=yCONFIG_KERNFS=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_TMPFS_POSIX_ACL=yCONFIG_TMPFS_XATTR=y
# CONFIG_TMPFS_INODE64 is not set CONFIG_HUGETLBFS=yCONFIG_HUGETLB_PAGE=y CONFIG_HUGETLB_PAGE_FREE_VMEMMAP=y
# CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON is not set CONFIG_MEMFD_CREATE=y CONFIG_ARCH_HAS_GIGANTIC_PAGE=y CONFIG_CONFIGFS_FS=yCONFIG_EFIVAR_FS=y
# end of Pseudo filesystems
1,266 lines not shown · raw message
Part of this message is not shown here. View the raw message.
Paolo Bonzini
maintainerRe: [KVM] d3750a0923: WARNING:possible_circular_locking_dependency_detected
Quoted 6 lines · kernel test robot
Chain exists of: fs_reclaim --> mmu_notifier_invalidate_range_start --> &(kvm)->mmu_lock Possible unsafe locking scenario:
Quoted 7 lines
CPU0 CPU1 ---- ---- lock(&(kvm)->mmu_lock); lock(mmu_notifier_invalidate_range_start); lock(&(kvm)->mmu_lock);
lock(fs_reclaim);
David, this is yours; basically, kvm_mmu_topup_memory_cache must be called outside the mmu_lock.
Paolo
Re: [KVM] d3750a0923: WARNING:possible_circular_locking_dependency_detected
Quoted 16 lines · Paolo Bonzini
Quoted 6 lines · kernel test robot
Chain exists of: fs_reclaim --> mmu_notifier_invalidate_range_start --> &(kvm)->mmu_lock Possible unsafe locking scenario:Quoted 7 lines
CPU0 CPU1 ---- ---- lock(&(kvm)->mmu_lock); lock(mmu_notifier_invalidate_range_start); lock(&(kvm)->mmu_lock);
lock(fs_reclaim);
Quoted 2 lines
David, this is yours; basically,
kvm_mmu_topup_memory_cachemust be called outside themmu_lock.
Ah, I see. kvm_arch_mmu_enable_log_dirty_pt_masked is called with mmu_lock already held. I'll make sure to address this in v1. In theory this should just go away when I switch away from using split_caches to Sean's suggestion of allocating under the mmu_lock with reclaim disabled.
RFC PATCH 14/15 KVM: x86/mmu: Add tracepoint for splitting large pages
In reply to David MatlackAdd a tracepoint that records whenever we split a large page.
--- arch/x86/kvm/mmu/mmutrace.h | 20 ++++++++++++++++++++ arch/x86/kvm/mmu/tdp_mmu.c | 2 ++ 2 files changed, 22 insertions(+)
arch/x86/kvm/mmu/mmutrace.h +20 -0
@@ -416,6 +416,26 @@ TRACE_EVENT( ) ); +TRACE_EVENT ( + kvm_mmu_split_large_page, + TP_PROTO(u64 gfn, u64 spte, int level), +TP_ARGS (gfn, spte, level), + +TP_STRUCT__entry ( + __field(u64, gfn) + __field(u64, spte) +__field (int, level) + ), + +TP_fast_assign ( + __entry->gfn = gfn; + __entry->spte = spte; + __entry->level = level; + ), + +TP_printk ("gfn %llx spte %llx level %d" , __entry->gfn, __entry->spte, __entry->level) +); +#endif /* _TRACE_KVMMMU_H */ #undef TRACE_INCLUDE_PATH
arch/x86/kvm/mmu/tdp_mmu.c +2 -0
@@ -1284,6 +1284,8 @@ static bool tdp_mmu_split_large_page_atomic(struct kvm *kvm, struct tdp_iter *itBUG_ON (mmu_split_caches_need_topup (kvm)); +trace_kvm_mmu_split_large_page (iter->gfn, large_spte, level); + child_sp =alloc_child_tdp_mmu_page (&kvm->arch.split_caches, iter);for (i =0 ; i <PT64_ENT_PER_PAGE ; i++) {
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
RFC PATCH 15/15 KVM: x86/mmu: Update page stats when splitting large pages
In reply to David MatlackWhen splitting large pages we need to update the pages stats to reflect all of the new pages at the lower level. We do not need to change the page stats for the large page that was removed as that is already handled tdp_mmu_set_spte_atomic.
--- arch/x86/kvm/mmu/tdp_mmu.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
arch/x86/kvm/mmu/tdp_mmu.c +6 -1
@@ -1299,7 +1299,12 @@ static bool tdp_mmu_split_large_page_atomic(struct kvm *kvm, struct tdp_iter *it child_sp->spt[i] = child_spte; } -return tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false); +if (!tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false)) +return false; + +kvm_update_page_stats (kvm, level -1 ,PT64_ENT_PER_PAGE ); + +return true; } static void tdp_mmu_split_large_pages_root(struct kvm *kvm, struct kvm_mmu_page *root,
Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Sean Christopherson
maintainerRe: [RFC PATCH 15/15] KVM: x86/mmu: Update page stats when splitting large pages
Quoted 15 lines · David Matlack
When splitting large pages we need to update the pages stats to reflect all of the new pages at the lower level. We do not need to change the page stats for the large page that was removed as that is already handled
tdp_mmu_set_spte_atomic.Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)arch/x86/kvm/mmu/tdp_mmu.c +0
-0
arch/x86/kvm/mmu/tdp_mmu.c static bool tdp_mmu_split_large_page_atomic(struct kvm *kvm, struct tdp_iter *it · line 1305
Quoted 8 lines
arch/x86/kvm/mmu/tdp_mmu.c +4
-1@@ -1299,7 +1299,12 @@ static bool tdp_mmu_split_large_page_atomic(struct kvm *kvm, struct tdp_iter *it child_sp->spt[i] = child_spte; } -return tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false); +if (!tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false)) +return false; + +kvm_update_page_stats (kvm, level -1 ,PT64_ENT_PER_PAGE );
This should be done when tdp_mmu_split_large_page_atomic() is introduced, otherwise this series is effectively introducing a bug and then fixing it. At a very quick glance, I don't see anything that would prevent squashing this in.
Quoted 8 lines
arch/x86/kvm/mmu/tdp_mmu.c +2
-0+ +return true; } static void tdp_mmu_split_large_pages_root(struct kvm *kvm, struct kvm_mmu_page *root,Signature · 1 line
2.34.0.rc2.393.gf8c9666880-goog
Re: [RFC PATCH 15/15] KVM: x86/mmu: Update page stats when splitting large pages
Quoted 20 lines · Sean Christopherson
Quoted 18 lines · David Matlack
When splitting large pages we need to update the pages stats to reflect all of the new pages at the lower level. We do not need to change the page stats for the large page that was removed as that is already handled
tdp_mmu_set_spte_atomic.Signed-off-by David Matlack <[email protected]>--- arch/x86/kvm/mmu/tdp_mmu.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)arch/x86/kvm/mmu/tdp_mmu.c +0
-0@@ -1299,7 +1299,12 @@ static bool tdp_mmu_split_large_page_atomic(struct kvm *kvm, struct tdp_iter *it child_sp->spt[i] = child_spte; }
Quoted 9 lines
arch/x86/kvm/mmu/tdp_mmu.c static bool tdp_mmu_split_large_page_atomic(struct kvm *kvm, struct tdp_iter *it · line 1305
Quoted 5 lines
arch/x86/kvm/mmu/tdp_mmu.c +4
-1-return tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false); +if (!tdp_mmu_install_sp_atomic (kvm, iter, child_sp, false)) +return false; + +kvm_update_page_stats (kvm, level -1 ,PT64_ENT_PER_PAGE );This should be done when
tdp_mmu_split_large_page_atomic()is introduced, otherwise this series is effectively introducing a bug and then fixing it. At a very quick glance, I don't see anything that would prevent squashing this in.
Will do.
Quoted 9 lines
Quoted 9 lines
arch/x86/kvm/mmu/tdp_mmu.c +2
-1+ +return true; } static void tdp_mmu_split_large_pages_root(struct kvm *kvm, struct kvm_mmu_page *root, --2.34.0.rc2.393.gf8c9666880-goog
Hi, David,
Quoted 16 lines · David Matlack
This series is a first pass at implementing Eager Page Splitting for the TDP MMU. For context on the motivation and design of Eager Page Splitting, please see the RFC design proposal and discussion [1].
Paolo, I went ahead and added splitting in both the intially-all-set case (only splitting the region passed to
CLEAR_DIRTY_LOG) and the case where we are not using initially-all-set (splitting the entire memslot when dirty logging is enabled) to give you an idea of what both look like.Note: I will be on vacation all of next week so I will not be able to respond to reviews until Monday November 29. I thought it would be useful to seed discussion and reviews with an early version of the code rather than putting it off another week. But feel free to also ignore this until I get back :)
Quoted 8 lines
This series compiles and passes the most basic splitting test:
$ ./dirty_log_perf_test -s anonymous_hugetlb_2mb -v 2 -i 4But please operate under the assumption that this code is probably buggy.
[1] https://lore.kernel.org/kvm/CALzav=dV_U4r1K9oDq4esb4mpBQDQ2ROQ5zH5wV3KpOaZrRW-A@mail.gmail.com/#t
Will there be more numbers to show in the formal patchset? It's interesting to know how "First Pass Dirty Memory Time" will change comparing to the rfc numbers; I can have a feel of it, but still. :) Also, not only how it speedup guest dirty apps, but also some general measurement on how it slows down KVM_SET_USER_MEMORY_REGION (!init-all-set) or CLEAR_LOG (init-all-set) would be even nicer (for CLEAR, I guess the 1st/2nd+ round will have different overhead).
Besides that, I'm also wondering whether we should still have a knob for it, as I'm wondering what if the use case is the kind where eager split huge page may not help at all. What I'm thinking:
- Read-mostly guest overload; split huge page will speed up rare writes, but
at the meantime drag readers down due to huge->small page mappings.
- Writes-over-very-limited-region workload: say we have 1T guest and the app in the guest only writes 10G part of it. Hmm not sure whether it exists..
- Postcopy targeted: it means precopy may only run a few iterations just to send the static pages, so the migration duration will be relatively short, and the write just didn't spread a lot to the whole guest mem.
I don't really think any of the example is strong enough as they're all very corner cased, but just to show what I meant to raise this question on whether unconditionally eager split is the best approach.
Thanks,
Signature · 1 line
Peter Xu
Quoted 22 lines · Peter Xu
Hi, David,
Quoted 18 lines · David Matlack
This series is a first pass at implementing Eager Page Splitting for the TDP MMU. For context on the motivation and design of Eager Page Splitting, please see the RFC design proposal and discussion [1].
Paolo, I went ahead and added splitting in both the intially-all-set case (only splitting the region passed to
CLEAR_DIRTY_LOG) and the case where we are not using initially-all-set (splitting the entire memslot when dirty logging is enabled) to give you an idea of what both look like.Note: I will be on vacation all of next week so I will not be able to respond to reviews until Monday November 29. I thought it would be useful to seed discussion and reviews with an early version of the code rather than putting it off another week. But feel free to also ignore this until I get back :)
This series compiles and passes the most basic splitting test:
Quoted 8 lines
Quoted 6 lines
$ ./dirty_log_perf_test -s anonymous_hugetlb_2mb -v 2 -i 4But please operate under the assumption that this code is probably buggy.
[1] https://lore.kernel.org/kvm/CALzav=dV_U4r1K9oDq4esb4mpBQDQ2ROQ5zH5wV3KpOaZrRW-A@mail.gmail.com/#t
Will there be more numbers to show in the formal patchset?
Yes definitely. I didn't have a lot of time to test this series, hence the RFC status. I'll include more thorough testing and performance evaluation in the cover letter for v1.
Quoted 17 lines
It's interesting to
know how "First Pass Dirty Memory Time" will change comparing to the rfc numbers; I can have a feel of it, but still. :) Also, not only how it speedup guest dirty apps, but also some general measurement on how it slows downKVM_SET_USER_MEMORY_REGION(!init-all-set) orCLEAR_LOG(init-all-set) would be even nicer (for CLEAR, I guess the 1st/2nd+ round will have different overhead).Besides that, I'm also wondering whether we should still have a knob for it, as I'm wondering what if the use case is the kind where eager split huge page may not help at all. What I'm thinking:
- Read-mostly guest overload; split huge page will speed up rare writes, but
at the meantime drag readers down due to huge->small page mappings.- Writes-over-very-limited-region workload: say we have 1T guest and the app in the guest only writes 10G part of it. Hmm not sure whether it exists..
Quoted 7 lines
- Postcopy targeted: it means precopy may only run a few iterations just to send the static pages, so the migration duration will be relatively short, and the write just didn't spread a lot to the whole guest mem.
I don't really think any of the example is strong enough as they're all very corner cased, but just to show what I meant to raise this question on whether unconditionally eager split is the best approach.
I'd be happy to add a knob if there's a userspace that wants to use it. I think the main challenge though is knowing when it is safe to disable eager splitting. For a small deployment where you know the VM workload, it might make sense. But for a public cloud provider the only feasible way would be to dynamically monitor the guest writing patterns. But then we're back at square one because that would require dirty logging. And even then, there's no guaranteed way to predict future guest write patterns based on past patterns.
The way forward here might be to do a hybrid of 2M and 4K dirty tracking (and maybe even 1G). For example, first start dirty logging at 2M granularity, and then log at 4K for any specific regions or memslots that aren't making progress. We'd still use Eager Page Splitting unconditionally though, first to split to 2M and then to split to 4K.
Quoted 6 lines
Thanks,
--
Peter Xu
Quoted 58 lines · David Matlack
Quoted 22 lines · Peter Xu
Hi, David,
Quoted 18 lines · David Matlack
This series is a first pass at implementing Eager Page Splitting for the TDP MMU. For context on the motivation and design of Eager Page Splitting, please see the RFC design proposal and discussion [1].
Paolo, I went ahead and added splitting in both the intially-all-set case (only splitting the region passed to
CLEAR_DIRTY_LOG) and the case where we are not using initially-all-set (splitting the entire memslot when dirty logging is enabled) to give you an idea of what both look like.Note: I will be on vacation all of next week so I will not be able to respond to reviews until Monday November 29. I thought it would be useful to seed discussion and reviews with an early version of the code rather than putting it off another week. But feel free to also ignore this until I get back :)
This series compiles and passes the most basic splitting test:
Quoted 8 lines
Quoted 6 lines
$ ./dirty_log_perf_test -s anonymous_hugetlb_2mb -v 2 -i 4But please operate under the assumption that this code is probably buggy.
[1] https://lore.kernel.org/kvm/CALzav=dV_U4r1K9oDq4esb4mpBQDQ2ROQ5zH5wV3KpOaZrRW-A@mail.gmail.com/#t
Will there be more numbers to show in the formal patchset?
Yes definitely. I didn't have a lot of time to test this series, hence the RFC status. I'll include more thorough testing and performance evaluation in the cover letter for v1.
Quoted 21 lines
It's interesting to
know how "First Pass Dirty Memory Time" will change comparing to the rfc numbers; I can have a feel of it, but still. :) Also, not only how it speedup guest dirty apps, but also some general measurement on how it slows downKVM_SET_USER_MEMORY_REGION(!init-all-set) orCLEAR_LOG(init-all-set) would be even nicer (for CLEAR, I guess the 1st/2nd+ round will have different overhead).Besides that, I'm also wondering whether we should still have a knob for it, as I'm wondering what if the use case is the kind where eager split huge page may not help at all. What I'm thinking:
- Read-mostly guest overload; split huge page will speed up rare writes, but
at the meantime drag readers down due to huge->small page mappings.- Writes-over-very-limited-region workload: say we have 1T guest and the app in the guest only writes 10G part of it. Hmm not sure whether it exists..
- Postcopy targeted: it means precopy may only run a few iterations just to send the static pages, so the migration duration will be relatively short, and the write just didn't spread a lot to the whole guest mem.
Quoted 7 lines
Quoted 3 lines
I don't really think any of the example is strong enough as they're all very corner cased, but just to show what I meant to raise this question on whether unconditionally eager split is the best approach.
I'd be happy to add a knob if there's a userspace that wants to use it. I think the main challenge though is knowing when it is safe to disable eager splitting.
Isn't it a performance feature? Why it'll be not safe?
Quoted 5 lines
For a small deployment where you know the VM workload, it might make sense. But for a public cloud provider the only feasible way would be to dynamically monitor the guest writing patterns. But then we're back at square one because that would require dirty logging. And even then, there's no guaranteed way to predict future guest write patterns based on past patterns.
Agreed, what I was thinking was not for public cloud usages, but for the cases where we can do specific tunings on some specific scenarios. It normally won't matter a lot with small or medium sized VMs but extreme use cases.
Quoted 7 lines
The way forward here might be to do a hybrid of 2M and 4K dirty tracking (and maybe even 1G). For example, first start dirty logging at 2M granularity, and then log at 4K for any specific regions or memslots that aren't making progress. We'd still use Eager Page Splitting unconditionally though, first to split to 2M and then to split to 4K.
Do you mean we'd also offer different granule dirty bitmap to the userspace too?
I remembered you mentioned 2mb dirty tracking in your rfc series, but I didn't expect it can be dynamically switched during tracking. That sounds a very intersting idea.
Thanks,
Signature · 1 line
Peter Xu
Quoted 75 lines · Peter Xu
Quoted 58 lines · David Matlack
Quoted 22 lines · Peter Xu
Hi, David,
Quoted 18 lines · David Matlack
This series is a first pass at implementing Eager Page Splitting for the TDP MMU. For context on the motivation and design of Eager Page Splitting, please see the RFC design proposal and discussion [1].
Paolo, I went ahead and added splitting in both the intially-all-set case (only splitting the region passed to
CLEAR_DIRTY_LOG) and the case where we are not using initially-all-set (splitting the entire memslot when dirty logging is enabled) to give you an idea of what both look like.Note: I will be on vacation all of next week so I will not be able to respond to reviews until Monday November 29. I thought it would be useful to seed discussion and reviews with an early version of the code rather than putting it off another week. But feel free to also ignore this until I get back :)
This series compiles and passes the most basic splitting test:
Quoted 8 lines
Quoted 6 lines
$ ./dirty_log_perf_test -s anonymous_hugetlb_2mb -v 2 -i 4But please operate under the assumption that this code is probably buggy.
[1] https://lore.kernel.org/kvm/CALzav=dV_U4r1K9oDq4esb4mpBQDQ2ROQ5zH5wV3KpOaZrRW-A@mail.gmail.com/#t
Will there be more numbers to show in the formal patchset?
Yes definitely. I didn't have a lot of time to test this series, hence the RFC status. I'll include more thorough testing and performance evaluation in the cover letter for v1.
Quoted 21 lines
It's interesting to
know how "First Pass Dirty Memory Time" will change comparing to the rfc numbers; I can have a feel of it, but still. :) Also, not only how it speedup guest dirty apps, but also some general measurement on how it slows downKVM_SET_USER_MEMORY_REGION(!init-all-set) orCLEAR_LOG(init-all-set) would be even nicer (for CLEAR, I guess the 1st/2nd+ round will have different overhead).Besides that, I'm also wondering whether we should still have a knob for it, as I'm wondering what if the use case is the kind where eager split huge page may not help at all. What I'm thinking:
- Read-mostly guest overload; split huge page will speed up rare writes, but
at the meantime drag readers down due to huge->small page mappings.- Writes-over-very-limited-region workload: say we have 1T guest and the app in the guest only writes 10G part of it. Hmm not sure whether it exists..
- Postcopy targeted: it means precopy may only run a few iterations just to send the static pages, so the migration duration will be relatively short, and the write just didn't spread a lot to the whole guest mem.
Quoted 7 lines
Quoted 3 lines
I don't really think any of the example is strong enough as they're all very corner cased, but just to show what I meant to raise this question on whether unconditionally eager split is the best approach.
I'd be happy to add a knob if there's a userspace that wants to use it. I think the main challenge though is knowing when it is safe to disable eager splitting.
Isn't it a performance feature? Why it'll be not safe?
Quoted 5 lines
For a small deployment where you know the VM workload, it might make sense. But for a public cloud provider the only feasible way would be to dynamically monitor the guest writing patterns. But then we're back at square one because that would require dirty logging. And even then, there's no guaranteed way to predict future guest write patterns based on past patterns.
Quoted 3 lines
Agreed, what I was thinking was not for public cloud usages, but for the cases where we can do specific tunings on some specific scenarios. It normally won't matter a lot with small or medium sized VMs but extreme use cases.
PS: I think even with a tunable, one static per-module parameter should be far enough for what I can imagine for now.
Quoted 20 lines
Quoted 8 lines
The way forward here might be to do a hybrid of 2M and 4K dirty tracking (and maybe even 1G). For example, first start dirty logging at 2M granularity, and then log at 4K for any specific regions or memslots that aren't making progress. We'd still use Eager Page Splitting unconditionally though, first to split to 2M and then to split to 4K.
Do you mean we'd also offer different granule dirty bitmap to the userspace too?
I remembered you mentioned 2mb dirty tracking in your rfc series, but I didn't expect it can be dynamically switched during tracking. That sounds a very intersting idea.
Thanks,
Signature · 1 line
Peter Xu
Signature · 1 line
Peter Xu
Quoted 64 lines · Peter Xu
Quoted 62 lines · David Matlack
Quoted 22 lines · Peter Xu
Hi, David,
Quoted 18 lines · David Matlack
This series is a first pass at implementing Eager Page Splitting for the TDP MMU. For context on the motivation and design of Eager Page Splitting, please see the RFC design proposal and discussion [1].
Paolo, I went ahead and added splitting in both the intially-all-set case (only splitting the region passed to
CLEAR_DIRTY_LOG) and the case where we are not using initially-all-set (splitting the entire memslot when dirty logging is enabled) to give you an idea of what both look like.Note: I will be on vacation all of next week so I will not be able to respond to reviews until Monday November 29. I thought it would be useful to seed discussion and reviews with an early version of the code rather than putting it off another week. But feel free to also ignore this until I get back :)
This series compiles and passes the most basic splitting test:
Quoted 8 lines
Quoted 6 lines
$ ./dirty_log_perf_test -s anonymous_hugetlb_2mb -v 2 -i 4But please operate under the assumption that this code is probably buggy.
[1] https://lore.kernel.org/kvm/CALzav=dV_U4r1K9oDq4esb4mpBQDQ2ROQ5zH5wV3KpOaZrRW-A@mail.gmail.com/#t
Will there be more numbers to show in the formal patchset?
Yes definitely. I didn't have a lot of time to test this series, hence the RFC status. I'll include more thorough testing and performance evaluation in the cover letter for v1.
Quoted 24 lines
It's interesting to
know how "First Pass Dirty Memory Time" will change comparing to the rfc numbers; I can have a feel of it, but still. :) Also, not only how it speedup guest dirty apps, but also some general measurement on how it slows downKVM_SET_USER_MEMORY_REGION(!init-all-set) orCLEAR_LOG(init-all-set) would be even nicer (for CLEAR, I guess the 1st/2nd+ round will have different overhead).Besides that, I'm also wondering whether we should still have a knob for it, as I'm wondering what if the use case is the kind where eager split huge page may not help at all. What I'm thinking:
- Read-mostly guest overload; split huge page will speed up rare writes, but
at the meantime drag readers down due to huge->small page mappings.- Writes-over-very-limited-region workload: say we have 1T guest and the app in the guest only writes 10G part of it. Hmm not sure whether it exists..
- Postcopy targeted: it means precopy may only run a few iterations just to send the static pages, so the migration duration will be relatively short, and the write just didn't spread a lot to the whole guest mem.
I don't really think any of the example is strong enough as they're all very corner cased, but just to show what I meant to raise this question on whether unconditionally eager split is the best approach.
Quoted 5 lines
Quoted 3 lines
I'd be happy to add a knob if there's a userspace that wants to use it. I think the main challenge though is knowing when it is safe to disable eager splitting.
Isn't it a performance feature? Why it'll be not safe?
Heh, "safe" is a bit overzealous. But we've found that as the vCPU count scales in VMs, not doing Eager Page Splitting leads to unacceptable performance degradations (per customers), especially when using the shadow MMU where hugepage write-protection faults are done while holding the MMU lock in write mode. So from that perspective, it's "unsafe" to skip Eager Page Splitting unless you are absolutely sure the guest workload will not be doing much writes.
Quoted 10 lines
Quoted 6 lines
For a small deployment where you know the VM workload, it might make sense. But for a public cloud provider the only feasible way would be to dynamically monitor the guest writing patterns. But then we're back at square one because that would require dirty logging. And even then, there's no guaranteed way to predict future guest write patterns based on past patterns.
Agreed, what I was thinking was not for public cloud usages, but for the cases where we can do specific tunings on some specific scenarios. It normally won't matter a lot with small or medium sized VMs but extreme use cases.
Ack. I'll include a module parameter in v1 like you suggested your other email.
Quoted 11 lines
Quoted 8 lines
The way forward here might be to do a hybrid of 2M and 4K dirty tracking (and maybe even 1G). For example, first start dirty logging at 2M granularity, and then log at 4K for any specific regions or memslots that aren't making progress. We'd still use Eager Page Splitting unconditionally though, first to split to 2M and then to split to 4K.
Do you mean we'd also offer different granule dirty bitmap to the userspace too?
Perhaps. The 2M dirty tracking work is still in very early research phases and the first version will likely not be so dynamic. But I could imagine we eventually get to the point where we are doing some hybrid approach.
Quoted 6 lines
I remembered you mentioned 2mb dirty tracking in your rfc series, but I didn't expect it can be dynamically switched during tracking. That sounds a very intersting idea.
Thanks,
Thanks for all the reviews and feedback on this series!
Quoted 4 lines
--
Peter Xu