KVM: arm64: Eager Huge-page splitting for dirty-logging
cover KVM: arm64: Eager Huge-page splitting for dirty-logging
Implement Eager Page Splitting for ARM.
Eager Page Splitting improves the performance of dirty-logging (used in live migrations) when guest memory is backed by huge-pages. It's an optimization used in Google Cloud since 2016 on x86, and for the last couple of months on ARM.
Background and motivation
=========================
Dirty logging is typically used for live-migration iterative copying. KVM implements dirty-logging at the PAGE_SIZE granularity (will refer to 4K pages from now on). It does it by faulting on write-protected 4K pages. Therefore, enabling dirty-logging on a huge-page requires breaking it into 4K pages in the first place. KVM does this breaking on fault, and because it's in the critical path it only maps the 4K page that faulted; every other 4K page is left unmapped. This is not great for performance on ARM for a couple of reasons:
- Splitting on fault can halt vcpus for milliseconds in some implementations. Splitting a block PTE requires using a broadcasted TLB invalidation (TLBI) for every huge-page (due to the break-before-make requirement). Note that x86 doesn't need this. We observed some implementations that take millliseconds to complete broadcasted TLBIs when done in parallel from multiple vcpus. And that's exactly what happens when doing it on fault: multiple vcpus fault at the same time triggering TLBIs in parallel.
- Read intensive guest workloads end up paying for dirty-logging. Only mapping the faulting 4K page means that all the other pages that were part of the huge-page will now be unmapped. The effect is that any access, including reads, now has to fault.
Eager Page Splitting (on ARM)
=============================
Eager Page Splitting fixes the above two issues by eagerly splitting huge-pages when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages. This is what the TDP MMU does for x86 [0], except that x86 does it for different reasons: to avoid grabbing the MMU lock on fault. Note that taking care of write-protection faults still requires grabbing the MMU lock on ARM, but not on x86 (with the fast_page_fault path).
An additional benefit of eagerly splitting huge-pages is that it can be done in a controlled way (e.g., via an IOCTL). This series provides two knobs for doing it, just like its x86 counterpart: when enabling dirty logging, and when using the KVM_CLEAR_DIRTY_LOG ioctl. The benefit of doing it on KVM_CLEAR_DIRTY_LOG is that this ioctl takes ranges, and not complete memslots like when enabling dirty logging. This means that the cost of splitting (mainly broadcasted TLBIs) can be throttled: split a range, wait for a bit, split another range, etc. The benefits of this approach were presented by Oliver Upton at KVM Forum 2022 [1].
Implementation
==============
Patches 1-3 add a pgtable utility function for splitting huge block
PTEs: kvm_pgtable_stage2_split(). Patches 4-8 add support for eagerly splitting huge-pages when enabling dirty-logging and when using the KVM_CLEAR_DIRTY_LOG ioctl. Note that this is just like what x86 does, and the code is actually based on it. And finally, patch 9:
KVM: arm64: Use local TLBI on permission relaxation
adds support for using local TLBIs instead of broadcasts when doing permission relaxation. This last patch is key to achieving good performance during dirty-logging, as eagerly breaking huge-pages replaces mapping new pages with permission relaxation. Got this patch (indirectly) from Marc Z. and took the liberty of adding a commit message.
Note: this applies on top of 6.2-rc3.
Performance evaluation
======================
The performance benefits were tested using the dirty_log_perf_test selftest with 2M huge-pages.
The first test uses a write-only sequential workload where the stride is 2M instead of 4K [2]. The idea with this experiment is to emulate a random access pattern writing a different huge-page at every access. Observe that the benefit increases with the number of vcpus: up to 5.76x for 152 vcpus.
./dirty_log_perf_test_sparse -s anonymous_hugetlb_2mb -b 1G -v $i -i 3 -m 2
+-------+----------+------------------+ | vCPUs | 6.2-rc3 | 6.2-rc3 + series | | | (ms) | (ms) | +-------+----------+------------------+ | 1 | 2.63 | 1.66 | | 2 | 2.95 | 1.70 | | 4 | 3.21 | 1.71 | | 8 | 4.97 | 1.78 | | 16 | 9.51 | 1.82 | | 32 | 20.15 | 3.03 | | 64 | 40.09 | 5.80 | | 128 | 80.08 | 12.24 | | 152 | 109.81 | 15.14 | +-------+----------+------------------+
This second test measures the benefit of eager page splitting on read intensive workloads (1 write for every 10 reads). As in the other test, the benefit increases with the number of vcpus, up to 8.82x for 152 vcpus.
./dirty_log_perf_test -s anonymous_hugetlb_2mb -b 1G -v $i -i 3 -m 2 -f 10
+-------+----------+------------------+ | vCPUs | 6.2-rc3 | 6.2-rc3 + series | | | (sec) | (sec) | +-------+----------+------------------+ | 1 | 0.65 | 0.07 | | 2 | 0.70 | 0.08 | | 4 | 0.71 | 0.08 | | 8 | 0.72 | 0.08 | | 16 | 0.76 | 0.08 | | 32 | 1.61 | 0.14 | | 64 | 3.46 | 0.30 | | 128 | 5.49 | 0.64 | | 152 | 6.44 | 0.63 | +-------+----------+------------------+
Changes from the RFC:
https://lore.kernel.org/kvmarm/[email protected]/
- dropped the changes to split on POST visits. No visible perf benefit.
- changed the kvm_pgtable_stage2_free_removed() implementation to reuse the stage2 mapper.
- dropped the FEAT_BBM changes and optimization. Will send this on a different series.
Thanks,
Ricardo
[0] https://lore.kernel.org/kvm/[email protected]/
[1] https://kvmforum2022.sched.com/event/15jJq/kvmarm-at-scale-improvements-to-the-mmu-in-the-face-of-hardware-growing-pains-oliver-upton-google
[2] https://github.com/ricarkol/linux/commit/f78e9102b2bff4fb7f30bee810d7d611a537b46d
[3] https://lore.kernel.org/kvmarm/[email protected]/
Marc Zyngier (1):
KVM: arm64: Use local TLBI on permission relaxation
Ricardo Koller (8):
KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
KVM: arm64: Add helper for creating removed stage2 subtrees
KVM: arm64: Add kvm_pgtable_stage2_split()
KVM: arm64: Refactor kvm_arch_commit_memory_region()
KVM: arm64: Add kvm_uninit_stage2_mmu()
KVM: arm64: Split huge pages when dirty logging is enabled
KVM: arm64: Open-code kvm_mmu_write_protect_pt_masked()
KVM: arm64: Split huge pages during KVM_CLEAR_DIRTY_LOG
arch/arm64/include/asm/kvm_asm.h | 4 + arch/arm64/include/asm/kvm_host.h | 30 +++++ arch/arm64/include/asm/kvm_mmu.h | 1 + arch/arm64/include/asm/kvm_pgtable.h | 62 ++++++++++ arch/arm64/kvm/hyp/nvhe/hyp-main.c | 10 ++ arch/arm64/kvm/hyp/nvhe/tlb.c | 54 +++++++++ arch/arm64/kvm/hyp/pgtable.c | 143 +++++++++++++++++++++-- arch/arm64/kvm/hyp/vhe/tlb.c | 32 +++++ arch/arm64/kvm/mmu.c | 168 ++++++++++++++++++++++----- 9 files changed, 466 insertions(+), 38 deletions(-)
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
PATCH 1/9 KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
Add a flag to kvm_pgtable_visit_ctx, KVM_PGTABLE_WALK_REMOVED, to indicate that the walk is on a removed table not accesible to the HW page-table walker. Then use it to avoid doing break-before-make or performing CMOs (Cache Maintenance Operations) when mapping a removed table. This is safe as these removed tables are not visible to the HW page-table walker. This will be used in a subsequent commit for replacing huge-page block PTEs into tables of 4K PTEs.
--- arch/arm64/include/asm/kvm_pgtable.h | 8 ++++++++ arch/arm64/kvm/hyp/pgtable.c | 27 ++++++++++++++++----------- 2 files changed, 24 insertions(+), 11 deletions(-)
arch/arm64/include/asm/kvm_pgtable.h +8 -0
@@ -188,12 +188,15 @@ typedef bool (*kvm_pgtable_force_pte_cb_t)(u64 addr, u64 end,* children. * @KVM_PGTABLE_WALK_SHARED: Indicates the page-tables may be shared * with other software walkers. +* @KVM_PGTABLE_WALK_REMOVED: Indicates the page-tables are +* removed: not visible to the HW walker. */ enum kvm_pgtable_walk_flags {KVM_PGTABLE_WALK_LEAF =BIT (0 ),KVM_PGTABLE_WALK_TABLE_PRE =BIT (1 ),KVM_PGTABLE_WALK_TABLE_POST =BIT (2 ),KVM_PGTABLE_WALK_SHARED =BIT (3 ), +KVM_PGTABLE_WALK_REMOVED =BIT (4 ), };struct kvm_pgtable_visit_ctx {
@@ -215,6 +218,11 @@ static inline bool kvm_pgtable_walk_shared(const struct kvm_pgtable_visit_ctx *creturn ctx->flags &KVM_PGTABLE_WALK_SHARED ; } +static inline bool kvm_pgtable_walk_removed (const struct kvm_pgtable_visit_ctx *ctx) +{ +return ctx->flags &KVM_PGTABLE_WALK_REMOVED ; +} +/** * struct kvm_pgtable_walker - Hook into a page-table walk. * @cb: Callback function to invoke during the walk.
arch/arm64/kvm/hyp/pgtable.c +16 -11
@@ -717,14 +717,17 @@ static bool stage2_try_break_pte(const struct kvm_pgtable_visit_ctx *ctx,if (!stage2_try_set_pte (ctx,KVM_INVALID_PTE_LOCKED ))return false; -/* -* Perform the appropriate TLB invalidation based on the evicted pte -* value (if any). -*/ -if (kvm_pte_table (ctx->old, ctx->level)) -kvm_call_hyp (__kvm_tlb_flush_vmid, mmu); -else if (kvm_pte_valid (ctx->old)) -kvm_call_hyp (__kvm_tlb_flush_vmid_ipa, mmu, ctx->addr, ctx->level); +if (!kvm_pgtable_walk_removed (ctx)) { +/* +* Perform the appropriate TLB invalidation based on the +* evicted pte value (if any). +*/ +if (kvm_pte_table (ctx->old, ctx->level)) +kvm_call_hyp (__kvm_tlb_flush_vmid, mmu); +else if (kvm_pte_valid (ctx->old)) +kvm_call_hyp (__kvm_tlb_flush_vmid_ipa, mmu, + ctx->addr, ctx->level); + }if (stage2_pte_is_counted (ctx->old)) mm_ops->put_page (ctx->ptep);
@@ -808,11 +811,13 @@ static int stage2_map_walker_try_leaf(const struct kvm_pgtable_visit_ctx *ctx,return -EAGAIN ;/* Perform CMOs before installation of the guest stage-2 PTE */ -if (mm_ops->dcache_clean_inval_poc &&stage2_pte_cacheable (pgt, new)) +if (!kvm_pgtable_walk_removed (ctx) && mm_ops->dcache_clean_inval_poc && +stage2_pte_cacheable (pgt, new)) mm_ops->dcache_clean_inval_poc (kvm_pte_follow (new, mm_ops), - granule); + granule); -if (mm_ops->icache_inval_pou &&stage2_pte_executable (new)) +if (!kvm_pgtable_walk_removed (ctx) && mm_ops->icache_inval_pou && +stage2_pte_executable (new)) mm_ops->icache_inval_pou (kvm_pte_follow (new, mm_ops), granule);stage2_make_pte (ctx, new);
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
Re: [PATCH 1/9] KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
Quoted 5 lines · Ricardo Koller
Add a flag to
kvm_pgtable_visit_ctx,KVM_PGTABLE_WALK_REMOVED, to indicate that the walk is on a removed table not accesible to the HW page-table walker. Then use it to avoid doing break-before-make or performing CMOs (Cache Maintenance Operations) when mapping a removed
Nit: Should this say unmapping? Or are we actually going to use this to map memory ?
Quoted 2 lines
table. This is safe as these removed tables are not visible to the HW page-table walker. This will be used in a subsequent commit for
...
Re: [PATCH 1/9] KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
Quoted 9 lines · Ben Gardon
Quoted 5 lines · Ricardo Koller
Add a flag to
kvm_pgtable_visit_ctx,KVM_PGTABLE_WALK_REMOVED, to indicate that the walk is on a removed table not accesible to the HW page-table walker. Then use it to avoid doing break-before-make or performing CMOs (Cache Maintenance Operations) when mapping a removedNit: Should this say unmapping? Or are we actually going to use this to map memory ?
I think the *_REMOVED term feels weird as it relates to constructing a page table. It'd be better if we instead added flags to describe the operations we intend to elide (i.e. CMOs and TLBIs). That way the implementation is generic enough that we can repurpose it for other use cases.
--
Thanks,
Oliver
Re: [PATCH 1/9] KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
Quoted 8 lines · Oliver Upton
Quoted 7 lines · Ben Gardon
Quoted 5 lines · Ricardo Koller
Add a flag to
kvm_pgtable_visit_ctx,KVM_PGTABLE_WALK_REMOVED, to indicate that the walk is on a removed table not accesible to the HW page-table walker. Then use it to avoid doing break-before-make or performing CMOs (Cache Maintenance Operations) when mapping a removed
Quoted 6 lines
Quoted 2 lines
Nit: Should this say unmapping? Or are we actually going to use this to map memory ?
I think the
*_REMOVEDterm feels weird as it relates to constructing a page table. It'd be better if we instead added flags to describe the operations we intend to elide (i.e. CMOs and TLBIs).
What about KVM_PGTABLE_WALK_ELIDE_BBM and KVM_PGTABLE_WALK_ELIDE_CMO?
Quoted 3 lines
That way the
implementation is generic enough that we can repurpose it for other use cases.
Aha, good point. I actually have a use case for it (FEAT_BBM).
Quoted 4 lines
--
Thanks,
Oliver
Re: [PATCH 1/9] KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
Quoted 10 lines · Ricardo Koller
Quoted 8 lines · Oliver Upton
Quoted 7 lines · Ben Gardon
Quoted 5 lines · Ricardo Koller
Add a flag to
kvm_pgtable_visit_ctx,KVM_PGTABLE_WALK_REMOVED, to indicate that the walk is on a removed table not accesible to the HW page-table walker. Then use it to avoid doing break-before-make or performing CMOs (Cache Maintenance Operations) when mapping a removed
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Nit: Should this say unmapping? Or are we actually going to use this to map memory ?
I think the
*_REMOVEDterm feels weird as it relates to constructing a page table. It'd be better if we instead added flags to describe the operations we intend to elide (i.e. CMOs and TLBIs).What about
KVM_PGTABLE_WALK_ELIDE_BBMandKVM_PGTABLE_WALK_ELIDE_CMO?
I like this, but please don't use elide in the code. I'm all for vocabulary, but that's not a common enough word to expect everyone to know. Perhaps just SKIP?
Quoted 11 lines
Quoted 4 lines
That way the
implementation is generic enough that we can repurpose it for other use cases.Aha, good point. I actually have a use case for it (
FEAT_BBM).Quoted 4 lines
--
Thanks,
Oliver
Re: [PATCH 1/9] KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
Quoted 19 lines · Ben Gardon
Quoted 17 lines · Ricardo Koller
Quoted 14 lines · Oliver Upton
Quoted 9 lines · Ben Gardon
Quoted 5 lines · Ricardo Koller
Add a flag to
kvm_pgtable_visit_ctx,KVM_PGTABLE_WALK_REMOVED, to indicate that the walk is on a removed table not accesible to the HW page-table walker. Then use it to avoid doing break-before-make or performing CMOs (Cache Maintenance Operations) when mapping a removedNit: Should this say unmapping? Or are we actually going to use this to map memory ?
I think the
*_REMOVEDterm feels weird as it relates to constructing a page table. It'd be better if we instead added flags to describe the operations we intend to elide (i.e. CMOs and TLBIs).
Quoted 5 lines
Quoted 1 line
What about
KVM_PGTABLE_WALK_ELIDE_BBMandKVM_PGTABLE_WALK_ELIDE_CMO?I like this, but please don't use elide in the code. I'm all for vocabulary, but that's not a common enough word to expect everyone to know. Perhaps just SKIP?
No problem, SKIP should be fine.
Quoted 12 lines
Quoted 12 lines
Quoted 5 lines
That way the
implementation is generic enough that we can repurpose it for other use cases.Aha, good point. I actually have a use case for it (
FEAT_BBM).Quoted 4 lines
--
Thanks,
Oliver
Re: [PATCH 1/9] KVM: arm64: Add KVM_PGTABLE_WALK_REMOVED into ctx->flags
In reply to Ben GardonQuoted 9 lines · Ben Gardon
Quoted 5 lines · Ricardo Koller
Add a flag to
kvm_pgtable_visit_ctx,KVM_PGTABLE_WALK_REMOVED, to indicate that the walk is on a removed table not accesible to the HW page-table walker. Then use it to avoid doing break-before-make or performing CMOs (Cache Maintenance Operations) when mapping a removedNit: Should this say unmapping? Or are we actually going to use this to map memory ?
As you mentioned in the next commit, this will be clearer if I use "unliked" instead of "removed". Might end up rewriting this message as well, as I will be using Oliver's suggestion of using multiple flags, one for each operation to elide.
Quoted 4 lines
Quoted 3 lines
table. This is safe as these removed tables are not visible to the HW page-table walker. This will be used in a subsequent commit for
...
PATCH 2/9 KVM: arm64: Add helper for creating removed stage2 subtrees
In reply to Ricardo KollerAdd a stage2 helper, kvm_pgtable_stage2_create_removed(), for creating removed tables (the opposite of kvm_pgtable_stage2_free_removed()). Creating a removed table is useful for splitting block PTEs into subtrees of 4K PTEs. For example, a 1G block PTE can be split into 4K PTEs by first creating a fully populated tree, and then use it to replace the 1G PTE in a single step. This will be used in a subsequent commit for eager huge-page splitting (a dirty-logging optimization).
No functional change intended. This new function will be used in a subsequent commit.
--- arch/arm64/include/asm/kvm_pgtable.h | 25 +++++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 47 ++++++++++++++++++++++++++++ 2 files changed, 72 insertions(+)
arch/arm64/include/asm/kvm_pgtable.h +25 -0
@@ -450,6 +450,31 @@ void kvm_pgtable_stage2_destroy(struct kvm_pgtable *pgt);*/ void kvm_pgtable_stage2_free_removed (struct kvm_pgtable_mm_ops *mm_ops,void *pgtable,u32 level); +/** +* kvm_pgtable_stage2_free_removed() - Create a removed stage-2 paging structure. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @new: Unlinked stage-2 paging structure to be created. +* @phys: Physical address of the memory to map. +* @level: Level of the stage-2 paging structure to be created. +* @prot: Permissions and attributes for the mapping. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* Create a removed page-table tree of PAGE_SIZE leaf PTEs under *new. +* This new page-table tree is not reachable (i.e., it is removed) from the +* root pgd and it's therefore unreachableby the hardware page-table +* walker. No TLB invalidation or CMOs are performed. +* +* If device attributes are not explicitly requested in @prot, then the +* mapping will be normal, cacheable. +* +* Return: 0 only if a fully populated tree was created, negative error +* code on failure. No partially-populated table can be returned. +*/ +int kvm_pgtable_stage2_create_removed (struct kvm_pgtable *pgt, +kvm_pte_t *new,u64 phys,u32 level, +enum kvm_pgtable_prot prot,void *mc); +/** * kvm_pgtable_stage2_map() - Install a mapping in a guest stage-2 page-table. * @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*().
arch/arm64/kvm/hyp/pgtable.c +47 -0
53 lines not on this page · raw message
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
kernel test robot
build botRe: [PATCH 2/9] KVM: arm64: Add helper for creating removed stage2 subtrees
Thank you for the patch! Perhaps something to improve:
Hi Ricardo,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on kvmarm/next]
[also build test WARNING on kvm/queue mst-vhost/linux-next linus/master v6.2-rc3 next-20230113] [cannot apply to kvm/linux-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ricardo-Koller/KVM-arm64-Add-KVM_PGTABLE_WALK_REMOVED-into-ctx-flags/20230113-115135 base: https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git next patch link: https://lore.kernel.org/r/20230113035000.480021-3-ricarkol%40google.com patch subject: [PATCH 2/9] KVM: arm64: Add helper for creating removed stage2 subtrees config: arm64-randconfig-s053-20230113 compiler: aarch64-linux-gcc (GCC) 12.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel-lab-lkp/linux/commit/0ab9076ff1dc0b5c4533bb211466a1c515373034
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Ricardo-Koller/KVM-arm64-Add-KVM_PGTABLE_WALK_REMOVED-into-ctx-flags/20230113-115135
git checkout 0ab9076ff1dc0b5c4533bb211466a1c515373034
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 olddefconfig COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/kvm/hyp/
If you fix the issue, kindly add following tag where applicable | Reported-by: kernel test robot <[email protected]>
sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/hyp/pgtable.c:1221:49: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected unsigned long long [noderef] [usertype] __rcu *[usertype] pgtable @@ got unsigned long long [usertype] *[assigned] pgtable @@
arch/arm64/kvm/hyp/pgtable.c:1221:49: sparse: expected unsigned long long [noderef] [usertype] __rcu *[usertype] pgtable
arch/arm64/kvm/hyp/pgtable.c:1221:49: sparse: got unsigned long long [usertype] *[assigned] pgtable
arch/arm64/kvm/hyp/pgtable.c:270:5: sparse: sparse: context imbalance in 'kvm_pgtable_walk' - different lock contexts for basic block
vim +1221 arch/arm64/kvm/hyp/pgtable.c
1183
1184 /*
1185 * map_data->force_pte is true in order to force creating PAGE_SIZE PTEs.
1186 * data->addr is 0 because the IPA is irrelevant for a removed table.
1187 */
1188 int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt,
1189 kvm_pte_t *new, u64 phys, u32 level,
1190 enum kvm_pgtable_prot prot, void *mc)
1191 {
1192 struct stage2_map_data map_data = {
1193 .phys = phys,
1194 .mmu = pgt->mmu,
1195 .memcache = mc,
1196 .force_pte = true,
1197 };
1198 struct kvm_pgtable_walker walker = {
1199 .cb = stage2_map_walker,
1200 .flags = KVM_PGTABLE_WALK_LEAF |
1201 KVM_PGTABLE_WALK_REMOVED,
1202 .arg = &map_data,
1203 };
1204 struct kvm_pgtable_walk_data data = {
1205 .walker = &walker,
1206 .addr = 0,
1207 .end = kvm_granule_size(level),
1208 };
1209 struct kvm_pgtable_mm_ops *mm_ops = pgt->mm_ops;
1210 kvm_pte_t *pgtable;
1211 int ret;
1212
1213 ret = stage2_set_prot_attr(pgt, prot, &map_data.attr);
1214 if (ret)
1215 return ret;
1216
1217 pgtable = mm_ops->zalloc_page(mc);
1218 if (!pgtable)
1219 return -ENOMEM;
1220
> 1221 ret = __kvm_pgtable_walk(&data, mm_ops, pgtable, level + 1);
1222 if (ret) {
1223 kvm_pgtable_stage2_free_removed(mm_ops, pgtable, level);
1224 mm_ops->put_page(pgtable);
1225 return ret;
1226 }
1227
1228 *new = kvm_init_table_pte(pgtable, mm_ops);
1229 return 0;
1230 }
1231
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests
#
# Automatically generated file; DO NOT EDIT.
# Linux/arm64 6.1.0-rc4 Kernel Configuration
#CONFIG_CC_VERSION_TEXT="aarch64-linux-gcc (GCC) 12.1.0" CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=120100 CONFIG_CLANG_VERSION=0CONFIG_AS_IS_GNU=yCONFIG_AS_VERSION=23800CONFIG_LD_IS_BFD=yCONFIG_LD_VERSION=23800CONFIG_LLD_VERSION=0 CONFIG_CC_HAS_ASM_GOTO_OUTPUT=y CONFIG_CC_HAS_ASM_INLINE=y CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y CONFIG_PAHOLE_VERSION=123CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_TABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32CONFIG_COMPILE_TEST=y
# CONFIG_WERROR is not setCONFIG_LOCALVERSION=""CONFIG_BUILD_SALT=""CONFIG_DEFAULT_INIT=""CONFIG_DEFAULT_HOSTNAME="(none)"
# CONFIG_SYSVIPC is not set
# CONFIG_WATCH_QUEUE is not setCONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_USELIB is not setCONFIG_HAVE_ARCH_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_IRQ_SHOW_LEVEL=yCONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=yCONFIG_GENERIC_IRQ_INJECTION=yCONFIG_HARDIRQS_SW_RESEND=yCONFIG_GENERIC_IRQ_CHIP=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_SIM=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_IRQ_FASTEOI_HIERARCHY_HANDLERS=yCONFIG_GENERIC_IRQ_IPI=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_IRQ_MSI_IOMMU=yCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=yCONFIG_GENERIC_IRQ_DEBUGFS=y
# end of IRQ subsystem
CONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_ARCH_HAS_TICK_BROADCAST=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=yCONFIG_HAVE_POSIX_CPU_TIMERS_TASK_WORK=yCONFIG_POSIX_CPU_TIMERS_TASK_WORK=y
# CONFIG_TIME_KUNIT_TEST is not setCONFIG_CONTEXT_TRACKING=yCONFIG_CONTEXT_TRACKING_IDLE=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_USER=y
# CONFIG_CONTEXT_TRACKING_USER_FORCE is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
# end of Timers subsystem
CONFIG_HAVE_EBPF_JIT=yCONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y
#
# BPF subsystem
#
# CONFIG_BPF_SYSCALL is not set
# end of BPF subsystem
CONFIG_PREEMPT_BUILD=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY 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=y
# CONFIG_IRQ_TIME_ACCOUNTING is not setCONFIG_HAVE_SCHED_AVG_IRQ=y
# CONFIG_BSD_PROCESS_ACCT is not set
# 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=yCONFIG_RCU_EXPERT=yCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU_GENERIC=y
# CONFIG_FORCE_TASKS_RCU is not setCONFIG_TASKS_RCU=yCONFIG_FORCE_TASKS_RUDE_RCU=yCONFIG_TASKS_RUDE_RCU=yCONFIG_FORCE_TASKS_TRACE_RCU=yCONFIG_TASKS_TRACE_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_FANOUT=64CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_BOOST is not setCONFIG_RCU_NOCB_CPU=y
# CONFIG_RCU_NOCB_CPU_DEFAULT_ALL is not setCONFIG_TASKS_TRACE_RCU_READ_MB=y
# end of RCU Subsystem
CONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_IKHEADERS=mCONFIG_GENERIC_SCHED_CLOCK=y
#
# Scheduler features
#
# end of Scheduler features
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_CC_HAS_INT128=y CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5" CONFIG_GCC12_NO_ARRAY_BOUNDS=y CONFIG_CC_NO_ARRAY_BOUNDS=y CONFIG_ARCH_SUPPORTS_INT128=y
# CONFIG_CGROUPS is not setCONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not setCONFIG_TIME_NS=yCONFIG_USER_NS=y
# CONFIG_PID_NS is not set CONFIG_CHECKPOINT_RESTORE=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=y
# CONFIG_RD_LZMA is not setCONFIG_RD_XZ=y
# CONFIG_RD_LZO is not setCONFIG_RD_LZ4=y
# CONFIG_RD_ZSTD is not set
# CONFIG_BOOT_CONFIG is not set CONFIG_INITRAMFS_PRESERVE_MTIME=y
# CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_LD_ORPHAN_WARN=yCONFIG_SYSCTL=yCONFIG_SYSCTL_EXCEPTION_TRACE=yCONFIG_EXPERT=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=y
# CONFIG_SYSFS_SYSCALL is not set CONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=y
# CONFIG_PRINTK is not setCONFIG_BUG=yCONFIG_BASE_FULL=y
# CONFIG_FUTEX is not setCONFIG_EPOLL=y
# CONFIG_SIGNALFD is not setCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_IO_URING=y
# CONFIG_ADVISE_SYSCALLS is not set CONFIG_MEMBARRIER=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_BASE_RELATIVE=y CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y CONFIG_KCMP=yCONFIG_RSEQ=yCONFIG_DEBUG_RSEQ=yCONFIG_EMBEDDED=yCONFIG_HAVE_PERF_EVENTS=y CONFIG_GUEST_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_PROFILING is not set
# end of General setup
CONFIG_ARM64=yCONFIG_GCC_SUPPORTS_DYNAMIC_FTRACE_WITH_REGS=yCONFIG_64BIT=yCONFIG_MMU=yCONFIG_ARM64_PAGE_SHIFT=12CONFIG_ARM64_CONT_PTE_SHIFT=4CONFIG_ARM64_CONT_PMD_SHIFT=4CONFIG_ARCH_MMAP_RND_BITS_MIN=18CONFIG_ARCH_MMAP_RND_BITS_MAX=24CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=11CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16CONFIG_NO_IOPORT_MAP=yCONFIG_STACKTRACE_SUPPORT=yCONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000CONFIG_LOCKDEP_SUPPORT=yCONFIG_GENERIC_BUG=yCONFIG_GENERIC_BUG_RELATIVE_POINTERS=yCONFIG_GENERIC_HWEIGHT=yCONFIG_GENERIC_CSUM=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE=yCONFIG_SMP=yCONFIG_KERNEL_MODE_NEON=yCONFIG_FIX_EARLYCON_MEM=yCONFIG_PGTABLE_LEVELS=3CONFIG_ARCH_SUPPORTS_UPROBES=yCONFIG_ARCH_PROC_KCORE_TEXT=y
#
# Platform selection
#
# CONFIG_ARCH_ACTIONS is not setCONFIG_ARCH_SUNXI=yCONFIG_ARCH_ALPINE=yCONFIG_ARCH_APPLE=yCONFIG_ARCH_BCM=yCONFIG_ARCH_BCM2835=y
# CONFIG_ARCH_BCM_IPROC is not setCONFIG_ARCH_BCMBCA=y
# CONFIG_ARCH_BRCMSTB is not set
# CONFIG_ARCH_BERLIN is not setCONFIG_ARCH_BITMAIN=yCONFIG_ARCH_EXYNOS=y
# CONFIG_ARCH_SPARX5 is not setCONFIG_ARCH_K3=yCONFIG_ARCH_LG1K=yCONFIG_ARCH_HISI=y
# CONFIG_ARCH_KEEMBAY is not set
# CONFIG_ARCH_MEDIATEK is not setCONFIG_ARCH_MESON=yCONFIG_ARCH_MVEBU=yCONFIG_ARCH_NXP=yCONFIG_ARCH_LAYERSCAPE=y
# CONFIG_ARCH_MXC is not setCONFIG_ARCH_S32=y
# CONFIG_ARCH_NPCM is not set
# CONFIG_ARCH_QCOM is not set
# CONFIG_ARCH_REALTEK is not setCONFIG_ARCH_RENESAS=y
# CONFIG_ARCH_ROCKCHIP is not set
# CONFIG_ARCH_SEATTLE is not set
# CONFIG_ARCH_INTEL_SOCFPGA is not setCONFIG_ARCH_SYNQUACER=y
# CONFIG_ARCH_TEGRA is not set
# CONFIG_ARCH_TESLA_FSD is not setCONFIG_ARCH_SPRD=y
# CONFIG_ARCH_THUNDER is not set
# CONFIG_ARCH_THUNDER2 is not set
# CONFIG_ARCH_UNIPHIER is not setCONFIG_ARCH_VEXPRESS=y
# CONFIG_ARCH_VISCONTI is not set
# CONFIG_ARCH_XGENE is not set
# CONFIG_ARCH_ZYNQMP is not set
# end of Platform selection
#
# Kernel Features
#
#
# ARM errata workarounds via the alternatives framework #CONFIG_ARM64_WORKAROUND_CLEAN_CACHE=y CONFIG_ARM64_ERRATUM_826319=y CONFIG_ARM64_ERRATUM_827319=y CONFIG_ARM64_ERRATUM_824069=y CONFIG_ARM64_ERRATUM_819472=y
# CONFIG_ARM64_ERRATUM_832075 is not set
# CONFIG_ARM64_ERRATUM_834220 is not set
# CONFIG_ARM64_ERRATUM_843419 is not set CONFIG_ARM64_LD_HAS_FIX_ERRATUM_843419=y
# CONFIG_ARM64_ERRATUM_1024718 is not set CONFIG_ARM64_WORKAROUND_SPECULATIVE_AT=y CONFIG_ARM64_ERRATUM_1165522=y CONFIG_ARM64_ERRATUM_1319367=y
# CONFIG_ARM64_ERRATUM_1530923 is not set CONFIG_ARM64_WORKAROUND_REPEAT_TLBI=y
# CONFIG_ARM64_ERRATUM_2441007 is not set CONFIG_ARM64_ERRATUM_1286807=y
# CONFIG_ARM64_ERRATUM_1463225 is not set CONFIG_ARM64_ERRATUM_1542419=y
# CONFIG_ARM64_ERRATUM_1508412 is not set
# CONFIG_ARM64_ERRATUM_2051678 is not set
# CONFIG_ARM64_ERRATUM_2077057 is not set
# CONFIG_ARM64_ERRATUM_2658417 is not set CONFIG_ARM64_WORKAROUND_TSB_FLUSH_FAILURE=y
# CONFIG_ARM64_ERRATUM_2054223 is not set CONFIG_ARM64_ERRATUM_2067961=y CONFIG_ARM64_ERRATUM_2441009=y
# CONFIG_ARM64_ERRATUM_2457168 is not set CONFIG_CAVIUM_ERRATUM_22375=y
# CONFIG_CAVIUM_ERRATUM_23154 is not set CONFIG_CAVIUM_ERRATUM_27456=y
# CONFIG_CAVIUM_ERRATUM_30115 is not set
# CONFIG_CAVIUM_TX2_ERRATUM_219 is not set CONFIG_FUJITSU_ERRATUM_010001=y
# CONFIG_HISILICON_ERRATUM_161600802 is not set # CONFIG_QCOM_FALKOR_ERRATUM_1003 is not set CONFIG_QCOM_FALKOR_ERRATUM_1009=y CONFIG_QCOM_QDF2400_ERRATUM_0065=y CONFIG_QCOM_FALKOR_ERRATUM_E1041=y CONFIG_NVIDIA_CARMEL_CNP_ERRATUM=y
# CONFIG_SOCIONEXT_SYNQUACER_PREITS is not set
# end of ARM errata workarounds via the alternatives framework
CONFIG_ARM64_4K_PAGES=y
# CONFIG_ARM64_16K_PAGES is not set
# CONFIG_ARM64_64K_PAGES is not setCONFIG_ARM64_VA_BITS_39=y
# CONFIG_ARM64_VA_BITS_48 is not setCONFIG_ARM64_VA_BITS=39CONFIG_ARM64_PA_BITS_48=yCONFIG_ARM64_PA_BITS=48CONFIG_CPU_BIG_ENDIAN=y
# CONFIG_CPU_LITTLE_ENDIAN is not set
# CONFIG_SCHED_MC is not setCONFIG_SCHED_CLUSTER=yCONFIG_SCHED_SMT=yCONFIG_NR_CPUS=256
# CONFIG_HOTPLUG_CPU is not set
# CONFIG_NUMA is not setCONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not setCONFIG_HZ=100CONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_CC_HAVE_SHADOW_CALL_STACK=yCONFIG_PARAVIRT=yCONFIG_PARAVIRT_TIME_ACCOUNTING=yCONFIG_KEXEC_FILE=yCONFIG_KEXEC_SIG=y
#
# Support for PE file signature verification disabled #CONFIG_CRASH_DUMP=yCONFIG_TRANS_TABLE=y
# CONFIG_XEN is not set CONFIG_ARCH_FORCE_MAX_ORDER=11 CONFIG_UNMAP_KERNEL_AT_EL0=y
# CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY is not set CONFIG_RODATA_FULL_DEFAULT_ENABLED=y
# CONFIG_ARM64_SW_TTBR0_PAN is not set CONFIG_ARM64_TAGGED_ADDR_ABI=y
# CONFIG_COMPAT is not set
#
# ARMv8.1 architectural features
#CONFIG_ARM64_HW_AFDBM=y
# CONFIG_ARM64_PAN is not setCONFIG_AS_HAS_LDAPR=yCONFIG_AS_HAS_LSE_ATOMICS=yCONFIG_ARM64_LSE_ATOMICS=yCONFIG_ARM64_USE_LSE_ATOMICS=y
# end of ARMv8.1 architectural features
#
# ARMv8.2 architectural features
#CONFIG_AS_HAS_ARMV8_2=yCONFIG_AS_HAS_SHA3=y
# CONFIG_ARM64_PMEM is not setCONFIG_ARM64_RAS_EXTN=y
# CONFIG_ARM64_CNP is not set
# end of ARMv8.2 architectural features
#
# ARMv8.3 architectural features
#
# CONFIG_ARM64_PTR_AUTH is not setCONFIG_CC_HAS_BRANCH_PROT_PAC_RET=yCONFIG_CC_HAS_SIGN_RETURN_ADDRESS=yCONFIG_AS_HAS_PAC=yCONFIG_AS_HAS_CFI_NEGATE_RA_STATE=y
# end of ARMv8.3 architectural features
#
# ARMv8.4 architectural features
#CONFIG_ARM64_AMU_EXTN=yCONFIG_AS_HAS_ARMV8_4=yCONFIG_ARM64_TLB_RANGE=y
# end of ARMv8.4 architectural features
#
# ARMv8.5 architectural features
#CONFIG_AS_HAS_ARMV8_5=yCONFIG_ARM64_BTI=yCONFIG_CC_HAS_BRANCH_PROT_PAC_RET_BTI=y
# CONFIG_ARM64_E0PD is not setCONFIG_ARM64_AS_HAS_MTE=y
# end of ARMv8.5 architectural features
#
# ARMv8.7 architectural features
#
# end of ARMv8.7 architectural features
# CONFIG_ARM64_SVE is not setCONFIG_ARM64_MODULE_PLTS=yCONFIG_ARM64_PSEUDO_NMI=y
# CONFIG_ARM64_DEBUG_PRIORITY_MASKING is not setCONFIG_RELOCATABLE=y
# CONFIG_RANDOMIZE_BASE is not setCONFIG_CC_HAVE_STACKPROTECTOR_SYSREG=yCONFIG_STACKPROTECTOR_PER_TASK=yCONFIG_ARCH_NR_GPIO=2048
# end of Kernel Features
#
# Boot options
#CONFIG_CMDLINE=""
# end of Boot options
#
# Power management options
#
# CONFIG_SUSPEND is not setCONFIG_PM=yCONFIG_PM_DEBUG=yCONFIG_PM_ADVANCED_DEBUG=yCONFIG_PM_CLK=yCONFIG_PM_GENERIC_DOMAINS=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not setCONFIG_PM_GENERIC_DOMAINS_OF=yCONFIG_CPU_PM=yCONFIG_ARCH_HIBERNATION_POSSIBLE=yCONFIG_ARCH_SUSPEND_POSSIBLE=y
# end of Power management options
#
# CPU Power Management
#
#
# CPU Idle
#CONFIG_CPU_IDLE=yCONFIG_CPU_IDLE_GOV_LADDER=y
# CONFIG_CPU_IDLE_GOV_MENU is not setCONFIG_CPU_IDLE_GOV_TEO=y
#
# ARM CPU Idle Drivers
#
# CONFIG_ARM_PSCI_CPUIDLE is not set
# CONFIG_ARM_CLPS711X_CPUIDLE is not set
# end of ARM CPU Idle Drivers # end of CPU Idle
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# end of CPU Frequency scaling # end of CPU Power Management
CONFIG_IRQ_BYPASS_MANAGER=yCONFIG_HAVE_KVM=yCONFIG_HAVE_KVM_IRQCHIP=yCONFIG_HAVE_KVM_IRQFD=yCONFIG_HAVE_KVM_IRQ_ROUTING=yCONFIG_HAVE_KVM_DIRTY_RING=yCONFIG_HAVE_KVM_DIRTY_RING_ACQ_REL=yCONFIG_NEED_KVM_DIRTY_RING_WITH_BITMAP=yCONFIG_HAVE_KVM_EVENTFD=yCONFIG_KVM_MMIO=yCONFIG_HAVE_KVM_MSI=yCONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=yCONFIG_KVM_VFIO=yCONFIG_HAVE_KVM_ARCH_TLB_FLUSH_ALL=yCONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=yCONFIG_HAVE_KVM_IRQ_BYPASS=yCONFIG_HAVE_KVM_VCPU_RUN_PID_CHANGE=yCONFIG_KVM_XFER_TO_GUEST_WORK=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=y
# CONFIG_NVHE_EL2_DEBUG is not set
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_KPROBES=yCONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not setCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_KRETPROBES=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_ARCH_CORRECT_STACKTRACE_ON_KRETPROBE=yCONFIG_HAVE_FUNCTION_ERROR_INJECTION=yCONFIG_HAVE_NMI=yCONFIG_TRACE_IRQFLAGS_SUPPORT=yCONFIG_TRACE_IRQFLAGS_NMI_SUPPORT=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_CONTIGUOUS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_GENERIC_IDLE_POLL_SETUP=yCONFIG_ARCH_HAS_FORTIFY_SOURCE=yCONFIG_ARCH_HAS_KEEPINITRD=yCONFIG_ARCH_HAS_SET_MEMORY=yCONFIG_ARCH_HAS_SET_DIRECT_MAP=yCONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=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_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_HAVE_ARCH_SECCOMP=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=y
# CONFIG_SECCOMP is not setCONFIG_HAVE_ARCH_STACKLEAK=yCONFIG_HAVE_STACKPROTECTOR=yCONFIG_STACKPROTECTOR=yCONFIG_STACKPROTECTOR_STRONG=yCONFIG_ARCH_SUPPORTS_SHADOW_CALL_STACK=y
# CONFIG_SHADOW_CALL_STACK is not setCONFIG_ARCH_SUPPORTS_LTO_CLANG_THIN=yCONFIG_LTO_NONE=yCONFIG_ARCH_SUPPORTS_CFI_CLANG=yCONFIG_HAVE_CONTEXT_TRACKING_USER=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_HUGE_VMAP=yCONFIG_HAVE_ARCH_HUGE_VMALLOC=yCONFIG_ARCH_WANT_HUGE_PMD_SHARE=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_RELA=yCONFIG_HAVE_SOFTIRQ_ON_OWN_STACK=yCONFIG_SOFTIRQ_ON_OWN_STACK=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_ARCH_MMAP_RND_BITS=18CONFIG_PAGE_SIZE_LESS_THAN_64KB=yCONFIG_PAGE_SIZE_LESS_THAN_256KB=yCONFIG_ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT=yCONFIG_ISA_BUS_API=yCONFIG_CLONE_BACKWARDS=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_HAVE_ARCH_VMAP_STACK=y
# CONFIG_VMAP_STACK is not setCONFIG_HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET=yCONFIG_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_COMPILER_H=yCONFIG_HAVE_ARCH_PREL32_RELOCATIONS=yCONFIG_LOCK_EVENT_COUNTS=yCONFIG_ARCH_HAS_RELR=yCONFIG_HAVE_PREEMPT_DYNAMIC=yCONFIG_HAVE_PREEMPT_DYNAMIC_KEY=yCONFIG_ARCH_WANT_LD_ORPHAN_WARN=yCONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=yCONFIG_ARCH_SUPPORTS_PAGE_TABLE_CHECK=yCONFIG_ARCH_HAVE_TRACE_MMIO_ACCESS=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
# CONFIG_GCC_PLUGINS is not set
# end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
# CONFIG_MODULE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set 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_MODULES_TREE_LOOKUP=y
# CONFIG_BLOCK is not set CONFIG_PREEMPT_NOTIFIERS=yCONFIG_ASN1=mCONFIG_UNINLINE_SPIN_UNLOCK=y CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_RWSEM_SPIN_ON_OWNER=y CONFIG_LOCK_SPIN_ON_OWNER=y CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y CONFIG_QUEUED_SPINLOCKS=y CONFIG_ARCH_USE_QUEUED_RWLOCKS=y CONFIG_QUEUED_RWLOCKS=y CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=y CONFIG_ARCH_HAS_SYSCALL_WRAPPER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_ARCH_BINFMT_ELF_STATE=yCONFIG_ARCH_BINFMT_ELF_EXTRA_PHDRS=yCONFIG_ARCH_HAVE_ELF_PROT=yCONFIG_ARCH_USE_GNU_PROPERTY=yCONFIG_ELFCORE=yCONFIG_BINFMT_SCRIPT=m
# CONFIG_BINFMT_MISC is not set
# CONFIG_COREDUMP is not set
# end of Executable file formats
#
# Memory Management options
#
#
# SLAB allocator options
#
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_SLAB_MERGE_DEFAULT=yCONFIG_SLAB_FREELIST_RANDOM=y
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SLUB_STATS is not setCONFIG_SLUB_CPU_PARTIAL=y
# end of SLAB allocator options
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not setCONFIG_COMPAT_BRK=yCONFIG_SPARSEMEM=yCONFIG_SPARSEMEM_EXTREME=yCONFIG_SPARSEMEM_VMEMMAP_ENABLE=yCONFIG_SPARSEMEM_VMEMMAP=yCONFIG_HAVE_FAST_GUP=yCONFIG_ARCH_KEEP_MEMBLOCK=yCONFIG_MEMORY_ISOLATION=yCONFIG_EXCLUSIVE_SYSTEM_RAM=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
# CONFIG_MEMORY_HOTPLUG is not setCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=yCONFIG_COMPACTION=yCONFIG_COMPACT_UNEVICTABLE_DEFAULT=1
# CONFIG_PAGE_REPORTING is not setCONFIG_MIGRATION=yCONFIG_ARCH_ENABLE_THP_MIGRATION=yCONFIG_CONTIG_ALLOC=yCONFIG_PHYS_ADDR_T_64BIT=yCONFIG_MMU_NOTIFIER=y
# CONFIG_KSM is not setCONFIG_DEFAULT_MMAP_MIN_ADDR=4096CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not setCONFIG_ARCH_WANTS_THP_SWAP=yCONFIG_TRANSPARENT_HUGEPAGE=yCONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not setCONFIG_READ_ONLY_THP_FOR_FS=yCONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not setCONFIG_CMA_SYSFS=yCONFIG_CMA_AREAS=7CONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_DEFERRED_STRUCT_PAGE_INIT is not setCONFIG_PAGE_IDLE_FLAG=yCONFIG_IDLE_PAGE_TRACKING=yCONFIG_ARCH_HAS_CACHE_LINE_SIZE=yCONFIG_ARCH_HAS_CURRENT_STACK_POINTER=yCONFIG_ARCH_HAS_PTE_DEVMAP=yCONFIG_ARCH_HAS_ZONE_DMA_SET=yCONFIG_ZONE_DMA=yCONFIG_ZONE_DMA32=y
# CONFIG_VM_EVENT_COUNTERS is not setCONFIG_PERCPU_STATS=y
# CONFIG_GUP_TEST is not setCONFIG_ARCH_HAS_PTE_SPECIAL=y
# CONFIG_USERFAULTFD is not setCONFIG_LRU_GEN=y
# CONFIG_LRU_GEN_ENABLED is not setCONFIG_LRU_GEN_STATS=y
#
# Data Access Monitoring
#
# CONFIG_DAMON is not set
# end of Data Access Monitoring # end of Memory Management options
# CONFIG_NET is not set
#
# Device Drivers
#CONFIG_ARM_AMBA=yCONFIG_HAVE_PCI=y
# CONFIG_PCI is not set
# CONFIG_PCCARD is not set
#
# Generic Driver Options
#CONFIG_AUXILIARY_BUS=yCONFIG_UEVENT_HELPER=yCONFIG_UEVENT_HELPER_PATH=""CONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=y
# CONFIG_DEVTMPFS_SAFE is not setCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=yCONFIG_FW_LOADER_PAGED_BUF=yCONFIG_FW_LOADER_SYSFS=yCONFIG_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER is not set
# CONFIG_FW_LOADER_COMPRESS is not setCONFIG_FW_UPLOAD=y
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=yCONFIG_ALLOW_DEV_COREDUMP=yCONFIG_DEV_COREDUMP=yCONFIG_DEBUG_DRIVER=y
# CONFIG_DEBUG_DEVRES is not setCONFIG_DEBUG_TEST_DRIVER_REMOVE=yCONFIG_TEST_ASYNC_DRIVER_PROBE=mCONFIG_GENERIC_CPU_AUTOPROBE=yCONFIG_GENERIC_CPU_VULNERABILITIES=yCONFIG_SOC_BUS=yCONFIG_REGMAP=yCONFIG_REGMAP_AC97=mCONFIG_REGMAP_I2C=yCONFIG_REGMAP_SPI=yCONFIG_REGMAP_SPMI=mCONFIG_REGMAP_W1=yCONFIG_REGMAP_MMIO=yCONFIG_REGMAP_IRQ=yCONFIG_REGMAP_SCCB=yCONFIG_REGMAP_SPI_AVMM=yCONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not setCONFIG_GENERIC_ARCH_TOPOLOGY=y
# end of Generic Driver Options
#
# Bus devices
#CONFIG_ARM_CCI=yCONFIG_ARM_CCI400_COMMON=y
# CONFIG_ARM_INTEGRATOR_LM is not set
# CONFIG_BRCMSTB_GISB_ARB is not set
# CONFIG_BT1_APB is not setCONFIG_BT1_AXI=y
# CONFIG_MOXTET is not setCONFIG_HISILICON_LPC=y
# CONFIG_INTEL_IXP4XX_EB is not setCONFIG_QCOM_EBI2=yCONFIG_SUN50I_DE2_BUS=y
# CONFIG_SUNXI_RSB is not setCONFIG_VEXPRESS_CONFIG=m
# CONFIG_FSL_MC_BUS is not set
# CONFIG_MHI_BUS is not set
# CONFIG_MHI_BUS_EP is not set
# end of Bus devices
#
# Firmware Drivers
#
#
# ARM System Control and Management Interface Protocol #CONFIG_ARM_SCMI_PROTOCOL=m CONFIG_ARM_SCMI_HAVE_TRANSPORT=y CONFIG_ARM_SCMI_HAVE_SHMEM=yCONFIG_ARM_SCMI_HAVE_MSG=y
# CONFIG_ARM_SCMI_TRANSPORT_MAILBOX is not set CONFIG_ARM_SCMI_TRANSPORT_SMC=y
# CONFIG_ARM_SCMI_TRANSPORT_SMC_ATOMIC_ENABLE is not set CONFIG_ARM_SCMI_TRANSPORT_VIRTIO=y
# CONFIG_ARM_SCMI_TRANSPORT_VIRTIO_VERSION1_COMPLIANCE is not set CONFIG_ARM_SCMI_TRANSPORT_VIRTIO_ATOMIC_ENABLE=y CONFIG_ARM_SCMI_POWER_DOMAIN=y CONFIG_ARM_SCMI_POWER_CONTROL=y
# end of ARM System Control and Management Interface Protocol
# CONFIG_ARM_SCPI_PROTOCOL is not setCONFIG_ARM_SCPI_POWER_DOMAIN=yCONFIG_FIRMWARE_MEMMAP=yCONFIG_QCOM_SCM=yCONFIG_QCOM_SCM_DOWNLOAD_MODE_DEFAULT=yCONFIG_TI_SCI_PROTOCOL=yCONFIG_TURRIS_MOX_RWTM=mCONFIG_ARM_FFA_TRANSPORT=yCONFIG_ARM_FFA_SMCCC=yCONFIG_BCM47XX_NVRAM=yCONFIG_BCM47XX_SPROM=yCONFIG_CS_DSP=mCONFIG_GOOGLE_FIRMWARE=yCONFIG_GOOGLE_COREBOOT_TABLE=yCONFIG_GOOGLE_FRAMEBUFFER_COREBOOT=m
# CONFIG_GOOGLE_MEMCONSOLE_COREBOOT is not setCONFIG_GOOGLE_VPD=mCONFIG_MESON_SM=yCONFIG_ARM_PSCI_FW=yCONFIG_HAVE_ARM_SMCCC=yCONFIG_HAVE_ARM_SMCCC_DISCOVERY=y
# CONFIG_ARM_SMCCC_SOC_ID is not set
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
# CONFIG_GNSS is not set
# CONFIG_MTD is not set
# CONFIG_MTD_NAND_ECC_MXIC is not setCONFIG_DTC=yCONFIG_OF=yCONFIG_OF_UNITTEST=yCONFIG_OF_ALL_DTBS=yCONFIG_OF_FLATTREE=yCONFIG_OF_EARLY_FLATTREE=yCONFIG_OF_KOBJ=yCONFIG_OF_DYNAMIC=yCONFIG_OF_ADDRESS=yCONFIG_OF_IRQ=yCONFIG_OF_RESERVED_MEM=yCONFIG_OF_RESOLVE=y
# CONFIG_OF_OVERLAY is not setCONFIG_PARPORT=yCONFIG_PARPORT_AX88796=yCONFIG_PARPORT_1284=yCONFIG_PARPORT_NOT_PC=y
#
# NVME Support
#
# end of NVME Support
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=m
# CONFIG_AD525X_DPOT is not setCONFIG_DUMMY_IRQ=mCONFIG_ICS932S401=yCONFIG_ATMEL_SSC=yCONFIG_ENCLOSURE_SERVICES=mCONFIG_GEHC_ACHC=mCONFIG_HI6421V600_IRQ=mCONFIG_QCOM_COINCELL=y
# CONFIG_QCOM_FASTRPC is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not setCONFIG_SENSORS_TSL2550=yCONFIG_SENSORS_BH1770=mCONFIG_SENSORS_APDS990X=y
# CONFIG_HMC6352 is not setCONFIG_DS1682=mCONFIG_LATTICE_ECP3_CONFIG=y
# CONFIG_SRAM is not set
# CONFIG_XILINX_SDFEC is not setCONFIG_OPEN_DICE=mCONFIG_VCPU_STALL_DETECTOR=y
# CONFIG_C2PORT is not set
#
# EEPROM support
#CONFIG_EEPROM_AT24=yCONFIG_EEPROM_AT25=mCONFIG_EEPROM_LEGACY=yCONFIG_EEPROM_MAX6875=mCONFIG_EEPROM_93CX6=yCONFIG_EEPROM_93XX46=yCONFIG_EEPROM_IDT_89HPESX=y
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
#
# Texas Instruments shared transport line discipline #
# end of Texas Instruments shared transport line discipline
CONFIG_SENSORS_LIS3_SPI=m
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_ALTERA_STAPL is not setCONFIG_ECHO=m
# CONFIG_UACCE is not set
# CONFIG_PVPANIC is not set
# end of Misc devices
#
# SCSI device support
#
# end of SCSI device support
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=m
# end of IEEE 1394 (FireWire) support
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=mCONFIG_INPUT_FF_MEMLESS=yCONFIG_INPUT_SPARSEKMAP=mCONFIG_INPUT_MATRIXKMAP=y
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=mCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=y
# CONFIG_INPUT_EVDEV is not setCONFIG_INPUT_EVBUG=m
#
# Input Device Drivers
#
# CONFIG_INPUT_KEYBOARD is not setCONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_PS2 is not set
# CONFIG_MOUSE_SERIAL is not setCONFIG_MOUSE_CYAPA=mCONFIG_MOUSE_ELAN_I2C=y
# CONFIG_MOUSE_ELAN_I2C_I2C is not set
# CONFIG_MOUSE_ELAN_I2C_SMBUS is not set
# CONFIG_MOUSE_VSXXXAA is not setCONFIG_MOUSE_GPIO=mCONFIG_MOUSE_SYNAPTICS_I2C=mCONFIG_INPUT_JOYSTICK=yCONFIG_JOYSTICK_ANALOG=mCONFIG_JOYSTICK_A3D=yCONFIG_JOYSTICK_ADC=yCONFIG_JOYSTICK_ADI=mCONFIG_JOYSTICK_COBRA=m
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not setCONFIG_JOYSTICK_GRIP_MP=mCONFIG_JOYSTICK_GUILLEMOT=yCONFIG_JOYSTICK_INTERACT=yCONFIG_JOYSTICK_SIDEWINDER=y
# CONFIG_JOYSTICK_TMDC is not setCONFIG_JOYSTICK_IFORCE=y
# CONFIG_JOYSTICK_IFORCE_232 is not setCONFIG_JOYSTICK_WARRIOR=m
# CONFIG_JOYSTICK_MAGELLAN is not setCONFIG_JOYSTICK_SPACEORB=y
# CONFIG_JOYSTICK_SPACEBALL is not setCONFIG_JOYSTICK_STINGER=yCONFIG_JOYSTICK_TWIDJOY=mCONFIG_JOYSTICK_ZHENHUA=mCONFIG_JOYSTICK_DB9=y
# CONFIG_JOYSTICK_GAMECON is not setCONFIG_JOYSTICK_TURBOGRAFX=yCONFIG_JOYSTICK_AS5011=m
# CONFIG_JOYSTICK_JOYDUMP is not setCONFIG_JOYSTICK_PSXPAD_SPI=m
# CONFIG_JOYSTICK_PSXPAD_SPI_FF is not setCONFIG_JOYSTICK_QWIIC=yCONFIG_JOYSTICK_FSIA6B=mCONFIG_JOYSTICK_SENSEHAT=m
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not setCONFIG_RMI4_CORE=y
# CONFIG_RMI4_I2C is not setCONFIG_RMI4_SPI=yCONFIG_RMI4_SMB=mCONFIG_RMI4_F03=yCONFIG_RMI4_F03_SERIO=yCONFIG_RMI4_2D_SENSOR=yCONFIG_RMI4_F11=yCONFIG_RMI4_F12=yCONFIG_RMI4_F30=yCONFIG_RMI4_F34=y
# CONFIG_RMI4_F3A is not setCONFIG_RMI4_F54=yCONFIG_RMI4_F55=y
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_SERIO_SERPORT=mCONFIG_SERIO_PARKBD=yCONFIG_SERIO_AMBAKMI=yCONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not setCONFIG_SERIO_PS2MULT=y
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not setCONFIG_SERIO_OLPC_APSP=yCONFIG_SERIO_SUN4I_PS2=mCONFIG_SERIO_GPIO_PS2=mCONFIG_USERIO=yCONFIG_GAMEPORT=y
# CONFIG_GAMEPORT_NS558 is not setCONFIG_GAMEPORT_L4=m
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=y
# CONFIG_CONSOLE_TRANSLATIONS is not set
# CONFIG_VT_CONSOLE is not setCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_UNIX98_PTYS is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_LDISC_AUTOLOAD is not set
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=yCONFIG_SERIAL_8250=mCONFIG_SERIAL_8250_DEPRECATED_OPTIONS=yCONFIG_SERIAL_8250_16550A_VARIANTS=y
# CONFIG_SERIAL_8250_FINTEK is not setCONFIG_SERIAL_8250_DMA=yCONFIG_SERIAL_8250_MEN_MCB=mCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_8250_RUNTIME_UARTS=4CONFIG_SERIAL_8250_EXTENDED=yCONFIG_SERIAL_8250_MANY_PORTS=yCONFIG_SERIAL_8250_ASPEED_VUART=mCONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not setCONFIG_SERIAL_8250_RSA=yCONFIG_SERIAL_8250_DWLIB=yCONFIG_SERIAL_8250_BCM2835AUX=mCONFIG_SERIAL_8250_DW=mCONFIG_SERIAL_8250_EM=mCONFIG_SERIAL_8250_IOC3=m
# CONFIG_SERIAL_8250_RT288X is not setCONFIG_SERIAL_8250_OMAP=mCONFIG_SERIAL_8250_LPC18XX=mCONFIG_SERIAL_8250_MT6577=mCONFIG_SERIAL_8250_UNIPHIER=mCONFIG_SERIAL_8250_INGENIC=mCONFIG_SERIAL_8250_PXA=mCONFIG_SERIAL_8250_TEGRA=m
# CONFIG_SERIAL_8250_BCM7271 is not set
# CONFIG_SERIAL_OF_PLATFORM is not set
#
# Non-8250 serial port support
#CONFIG_SERIAL_AMBA_PL010=y CONFIG_SERIAL_AMBA_PL010_CONSOLE=y
# CONFIG_SERIAL_AMBA_PL011 is not set
# CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST is not set CONFIG_SERIAL_ATMEL=y CONFIG_SERIAL_ATMEL_CONSOLE=y
# CONFIG_SERIAL_ATMEL_PDC is not set CONFIG_SERIAL_ATMEL_TTYAT=y CONFIG_SERIAL_KGDB_NMI=y CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y
# CONFIG_SERIAL_CLPS711X is not set
# CONFIG_SERIAL_SAMSUNG is not set CONFIG_SERIAL_TEGRA=y
# CONFIG_SERIAL_TEGRA_TCU is not set CONFIG_SERIAL_MAX3100=m
# CONFIG_SERIAL_MAX310X is not set CONFIG_SERIAL_IMX=m CONFIG_SERIAL_IMX_CONSOLE=m CONFIG_SERIAL_IMX_EARLYCON=y CONFIG_SERIAL_UARTLITE=y
# CONFIG_SERIAL_UARTLITE_CONSOLE is not set CONFIG_SERIAL_UARTLITE_NR_UARTS=1 CONFIG_SERIAL_SH_SCI=y CONFIG_SERIAL_SH_SCI_NR_UARTS=18
# CONFIG_SERIAL_SH_SCI_CONSOLE is not set CONFIG_SERIAL_SH_SCI_EARLYCON=y
# CONFIG_SERIAL_SH_SCI_DMA is not set CONFIG_SERIAL_HS_LPC32XX=y CONFIG_SERIAL_HS_LPC32XX_CONSOLE=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_CONSOLE_POLL=y
# CONFIG_SERIAL_MSM is not set CONFIG_SERIAL_VT8500=y CONFIG_SERIAL_VT8500_CONSOLE=y CONFIG_SERIAL_OMAP=y CONFIG_SERIAL_OMAP_CONSOLE=y CONFIG_SERIAL_SIFIVE=y CONFIG_SERIAL_SIFIVE_CONSOLE=y
# CONFIG_SERIAL_LANTIQ is not set CONFIG_SERIAL_QE=yCONFIG_SERIAL_SCCNXP=m CONFIG_SERIAL_SC16IS7XX=y
# CONFIG_SERIAL_SC16IS7XX_I2C is not set
# CONFIG_SERIAL_SC16IS7XX_SPI is not set CONFIG_SERIAL_TIMBERDALE=y CONFIG_SERIAL_BCM63XX=y
# CONFIG_SERIAL_BCM63XX_CONSOLE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set CONFIG_SERIAL_ALTERA_UART=y CONFIG_SERIAL_ALTERA_UART_MAXPORTS=4 CONFIG_SERIAL_ALTERA_UART_BAUDRATE=115200
# CONFIG_SERIAL_ALTERA_UART_CONSOLE is not set # CONFIG_SERIAL_MXS_AUART is not set CONFIG_SERIAL_XILINX_PS_UART=m
# CONFIG_SERIAL_MPS2_UART_CONSOLE is not set CONFIG_SERIAL_MPS2_UART=yCONFIG_SERIAL_ARC=m CONFIG_SERIAL_ARC_NR_PORTS=1 CONFIG_SERIAL_FSL_LPUART=y
# CONFIG_SERIAL_FSL_LPUART_CONSOLE is not set CONFIG_SERIAL_CONEXANT_DIGICOLOR=y
# CONFIG_SERIAL_CONEXANT_DIGICOLOR_CONSOLE is not set CONFIG_SERIAL_ST_ASC=m CONFIG_SERIAL_MEN_Z135=yCONFIG_SERIAL_SPRD=y
# CONFIG_SERIAL_SPRD_CONSOLE is not set CONFIG_SERIAL_STM32=y CONFIG_SERIAL_STM32_CONSOLE=y CONFIG_SERIAL_MVEBU_UART=y
# CONFIG_SERIAL_MVEBU_CONSOLE is not set
# CONFIG_SERIAL_OWL is not set
# CONFIG_SERIAL_RDA is not set CONFIG_SERIAL_MILBEAUT_USIO=m CONFIG_SERIAL_MILBEAUT_USIO_PORTS=4
# CONFIG_SERIAL_LITEUART is not set CONFIG_SERIAL_SUNPLUS=m
# CONFIG_SERIAL_SUNPLUS_CONSOLE is not set
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=yCONFIG_SERIAL_NONSTANDARD=yCONFIG_N_HDLC=m
# CONFIG_NULL_TTY is not setCONFIG_HVC_DRIVER=yCONFIG_HVC_DCC=yCONFIG_HVC_DCC_SERIALIZE_SMP=yCONFIG_RPMSG_TTY=mCONFIG_SERIAL_DEV_BUS=m
# CONFIG_TTY_PRINTK is not setCONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not setCONFIG_PPDEV=y
# CONFIG_VIRTIO_CONSOLE is not setCONFIG_IPMI_HANDLER=yCONFIG_IPMI_PLAT_DATA=y
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not setCONFIG_IPMI_SI=y
# CONFIG_IPMI_SSIF is not setCONFIG_IPMI_IPMB=mCONFIG_IPMI_WATCHDOG=mCONFIG_IPMI_POWEROFF=mCONFIG_IPMI_KCS_BMC=yCONFIG_ASPEED_KCS_IPMI_BMC=y
# CONFIG_NPCM7XX_KCS_IPMI_BMC is not set
# CONFIG_IPMI_KCS_BMC_CDEV_IPMI is not set
# CONFIG_IPMI_KCS_BMC_SERIO is not setCONFIG_ASPEED_BT_IPMI_BMC=y
# CONFIG_IPMB_DEVICE_INTERFACE is not setCONFIG_HW_RANDOM=mCONFIG_HW_RANDOM_TIMERIOMEM=mCONFIG_HW_RANDOM_ATMEL=mCONFIG_HW_RANDOM_BA431=m
# CONFIG_HW_RANDOM_BCM2835 is not setCONFIG_HW_RANDOM_IPROC_RNG200=m
# CONFIG_HW_RANDOM_IXP4XX is not setCONFIG_HW_RANDOM_OMAP=mCONFIG_HW_RANDOM_OMAP3_ROM=mCONFIG_HW_RANDOM_VIRTIO=mCONFIG_HW_RANDOM_IMX_RNGC=mCONFIG_HW_RANDOM_NOMADIK=m
# CONFIG_HW_RANDOM_HISI is not set
# CONFIG_HW_RANDOM_STM32 is not setCONFIG_HW_RANDOM_MESON=mCONFIG_HW_RANDOM_MTK=m
# CONFIG_HW_RANDOM_EXYNOS is not setCONFIG_HW_RANDOM_NPCM=m
# CONFIG_HW_RANDOM_KEYSTONE is not setCONFIG_HW_RANDOM_CCTRNG=m
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_HW_RANDOM_ARM_SMCCC_TRNG is not setCONFIG_DEVMEM=yCONFIG_TCG_TPM=m
# CONFIG_HW_RANDOM_TPM is not setCONFIG_TCG_TIS_CORE=mCONFIG_TCG_TIS=mCONFIG_TCG_TIS_SPI=mCONFIG_TCG_TIS_SPI_CR50=yCONFIG_TCG_TIS_I2C=m
# CONFIG_TCG_TIS_SYNQUACER is not set
# CONFIG_TCG_TIS_I2C_CR50 is not set
# CONFIG_TCG_TIS_I2C_ATMEL is not setCONFIG_TCG_TIS_I2C_INFINEON=mCONFIG_TCG_TIS_I2C_NUVOTON=m
# CONFIG_TCG_VTPM_PROXY is not setCONFIG_TCG_TIS_ST33ZP24=mCONFIG_TCG_TIS_ST33ZP24_I2C=m
# CONFIG_TCG_TIS_ST33ZP24_SPI is not set
# CONFIG_XILLYBUS is not setCONFIG_RANDOM_TRUST_CPU=yCONFIG_RANDOM_TRUST_BOOTLOADER=y
# end of Character devices
#
# I2C support
#CONFIG_I2C=yCONFIG_I2C_BOARDINFO=y
# CONFIG_I2C_COMPAT is not set
# CONFIG_I2C_CHARDEV is not setCONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#CONFIG_I2C_ARB_GPIO_CHALLENGE=m
# CONFIG_I2C_MUX_GPIO is not setCONFIG_I2C_MUX_GPMUX=yCONFIG_I2C_MUX_LTC4306=y
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_PINCTRL is not set
# CONFIG_I2C_MUX_REG is not setCONFIG_I2C_DEMUX_PINCTRL=mCONFIG_I2C_MUX_MLXCPLD=y
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=mCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=y
#
# I2C Hardware Bus support
#CONFIG_I2C_HIX5HD2=m
#
# I2C system bus drivers (mostly embedded / system-on-chip) #CONFIG_I2C_ALTERA=m
# CONFIG_I2C_ASPEED is not set
# CONFIG_I2C_AT91 is not setCONFIG_I2C_AXXIA=mCONFIG_I2C_BCM2835=y
# CONFIG_I2C_BCM_IPROC is not set CONFIG_I2C_BCM_KONA=yCONFIG_I2C_BRCMSTB=mCONFIG_I2C_CADENCE=y
# CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DAVINCI=yCONFIG_I2C_DESIGNWARE_CORE=m
# CONFIG_I2C_DESIGNWARE_SLAVE is not set CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_DIGICOLOR=yCONFIG_I2C_EMEV2=yCONFIG_I2C_EXYNOS5=yCONFIG_I2C_GPIO=m
# CONFIG_I2C_GPIO_FAULT_INJECTOR is not set CONFIG_I2C_HIGHLANDER=y
# CONFIG_I2C_HISI is not setCONFIG_I2C_IMG=mCONFIG_I2C_IMX=mCONFIG_I2C_IMX_LPI2C=m
# CONFIG_I2C_IOP3XX is not setCONFIG_I2C_JZ4780=yCONFIG_I2C_LPC2K=mCONFIG_I2C_MESON=yCONFIG_I2C_MICROCHIP_CORE=mCONFIG_I2C_MT65XX=mCONFIG_I2C_MT7621=m
# CONFIG_I2C_MV64XXX is not setCONFIG_I2C_MXS=m
# CONFIG_I2C_NOMADIK is not set
# CONFIG_I2C_NPCM is not setCONFIG_I2C_OCORES=yCONFIG_I2C_OMAP=m
# CONFIG_I2C_OWL is not set
# CONFIG_I2C_APPLE is not set CONFIG_I2C_PCA_PLATFORM=yCONFIG_I2C_PNX=y
# CONFIG_I2C_PXA is not setCONFIG_I2C_QCOM_CCI=mCONFIG_I2C_QUP=y
# CONFIG_I2C_RIIC is not setCONFIG_I2C_RK3X=yCONFIG_I2C_RZV2M=mCONFIG_I2C_S3C2410=mCONFIG_I2C_SH_MOBILE=y
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_SPRD is not set
# CONFIG_I2C_ST is not setCONFIG_I2C_STM32F4=yCONFIG_I2C_STM32F7=m
# CONFIG_I2C_SUN6I_P2WI is not set CONFIG_I2C_SYNQUACER=yCONFIG_I2C_TEGRA=yCONFIG_I2C_TEGRA_BPMP=yCONFIG_I2C_UNIPHIER=mCONFIG_I2C_UNIPHIER_F=mCONFIG_I2C_VERSATILE=mCONFIG_I2C_WMT=mCONFIG_I2C_XILINX=mCONFIG_I2C_XLP9XX=mCONFIG_I2C_RCAR=m
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT is not setCONFIG_I2C_TAOS_EVM=m
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_MLXCPLD is not setCONFIG_I2C_VIRTIO=m
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=mCONFIG_I2C_SLAVE=y
# CONFIG_I2C_SLAVE_EEPROM is not setCONFIG_I2C_SLAVE_TESTUNIT=mCONFIG_I2C_DEBUG_CORE=y
# CONFIG_I2C_DEBUG_ALGO is not setCONFIG_I2C_DEBUG_BUS=y
# end of I2C support
CONFIG_I3C=yCONFIG_CDNS_I3C_MASTER=yCONFIG_DW_I3C_MASTER=m
# CONFIG_SVC_I3C_MASTER is not setCONFIG_MIPI_I3C_HCI=yCONFIG_SPI=yCONFIG_SPI_DEBUG=yCONFIG_SPI_MASTER=yCONFIG_SPI_MEM=y
#
# SPI Master Controller Drivers
#CONFIG_SPI_ALTERA=yCONFIG_SPI_ALTERA_CORE=y
# CONFIG_SPI_AR934X is not setCONFIG_SPI_ATH79=y
# CONFIG_SPI_ARMADA_3700 is not setCONFIG_SPI_ASPEED_SMC=yCONFIG_SPI_ATMEL=y
# CONFIG_SPI_AT91_USART is not setCONFIG_SPI_ATMEL_QUADSPI=m
# CONFIG_SPI_AXI_SPI_ENGINE is not setCONFIG_SPI_BCM2835=yCONFIG_SPI_BCM2835AUX=mCONFIG_SPI_BCM63XX=m
# CONFIG_SPI_BCM63XX_HSSPI is not setCONFIG_SPI_BCM_QSPI=mCONFIG_SPI_BITBANG=yCONFIG_SPI_BUTTERFLY=m
# CONFIG_SPI_CADENCE is not setCONFIG_SPI_CADENCE_QUADSPI=m
# CONFIG_SPI_CADENCE_XSPI is not setCONFIG_SPI_CLPS711X=yCONFIG_SPI_DESIGNWARE=mCONFIG_SPI_DW_DMA=y
# CONFIG_SPI_DW_MMIO is not set
# CONFIG_SPI_DW_BT1 is not setCONFIG_SPI_EP93XX=yCONFIG_SPI_FSL_LPSPI=yCONFIG_SPI_FSL_QUADSPI=mCONFIG_SPI_GXP=m
# CONFIG_SPI_HISI_KUNPENG is not set
# CONFIG_SPI_HISI_SFC_V3XX is not set
# CONFIG_SPI_NXP_FLEXSPI is not setCONFIG_SPI_GPIO=mCONFIG_SPI_IMG_SPFI=y
# CONFIG_SPI_IMX is not set
# CONFIG_SPI_INGENIC is not setCONFIG_SPI_INTEL=mCONFIG_SPI_INTEL_PLATFORM=mCONFIG_SPI_JCORE=yCONFIG_SPI_LM70_LLP=mCONFIG_SPI_LP8841_RTC=yCONFIG_SPI_FSL_LIB=mCONFIG_SPI_FSL_SPI=m
# CONFIG_SPI_FSL_DSPI is not setCONFIG_SPI_MESON_SPICC=yCONFIG_SPI_MESON_SPIFC=yCONFIG_SPI_MICROCHIP_CORE=mCONFIG_SPI_MICROCHIP_CORE_QSPI=mCONFIG_SPI_MT65XX=yCONFIG_SPI_MT7621=y
# CONFIG_SPI_MTK_NOR is not setCONFIG_SPI_NPCM_FIU=m
# CONFIG_SPI_NPCM_PSPI is not set
# CONFIG_SPI_LANTIQ_SSC is not setCONFIG_SPI_OC_TINY=mCONFIG_SPI_OMAP24XX=y
# CONFIG_SPI_TI_QSPI is not setCONFIG_SPI_OMAP_100K=y
# CONFIG_SPI_ORION is not set
# CONFIG_SPI_PIC32 is not setCONFIG_SPI_PIC32_SQI=m
# CONFIG_SPI_PL022 is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_ROCKCHIP is not setCONFIG_SPI_ROCKCHIP_SFC=m
# CONFIG_SPI_RPCIF is not set
# CONFIG_SPI_RSPI is not setCONFIG_SPI_QUP=mCONFIG_SPI_S3C64XX=mCONFIG_SPI_SC18IS602=yCONFIG_SPI_SH_MSIOF=mCONFIG_SPI_SH=yCONFIG_SPI_SH_HSPI=mCONFIG_SPI_SIFIVE=m
# CONFIG_SPI_SLAVE_MT27XX is not setCONFIG_SPI_SPRD=yCONFIG_SPI_SPRD_ADI=m
# CONFIG_SPI_STM32 is not setCONFIG_SPI_STM32_QSPI=m
# CONFIG_SPI_ST_SSC4 is not setCONFIG_SPI_SUN4I=yCONFIG_SPI_SUN6I=mCONFIG_SPI_SUNPLUS_SP7021=yCONFIG_SPI_SYNQUACER=yCONFIG_SPI_MXIC=mCONFIG_SPI_TEGRA210_QUAD=m
# CONFIG_SPI_TEGRA114 is not set
# CONFIG_SPI_TEGRA20_SFLASH is not set
# CONFIG_SPI_TEGRA20_SLINK is not setCONFIG_SPI_UNIPHIER=mCONFIG_SPI_XCOMM=yCONFIG_SPI_XILINX=y
# CONFIG_SPI_XLP is not set
# CONFIG_SPI_XTENSA_XTFPGA is not setCONFIG_SPI_ZYNQ_QSPI=y
# CONFIG_SPI_ZYNQMP_GQSPI is not set
# CONFIG_SPI_AMD is not set
#
# SPI Multiplexer support
#CONFIG_SPI_MUX=y
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_LOOPBACK_TEST is not setCONFIG_SPI_TLE62X0=yCONFIG_SPI_SLAVE=yCONFIG_SPI_SLAVE_TIME=m
# CONFIG_SPI_SLAVE_SYSTEM_CONTROL is not setCONFIG_SPI_DYNAMIC=yCONFIG_SPMI=mCONFIG_SPMI_HISI3670=m
# CONFIG_SPMI_MSM_PMIC_ARB is not set
# CONFIG_SPMI_MTK_PMIF is not set
# CONFIG_HSI is not setCONFIG_PPS=mCONFIG_PPS_DEBUG=y
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not setCONFIG_PPS_CLIENT_LDISC=m
# CONFIG_PPS_CLIENT_PARPORT is not set
# CONFIG_PPS_CLIENT_GPIO is not set
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK_OPTIONAL=y
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. #
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_GENERIC_PINCTRL_GROUPS=yCONFIG_PINMUX=yCONFIG_GENERIC_PINMUX_FUNCTIONS=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=yCONFIG_DEBUG_PINCTRL=y
# CONFIG_PINCTRL_AMD is not set
# CONFIG_PINCTRL_APPLE_GPIO is not setCONFIG_PINCTRL_AS3722=m
# CONFIG_PINCTRL_AT91PIO4 is not setCONFIG_PINCTRL_AXP209=m
# CONFIG_PINCTRL_BM1880 is not setCONFIG_PINCTRL_CY8C95X0=yCONFIG_PINCTRL_DA850_PUPD=yCONFIG_PINCTRL_EQUILIBRIUM=mCONFIG_PINCTRL_INGENIC=yCONFIG_PINCTRL_KEEMBAY=mCONFIG_PINCTRL_LPC18XX=y
# CONFIG_PINCTRL_MAX77620 is not setCONFIG_PINCTRL_MCP23S08_I2C=mCONFIG_PINCTRL_MCP23S08_SPI=mCONFIG_PINCTRL_MCP23S08=m
# CONFIG_PINCTRL_MICROCHIP_SGPIO is not setCONFIG_PINCTRL_OCELOT=y
# CONFIG_PINCTRL_PISTACHIO is not setCONFIG_PINCTRL_RK805=mCONFIG_PINCTRL_ROCKCHIP=y
# CONFIG_PINCTRL_SINGLE is not setCONFIG_PINCTRL_STMFX=m
# CONFIG_PINCTRL_SX150X is not setCONFIG_PINCTRL_THUNDERBAY=mCONFIG_PINCTRL_OWL=y
# CONFIG_PINCTRL_S500 is not set
# CONFIG_PINCTRL_S700 is not set
# CONFIG_PINCTRL_S900 is not setCONFIG_PINCTRL_ASPEED=y
# CONFIG_PINCTRL_ASPEED_G4 is not setCONFIG_PINCTRL_ASPEED_G5=yCONFIG_PINCTRL_ASPEED_G6=y
# CONFIG_PINCTRL_BCM281XX is not setCONFIG_PINCTRL_BCM2835=yCONFIG_PINCTRL_BCM4908=mCONFIG_PINCTRL_BCM63XX=yCONFIG_PINCTRL_BCM6318=yCONFIG_PINCTRL_BCM6328=yCONFIG_PINCTRL_BCM6358=y
# CONFIG_PINCTRL_BCM6362 is not setCONFIG_PINCTRL_BCM6368=y
# CONFIG_PINCTRL_BCM63268 is not setCONFIG_PINCTRL_IPROC_GPIO=y
# CONFIG_PINCTRL_CYGNUS_MUX is not setCONFIG_PINCTRL_NS=y
# CONFIG_PINCTRL_NSP_GPIO is not set
# CONFIG_PINCTRL_NS2_MUX is not setCONFIG_PINCTRL_NSP_MUX=yCONFIG_PINCTRL_BERLIN=y
# CONFIG_PINCTRL_AS370 is not setCONFIG_PINCTRL_BERLIN_BG4CT=yCONFIG_PINCTRL_MADERA=yCONFIG_PINCTRL_CS47L90=yCONFIG_PINCTRL_CS47L92=y
#
# Intel pinctrl drivers
#
# end of Intel pinctrl drivers
#
# MediaTek pinctrl drivers
#CONFIG_EINT_MTK=yCONFIG_PINCTRL_MTK=yCONFIG_PINCTRL_MTK_V2=yCONFIG_PINCTRL_MTK_MOORE=yCONFIG_PINCTRL_MTK_PARIS=y
# CONFIG_PINCTRL_MT2701 is not set
# CONFIG_PINCTRL_MT7623 is not setCONFIG_PINCTRL_MT7629=yCONFIG_PINCTRL_MT8135=y
# CONFIG_PINCTRL_MT8127 is not set
# CONFIG_PINCTRL_MT2712 is not setCONFIG_PINCTRL_MT6765=mCONFIG_PINCTRL_MT6779=y
# CONFIG_PINCTRL_MT6795 is not setCONFIG_PINCTRL_MT6797=y
# CONFIG_PINCTRL_MT7622 is not setCONFIG_PINCTRL_MT7986=y
# CONFIG_PINCTRL_MT8167 is not set
# CONFIG_PINCTRL_MT8173 is not setCONFIG_PINCTRL_MT8183=yCONFIG_PINCTRL_MT8186=yCONFIG_PINCTRL_MT8188=y
# CONFIG_PINCTRL_MT8192 is not set
# CONFIG_PINCTRL_MT8195 is not setCONFIG_PINCTRL_MT8365=y
# CONFIG_PINCTRL_MT8516 is not setCONFIG_PINCTRL_MT6397=y
# end of MediaTek pinctrl drivers
CONFIG_PINCTRL_MESON=mCONFIG_PINCTRL_MESON_GXBB=mCONFIG_PINCTRL_MESON_GXL=mCONFIG_PINCTRL_MESON8_PMX=m
# CONFIG_PINCTRL_MESON_AXG is not setCONFIG_PINCTRL_MESON_AXG_PMX=mCONFIG_PINCTRL_MESON_G12A=mCONFIG_PINCTRL_MESON_A1=mCONFIG_PINCTRL_MESON_S4=mCONFIG_PINCTRL_MVEBU=yCONFIG_PINCTRL_ARMADA_AP806=yCONFIG_PINCTRL_ARMADA_CP110=yCONFIG_PINCTRL_AC5=yCONFIG_PINCTRL_ARMADA_37XX=y
# CONFIG_PINCTRL_WPCM450 is not set
# CONFIG_PINCTRL_NPCM7XX is not setCONFIG_PINCTRL_PXA=yCONFIG_PINCTRL_PXA25X=mCONFIG_PINCTRL_PXA27X=m
# CONFIG_PINCTRL_MSM is not setCONFIG_PINCTRL_QCOM_SPMI_PMIC=m
# CONFIG_PINCTRL_QCOM_SSBI_PMIC is not set
# CONFIG_PINCTRL_SC7280_LPASS_LPI is not setCONFIG_PINCTRL_SM8250_LPASS_LPI=mCONFIG_PINCTRL_SM8450_LPASS_LPI=mCONFIG_PINCTRL_SC8280XP_LPASS_LPI=mCONFIG_PINCTRL_LPASS_LPI=m
#
# Renesas pinctrl drivers
#CONFIG_PINCTRL_RENESAS=yCONFIG_PINCTRL_SH_PFC=yCONFIG_PINCTRL_SH_PFC_GPIO=yCONFIG_PINCTRL_SH_FUNC_GPIO=yCONFIG_PINCTRL_PFC_EMEV2=y
# CONFIG_PINCTRL_PFC_R8A77995 is not set
# CONFIG_PINCTRL_PFC_R8A7794 is not setCONFIG_PINCTRL_PFC_R8A77990=y
# CONFIG_PINCTRL_PFC_R8A7779 is not set
# CONFIG_PINCTRL_PFC_R8A7790 is not setCONFIG_PINCTRL_PFC_R8A77950=yCONFIG_PINCTRL_PFC_R8A77951=y
# CONFIG_PINCTRL_PFC_R8A7778 is not setCONFIG_PINCTRL_PFC_R8A7793=y
# CONFIG_PINCTRL_PFC_R8A7791 is not set
# CONFIG_PINCTRL_PFC_R8A77965 is not setCONFIG_PINCTRL_PFC_R8A77960=yCONFIG_PINCTRL_PFC_R8A77961=yCONFIG_PINCTRL_PFC_R8A779F0=y
# CONFIG_PINCTRL_PFC_R8A7792 is not set
# CONFIG_PINCTRL_PFC_R8A77980 is not setCONFIG_PINCTRL_PFC_R8A77970=yCONFIG_PINCTRL_PFC_R8A779A0=yCONFIG_PINCTRL_PFC_R8A779G0=y
# CONFIG_PINCTRL_PFC_R8A7740 is not set
# CONFIG_PINCTRL_PFC_R8A73A4 is not set
# CONFIG_PINCTRL_RZA1 is not setCONFIG_PINCTRL_RZA2=yCONFIG_PINCTRL_RZG2L=y
# CONFIG_PINCTRL_PFC_R8A77470 is not set
# CONFIG_PINCTRL_PFC_R8A7745 is not set
# CONFIG_PINCTRL_PFC_R8A7742 is not setCONFIG_PINCTRL_PFC_R8A7743=y
# CONFIG_PINCTRL_PFC_R8A7744 is not setCONFIG_PINCTRL_PFC_R8A774C0=yCONFIG_PINCTRL_PFC_R8A774E1=yCONFIG_PINCTRL_PFC_R8A774A1=y
# CONFIG_PINCTRL_PFC_R8A774B1 is not set
# CONFIG_PINCTRL_RZN1 is not setCONFIG_PINCTRL_RZV2M=yCONFIG_PINCTRL_PFC_SH7203=y
# CONFIG_PINCTRL_PFC_SH7264 is not setCONFIG_PINCTRL_PFC_SH7269=yCONFIG_PINCTRL_PFC_SH7720=yCONFIG_PINCTRL_PFC_SH7722=y
# CONFIG_PINCTRL_PFC_SH7734 is not set
# CONFIG_PINCTRL_PFC_SH7757 is not setCONFIG_PINCTRL_PFC_SH7785=yCONFIG_PINCTRL_PFC_SH7786=y
# CONFIG_PINCTRL_PFC_SH73A0 is not set
# CONFIG_PINCTRL_PFC_SH7723 is not set
# CONFIG_PINCTRL_PFC_SH7724 is not setCONFIG_PINCTRL_PFC_SHX3=y
# end of Renesas pinctrl drivers
CONFIG_PINCTRL_SAMSUNG=yCONFIG_PINCTRL_EXYNOS=y
# CONFIG_PINCTRL_EXYNOS_ARM is not setCONFIG_PINCTRL_EXYNOS_ARM64=yCONFIG_PINCTRL_S3C24XX=yCONFIG_PINCTRL_S3C64XX=yCONFIG_PINCTRL_SPRD=yCONFIG_PINCTRL_SPRD_SC9860=yCONFIG_PINCTRL_STARFIVE_JH7100=mCONFIG_PINCTRL_STM32=yCONFIG_PINCTRL_STM32F429=y
# CONFIG_PINCTRL_STM32F469 is not setCONFIG_PINCTRL_STM32F746=yCONFIG_PINCTRL_STM32F769=yCONFIG_PINCTRL_STM32H743=y
# CONFIG_PINCTRL_STM32MP135 is not set
# CONFIG_PINCTRL_STM32MP157 is not setCONFIG_PINCTRL_SUNXI=y
# CONFIG_PINCTRL_SUN4I_A10 is not setCONFIG_PINCTRL_SUN5I=y
# CONFIG_PINCTRL_SUN6I_A31 is not set
# CONFIG_PINCTRL_SUN6I_A31_R is not set
# CONFIG_PINCTRL_SUN8I_A23 is not setCONFIG_PINCTRL_SUN8I_A33=y
# CONFIG_PINCTRL_SUN8I_A83T is not set
# CONFIG_PINCTRL_SUN8I_A83T_R is not setCONFIG_PINCTRL_SUN8I_A23_R=y
# CONFIG_PINCTRL_SUN8I_H3 is not setCONFIG_PINCTRL_SUN8I_H3_R=yCONFIG_PINCTRL_SUN8I_V3S=yCONFIG_PINCTRL_SUN9I_A80=yCONFIG_PINCTRL_SUN9I_A80_R=yCONFIG_PINCTRL_SUN20I_D1=y
# CONFIG_PINCTRL_SUN50I_A64 is not set
# CONFIG_PINCTRL_SUN50I_A64_R is not setCONFIG_PINCTRL_SUN50I_A100=yCONFIG_PINCTRL_SUN50I_A100_R=yCONFIG_PINCTRL_SUN50I_H5=y
# CONFIG_PINCTRL_SUN50I_H6 is not set
# CONFIG_PINCTRL_SUN50I_H6_R is not set
# CONFIG_PINCTRL_SUN50I_H616 is not setCONFIG_PINCTRL_SUN50I_H616_R=yCONFIG_PINCTRL_TI_IODELAY=yCONFIG_PINCTRL_UNIPHIER=y
# CONFIG_PINCTRL_UNIPHIER_LD4 is not setCONFIG_PINCTRL_UNIPHIER_PRO4=yCONFIG_PINCTRL_UNIPHIER_SLD8=y
# CONFIG_PINCTRL_UNIPHIER_PRO5 is not set
# CONFIG_PINCTRL_UNIPHIER_PXS2 is not set
# CONFIG_PINCTRL_UNIPHIER_LD6B is not set
# CONFIG_PINCTRL_UNIPHIER_LD11 is not set
# CONFIG_PINCTRL_UNIPHIER_LD20 is not set
# CONFIG_PINCTRL_UNIPHIER_PXS3 is not setCONFIG_PINCTRL_UNIPHIER_NX1=y
# CONFIG_PINCTRL_TMPV7700 is not setCONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_OF_GPIO=yCONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not setCONFIG_GPIO_CDEV=yCONFIG_GPIO_CDEV_V1=yCONFIG_GPIO_GENERIC=yCONFIG_GPIO_REGMAP=yCONFIG_GPIO_MAX730X=y
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_74XX_MMIO=yCONFIG_GPIO_ALTERA=mCONFIG_GPIO_ASPEED=mCONFIG_GPIO_ASPEED_SGPIO=y
# CONFIG_GPIO_ATH79 is not set
# CONFIG_GPIO_RASPBERRYPI_EXP is not set
# CONFIG_GPIO_BCM_KONA is not setCONFIG_GPIO_BCM_XGS_IPROC=yCONFIG_GPIO_BRCMSTB=m
# CONFIG_GPIO_CADENCE is not setCONFIG_GPIO_CLPS711X=y
# CONFIG_GPIO_DAVINCI is not setCONFIG_GPIO_DWAPB=mCONFIG_GPIO_EIC_SPRD=yCONFIG_GPIO_EM=mCONFIG_GPIO_FTGPIO010=yCONFIG_GPIO_GENERIC_PLATFORM=yCONFIG_GPIO_GRGPIO=y
# CONFIG_GPIO_HISI is not setCONFIG_GPIO_HLWD=m
# CONFIG_GPIO_IOP is not set
# CONFIG_GPIO_LOGICVC is not setCONFIG_GPIO_LPC18XX=yCONFIG_GPIO_LPC32XX=mCONFIG_GPIO_MB86S7X=mCONFIG_GPIO_MENZ127=y
# CONFIG_GPIO_MPC8XXX is not setCONFIG_GPIO_MT7621=yCONFIG_GPIO_MVEBU=y
# CONFIG_GPIO_MXC is not setCONFIG_GPIO_MXS=yCONFIG_GPIO_PL061=m
# CONFIG_GPIO_PMIC_EIC_SPRD is not set
# CONFIG_GPIO_PXA is not setCONFIG_GPIO_RCAR=mCONFIG_GPIO_RDA=y
# CONFIG_GPIO_ROCKCHIP is not set
# CONFIG_GPIO_SAMA5D2_PIOBU is not setCONFIG_GPIO_SIFIVE=y
# CONFIG_GPIO_SNPS_CREG is not setCONFIG_GPIO_SPRD=m
# CONFIG_GPIO_STP_XWAY is not set
# CONFIG_GPIO_SYSCON is not setCONFIG_GPIO_TEGRA=m
# CONFIG_GPIO_TEGRA186 is not setCONFIG_GPIO_TS4800=y
# CONFIG_GPIO_UNIPHIER is not setCONFIG_GPIO_VISCONTI=y
# CONFIG_GPIO_XGENE is not setCONFIG_GPIO_XGENE_SB=mCONFIG_GPIO_XILINX=y
# CONFIG_GPIO_XLP is not setCONFIG_GPIO_AMD_FCH=yCONFIG_GPIO_IDT3243X=m
# end of Memory mapped GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADNP is not setCONFIG_GPIO_GW_PLD=mCONFIG_GPIO_MAX7300=mCONFIG_GPIO_MAX732X=y
# CONFIG_GPIO_MAX732X_IRQ is not setCONFIG_GPIO_PCA953X=mCONFIG_GPIO_PCA953X_IRQ=yCONFIG_GPIO_PCA9570=mCONFIG_GPIO_PCF857X=y
# CONFIG_GPIO_TPIC2810 is not set
# CONFIG_GPIO_TS4900 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#CONFIG_GPIO_ADP5520=y
# CONFIG_GPIO_BD9571MWV is not setCONFIG_GPIO_DA9052=mCONFIG_GPIO_DA9055=m
# CONFIG_GPIO_LP873X is not setCONFIG_GPIO_LP87565=mCONFIG_GPIO_MADERA=mCONFIG_GPIO_MAX77620=mCONFIG_GPIO_SL28CPLD=m
# CONFIG_GPIO_STMPE is not setCONFIG_GPIO_TC3589X=y
# CONFIG_GPIO_TPS65086 is not setCONFIG_GPIO_TPS6586X=yCONFIG_GPIO_TPS65912=mCONFIG_GPIO_TWL4030=yCONFIG_GPIO_WM831X=mCONFIG_GPIO_WM8994=m
# end of MFD GPIO expanders
#
# SPI GPIO expanders
#CONFIG_GPIO_74X164=yCONFIG_GPIO_MAX3191X=mCONFIG_GPIO_MAX7301=yCONFIG_GPIO_MC33880=mCONFIG_GPIO_PISOSR=mCONFIG_GPIO_XRA1403=m
# end of SPI GPIO expanders
#
# Virtual GPIO drivers
#
# CONFIG_GPIO_AGGREGATOR is not setCONFIG_GPIO_MOCKUP=yCONFIG_GPIO_VIRTIO=mCONFIG_GPIO_SIM=y
# end of Virtual GPIO drivers
CONFIG_W1=y
#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_DS2482 is not set
# CONFIG_W1_MASTER_MXC is not set
# CONFIG_W1_MASTER_DS1WM is not set
# CONFIG_W1_MASTER_GPIO is not setCONFIG_W1_MASTER_SGI=m
# end of 1-wire Bus Masters
#
# 1-wire Slaves
#CONFIG_W1_SLAVE_THERM=yCONFIG_W1_SLAVE_SMEM=y
# CONFIG_W1_SLAVE_DS2405 is not setCONFIG_W1_SLAVE_DS2408=y
# CONFIG_W1_SLAVE_DS2408_READBACK is not setCONFIG_W1_SLAVE_DS2413=m
# CONFIG_W1_SLAVE_DS2406 is not setCONFIG_W1_SLAVE_DS2423=y
# CONFIG_W1_SLAVE_DS2805 is not set
# CONFIG_W1_SLAVE_DS2430 is not setCONFIG_W1_SLAVE_DS2431=yCONFIG_W1_SLAVE_DS2433=m
# CONFIG_W1_SLAVE_DS2433_CRC is not setCONFIG_W1_SLAVE_DS2438=m
# CONFIG_W1_SLAVE_DS250X is not setCONFIG_W1_SLAVE_DS2780=yCONFIG_W1_SLAVE_DS2781=y
# CONFIG_W1_SLAVE_DS28E04 is not set
# CONFIG_W1_SLAVE_DS28E17 is not set
# end of 1-wire Slaves
CONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_AS3722 is not setCONFIG_POWER_RESET_ATC260X=yCONFIG_POWER_RESET_BRCMKONA=y
# CONFIG_POWER_RESET_BRCMSTB is not setCONFIG_POWER_RESET_GEMINI_POWEROFF=y
# CONFIG_POWER_RESET_GPIO is not set
# CONFIG_POWER_RESET_GPIO_RESTART is not set
# CONFIG_POWER_RESET_HISI is not setCONFIG_POWER_RESET_OCELOT_RESET=y
# CONFIG_POWER_RESET_LTC2952 is not setCONFIG_POWER_RESET_REGULATOR=yCONFIG_POWER_RESET_RESTART=y
# CONFIG_POWER_RESET_TPS65086 is not set
# CONFIG_POWER_RESET_XGENE is not set
# CONFIG_POWER_RESET_KEYSTONE is not setCONFIG_POWER_RESET_SYSCON=y
# CONFIG_POWER_RESET_SYSCON_POWEROFF is not setCONFIG_POWER_RESET_RMOBILE=mCONFIG_REBOOT_MODE=m
# CONFIG_SYSCON_REBOOT_MODE is not setCONFIG_POWER_RESET_SC27XX=yCONFIG_NVMEM_REBOOT_MODE=mCONFIG_POWER_SUPPLY=yCONFIG_POWER_SUPPLY_DEBUG=y
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_IP5XXX_POWER is not set
# CONFIG_MAX8925_POWER is not setCONFIG_WM831X_BACKUP=y
# CONFIG_WM831X_POWER is not setCONFIG_TEST_POWER=m
# CONFIG_CHARGER_ADP5061 is not setCONFIG_BATTERY_ACT8945A=mCONFIG_BATTERY_CW2015=y
# CONFIG_BATTERY_DS2760 is not setCONFIG_BATTERY_DS2780=yCONFIG_BATTERY_DS2781=y
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_LEGO_EV3 is not set
# CONFIG_BATTERY_SAMSUNG_SDI is not set
# CONFIG_BATTERY_INGENIC is not setCONFIG_BATTERY_SBS=yCONFIG_CHARGER_SBS=yCONFIG_MANAGER_SBS=m
# CONFIG_BATTERY_BQ27XXX is not setCONFIG_BATTERY_DA9052=mCONFIG_CHARGER_DA9150=mCONFIG_BATTERY_DA9150=mCONFIG_AXP20X_POWER=m
# CONFIG_BATTERY_MAX17040 is not setCONFIG_BATTERY_MAX17042=yCONFIG_BATTERY_MAX1721X=y
# CONFIG_BATTERY_TWL4030_MADC is not set
# CONFIG_CHARGER_PCF50633 is not setCONFIG_BATTERY_RX51=m
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_TWL4030 is not setCONFIG_CHARGER_LP8727=y
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_MANAGER is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_LTC4162L is not set
# CONFIG_CHARGER_DETECTOR_MAX14656 is not setCONFIG_CHARGER_MAX77693=yCONFIG_CHARGER_MAX77976=mCONFIG_CHARGER_MAX8997=mCONFIG_CHARGER_MT6360=m
# CONFIG_CHARGER_MT6370 is not set
# CONFIG_CHARGER_QCOM_SMBB is not setCONFIG_CHARGER_BQ2415X=yCONFIG_CHARGER_BQ24190=yCONFIG_CHARGER_BQ24257=mCONFIG_CHARGER_BQ24735=m
# CONFIG_CHARGER_BQ2515X is not setCONFIG_CHARGER_BQ25890=mCONFIG_CHARGER_BQ25980=y
# CONFIG_CHARGER_BQ256XX is not set
# CONFIG_CHARGER_RK817 is not setCONFIG_CHARGER_SMB347=yCONFIG_CHARGER_TPS65090=mCONFIG_CHARGER_TPS65217=mCONFIG_BATTERY_GAUGE_LTC2941=y
# CONFIG_BATTERY_GOLDFISH is not setCONFIG_BATTERY_RT5033=mCONFIG_CHARGER_RT9455=yCONFIG_CHARGER_SC2731=yCONFIG_FUEL_GAUGE_SC27XX=mCONFIG_CHARGER_UCS1002=mCONFIG_CHARGER_BD99954=y
# CONFIG_BATTERY_UG3105 is not setCONFIG_HWMON=mCONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#CONFIG_SENSORS_AD7314=m CONFIG_SENSORS_AD7414=m CONFIG_SENSORS_AD7418=m
# CONFIG_SENSORS_ADM1025 is not set CONFIG_SENSORS_ADM1026=m CONFIG_SENSORS_ADM1029=m CONFIG_SENSORS_ADM1031=m
# CONFIG_SENSORS_ADM1177 is not set CONFIG_SENSORS_ADM9240=m CONFIG_SENSORS_ADT7X10=m CONFIG_SENSORS_ADT7310=m
# CONFIG_SENSORS_ADT7410 is not set CONFIG_SENSORS_ADT7411=m CONFIG_SENSORS_ADT7462=m CONFIG_SENSORS_ADT7470=m
# CONFIG_SENSORS_ADT7475 is not set CONFIG_SENSORS_AHT10=m CONFIG_SENSORS_AS370=m CONFIG_SENSORS_ASC7621=m
# CONFIG_SENSORS_AXI_FAN_CONTROL is not set # CONFIG_SENSORS_ARM_SCMI is not set
# CONFIG_SENSORS_ASB100 is not set CONFIG_SENSORS_ASPEED=m CONFIG_SENSORS_ATXP1=m
# CONFIG_SENSORS_BT1_PVT is not set CONFIG_SENSORS_CORSAIR_CPRO=m CONFIG_SENSORS_CORSAIR_PSU=m CONFIG_SENSORS_DS620=m CONFIG_SENSORS_DS1621=m CONFIG_SENSORS_DA9052_ADC=m CONFIG_SENSORS_DA9055=m
# CONFIG_SENSORS_SPARX5 is not set
# CONFIG_SENSORS_F71805F is not set CONFIG_SENSORS_F71882FG=m CONFIG_SENSORS_F75375S=m
# CONFIG_SENSORS_GSC is not set CONFIG_SENSORS_MC13783_ADC=m
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_G762 is not set CONFIG_SENSORS_GPIO_FAN=m CONFIG_SENSORS_HIH6130=m CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IIO_HWMON=m
# CONFIG_SENSORS_IT87 is not set CONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not set CONFIG_SENSORS_LAN966X=m CONFIG_SENSORS_LINEAGE=m CONFIG_SENSORS_LTC2945=m CONFIG_SENSORS_LTC2947=m CONFIG_SENSORS_LTC2947_I2C=m
# CONFIG_SENSORS_LTC2947_SPI is not set
# CONFIG_SENSORS_LTC2990 is not set
# CONFIG_SENSORS_LTC2992 is not set CONFIG_SENSORS_LTC4151=m
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4222 is not set CONFIG_SENSORS_LTC4245=m CONFIG_SENSORS_LTC4260=m CONFIG_SENSORS_LTC4261=m
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX127 is not set
# CONFIG_SENSORS_MAX16065 is not set CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_MAX1668 is not set CONFIG_SENSORS_MAX197=m CONFIG_SENSORS_MAX31722=m CONFIG_SENSORS_MAX31730=m
# CONFIG_SENSORS_MAX31760 is not set CONFIG_SENSORS_MAX6620=m CONFIG_SENSORS_MAX6621=m CONFIG_SENSORS_MAX6639=m CONFIG_SENSORS_MAX6650=m CONFIG_SENSORS_MAX6697=m CONFIG_SENSORS_MAX31790=m CONFIG_SENSORS_MCP3021=m CONFIG_SENSORS_TC654=m CONFIG_SENSORS_TPS23861=m
# CONFIG_SENSORS_MR75203 is not set CONFIG_SENSORS_ADCXX=m
# CONFIG_SENSORS_LM63 is not set CONFIG_SENSORS_LM70=m
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set CONFIG_SENSORS_LM77=m
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_LM90=m CONFIG_SENSORS_LM92=m CONFIG_SENSORS_LM93=m
# CONFIG_SENSORS_LM95234 is not set CONFIG_SENSORS_LM95241=m CONFIG_SENSORS_LM95245=m CONFIG_SENSORS_PC87360=m CONFIG_SENSORS_PC87427=m CONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not set CONFIG_SENSORS_NCT6775_CORE=m CONFIG_SENSORS_NCT6775=m CONFIG_SENSORS_NCT6775_I2C=m CONFIG_SENSORS_NCT7802=m CONFIG_SENSORS_NPCM7XX=m CONFIG_SENSORS_NSA320=m
# CONFIG_SENSORS_OCC_P8_I2C is not set CONFIG_SENSORS_PCF8591=m CONFIG_SENSORS_PECI_CPUTEMP=m CONFIG_SENSORS_PECI_DIMMTEMP=m CONFIG_SENSORS_PECI=mCONFIG_PMBUS=m
# CONFIG_SENSORS_PMBUS is not set CONFIG_SENSORS_ADM1266=m CONFIG_SENSORS_ADM1275=m
# CONFIG_SENSORS_BEL_PFE is not set CONFIG_SENSORS_BPA_RS600=m CONFIG_SENSORS_DELTA_AHE50DC_FAN=m CONFIG_SENSORS_FSP_3Y=m
# CONFIG_SENSORS_IBM_CFFPS is not set CONFIG_SENSORS_DPS920AB=m CONFIG_SENSORS_INSPUR_IPSPS=m
# CONFIG_SENSORS_IR35221 is not set CONFIG_SENSORS_IR36021=m
# CONFIG_SENSORS_IR38064 is not set CONFIG_SENSORS_IRPS5401=m CONFIG_SENSORS_ISL68137=m CONFIG_SENSORS_LM25066=m CONFIG_SENSORS_LM25066_REGULATOR=y CONFIG_SENSORS_LT7182S=m
# CONFIG_SENSORS_LTC2978 is not set CONFIG_SENSORS_LTC3815=m CONFIG_SENSORS_MAX15301=m CONFIG_SENSORS_MAX16064=m CONFIG_SENSORS_MAX16601=m
# CONFIG_SENSORS_MAX20730 is not set
# CONFIG_SENSORS_MAX20751 is not set
# CONFIG_SENSORS_MAX31785 is not set CONFIG_SENSORS_MAX34440=m
# CONFIG_SENSORS_MAX8688 is not set CONFIG_SENSORS_MP2888=m CONFIG_SENSORS_MP2975=m CONFIG_SENSORS_MP5023=m
# CONFIG_SENSORS_PIM4328 is not set
# CONFIG_SENSORS_PLI1209BC is not set CONFIG_SENSORS_PM6764TR=m
# CONFIG_SENSORS_PXE1610 is not set CONFIG_SENSORS_Q54SJ108A2=m CONFIG_SENSORS_STPDDC60=m
# CONFIG_SENSORS_TPS40422 is not set CONFIG_SENSORS_TPS53679=m
# CONFIG_SENSORS_TPS546D24 is not set CONFIG_SENSORS_UCD9000=m
# CONFIG_SENSORS_UCD9200 is not set CONFIG_SENSORS_XDPE152=m CONFIG_SENSORS_XDPE122=m
# CONFIG_SENSORS_XDPE122_REGULATOR is not set CONFIG_SENSORS_ZL6100=m CONFIG_SENSORS_PWM_FAN=m
# CONFIG_SENSORS_RASPBERRYPI_HWMON is not set # CONFIG_SENSORS_SL28CPLD is not set CONFIG_SENSORS_SBTSI=m CONFIG_SENSORS_SBRMI=m CONFIG_SENSORS_SHT15=m CONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set CONFIG_SENSORS_SHT4x=m CONFIG_SENSORS_SHTC1=m CONFIG_SENSORS_SY7636A=m CONFIG_SENSORS_DME1737=m CONFIG_SENSORS_EMC1403=m CONFIG_SENSORS_EMC2103=m CONFIG_SENSORS_EMC2305=m
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set CONFIG_SENSORS_STTS751=m CONFIG_SENSORS_SMM665=m CONFIG_SENSORS_ADC128D818=m CONFIG_SENSORS_ADS7828=m CONFIG_SENSORS_ADS7871=m CONFIG_SENSORS_AMC6821=m CONFIG_SENSORS_INA209=m CONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA238 is not set CONFIG_SENSORS_INA3221=m
# CONFIG_SENSORS_TC74 is not set
# CONFIG_SENSORS_THMC50 is not set CONFIG_SENSORS_TMP102=m CONFIG_SENSORS_TMP103=m CONFIG_SENSORS_TMP108=m CONFIG_SENSORS_TMP401=m
# CONFIG_SENSORS_TMP421 is not set CONFIG_SENSORS_TMP464=m
# CONFIG_SENSORS_TMP513 is not set CONFIG_SENSORS_VEXPRESS=m CONFIG_SENSORS_VT1211=m CONFIG_SENSORS_W83773G=m CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83791D=m
# CONFIG_SENSORS_W83792D is not set CONFIG_SENSORS_W83793=m CONFIG_SENSORS_W83795=m CONFIG_SENSORS_W83795_FANCTRL=y CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83L786NG=m
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set CONFIG_SENSORS_WM831X=m CONFIG_SENSORS_INTEL_M10_BMC_HWMON=m CONFIG_THERMAL=y
# CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_OF=y
# CONFIG_THERMAL_WRITABLE_TRIPS is not set 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 is not set CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_CPU_THERMAL is not set CONFIG_DEVFREQ_THERMAL=y
# CONFIG_THERMAL_EMULATION is not set CONFIG_THERMAL_MMIO=m CONFIG_HISI_THERMAL=yCONFIG_IMX_THERMAL=y CONFIG_IMX8MM_THERMAL=y CONFIG_K3_THERMAL=m
# CONFIG_MAX77620_THERMAL is not set CONFIG_QORIQ_THERMAL=m CONFIG_SPEAR_THERMAL=y
# CONFIG_SUN8I_THERMAL is not set CONFIG_ROCKCHIP_THERMAL=m
# CONFIG_RCAR_THERMAL is not set
# CONFIG_RCAR_GEN3_THERMAL is not set
# CONFIG_RZG2L_THERMAL is not set
# CONFIG_KIRKWOOD_THERMAL is not set
# CONFIG_DOVE_THERMAL is not set
# CONFIG_ARMADA_THERMAL is not set CONFIG_DA9062_THERMAL=m
# CONFIG_MTK_THERMAL is not set CONFIG_AMLOGIC_THERMAL=m
#
# Intel thermal drivers
#
#
# ACPI INT340X thermal drivers
#
# end of ACPI INT340X thermal drivers # end of Intel thermal drivers
#
# Broadcom thermal drivers
#CONFIG_BCM2711_THERMAL=mCONFIG_BCM2835_THERMAL=y
# CONFIG_BRCMSTB_THERMAL is not set
# CONFIG_BCM_NS_THERMAL is not setCONFIG_BCM_SR_THERMAL=m
# end of Broadcom thermal drivers
#
# Texas Instruments thermal drivers
#CONFIG_TI_SOC_THERMAL=m
# CONFIG_TI_THERMAL is not setCONFIG_OMAP3_THERMAL=yCONFIG_OMAP4_THERMAL=yCONFIG_OMAP5_THERMAL=yCONFIG_DRA752_THERMAL=y
# end of Texas Instruments thermal drivers
#
# Samsung thermal drivers
#CONFIG_EXYNOS_THERMAL=y
# end of Samsung thermal drivers
#
# NVIDIA Tegra thermal drivers
#
# CONFIG_TEGRA_SOCTHERM is not set
# CONFIG_TEGRA_BPMP_THERMAL is not setCONFIG_TEGRA30_TSENSOR=m
# end of NVIDIA Tegra thermal drivers
CONFIG_GENERIC_ADC_THERMAL=m
#
# Qualcomm thermal drivers
#CONFIG_QCOM_TSENS=y
# CONFIG_QCOM_SPMI_ADC_TM5 is not setCONFIG_QCOM_SPMI_TEMP_ALARM=m
# end of Qualcomm thermal drivers
CONFIG_UNIPHIER_THERMAL=yCONFIG_SPRD_THERMAL=y
# CONFIG_WATCHDOG is not setCONFIG_SSB_POSSIBLE=yCONFIG_SSB=mCONFIG_SSB_SPROM=yCONFIG_SSB_SDIOHOST_POSSIBLE=yCONFIG_SSB_SDIOHOST=yCONFIG_SSB_HOST_SOC=y
# CONFIG_SSB_DRIVER_GPIO is not setCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=mCONFIG_BCMA_HOST_SOC=yCONFIG_BCMA_DRIVER_MIPS=yCONFIG_BCMA_PFLASH=yCONFIG_BCMA_SFLASH=yCONFIG_BCMA_NFLASH=y
# CONFIG_BCMA_DRIVER_GMAC_CMN is not setCONFIG_BCMA_DRIVER_GPIO=yCONFIG_BCMA_DEBUG=y
#
# Multifunction device drivers
#CONFIG_MFD_CORE=yCONFIG_MFD_ACT8945A=mCONFIG_MFD_SUN4I_GPADC=mCONFIG_MFD_AS3711=yCONFIG_MFD_AS3722=mCONFIG_PMIC_ADP5520=yCONFIG_MFD_AAT2870_CORE=yCONFIG_MFD_AT91_USART=yCONFIG_MFD_ATMEL_FLEXCOM=y
# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_MFD_BCM590XX is not setCONFIG_MFD_BD9571MWV=yCONFIG_MFD_AXP20X=mCONFIG_MFD_AXP20X_I2C=mCONFIG_MFD_MADERA=yCONFIG_MFD_MADERA_I2C=y
# CONFIG_MFD_MADERA_SPI is not set
# CONFIG_MFD_CS47L15 is not set
# CONFIG_MFD_CS47L35 is not set
# CONFIG_MFD_CS47L85 is not setCONFIG_MFD_CS47L90=yCONFIG_MFD_CS47L92=yCONFIG_MFD_ASIC3=y
# CONFIG_PMIC_DA903X is not setCONFIG_PMIC_DA9052=yCONFIG_MFD_DA9052_SPI=y
# CONFIG_MFD_DA9052_I2C is not setCONFIG_MFD_DA9055=y
# CONFIG_MFD_DA9062 is not setCONFIG_MFD_DA9063=yCONFIG_MFD_DA9150=mCONFIG_MFD_ENE_KB3930=y
# CONFIG_MFD_EXYNOS_LPASS is not setCONFIG_MFD_GATEWORKS_GSC=yCONFIG_MFD_MC13XXX=yCONFIG_MFD_MC13XXX_SPI=yCONFIG_MFD_MC13XXX_I2C=yCONFIG_MFD_MP2629=yCONFIG_MFD_MXS_LRADC=mCONFIG_MFD_MX25_TSADC=yCONFIG_MFD_HI6421_PMIC=m
# CONFIG_MFD_HI6421_SPMI is not set
# CONFIG_MFD_HI655X_PMIC is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_IQS62X 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 setCONFIG_MFD_MAX77620=y
# CONFIG_MFD_MAX77650 is not setCONFIG_MFD_MAX77686=mCONFIG_MFD_MAX77693=yCONFIG_MFD_MAX77714=y
# CONFIG_MFD_MAX77843 is not setCONFIG_MFD_MAX8907=mCONFIG_MFD_MAX8925=yCONFIG_MFD_MAX8997=yCONFIG_MFD_MAX8998=yCONFIG_MFD_MT6360=mCONFIG_MFD_MT6370=m
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not setCONFIG_MFD_OCELOT=y
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_CPCAP is not setCONFIG_MFD_NTXEC=yCONFIG_MFD_RETU=yCONFIG_MFD_PCF50633=mCONFIG_PCF50633_ADC=m
# CONFIG_PCF50633_GPIO is not set
# CONFIG_UCB1400_CORE is not setCONFIG_MFD_PM8XXX=m
# CONFIG_MFD_SPMI_PMIC is not setCONFIG_MFD_SY7636A=y
# CONFIG_MFD_RT4831 is not setCONFIG_MFD_RT5033=yCONFIG_MFD_RT5120=y
# CONFIG_MFD_RC5T583 is not setCONFIG_MFD_RK808=y
# CONFIG_MFD_RN5T618 is not setCONFIG_MFD_SEC_CORE=m
# CONFIG_MFD_SI476X_CORE is not setCONFIG_MFD_SIMPLE_MFD_I2C=y
# CONFIG_MFD_SL28CPLD is not setCONFIG_MFD_SM501=y
# CONFIG_MFD_SM501_GPIO is not setCONFIG_MFD_SKY81452=mCONFIG_MFD_SC27XX_PMIC=yCONFIG_ABX500_CORE=yCONFIG_MFD_STMPE=y
#
# STMicroelectronics STMPE Interface Drivers
#
# CONFIG_STMPE_I2C is not setCONFIG_STMPE_SPI=y
# end of STMicroelectronics STMPE Interface Drivers
CONFIG_MFD_SUN6I_PRCM=yCONFIG_MFD_SYSCON=y
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not setCONFIG_MFD_LP8788=yCONFIG_MFD_TI_LMU=m
# CONFIG_MFD_PALMAS is not setCONFIG_TPS6105X=y
# CONFIG_TPS65010 is not setCONFIG_TPS6507X=mCONFIG_MFD_TPS65086=mCONFIG_MFD_TPS65090=yCONFIG_MFD_TPS65217=mCONFIG_MFD_TI_LP873X=mCONFIG_MFD_TI_LP87565=y
# CONFIG_MFD_TPS65218 is not setCONFIG_MFD_TPS6586X=y
# CONFIG_MFD_TPS65910 is not setCONFIG_MFD_TPS65912=mCONFIG_MFD_TPS65912_I2C=m
# CONFIG_MFD_TPS65912_SPI is not setCONFIG_TWL4030_CORE=yCONFIG_MFD_TWL4030_AUDIO=y
# CONFIG_TWL6040_CORE is not setCONFIG_MFD_WL1273_CORE=m
# CONFIG_MFD_LM3533 is not setCONFIG_MFD_TC3589X=yCONFIG_MFD_TQMX86=m
# CONFIG_MFD_LOCHNAGAR is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not setCONFIG_MFD_WM831X=yCONFIG_MFD_WM831X_I2C=yCONFIG_MFD_WM831X_SPI=y
# CONFIG_MFD_WM8350_I2C is not setCONFIG_MFD_WM8994=mCONFIG_MFD_STW481X=yCONFIG_MFD_ROHM_BD718XX=m
# CONFIG_MFD_ROHM_BD71828 is not setCONFIG_MFD_ROHM_BD957XMUF=y
# CONFIG_MFD_STM32_LPTIMER is not setCONFIG_MFD_STM32_TIMERS=yCONFIG_MFD_STPMIC1=yCONFIG_MFD_STMFX=yCONFIG_MFD_ATC260X=yCONFIG_MFD_ATC260X_I2C=y
# CONFIG_MFD_KHADAS_MCU is not set
# CONFIG_MFD_ACER_A500_EC is not setCONFIG_MFD_QCOM_PM8008=mCONFIG_MFD_VEXPRESS_SYSREG=mCONFIG_RAVE_SP_CORE=mCONFIG_MFD_INTEL_M10_BMC=y
# CONFIG_MFD_RSMU_I2C is not set
# CONFIG_MFD_RSMU_SPI is not set
# end of Multifunction device drivers
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set CONFIG_REGULATOR_FIXED_VOLTAGE=y CONFIG_REGULATOR_VIRTUAL_CONSUMER=y
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set CONFIG_REGULATOR_88PG86X=m
# CONFIG_REGULATOR_ACT8865 is not set
# CONFIG_REGULATOR_ACT8945A is not set CONFIG_REGULATOR_AD5398=y
# CONFIG_REGULATOR_ANATOP is not set CONFIG_REGULATOR_AAT2870=m CONFIG_REGULATOR_ARIZONA_LDO1=m
# CONFIG_REGULATOR_ARIZONA_MICSUPP is not set CONFIG_REGULATOR_ARM_SCMI=m CONFIG_REGULATOR_AS3711=m CONFIG_REGULATOR_AS3722=m CONFIG_REGULATOR_ATC260X=m CONFIG_REGULATOR_AXP20X=m CONFIG_REGULATOR_BD718XX=m CONFIG_REGULATOR_BD9571MWV=y CONFIG_REGULATOR_BD957XMUF=m CONFIG_REGULATOR_DA9052=m
# CONFIG_REGULATOR_DA9055 is not set CONFIG_REGULATOR_DA9063=m
# CONFIG_REGULATOR_DA9121 is not set CONFIG_REGULATOR_DA9210=m CONFIG_REGULATOR_DA9211=m CONFIG_REGULATOR_FAN53555=y CONFIG_REGULATOR_FAN53880=y CONFIG_REGULATOR_GPIO=mCONFIG_REGULATOR_HI6421=m CONFIG_REGULATOR_HI6421V530=m
# CONFIG_REGULATOR_ISL9305 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_LM363X is not set CONFIG_REGULATOR_LP3971=y CONFIG_REGULATOR_LP3972=y
# CONFIG_REGULATOR_LP872X is not set CONFIG_REGULATOR_LP873X=m CONFIG_REGULATOR_LP8755=y
# CONFIG_REGULATOR_LP87565 is not set CONFIG_REGULATOR_LP8788=y
# CONFIG_REGULATOR_LTC3589 is not set
# CONFIG_REGULATOR_LTC3676 is not set
# CONFIG_REGULATOR_MAX1586 is not set CONFIG_REGULATOR_MAX77620=m CONFIG_REGULATOR_MAX77650=m CONFIG_REGULATOR_MAX8649=m
# CONFIG_REGULATOR_MAX8660 is not set CONFIG_REGULATOR_MAX8893=m CONFIG_REGULATOR_MAX8907=m CONFIG_REGULATOR_MAX8925=m CONFIG_REGULATOR_MAX8952=y CONFIG_REGULATOR_MAX8973=m CONFIG_REGULATOR_MAX8997=m
# CONFIG_REGULATOR_MAX8998 is not set CONFIG_REGULATOR_MAX20086=m CONFIG_REGULATOR_MAX77686=m CONFIG_REGULATOR_MAX77693=m CONFIG_REGULATOR_MAX77802=m CONFIG_REGULATOR_MAX77826=m CONFIG_REGULATOR_MC13XXX_CORE=y
# CONFIG_REGULATOR_MC13783 is not set CONFIG_REGULATOR_MC13892=y CONFIG_REGULATOR_MCP16502=m CONFIG_REGULATOR_MP5416=y CONFIG_REGULATOR_MP8859=y CONFIG_REGULATOR_MP886X=m
# CONFIG_REGULATOR_MPQ7920 is not set
# CONFIG_REGULATOR_MT6311 is not set CONFIG_REGULATOR_MT6315=m
# CONFIG_REGULATOR_MT6360 is not set CONFIG_REGULATOR_MT6370=m CONFIG_REGULATOR_MT6380=m
# CONFIG_REGULATOR_PBIAS is not set CONFIG_REGULATOR_PCA9450=y CONFIG_REGULATOR_PCF50633=m
# CONFIG_REGULATOR_PF8X00 is not set CONFIG_REGULATOR_PFUZE100=m CONFIG_REGULATOR_PV88060=y CONFIG_REGULATOR_PV88080=y CONFIG_REGULATOR_PV88090=yCONFIG_REGULATOR_PWM=y CONFIG_REGULATOR_QCOM_RPMH=m
# CONFIG_REGULATOR_QCOM_SMD_RPM is not set CONFIG_REGULATOR_QCOM_SPMI=y CONFIG_REGULATOR_QCOM_USB_VBUS=y
# CONFIG_REGULATOR_RASPBERRYPI_TOUCHSCREEN_ATTINY is not set CONFIG_REGULATOR_RK808=mCONFIG_REGULATOR_ROHM=mCONFIG_REGULATOR_RT4801=m CONFIG_REGULATOR_RT5033=m
# CONFIG_REGULATOR_RT5120 is not set CONFIG_REGULATOR_RT5190A=y CONFIG_REGULATOR_RT5759=y CONFIG_REGULATOR_RT6160=m
# CONFIG_REGULATOR_RT6245 is not set
# CONFIG_REGULATOR_RTQ2134 is not set CONFIG_REGULATOR_RTMV20=y
# CONFIG_REGULATOR_RTQ6752 is not set CONFIG_REGULATOR_S2MPA01=y CONFIG_REGULATOR_S2MPS11=m CONFIG_REGULATOR_S5M8767=m CONFIG_REGULATOR_SC2731=m CONFIG_REGULATOR_SKY81452=m CONFIG_REGULATOR_SLG51000=y
# CONFIG_REGULATOR_STM32_BOOSTER is not set
# CONFIG_REGULATOR_STM32_VREFBUF is not set CONFIG_REGULATOR_STM32_PWR=y
# CONFIG_REGULATOR_STPMIC1 is not set
# CONFIG_REGULATOR_TI_ABB is not set
# CONFIG_REGULATOR_STW481X_VMMC is not set CONFIG_REGULATOR_SY7636A=m CONFIG_REGULATOR_SY8106A=m
# CONFIG_REGULATOR_SY8824X is not set CONFIG_REGULATOR_SY8827N=y CONFIG_REGULATOR_TPS51632=m
# CONFIG_REGULATOR_TPS6105X is not set
# CONFIG_REGULATOR_TPS62360 is not set CONFIG_REGULATOR_TPS6286X=y CONFIG_REGULATOR_TPS65023=m CONFIG_REGULATOR_TPS6507X=m CONFIG_REGULATOR_TPS65086=m CONFIG_REGULATOR_TPS65090=y CONFIG_REGULATOR_TPS65132=m CONFIG_REGULATOR_TPS65217=m CONFIG_REGULATOR_TPS6524X=m CONFIG_REGULATOR_TPS6586X=m CONFIG_REGULATOR_TPS65912=m
# CONFIG_REGULATOR_TPS68470 is not set
# CONFIG_REGULATOR_TWL4030 is not set CONFIG_REGULATOR_UNIPHIER=m
# CONFIG_REGULATOR_VCTRL is not set
# CONFIG_REGULATOR_VEXPRESS is not set
# CONFIG_REGULATOR_WM831X is not set CONFIG_REGULATOR_WM8994=m CONFIG_REGULATOR_QCOM_LABIBB=yCONFIG_RC_CORE=yCONFIG_LIRC=y
# CONFIG_RC_MAP is not setCONFIG_RC_DECODERS=yCONFIG_IR_IMON_DECODER=m
# CONFIG_IR_JVC_DECODER is not set CONFIG_IR_MCE_KBD_DECODER=y CONFIG_IR_NEC_DECODER=mCONFIG_IR_RC5_DECODER=mCONFIG_IR_RC6_DECODER=mCONFIG_IR_RCMM_DECODER=mCONFIG_IR_SANYO_DECODER=y CONFIG_IR_SHARP_DECODER=mCONFIG_IR_SONY_DECODER=m
# CONFIG_IR_XMP_DECODER is not set CONFIG_RC_DEVICES=y
# CONFIG_IR_ENE is not setCONFIG_IR_FINTEK=mCONFIG_IR_GPIO_CIR=yCONFIG_IR_GPIO_TX=yCONFIG_IR_HIX5HD2=m
# CONFIG_IR_ITE_CIR is not setCONFIG_IR_MESON=y
# CONFIG_IR_MESON_TX is not set
# CONFIG_IR_MTK is not setCONFIG_IR_NUVOTON=mCONFIG_IR_PWM_TX=yCONFIG_IR_RX51=mCONFIG_IR_SERIAL=yCONFIG_IR_SERIAL_TRANSMITTER=y
# CONFIG_IR_SPI is not set
# CONFIG_IR_SUNXI is not set
# CONFIG_IR_WINBOND_CIR is not set CONFIG_RC_LOOPBACK=mCONFIG_RC_ST=mCONFIG_IR_IMG=yCONFIG_IR_IMG_RAW=yCONFIG_IR_IMG_HW=y
# CONFIG_IR_IMG_NEC is not set
# CONFIG_IR_IMG_JVC is not set CONFIG_IR_IMG_SONY=yCONFIG_IR_IMG_SHARP=y
# CONFIG_IR_IMG_SANYO is not set CONFIG_IR_IMG_RC5=y
# CONFIG_IR_IMG_RC6 is not setCONFIG_CEC_CORE=yCONFIG_CEC_NOTIFIER=y
#
# CEC support
#
# CONFIG_MEDIA_CEC_RC is not setCONFIG_MEDIA_CEC_SUPPORT=y
# CONFIG_CEC_CH7322 is not setCONFIG_CEC_MESON_AO=m
# CONFIG_CEC_MESON_G12A_AO is not set
# CONFIG_CEC_GPIO is not setCONFIG_CEC_SAMSUNG_S5P=y
# CONFIG_CEC_STI is not setCONFIG_CEC_STM32=yCONFIG_CEC_TEGRA=y
# end of CEC support
CONFIG_MEDIA_SUPPORT=yCONFIG_MEDIA_SUPPORT_FILTER=yCONFIG_MEDIA_SUBDRV_AUTOSELECT=y
#
# 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=y
# CONFIG_MEDIA_PLATFORM_SUPPORT is not set
# CONFIG_MEDIA_TEST_SUPPORT is not set
# end of Media device types
CONFIG_VIDEO_DEV=yCONFIG_MEDIA_CONTROLLER=yCONFIG_DVB_CORE=y
#
# Video4Linux options
#CONFIG_VIDEO_V4L2_I2C=yCONFIG_VIDEO_V4L2_SUBDEV_API=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not setCONFIG_V4L2_FLASH_LED_CLASS=mCONFIG_V4L2_FWNODE=yCONFIG_V4L2_ASYNC=y
# 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_MAX_ADAPTERS=16
# CONFIG_DVB_DYNAMIC_MINORS is not setCONFIG_DVB_DEMUX_SECTION_LOSS_LOG=y
# CONFIG_DVB_ULE_DEBUG is not set
# end of Digital TV options
#
# Media drivers
#
#
# Drivers filtered as selected at 'Filter media drivers' #
#
# Media drivers
#
# CONFIG_RADIO_ADAPTERS is not set
#
# FireWire (IEEE 1394) Adapters
#
# CONFIG_DVB_FIREDTV is not setCONFIG_VIDEOBUF2_CORE=yCONFIG_VIDEOBUF2_V4L2=yCONFIG_VIDEOBUF2_MEMOPS=yCONFIG_VIDEOBUF2_VMALLOC=y
# end of Media drivers
#
# Media ancillary drivers
#CONFIG_MEDIA_ATTACH=y
#
# IR I2C driver auto-selected by 'Autoselect ancillary drivers' #
# CONFIG_VIDEO_IR_I2C is not set
#
# Camera sensor devices
#CONFIG_VIDEO_APTINA_PLL=mCONFIG_VIDEO_CCS_PLL=y
# CONFIG_VIDEO_AR0521 is not setCONFIG_VIDEO_HI556=m
# CONFIG_VIDEO_HI846 is not setCONFIG_VIDEO_HI847=m
# CONFIG_VIDEO_IMX208 is not set
# CONFIG_VIDEO_IMX214 is not setCONFIG_VIDEO_IMX219=yCONFIG_VIDEO_IMX258=mCONFIG_VIDEO_IMX274=yCONFIG_VIDEO_IMX290=mCONFIG_VIDEO_IMX319=mCONFIG_VIDEO_IMX334=yCONFIG_VIDEO_IMX335=m
# CONFIG_VIDEO_IMX355 is not set
# CONFIG_VIDEO_IMX412 is not setCONFIG_VIDEO_MAX9271_LIB=mCONFIG_VIDEO_MT9M001=m
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9M111 is not setCONFIG_VIDEO_MT9P031=mCONFIG_VIDEO_MT9T001=m
# CONFIG_VIDEO_MT9T112 is not setCONFIG_VIDEO_MT9V011=yCONFIG_VIDEO_MT9V032=yCONFIG_VIDEO_MT9V111=yCONFIG_VIDEO_NOON010PC30=m
# CONFIG_VIDEO_OG01A1B is not set
# CONFIG_VIDEO_OV02A10 is not setCONFIG_VIDEO_OV08D10=m
# CONFIG_VIDEO_OV13858 is not setCONFIG_VIDEO_OV13B10=y
# CONFIG_VIDEO_OV2640 is not set
# CONFIG_VIDEO_OV2659 is not setCONFIG_VIDEO_OV2680=m
# CONFIG_VIDEO_OV2685 is not setCONFIG_VIDEO_OV2740=y
# CONFIG_VIDEO_OV5640 is not setCONFIG_VIDEO_OV5645=y
# CONFIG_VIDEO_OV5647 is not setCONFIG_VIDEO_OV5648=mCONFIG_VIDEO_OV5670=y
# CONFIG_VIDEO_OV5675 is not setCONFIG_VIDEO_OV5693=yCONFIG_VIDEO_OV5695=yCONFIG_VIDEO_OV6650=yCONFIG_VIDEO_OV7251=mCONFIG_VIDEO_OV7640=y
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV772X is not setCONFIG_VIDEO_OV7740=yCONFIG_VIDEO_OV8856=m
# CONFIG_VIDEO_OV8865 is not setCONFIG_VIDEO_OV9282=y
# CONFIG_VIDEO_OV9640 is not setCONFIG_VIDEO_OV9650=mCONFIG_VIDEO_OV9734=yCONFIG_VIDEO_RDACM20=mCONFIG_VIDEO_RDACM21=mCONFIG_VIDEO_RJ54N1=m
# CONFIG_VIDEO_S5C73M3 is not set
# CONFIG_VIDEO_S5K4ECGX is not setCONFIG_VIDEO_S5K5BAF=yCONFIG_VIDEO_S5K6A3=yCONFIG_VIDEO_S5K6AA=y
# CONFIG_VIDEO_SR030PC30 is not setCONFIG_VIDEO_VS6624=mCONFIG_VIDEO_CCS=yCONFIG_VIDEO_ET8EK8=yCONFIG_VIDEO_M5MOLS=y
# end of Camera sensor devices
#
# Lens drivers
#
# CONFIG_VIDEO_AD5820 is not setCONFIG_VIDEO_AK7375=mCONFIG_VIDEO_DW9714=mCONFIG_VIDEO_DW9768=yCONFIG_VIDEO_DW9807_VCM=m
# end of Lens drivers
#
# Flash devices
#CONFIG_VIDEO_ADP1653=m
# CONFIG_VIDEO_LM3560 is not setCONFIG_VIDEO_LM3646=y
# end of Flash devices
#
# Audio decoders, processors and mixers
#CONFIG_VIDEO_CS3308=yCONFIG_VIDEO_CS5345=yCONFIG_VIDEO_CS53L32A=yCONFIG_VIDEO_MSP3400=mCONFIG_VIDEO_SONY_BTF_MPX=mCONFIG_VIDEO_TDA1997X=m
# CONFIG_VIDEO_TDA7432 is not set
# CONFIG_VIDEO_TDA9840 is not setCONFIG_VIDEO_TEA6415C=yCONFIG_VIDEO_TEA6420=mCONFIG_VIDEO_TLV320AIC23B=yCONFIG_VIDEO_TVAUDIO=m
# CONFIG_VIDEO_UDA1342 is not setCONFIG_VIDEO_VP27SMPX=yCONFIG_VIDEO_WM8739=m
# CONFIG_VIDEO_WM8775 is not set
# end of Audio decoders, processors and mixers
#
# RDS decoders
#CONFIG_VIDEO_SAA6588=y
# end of RDS decoders
#
# Video decoders
#
# CONFIG_VIDEO_ADV7180 is not setCONFIG_VIDEO_ADV7183=mCONFIG_VIDEO_ADV748X=m
# CONFIG_VIDEO_ADV7604 is not setCONFIG_VIDEO_ADV7842=m
# CONFIG_VIDEO_ADV7842_CEC is not set
# CONFIG_VIDEO_BT819 is not setCONFIG_VIDEO_BT856=y
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_ISL7998X is not setCONFIG_VIDEO_KS0127=y
# CONFIG_VIDEO_MAX9286 is not setCONFIG_VIDEO_ML86V7667=m
# CONFIG_VIDEO_SAA7110 is not setCONFIG_VIDEO_SAA711X=y
# CONFIG_VIDEO_TC358743 is not setCONFIG_VIDEO_TVP514X=m
# CONFIG_VIDEO_TVP5150 is not setCONFIG_VIDEO_TVP7002=mCONFIG_VIDEO_TW2804=yCONFIG_VIDEO_TW9903=m
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_TW9910 is not setCONFIG_VIDEO_VPX3220=y
#
# Video and audio decoders
#CONFIG_VIDEO_SAA717X=y
# CONFIG_VIDEO_CX25840 is not set
# end of Video decoders
#
# Video encoders
#
# CONFIG_VIDEO_AD9389B is not setCONFIG_VIDEO_ADV7170=m
# CONFIG_VIDEO_ADV7175 is not setCONFIG_VIDEO_ADV7343=yCONFIG_VIDEO_ADV7393=yCONFIG_VIDEO_ADV7511=yCONFIG_VIDEO_ADV7511_CEC=yCONFIG_VIDEO_AK881X=m
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_SAA7185 is not setCONFIG_VIDEO_THS8200=y
# end of Video encoders
#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not setCONFIG_VIDEO_UPD64083=y
# end of Video improvement chips
#
# Audio/Video compression chips
#CONFIG_VIDEO_SAA6752HS=m
# end of Audio/Video compression chips
#
# SDR tuner chips
#CONFIG_SDR_MAX2175=m
# end of SDR tuner chips
#
# Miscellaneous helper chips
#CONFIG_VIDEO_I2C=yCONFIG_VIDEO_M52790=mCONFIG_VIDEO_ST_MIPID02=yCONFIG_VIDEO_THS7303=y
# end of Miscellaneous helper chips
#
# Media SPI Adapters
#
# CONFIG_CXD2880_SPI_DRV is not setCONFIG_VIDEO_GS1662=m
# end of Media SPI Adapters
CONFIG_MEDIA_TUNER=y
#
# Customize TV tuners
#CONFIG_MEDIA_TUNER_E4000=m
# CONFIG_MEDIA_TUNER_FC0011 is not setCONFIG_MEDIA_TUNER_FC0012=yCONFIG_MEDIA_TUNER_FC0013=m
# CONFIG_MEDIA_TUNER_FC2580 is not setCONFIG_MEDIA_TUNER_IT913X=mCONFIG_MEDIA_TUNER_M88RS6000T=mCONFIG_MEDIA_TUNER_MAX2165=mCONFIG_MEDIA_TUNER_MC44S803=yCONFIG_MEDIA_TUNER_MSI001=mCONFIG_MEDIA_TUNER_MT2060=mCONFIG_MEDIA_TUNER_MT2063=mCONFIG_MEDIA_TUNER_MT20XX=yCONFIG_MEDIA_TUNER_MT2131=y
# CONFIG_MEDIA_TUNER_MT2266 is not setCONFIG_MEDIA_TUNER_MXL301RF=y
# CONFIG_MEDIA_TUNER_MXL5005S is not setCONFIG_MEDIA_TUNER_MXL5007T=mCONFIG_MEDIA_TUNER_QM1D1B0004=mCONFIG_MEDIA_TUNER_QM1D1C0042=mCONFIG_MEDIA_TUNER_QT1010=yCONFIG_MEDIA_TUNER_R820T=yCONFIG_MEDIA_TUNER_SI2157=yCONFIG_MEDIA_TUNER_SIMPLE=y
# CONFIG_MEDIA_TUNER_TDA18212 is not setCONFIG_MEDIA_TUNER_TDA18218=mCONFIG_MEDIA_TUNER_TDA18250=mCONFIG_MEDIA_TUNER_TDA18271=yCONFIG_MEDIA_TUNER_TDA827X=yCONFIG_MEDIA_TUNER_TDA8290=yCONFIG_MEDIA_TUNER_TDA9887=yCONFIG_MEDIA_TUNER_TEA5761=yCONFIG_MEDIA_TUNER_TEA5767=y
# CONFIG_MEDIA_TUNER_TUA9001 is not setCONFIG_MEDIA_TUNER_XC2028=yCONFIG_MEDIA_TUNER_XC4000=yCONFIG_MEDIA_TUNER_XC5000=y
# end of Customize TV tuners
#
# Customise DVB Frontends
#
#
# Multistandard (satellite) frontends
#
# CONFIG_DVB_M88DS3103 is not setCONFIG_DVB_MXL5XX=mCONFIG_DVB_STB0899=mCONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=mCONFIG_DVB_STV0910=m
CONFIG_DVB_STV6110x=yCONFIG_DVB_STV6111=m
#
# Multistandard (cable + terrestrial) frontends
#
# CONFIG_DVB_DRXK is not setCONFIG_DVB_MN88472=yCONFIG_DVB_MN88473=mCONFIG_DVB_SI2165=yCONFIG_DVB_TDA18271C2DD=y
#
# DVB-S (satellite) frontends
#
# CONFIG_DVB_CX24110 is not setCONFIG_DVB_CX24116=mCONFIG_DVB_CX24117=mCONFIG_DVB_CX24120=mCONFIG_DVB_CX24123=mCONFIG_DVB_DS3000=mCONFIG_DVB_MB86A16=m
# CONFIG_DVB_MT312 is not set
# CONFIG_DVB_S5H1420 is not setCONFIG_DVB_SI21XX=yCONFIG_DVB_STB6000=yCONFIG_DVB_STV0288=yCONFIG_DVB_STV0299=m
# CONFIG_DVB_STV0900 is not setCONFIG_DVB_STV6110=m
# CONFIG_DVB_TDA10071 is not setCONFIG_DVB_TDA10086=y
# CONFIG_DVB_TDA8083 is not setCONFIG_DVB_TDA8261=mCONFIG_DVB_TDA826X=yCONFIG_DVB_TS2020=mCONFIG_DVB_TUA6100=y
# CONFIG_DVB_TUNER_CX24113 is not set
# CONFIG_DVB_TUNER_ITD1000 is not setCONFIG_DVB_VES1X93=m
# CONFIG_DVB_ZL10036 is not setCONFIG_DVB_ZL10039=m
#
# DVB-T (terrestrial) frontends
#CONFIG_DVB_AF9013=mCONFIG_DVB_CX22700=mCONFIG_DVB_CX22702=mCONFIG_DVB_CXD2820R=mCONFIG_DVB_CXD2841ER=yCONFIG_DVB_DIB3000MB=mCONFIG_DVB_DIB3000MC=m
# CONFIG_DVB_DIB7000M is not setCONFIG_DVB_DIB7000P=yCONFIG_DVB_DIB9000=yCONFIG_DVB_DRXD=mCONFIG_DVB_EC100=yCONFIG_DVB_L64781=mCONFIG_DVB_MT352=yCONFIG_DVB_NXT6000=m
# CONFIG_DVB_RTL2830 is not setCONFIG_DVB_RTL2832=yCONFIG_DVB_S5H1432=mCONFIG_DVB_SI2168=mCONFIG_DVB_SP887X=y
# CONFIG_DVB_STV0367 is not set
# CONFIG_DVB_TDA10048 is not set
# CONFIG_DVB_TDA1004X is not setCONFIG_DVB_ZD1301_DEMOD=yCONFIG_DVB_ZL10353=y
# CONFIG_DVB_CXD2880 is not set
#
# DVB-C (cable) frontends
#CONFIG_DVB_STV0297=y
# CONFIG_DVB_TDA10021 is not setCONFIG_DVB_TDA10023=mCONFIG_DVB_VES1820=y
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #CONFIG_DVB_AU8522=yCONFIG_DVB_AU8522_DTV=y
# CONFIG_DVB_AU8522_V4L is not set CONFIG_DVB_BCM3510=yCONFIG_DVB_LG2160=m
# CONFIG_DVB_LGDT3305 is not set CONFIG_DVB_LGDT3306A=m
# CONFIG_DVB_LGDT330X is not setCONFIG_DVB_MXL692=yCONFIG_DVB_NXT200X=m
# CONFIG_DVB_OR51132 is not setCONFIG_DVB_OR51211=mCONFIG_DVB_S5H1409=y
# CONFIG_DVB_S5H1411 is not set
#
# ISDB-T (terrestrial) frontends
#CONFIG_DVB_DIB8000=mCONFIG_DVB_MB86A20S=yCONFIG_DVB_S921=m
#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends #CONFIG_DVB_MN88443X=mCONFIG_DVB_TC90522=y
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=m
# CONFIG_DVB_TUNER_DIB0070 is not setCONFIG_DVB_TUNER_DIB0090=y
#
# SEC control devices for DVB-S
#CONFIG_DVB_A8293=yCONFIG_DVB_AF9033=yCONFIG_DVB_ASCOT2E=mCONFIG_DVB_ATBM8830=m
# CONFIG_DVB_HELENE is not setCONFIG_DVB_HORUS3A=mCONFIG_DVB_ISL6405=yCONFIG_DVB_ISL6421=yCONFIG_DVB_ISL6423=mCONFIG_DVB_IX2505V=yCONFIG_DVB_LGS8GL5=mCONFIG_DVB_LGS8GXX=mCONFIG_DVB_LNBH25=y
# CONFIG_DVB_LNBH29 is not set
# CONFIG_DVB_LNBP21 is not setCONFIG_DVB_LNBP22=yCONFIG_DVB_M88RS2000=y
CONFIG_DVB_TDA665x=mCONFIG_DVB_DRX39XYJ=m
#
# Common Interface (EN50221) controller drivers
#CONFIG_DVB_CXD2099=mCONFIG_DVB_SP2=y
# end of Customise DVB Frontends # end of Media ancillary drivers
#
# Graphics support
#CONFIG_APERTURE_HELPERS=yCONFIG_IMX_IPUV3_CORE=mCONFIG_DRM=yCONFIG_DRM_MIPI_DBI=yCONFIG_DRM_MIPI_DSI=yCONFIG_DRM_DEBUG_MM=yCONFIG_DRM_KUNIT_TEST=mCONFIG_DRM_KMS_HELPER=yCONFIG_DRM_DEBUG_DP_MST_TOPOLOGY_REFS=y
# CONFIG_DRM_DEBUG_MODESET_LOCK is not set
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not setCONFIG_DRM_DP_AUX_BUS=yCONFIG_DRM_DISPLAY_HELPER=yCONFIG_DRM_DISPLAY_DP_HELPER=yCONFIG_DRM_DISPLAY_HDMI_HELPER=y
# CONFIG_DRM_DP_AUX_CHARDEV is not setCONFIG_DRM_DP_CEC=yCONFIG_DRM_BUDDY=mCONFIG_DRM_GEM_DMA_HELPER=yCONFIG_DRM_GEM_SHMEM_HELPER=yCONFIG_DRM_SCHED=y
#
# I2C encoder or helper chips
#CONFIG_DRM_I2C_CH7006=yCONFIG_DRM_I2C_SIL164=y
# 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
#
# CONFIG_DRM_HDLCD is not setCONFIG_DRM_MALI_DISPLAY=mCONFIG_DRM_KOMEDA=m
# end of ARM devices
CONFIG_DRM_KMB_DISPLAY=y
# CONFIG_DRM_VGEM is not setCONFIG_DRM_VKMS=mCONFIG_DRM_EXYNOS=m
#
# CRTCs
#CONFIG_DRM_EXYNOS_FIMD=yCONFIG_DRM_EXYNOS5433_DECON=y
# CONFIG_DRM_EXYNOS7_DECON is not setCONFIG_DRM_EXYNOS_MIXER=y
# CONFIG_DRM_EXYNOS_VIDI is not set
#
# Encoders and Bridges
#CONFIG_DRM_EXYNOS_DPI=y
# CONFIG_DRM_EXYNOS_DSI is not set
# CONFIG_DRM_EXYNOS_DP is not setCONFIG_DRM_EXYNOS_HDMI=yCONFIG_DRM_EXYNOS_MIC=y
#
# Sub-drivers
#
# CONFIG_DRM_EXYNOS_G2D is not setCONFIG_DRM_EXYNOS_IPP=yCONFIG_DRM_EXYNOS_FIMC=y
# CONFIG_DRM_EXYNOS_ROTATOR is not setCONFIG_DRM_EXYNOS_SCALER=y
# CONFIG_DRM_EXYNOS_GSC is not setCONFIG_DRM_RCAR_DU=y
# CONFIG_DRM_RCAR_USE_CMM is not set
# CONFIG_DRM_RCAR_DW_HDMI is not set
# CONFIG_DRM_RCAR_USE_LVDS is not set
# CONFIG_DRM_RCAR_MIPI_DSI is not setCONFIG_DRM_RCAR_WRITEBACK=yCONFIG_DRM_SUN4I=yCONFIG_DRM_SUN4I_HDMI=y
# CONFIG_DRM_SUN4I_HDMI_CEC is not set
# CONFIG_DRM_SUN4I_BACKEND is not set
# CONFIG_DRM_SUN6I_DSI is not setCONFIG_DRM_SUN8I_DW_HDMI=mCONFIG_DRM_SUN8I_MIXER=mCONFIG_DRM_SUN8I_TCON_TOP=y
# CONFIG_DRM_VIRTIO_GPU is not set
# CONFIG_DRM_MSM is not setCONFIG_DRM_PANEL=y
#
# Display Panels
#
# CONFIG_DRM_PANEL_ABT_Y030XX067A is not set CONFIG_DRM_PANEL_ARM_VERSATILE=m CONFIG_DRM_PANEL_ASUS_Z00T_TM5P5_NT35596=y
# CONFIG_DRM_PANEL_BOE_BF060Y8M_AJ0 is not set # CONFIG_DRM_PANEL_BOE_HIMAX8279D is not set # CONFIG_DRM_PANEL_BOE_TV101WUM_NL6 is not set # CONFIG_DRM_PANEL_DSI_CM is not set CONFIG_DRM_PANEL_LVDS=y
# CONFIG_DRM_PANEL_SIMPLE is not set CONFIG_DRM_PANEL_EDP=y CONFIG_DRM_PANEL_EBBG_FT8719=m
# CONFIG_DRM_PANEL_ELIDA_KD35T133 is not set # CONFIG_DRM_PANEL_FEIXIN_K101_IM2BA02 is not set CONFIG_DRM_PANEL_FEIYANG_FY07024DI26A30D=m CONFIG_DRM_PANEL_ILITEK_IL9322=y CONFIG_DRM_PANEL_ILITEK_ILI9341=y CONFIG_DRM_PANEL_ILITEK_ILI9881C=m CONFIG_DRM_PANEL_INNOLUX_EJ030NA=y
# CONFIG_DRM_PANEL_INNOLUX_P079ZCA is not set # CONFIG_DRM_PANEL_JDI_LT070ME05000 is not set # CONFIG_DRM_PANEL_JDI_R63452 is not set
# CONFIG_DRM_PANEL_KHADAS_TS050 is not set CONFIG_DRM_PANEL_KINGDISPLAY_KD097D04=y CONFIG_DRM_PANEL_LEADTEK_LTK050H3146W=m
# CONFIG_DRM_PANEL_LEADTEK_LTK500HD1829 is not set CONFIG_DRM_PANEL_SAMSUNG_LD9040=y
# CONFIG_DRM_PANEL_LG_LB035Q02 is not set CONFIG_DRM_PANEL_LG_LG4573=y CONFIG_DRM_PANEL_NEC_NL8048HL11=m
# CONFIG_DRM_PANEL_NEWVISION_NV3052C is not set CONFIG_DRM_PANEL_NOVATEK_NT35510=m CONFIG_DRM_PANEL_NOVATEK_NT35560=y
# CONFIG_DRM_PANEL_NOVATEK_NT35950 is not set CONFIG_DRM_PANEL_NOVATEK_NT36672A=y
# CONFIG_DRM_PANEL_NOVATEK_NT39016 is not set CONFIG_DRM_PANEL_MANTIX_MLAF057WE51=m CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO=m CONFIG_DRM_PANEL_ORISETECH_OTM8009A=y CONFIG_DRM_PANEL_OSD_OSD101T2587_53TS=m CONFIG_DRM_PANEL_PANASONIC_VVX10F034N00=y
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set CONFIG_DRM_PANEL_RAYDIUM_RM67191=y
# CONFIG_DRM_PANEL_RAYDIUM_RM68200 is not set # CONFIG_DRM_PANEL_RONBO_RB070D30 is not set # CONFIG_DRM_PANEL_SAMSUNG_ATNA33XC20 is not set CONFIG_DRM_PANEL_SAMSUNG_DB7430=m CONFIG_DRM_PANEL_SAMSUNG_S6D16D0=y
# CONFIG_DRM_PANEL_SAMSUNG_S6D27A1 is not set CONFIG_DRM_PANEL_SAMSUNG_S6E3HA2=y CONFIG_DRM_PANEL_SAMSUNG_S6E63J0X03=m CONFIG_DRM_PANEL_SAMSUNG_S6E63M0=y CONFIG_DRM_PANEL_SAMSUNG_S6E63M0_SPI=y CONFIG_DRM_PANEL_SAMSUNG_S6E63M0_DSI=m CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01=y # CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0 is not set CONFIG_DRM_PANEL_SAMSUNG_SOFEF00=y CONFIG_DRM_PANEL_SEIKO_43WVF1G=y
# CONFIG_DRM_PANEL_SHARP_LQ101R1SX01 is not set # CONFIG_DRM_PANEL_SHARP_LS037V7DW01 is not set CONFIG_DRM_PANEL_SHARP_LS043T1LE01=m CONFIG_DRM_PANEL_SHARP_LS060T1SX01=y CONFIG_DRM_PANEL_SITRONIX_ST7701=m CONFIG_DRM_PANEL_SITRONIX_ST7703=m CONFIG_DRM_PANEL_SITRONIX_ST7789V=m
# CONFIG_DRM_PANEL_SONY_ACX565AKM is not set CONFIG_DRM_PANEL_SONY_TULIP_TRULY_NT35521=m
# CONFIG_DRM_PANEL_TDO_TL070WSH30 is not set CONFIG_DRM_PANEL_TPO_TD028TTEC1=m
# CONFIG_DRM_PANEL_TPO_TD043MTEA1 is not set # CONFIG_DRM_PANEL_TPO_TPG110 is not set CONFIG_DRM_PANEL_TRULY_NT35597_WQXGA=m
# CONFIG_DRM_PANEL_VISIONOX_RM69299 is not set CONFIG_DRM_PANEL_WIDECHIPS_WS2401=y
# CONFIG_DRM_PANEL_XINPENG_XPP055C272 is not set
# end of Display Panels
CONFIG_DRM_BRIDGE=yCONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#CONFIG_DRM_CDNS_DSI=m
# CONFIG_DRM_CHIPONE_ICN6211 is not set CONFIG_DRM_CHRONTEL_CH7033=m CONFIG_DRM_CROS_EC_ANX7688=y CONFIG_DRM_DISPLAY_CONNECTOR=y CONFIG_DRM_FSL_LDB=m
# CONFIG_DRM_ITE_IT6505 is not set
# CONFIG_DRM_LONTIUM_LT8912B is not set CONFIG_DRM_LONTIUM_LT9211=m CONFIG_DRM_LONTIUM_LT9611=y
# CONFIG_DRM_LONTIUM_LT9611UXC is not set CONFIG_DRM_ITE_IT66121=m CONFIG_DRM_LVDS_CODEC=y
# CONFIG_DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW is not set CONFIG_DRM_NWL_MIPI_DSI=m CONFIG_DRM_NXP_PTN3460=y CONFIG_DRM_PARADE_PS8622=y CONFIG_DRM_PARADE_PS8640=y CONFIG_DRM_SIL_SII8620=yCONFIG_DRM_SII902X=mCONFIG_DRM_SII9234=m CONFIG_DRM_SIMPLE_BRIDGE=y CONFIG_DRM_THINE_THC63LVD1024=y CONFIG_DRM_TOSHIBA_TC358762=y
# CONFIG_DRM_TOSHIBA_TC358764 is not set
# CONFIG_DRM_TOSHIBA_TC358767 is not set
# CONFIG_DRM_TOSHIBA_TC358768 is not set
# CONFIG_DRM_TOSHIBA_TC358775 is not set CONFIG_DRM_TI_DLPC3433=y CONFIG_DRM_TI_TFP410=m CONFIG_DRM_TI_SN65DSI83=y CONFIG_DRM_TI_SN65DSI86=m CONFIG_DRM_TI_TPD12S015=m
# CONFIG_DRM_ANALOGIX_ANX6345 is not set
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
# CONFIG_DRM_ANALOGIX_ANX7625 is not set CONFIG_DRM_I2C_ADV7511=y
# CONFIG_DRM_I2C_ADV7511_AUDIO is not set CONFIG_DRM_I2C_ADV7511_CEC=y
# CONFIG_DRM_CDNS_MHDP8546 is not set CONFIG_DRM_IMX8QM_LDB=m CONFIG_DRM_IMX8QXP_LDB=m CONFIG_DRM_IMX8QXP_PIXEL_COMBINER=m CONFIG_DRM_IMX8QXP_PIXEL_LINK_TO_DPI=m CONFIG_DRM_DW_HDMI=m
# CONFIG_DRM_DW_HDMI_AHB_AUDIO is not set CONFIG_DRM_DW_HDMI_I2S_AUDIO=m CONFIG_DRM_DW_HDMI_GP_AUDIO=m CONFIG_DRM_DW_HDMI_CEC=m
# end of Display Interface Bridges
CONFIG_DRM_IMX=mCONFIG_DRM_IMX_PARALLEL_DISPLAY=mCONFIG_DRM_IMX_TVE=mCONFIG_DRM_IMX_LDB=mCONFIG_DRM_IMX_HDMI=mCONFIG_DRM_INGENIC=m
# CONFIG_DRM_INGENIC_IPU is not setCONFIG_DRM_V3D=mCONFIG_DRM_VC4=mCONFIG_DRM_VC4_HDMI_CEC=y
# CONFIG_DRM_ETNAVIV is not setCONFIG_DRM_HISI_KIRIN=mCONFIG_DRM_LOGICVC=yCONFIG_DRM_MXS=yCONFIG_DRM_MXSFB=yCONFIG_DRM_IMX_LCDIF=yCONFIG_DRM_MESON=yCONFIG_DRM_MESON_DW_HDMI=m
# CONFIG_DRM_ARCPGU is not set
# CONFIG_DRM_PANEL_MIPI_DBI is not setCONFIG_DRM_SIMPLEDRM=m
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9163 is not set
# CONFIG_TINYDRM_ILI9225 is not setCONFIG_TINYDRM_ILI9341=m
# CONFIG_TINYDRM_ILI9486 is not setCONFIG_TINYDRM_MI0283QT=m
# CONFIG_TINYDRM_REPAPER is not setCONFIG_TINYDRM_ST7586=yCONFIG_TINYDRM_ST7735R=yCONFIG_DRM_PL111=mCONFIG_DRM_TVE200=m
# CONFIG_DRM_LIMA is not setCONFIG_DRM_PANFROST=yCONFIG_DRM_ASPEED_GFX=yCONFIG_DRM_MCDE=m
# CONFIG_DRM_TIDSS is not setCONFIG_DRM_SSD130X=mCONFIG_DRM_SSD130X_I2C=m
# CONFIG_DRM_SSD130X_SPI is not setCONFIG_DRM_SPRD=m
# CONFIG_DRM_LEGACY is not setCONFIG_DRM_EXPORT_FOR_TESTS=yCONFIG_DRM_PANEL_ORIENTATION_QUIRKS=yCONFIG_DRM_NOMODESET=yCONFIG_DRM_LIB_RANDOM=y
#
# Frame buffer Devices
#CONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB=m
# CONFIG_FIRMWARE_EDID is not setCONFIG_FB_CFB_FILLRECT=mCONFIG_FB_CFB_COPYAREA=mCONFIG_FB_CFB_IMAGEBLIT=mCONFIG_FB_SYS_FILLRECT=mCONFIG_FB_SYS_COPYAREA=mCONFIG_FB_SYS_IMAGEBLIT=mCONFIG_FB_FOREIGN_ENDIAN=yCONFIG_FB_BOTH_ENDIAN=y
# CONFIG_FB_BIG_ENDIAN is not set
# CONFIG_FB_LITTLE_ENDIAN is not setCONFIG_FB_SYS_FOPS=mCONFIG_FB_DEFERRED_IO=yCONFIG_FB_BACKLIGHT=mCONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
#
# Frame buffer hardware drivers
#CONFIG_FB_ARMCLCD=m
# CONFIG_FB_CLPS711X is not set
# CONFIG_FB_IMX is not setCONFIG_FB_ARC=m
# CONFIG_FB_PVR2 is not set
# CONFIG_FB_OPENCORES is not set CONFIG_FB_S1D13XXX=m
# CONFIG_FB_ATMEL is not set
# CONFIG_FB_PXA168 is not set
# CONFIG_FB_W100 is not set CONFIG_FB_SH_MOBILE_LCDC=mCONFIG_FB_TMIO=m
# CONFIG_FB_TMIO_ACCELL is not set
# CONFIG_FB_S3C is not setCONFIG_FB_SM501=m
# CONFIG_FB_IBM_GXT4500 is not set CONFIG_FB_GOLDFISH=m
# CONFIG_FB_DA8XX is not set CONFIG_FB_VIRTUAL=mCONFIG_FB_METRONOME=mCONFIG_FB_BROADSHEET=mCONFIG_FB_SIMPLE=mCONFIG_FB_SSD1307=mCONFIG_FB_OMAP2=m
# CONFIG_FB_OMAP2_DEBUG_SUPPORT is not set CONFIG_FB_OMAP2_NUM_FBS=3 CONFIG_FB_OMAP2_DSS_INIT=y CONFIG_FB_OMAP2_DSS=m CONFIG_FB_OMAP2_DSS_DEBUG=y CONFIG_FB_OMAP2_DSS_DEBUGFS=y
# CONFIG_FB_OMAP2_DSS_COLLECT_IRQ_STATS is not set CONFIG_FB_OMAP2_DSS_DPI=y CONFIG_FB_OMAP2_DSS_VENC=y CONFIG_FB_OMAP2_DSS_HDMI_COMMON=y CONFIG_FB_OMAP4_DSS_HDMI=y CONFIG_FB_OMAP5_DSS_HDMI=y CONFIG_FB_OMAP2_DSS_SDI=y
# CONFIG_FB_OMAP2_DSS_DSI is not set CONFIG_FB_OMAP2_DSS_MIN_FCK_PER_PCK=0
# CONFIG_FB_OMAP2_DSS_SLEEP_AFTER_VENC_RESET is not set
#
# OMAPFB Panel and Encoder Drivers
#
# CONFIG_FB_OMAP2_ENCODER_OPA362 is not set # CONFIG_FB_OMAP2_ENCODER_TFP410 is not set CONFIG_FB_OMAP2_ENCODER_TPD12S015=m CONFIG_FB_OMAP2_CONNECTOR_DVI=m CONFIG_FB_OMAP2_CONNECTOR_HDMI=m CONFIG_FB_OMAP2_CONNECTOR_ANALOG_TV=m CONFIG_FB_OMAP2_PANEL_DPI=m
# CONFIG_FB_OMAP2_PANEL_DSI_CM is not set CONFIG_FB_OMAP2_PANEL_SONY_ACX565AKM=m CONFIG_FB_OMAP2_PANEL_LGPHILIPS_LB035Q02=m
# CONFIG_FB_OMAP2_PANEL_SHARP_LS037V7DW01 is not set CONFIG_FB_OMAP2_PANEL_TPO_TD043MTEA1=m
# end of OMAPFB Panel and Encoder Drivers
CONFIG_MMP_DISP=yCONFIG_MMP_DISP_CONTROLLER=yCONFIG_MMP_DISP_SPI=y
# CONFIG_MMP_PANEL_TPOHVGA is not setCONFIG_MMP_FB=m
# end of Frame buffer Devices
#
# Backlight & LCD device support
#CONFIG_LCD_CLASS_DEVICE=y
# CONFIG_LCD_L4F00242T03 is not setCONFIG_LCD_LMS283GF05=y
# CONFIG_LCD_LTV350QV is not setCONFIG_LCD_ILI922X=mCONFIG_LCD_ILI9320=y
# CONFIG_LCD_TDO24M is not setCONFIG_LCD_VGG2432A4=y
# CONFIG_LCD_PLATFORM is not setCONFIG_LCD_AMS369FG06=m
# CONFIG_LCD_LMS501KF03 is not setCONFIG_LCD_HX8357=yCONFIG_LCD_OTM3225A=yCONFIG_BACKLIGHT_CLASS_DEVICE=yCONFIG_BACKLIGHT_KTD253=mCONFIG_BACKLIGHT_OMAP1=yCONFIG_BACKLIGHT_PWM=mCONFIG_BACKLIGHT_DA9052=mCONFIG_BACKLIGHT_MAX8925=mCONFIG_BACKLIGHT_MT6370=m
# CONFIG_BACKLIGHT_QCOM_WLED is not setCONFIG_BACKLIGHT_WM831X=yCONFIG_BACKLIGHT_ADP5520=yCONFIG_BACKLIGHT_ADP8860=mCONFIG_BACKLIGHT_ADP8870=y
# CONFIG_BACKLIGHT_PCF50633 is not setCONFIG_BACKLIGHT_AAT2870=yCONFIG_BACKLIGHT_LM3630A=m
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_LP8788 is not setCONFIG_BACKLIGHT_PANDORA=m
# CONFIG_BACKLIGHT_SKY81452 is not setCONFIG_BACKLIGHT_TPS65217=mCONFIG_BACKLIGHT_AS3711=yCONFIG_BACKLIGHT_GPIO=yCONFIG_BACKLIGHT_LV5207LP=mCONFIG_BACKLIGHT_BD6107=mCONFIG_BACKLIGHT_ARCXCNN=mCONFIG_BACKLIGHT_RAVE_SP=mCONFIG_BACKLIGHT_LED=m
# end of Backlight & LCD device support
CONFIG_VIDEOMODE_HELPERS=yCONFIG_HDMI=y
#
# Console display driver support
#CONFIG_DUMMY_CONSOLE=yCONFIG_DUMMY_CONSOLE_COLUMNS=80CONFIG_DUMMY_CONSOLE_ROWS=25CONFIG_FRAMEBUFFER_CONSOLE=yCONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION=yCONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=yCONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# end of Console display driver support
# CONFIG_LOGO is not set
# end of Graphics support
CONFIG_SOUND=yCONFIG_SND=mCONFIG_SND_TIMER=mCONFIG_SND_PCM=mCONFIG_SND_PCM_ELD=yCONFIG_SND_PCM_IEC958=yCONFIG_SND_DMAENGINE_PCM=mCONFIG_SND_HWDEP=mCONFIG_SND_SEQ_DEVICE=mCONFIG_SND_RAWMIDI=mCONFIG_SND_COMPRESS_OFFLOAD=mCONFIG_SND_JACK=yCONFIG_SND_JACK_INPUT_DEV=y
# CONFIG_SND_OSSEMUL is not setCONFIG_SND_PCM_TIMER=yCONFIG_SND_DYNAMIC_MINORS=yCONFIG_SND_MAX_CARDS=32
# CONFIG_SND_SUPPORT_OLD_API is not set
# CONFIG_SND_PROC_FS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_CTL_FAST_LOOKUP is not setCONFIG_SND_DEBUG=yCONFIG_SND_DEBUG_VERBOSE=y
# CONFIG_SND_CTL_INPUT_VALIDATION is not set
# CONFIG_SND_CTL_DEBUG is not setCONFIG_SND_JACK_INJECTION_DEBUG=yCONFIG_SND_VMASTER=yCONFIG_SND_CTL_LED=mCONFIG_SND_SEQUENCER=mCONFIG_SND_SEQ_DUMMY=mCONFIG_SND_SEQ_MIDI_EVENT=mCONFIG_SND_SEQ_MIDI=mCONFIG_SND_AC97_CODEC=m
# CONFIG_SND_DRIVERS is not set
#
# HD-Audio
#CONFIG_SND_HDA=mCONFIG_SND_HDA_GENERIC_LEDS=y
# CONFIG_SND_HDA_HWDEP is not set
# CONFIG_SND_HDA_RECONFIG is not set
# CONFIG_SND_HDA_INPUT_BEEP is not set
# CONFIG_SND_HDA_PATCH_LOADER is not setCONFIG_SND_HDA_CODEC_REALTEK=m
# CONFIG_SND_HDA_CODEC_ANALOG is not setCONFIG_SND_HDA_CODEC_SIGMATEL=m
# CONFIG_SND_HDA_CODEC_VIA is not setCONFIG_SND_HDA_CODEC_HDMI=mCONFIG_SND_HDA_CODEC_CIRRUS=m
# CONFIG_SND_HDA_CODEC_CS8409 is not setCONFIG_SND_HDA_CODEC_CONEXANT=mCONFIG_SND_HDA_CODEC_CA0110=mCONFIG_SND_HDA_CODEC_CA0132=mCONFIG_SND_HDA_CODEC_CA0132_DSP=yCONFIG_SND_HDA_CODEC_CMEDIA=m
# CONFIG_SND_HDA_CODEC_SI3054 is not setCONFIG_SND_HDA_GENERIC=mCONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
# end of HD-Audio
CONFIG_SND_HDA_CORE=mCONFIG_SND_HDA_DSP_LOADER=yCONFIG_SND_HDA_EXT_CORE=mCONFIG_SND_HDA_PREALLOC_SIZE=64CONFIG_SND_PXA2XX_LIB=mCONFIG_SND_SPI=y
# CONFIG_SND_AT73C213 is not setCONFIG_SND_FIREWIRE=yCONFIG_SND_FIREWIRE_LIB=mCONFIG_SND_DICE=mCONFIG_SND_OXFW=m
# CONFIG_SND_ISIGHT is not setCONFIG_SND_FIREWORKS=mCONFIG_SND_BEBOB=mCONFIG_SND_FIREWIRE_DIGI00X=mCONFIG_SND_FIREWIRE_TASCAM=m
# CONFIG_SND_FIREWIRE_MOTU is not set
# CONFIG_SND_FIREFACE is not setCONFIG_SND_SOC=mCONFIG_SND_SOC_AC97_BUS=yCONFIG_SND_SOC_GENERIC_DMAENGINE_PCM=yCONFIG_SND_SOC_COMPRESS=yCONFIG_SND_SOC_UTILS_KUNIT_TEST=mCONFIG_SND_SOC_ADI=mCONFIG_SND_SOC_ADI_AXI_I2S=mCONFIG_SND_SOC_ADI_AXI_SPDIF=mCONFIG_SND_SOC_AMD_ACP=mCONFIG_SND_SOC_AMD_CZ_RT5645_MACH=mCONFIG_SND_AMD_ACP_CONFIG=mCONFIG_SND_SOC_APPLE_MCA=mCONFIG_SND_ATMEL_SOC=mCONFIG_SND_ATMEL_SOC_PDC=yCONFIG_SND_ATMEL_SOC_DMA=yCONFIG_SND_ATMEL_SOC_SSC=mCONFIG_SND_ATMEL_SOC_SSC_PDC=mCONFIG_SND_ATMEL_SOC_SSC_DMA=m
# CONFIG_SND_AT91_SOC_SAM9G20_WM8731 is not setCONFIG_SND_ATMEL_SOC_WM8904=m
# CONFIG_SND_AT91_SOC_SAM9X5_WM8731 is not set
# CONFIG_SND_ATMEL_SOC_CLASSD is not setCONFIG_SND_ATMEL_SOC_PDMIC=m
# CONFIG_SND_ATMEL_SOC_I2S is not set
# CONFIG_SND_SOC_MIKROE_PROTO is not setCONFIG_SND_MCHP_SOC_I2S_MCC=m
# CONFIG_SND_MCHP_SOC_SPDIFTX is not setCONFIG_SND_MCHP_SOC_SPDIFRX=mCONFIG_SND_MCHP_SOC_PDMC=m
# CONFIG_SND_BCM2835_SOC_I2S is not setCONFIG_SND_SOC_CYGNUS=mCONFIG_SND_BCM63XX_I2S_WHISTLER=m
# CONFIG_SND_EP93XX_SOC is not set
# CONFIG_SND_DESIGNWARE_I2S is not set
#
# SoC Audio for Freescale CPUs
#
#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not setCONFIG_SND_SOC_FSL_SAI=mCONFIG_SND_SOC_FSL_MQS=mCONFIG_SND_SOC_FSL_AUDMIX=mCONFIG_SND_SOC_FSL_SSI=m
# CONFIG_SND_SOC_FSL_SPDIF is not setCONFIG_SND_SOC_FSL_ESAI=mCONFIG_SND_SOC_FSL_MICFIL=mCONFIG_SND_SOC_FSL_XCVR=mCONFIG_SND_SOC_FSL_AUD2HTX=mCONFIG_SND_SOC_FSL_UTILS=mCONFIG_SND_SOC_FSL_RPMSG=mCONFIG_SND_SOC_IMX_PCM_DMA=mCONFIG_SND_SOC_IMX_AUDIO_RPMSG=mCONFIG_SND_SOC_IMX_PCM_RPMSG=mCONFIG_SND_SOC_IMX_AUDMUX=mCONFIG_SND_IMX_SOC=m
#
# SoC Audio support for Freescale i.MX boards:
#
# CONFIG_SND_SOC_IMX_ES8328 is not setCONFIG_SND_SOC_IMX_SGTL5000=m
# CONFIG_SND_SOC_IMX_SPDIF is not set
# CONFIG_SND_SOC_FSL_ASOC_CARD is not setCONFIG_SND_SOC_IMX_AUDMIX=mCONFIG_SND_SOC_IMX_HDMI=mCONFIG_SND_SOC_IMX_RPMSG=mCONFIG_SND_SOC_IMX_CARD=m
# end of SoC Audio for Freescale CPUs
CONFIG_SND_I2S_HI6210_I2S=m CONFIG_SND_JZ4740_SOC_I2S=m CONFIG_SND_KIRKWOOD_SOC=m CONFIG_SND_KIRKWOOD_SOC_ARMADA370_DB=m CONFIG_SND_SOC_IMG=y
# CONFIG_SND_SOC_IMG_I2S_IN is not set
# CONFIG_SND_SOC_IMG_I2S_OUT is not set CONFIG_SND_SOC_IMG_PARALLEL_OUT=m CONFIG_SND_SOC_IMG_SPDIF_IN=m CONFIG_SND_SOC_IMG_SPDIF_OUT=m CONFIG_SND_SOC_IMG_PISTACHIO_INTERNAL_DAC=m CONFIG_SND_SOC_INTEL_SST_TOPLEVEL=y CONFIG_SND_SOC_INTEL_KEEMBAY=m CONFIG_SND_SOC_INTEL_MACH=y CONFIG_SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES=y CONFIG_SND_SOC_MEDIATEK=m CONFIG_SND_SOC_MT8186=m
# CONFIG_SND_SOC_MT8186_MT6366_DA7219_MAX98357 is not set # CONFIG_SND_SOC_MT8186_MT6366_RT1019_RT5682S is not set # CONFIG_SND_SOC_MTK_BTCVSD is not set
# CONFIG_SND_SOC_MT8195 is not set
#
# ASoC support for Amlogic platforms
#CONFIG_SND_MESON_AIU=mCONFIG_SND_MESON_AXG_FIFO=mCONFIG_SND_MESON_AXG_FRDDR=mCONFIG_SND_MESON_AXG_TODDR=m
# CONFIG_SND_MESON_AXG_TDMIN is not set
# CONFIG_SND_MESON_AXG_TDMOUT is not set
# CONFIG_SND_MESON_AXG_SOUND_CARD is not setCONFIG_SND_MESON_AXG_SPDIFOUT=mCONFIG_SND_MESON_AXG_SPDIFIN=mCONFIG_SND_MESON_AXG_PDM=mCONFIG_SND_MESON_CODEC_GLUE=m
# CONFIG_SND_MESON_GX_SOUND_CARD is not set
# CONFIG_SND_MESON_G12A_TOACODEC is not set
# CONFIG_SND_MESON_G12A_TOHDMITX is not set
# CONFIG_SND_SOC_MESON_T9015 is not set
# end of ASoC support for Amlogic platforms
CONFIG_SND_MXS_SOC=m CONFIG_SND_SOC_MXS_SGTL5000=m CONFIG_SND_PXA2XX_SOC=m CONFIG_SND_SOC_QCOM=m CONFIG_SND_SOC_LPASS_CPU=m CONFIG_SND_SOC_LPASS_PLATFORM=m CONFIG_SND_SOC_LPASS_IPQ806X=m CONFIG_SND_SOC_STORM=m
# CONFIG_SND_SOC_APQ8016_SBC is not set
# CONFIG_SND_SOC_SC7180 is not set CONFIG_SND_SOC_ROCKCHIP=m CONFIG_SND_SOC_ROCKCHIP_I2S=m CONFIG_SND_SOC_ROCKCHIP_I2S_TDM=m CONFIG_SND_SOC_ROCKCHIP_PDM=m
# CONFIG_SND_SOC_ROCKCHIP_SPDIF is not set # CONFIG_SND_SOC_ROCKCHIP_MAX98090 is not set CONFIG_SND_SOC_ROCKCHIP_RT5645=m CONFIG_SND_SOC_RK3288_HDMI_ANALOG=m CONFIG_SND_SOC_RK3399_GRU_SOUND=m CONFIG_SND_SOC_SAMSUNG=m CONFIG_SND_S3C24XX_I2S=m CONFIG_SND_SAMSUNG_PCM=m CONFIG_SND_SAMSUNG_SPDIF=m CONFIG_SND_SAMSUNG_I2S=m CONFIG_SND_SOC_SAMSUNG_NEO1973_WM8753=m CONFIG_SND_SOC_SAMSUNG_SMDK_WM8580=m CONFIG_SND_SOC_SAMSUNG_SMDK_WM8994=m CONFIG_SND_SOC_SAMSUNG_S3C24XX_UDA134X=m CONFIG_SND_SOC_SAMSUNG_SIMTEC=m CONFIG_SND_SOC_SAMSUNG_SIMTEC_TLV320AIC23=m CONFIG_SND_SOC_SAMSUNG_SIMTEC_HERMES=m CONFIG_SND_SOC_SAMSUNG_H1940_UDA1380=m
# CONFIG_SND_SOC_SAMSUNG_RX1950_UDA1380 is not set CONFIG_SND_SOC_SMARTQ=m
# CONFIG_SND_SOC_SAMSUNG_SMDK_SPDIF is not set CONFIG_SND_SOC_SMDK_WM8994_PCM=m CONFIG_SND_SOC_SPEYSIDE=m CONFIG_SND_SOC_TOBERMORY=m CONFIG_SND_SOC_LOWLAND=m CONFIG_SND_SOC_LITTLEMILL=m
# CONFIG_SND_SOC_SNOW is not set CONFIG_SND_SOC_ODROID=m
# CONFIG_SND_SOC_ARNDALE is not set
# CONFIG_SND_SOC_SAMSUNG_ARIES_WM8994 is not set # CONFIG_SND_SOC_SAMSUNG_MIDAS_WM1811 is not set
#
# SoC Audio support for Renesas SoCs
#
# CONFIG_SND_SOC_SH4_FSI is not setCONFIG_SND_SOC_RCAR=m
# CONFIG_SND_SOC_RZ is not set
# end of SoC Audio support for Renesas SoCs
CONFIG_SND_SOC_SOF_TOPLEVEL=y
# CONFIG_SND_SOC_SOF_ACPI is not setCONFIG_SND_SOC_SOF_OF=m
# CONFIG_SND_SOC_SOF_AMD_TOPLEVEL is not set
# CONFIG_SND_SOC_SOF_IMX_TOPLEVEL is not setCONFIG_SND_SOC_SOF_INTEL_TOPLEVEL=yCONFIG_SND_SOC_SOF_MTK_TOPLEVEL=yCONFIG_SND_SOC_SPRD=m
# CONFIG_SND_SOC_SPRD_MCDT is not setCONFIG_SND_SOC_STI=m
#
# STMicroelectronics STM32 SOC audio support
#CONFIG_SND_SOC_STM32_SAI=mCONFIG_SND_SOC_STM32_I2S=m
# CONFIG_SND_SOC_STM32_SPDIFRX is not set
# end of STMicroelectronics STM32 SOC audio support
#
# Allwinner SoC Audio support
#CONFIG_SND_SUN4I_CODEC=mCONFIG_SND_SUN8I_CODEC=mCONFIG_SND_SUN8I_CODEC_ANALOG=mCONFIG_SND_SUN50I_CODEC_ANALOG=mCONFIG_SND_SUN4I_I2S=m
# CONFIG_SND_SUN4I_SPDIF is not setCONFIG_SND_SUN50I_DMIC=mCONFIG_SND_SUN8I_ADDA_PR_REGMAP=m
# end of Allwinner SoC Audio support
CONFIG_SND_SOC_TEGRA=mCONFIG_SND_SOC_TEGRA20_AC97=mCONFIG_SND_SOC_TEGRA20_DAS=mCONFIG_SND_SOC_TEGRA20_I2S=mCONFIG_SND_SOC_TEGRA20_SPDIF=mCONFIG_SND_SOC_TEGRA30_AHUB=mCONFIG_SND_SOC_TEGRA30_I2S=m
# CONFIG_SND_SOC_TEGRA210_AHUB is not setCONFIG_SND_SOC_TEGRA210_DMIC=mCONFIG_SND_SOC_TEGRA210_I2S=m
# CONFIG_SND_SOC_TEGRA210_OPE is not setCONFIG_SND_SOC_TEGRA186_ASRC=mCONFIG_SND_SOC_TEGRA186_DSPK=mCONFIG_SND_SOC_TEGRA210_ADMAIF=m
# CONFIG_SND_SOC_TEGRA210_MVC is not setCONFIG_SND_SOC_TEGRA210_SFC=mCONFIG_SND_SOC_TEGRA210_AMX=mCONFIG_SND_SOC_TEGRA210_ADX=m
# CONFIG_SND_SOC_TEGRA210_MIXER is not setCONFIG_SND_SOC_TEGRA_MACHINE_DRV=m
# CONFIG_SND_SOC_TEGRA_RT5640 is not set
# CONFIG_SND_SOC_TEGRA_WM8753 is not setCONFIG_SND_SOC_TEGRA_WM8903=mCONFIG_SND_SOC_TEGRA_WM9712=mCONFIG_SND_SOC_TEGRA_TRIMSLICE=m
# CONFIG_SND_SOC_TEGRA_ALC5632 is not set
# CONFIG_SND_SOC_TEGRA_MAX98090 is not setCONFIG_SND_SOC_TEGRA_RT5677=mCONFIG_SND_SOC_TEGRA_SGTL5000=m
#
# Audio support for Texas Instruments SoCs
#CONFIG_SND_SOC_TI_EDMA_PCM=mCONFIG_SND_SOC_TI_SDMA_PCM=m
#
# Texas Instruments DAI support for:
#CONFIG_SND_SOC_DAVINCI_ASP=m
# CONFIG_SND_SOC_DAVINCI_MCASP is not set
# CONFIG_SND_SOC_DAVINCI_VCIF is not set
# CONFIG_SND_SOC_OMAP_DMIC is not setCONFIG_SND_SOC_OMAP_MCBSP=m
# CONFIG_SND_SOC_OMAP_MCPDM is not set
#
# Audio support for boards with Texas Instruments SoCs #CONFIG_SND_SOC_OMAP3_TWL4030=m CONFIG_SND_SOC_OMAP_HDMI=m
# CONFIG_SND_SOC_J721E_EVM is not set
# end of Audio support for Texas Instruments SoCs
# CONFIG_SND_SOC_UNIPHIER is not set CONFIG_SND_SOC_XILINX_I2S=m
# CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set CONFIG_SND_SOC_XILINX_SPDIF=m CONFIG_SND_SOC_XTFPGA_I2S=m CONFIG_SND_SOC_I2C_AND_SPI=m
#
# CODEC drivers
#CONFIG_SND_SOC_ALL_CODECS=m
# CONFIG_SND_SOC_88PM860X is not setCONFIG_SND_SOC_WM_HUBS=mCONFIG_SND_SOC_WM_ADSP=mCONFIG_SND_SOC_AB8500_CODEC=mCONFIG_SND_SOC_AC97_CODEC=mCONFIG_SND_SOC_AD1836=mCONFIG_SND_SOC_AD193X=mCONFIG_SND_SOC_AD193X_SPI=mCONFIG_SND_SOC_AD193X_I2C=mCONFIG_SND_SOC_AD1980=mCONFIG_SND_SOC_AD73311=mCONFIG_SND_SOC_ADAU_UTILS=mCONFIG_SND_SOC_ADAU1372=mCONFIG_SND_SOC_ADAU1372_I2C=mCONFIG_SND_SOC_ADAU1372_SPI=mCONFIG_SND_SOC_ADAU1373=mCONFIG_SND_SOC_ADAU1701=mCONFIG_SND_SOC_ADAU17X1=mCONFIG_SND_SOC_ADAU1761=mCONFIG_SND_SOC_ADAU1761_I2C=mCONFIG_SND_SOC_ADAU1761_SPI=mCONFIG_SND_SOC_ADAU1781=mCONFIG_SND_SOC_ADAU1781_I2C=mCONFIG_SND_SOC_ADAU1781_SPI=mCONFIG_SND_SOC_ADAU1977=mCONFIG_SND_SOC_ADAU1977_SPI=mCONFIG_SND_SOC_ADAU1977_I2C=mCONFIG_SND_SOC_ADAU7002=mCONFIG_SND_SOC_ADAU7118=mCONFIG_SND_SOC_ADAU7118_HW=mCONFIG_SND_SOC_ADAU7118_I2C=mCONFIG_SND_SOC_ADAV80X=mCONFIG_SND_SOC_ADAV801=mCONFIG_SND_SOC_ADAV803=mCONFIG_SND_SOC_ADS117X=mCONFIG_SND_SOC_AK4104=m
# CONFIG_SND_SOC_AK4118 is not setCONFIG_SND_SOC_AK4375=mCONFIG_SND_SOC_AK4458=mCONFIG_SND_SOC_AK4535=mCONFIG_SND_SOC_AK4554=mCONFIG_SND_SOC_AK4613=mCONFIG_SND_SOC_AK4641=mCONFIG_SND_SOC_AK4642=mCONFIG_SND_SOC_AK4671=mCONFIG_SND_SOC_AK5386=mCONFIG_SND_SOC_AK5558=m
# CONFIG_SND_SOC_ALC5623 is not setCONFIG_SND_SOC_ALC5632=mCONFIG_SND_SOC_AW8738=mCONFIG_SND_SOC_BD28623=mCONFIG_SND_SOC_BT_SCO=mCONFIG_SND_SOC_CPCAP=mCONFIG_SND_SOC_CQ0093VC=m
# CONFIG_SND_SOC_CROS_EC_CODEC is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS35L33 is not setCONFIG_SND_SOC_CS35L34=mCONFIG_SND_SOC_CS35L35=mCONFIG_SND_SOC_CS35L36=m
# CONFIG_SND_SOC_CS35L41_SPI is not set
# CONFIG_SND_SOC_CS35L41_I2C is not setCONFIG_SND_SOC_CS35L45_TABLES=mCONFIG_SND_SOC_CS35L45=mCONFIG_SND_SOC_CS35L45_SPI=mCONFIG_SND_SOC_CS35L45_I2C=mCONFIG_SND_SOC_CS42L42_CORE=mCONFIG_SND_SOC_CS42L42=mCONFIG_SND_SOC_CS42L51=mCONFIG_SND_SOC_CS42L51_I2C=mCONFIG_SND_SOC_CS42L52=mCONFIG_SND_SOC_CS42L56=mCONFIG_SND_SOC_CS42L73=m
# CONFIG_SND_SOC_CS42L83 is not set
# CONFIG_SND_SOC_CS4234 is not setCONFIG_SND_SOC_CS4265=mCONFIG_SND_SOC_CS4270=mCONFIG_SND_SOC_CS4271=mCONFIG_SND_SOC_CS4271_I2C=m
# CONFIG_SND_SOC_CS4271_SPI is not setCONFIG_SND_SOC_CS42XX8=mCONFIG_SND_SOC_CS42XX8_I2C=mCONFIG_SND_SOC_CS43130=m
# CONFIG_SND_SOC_CS4341 is not setCONFIG_SND_SOC_CS4349=m
# CONFIG_SND_SOC_CS47L15 is not set
# CONFIG_SND_SOC_CS47L24 is not set
# CONFIG_SND_SOC_CS47L35 is not set
# CONFIG_SND_SOC_CS47L85 is not setCONFIG_SND_SOC_CS47L90=mCONFIG_SND_SOC_CS47L92=mCONFIG_SND_SOC_CS53L30=mCONFIG_SND_SOC_CX20442=mCONFIG_SND_SOC_CX2072X=m
# CONFIG_SND_SOC_JZ4740_CODEC is not setCONFIG_SND_SOC_JZ4725B_CODEC=mCONFIG_SND_SOC_JZ4760_CODEC=mCONFIG_SND_SOC_JZ4770_CODEC=mCONFIG_SND_SOC_L3=mCONFIG_SND_SOC_DA7210=mCONFIG_SND_SOC_DA7213=mCONFIG_SND_SOC_DA7218=mCONFIG_SND_SOC_DA7219=mCONFIG_SND_SOC_DA732X=mCONFIG_SND_SOC_DA9055=mCONFIG_SND_SOC_DMIC=mCONFIG_SND_SOC_HDMI_CODEC=m
# CONFIG_SND_SOC_ES7134 is not setCONFIG_SND_SOC_ES7241=mCONFIG_SND_SOC_ES8316=mCONFIG_SND_SOC_ES8326=mCONFIG_SND_SOC_ES8328=mCONFIG_SND_SOC_ES8328_I2C=mCONFIG_SND_SOC_ES8328_SPI=mCONFIG_SND_SOC_GTM601=mCONFIG_SND_SOC_HDAC_HDMI=mCONFIG_SND_SOC_HDAC_HDA=mCONFIG_SND_SOC_HDA=mCONFIG_SND_SOC_ICS43432=m
# CONFIG_SND_SOC_INNO_RK3036 is not setCONFIG_SND_SOC_ISABELLE=mCONFIG_SND_SOC_LM49453=m
# CONFIG_SND_SOC_LOCHNAGAR_SC is not setCONFIG_SND_SOC_MADERA=mCONFIG_SND_SOC_MAX98088=mCONFIG_SND_SOC_MAX98090=mCONFIG_SND_SOC_MAX98095=mCONFIG_SND_SOC_MAX98357A=mCONFIG_SND_SOC_MAX98371=m
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9867 is not setCONFIG_SND_SOC_MAX98925=mCONFIG_SND_SOC_MAX98926=m
# CONFIG_SND_SOC_MAX98927 is not setCONFIG_SND_SOC_MAX98520=mCONFIG_SND_SOC_MAX98373=mCONFIG_SND_SOC_MAX98373_I2C=m
# CONFIG_SND_SOC_MAX98373_SDW is not set
# CONFIG_SND_SOC_MAX98390 is not setCONFIG_SND_SOC_MAX98396=mCONFIG_SND_SOC_MAX9850=mCONFIG_SND_SOC_MAX9860=m
# CONFIG_SND_SOC_MSM8916_WCD_ANALOG is not setCONFIG_SND_SOC_MSM8916_WCD_DIGITAL=mCONFIG_SND_SOC_PCM1681=mCONFIG_SND_SOC_PCM1789=mCONFIG_SND_SOC_PCM1789_I2C=m
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not setCONFIG_SND_SOC_PCM186X=m
# CONFIG_SND_SOC_PCM186X_I2C is not setCONFIG_SND_SOC_PCM186X_SPI=mCONFIG_SND_SOC_PCM3008=mCONFIG_SND_SOC_PCM3060=mCONFIG_SND_SOC_PCM3060_I2C=m
# CONFIG_SND_SOC_PCM3060_SPI is not setCONFIG_SND_SOC_PCM3168A=mCONFIG_SND_SOC_PCM3168A_I2C=mCONFIG_SND_SOC_PCM3168A_SPI=mCONFIG_SND_SOC_PCM5102A=m
CONFIG_SND_SOC_PCM512x=m
# CONFIG_SND_SOC_PCM512x_I2C is not set
CONFIG_SND_SOC_PCM512x_SPI=mCONFIG_SND_SOC_RK3328=mCONFIG_SND_SOC_RK817=mCONFIG_SND_SOC_RL6231=mCONFIG_SND_SOC_RL6347A=mCONFIG_SND_SOC_RT274=mCONFIG_SND_SOC_RT286=mCONFIG_SND_SOC_RT298=mCONFIG_SND_SOC_RT1011=mCONFIG_SND_SOC_RT1015=mCONFIG_SND_SOC_RT1015P=mCONFIG_SND_SOC_RT1016=mCONFIG_SND_SOC_RT1019=mCONFIG_SND_SOC_RT1305=mCONFIG_SND_SOC_RT1308=m
# CONFIG_SND_SOC_RT1308_SDW is not set
# CONFIG_SND_SOC_RT1316_SDW is not setCONFIG_SND_SOC_RT5514=mCONFIG_SND_SOC_RT5514_SPI=m
# CONFIG_SND_SOC_RT5616 is not setCONFIG_SND_SOC_RT5631=mCONFIG_SND_SOC_RT5640=mCONFIG_SND_SOC_RT5645=mCONFIG_SND_SOC_RT5651=mCONFIG_SND_SOC_RT5659=mCONFIG_SND_SOC_RT5660=mCONFIG_SND_SOC_RT5663=mCONFIG_SND_SOC_RT5665=mCONFIG_SND_SOC_RT5668=mCONFIG_SND_SOC_RT5670=mCONFIG_SND_SOC_RT5677=mCONFIG_SND_SOC_RT5677_SPI=mCONFIG_SND_SOC_RT5682=mCONFIG_SND_SOC_RT5682_I2C=m
# CONFIG_SND_SOC_RT5682_SDW is not setCONFIG_SND_SOC_RT5682S=m
# CONFIG_SND_SOC_RT700_SDW is not set
# CONFIG_SND_SOC_RT711_SDW is not set
# CONFIG_SND_SOC_RT711_SDCA_SDW is not set
# CONFIG_SND_SOC_RT715_SDW is not set
# CONFIG_SND_SOC_RT715_SDCA_SDW is not setCONFIG_SND_SOC_RT9120=m
# CONFIG_SND_SOC_SDW_MOCKUP is not setCONFIG_SND_SOC_SGTL5000=mCONFIG_SND_SOC_SI476X=mCONFIG_SND_SOC_SIGMADSP=mCONFIG_SND_SOC_SIGMADSP_I2C=mCONFIG_SND_SOC_SIGMADSP_REGMAP=m
# CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not setCONFIG_SND_SOC_SIMPLE_MUX=mCONFIG_SND_SOC_SPDIF=m
# CONFIG_SND_SOC_SRC4XXX_I2C is not set
# CONFIG_SND_SOC_SSM2305 is not setCONFIG_SND_SOC_SSM2518=mCONFIG_SND_SOC_SSM2602=m
# CONFIG_SND_SOC_SSM2602_SPI is not setCONFIG_SND_SOC_SSM2602_I2C=m
# CONFIG_SND_SOC_SSM4567 is not set
# CONFIG_SND_SOC_STA32X is not setCONFIG_SND_SOC_STA350=mCONFIG_SND_SOC_STA529=mCONFIG_SND_SOC_STAC9766=mCONFIG_SND_SOC_STI_SAS=m
# CONFIG_SND_SOC_TAS2552 is not setCONFIG_SND_SOC_TAS2562=mCONFIG_SND_SOC_TAS2764=mCONFIG_SND_SOC_TAS2770=mCONFIG_SND_SOC_TAS2780=mCONFIG_SND_SOC_TAS5086=mCONFIG_SND_SOC_TAS571X=mCONFIG_SND_SOC_TAS5720=mCONFIG_SND_SOC_TAS5805M=mCONFIG_SND_SOC_TAS6424=mCONFIG_SND_SOC_TDA7419=m
# CONFIG_SND_SOC_TFA9879 is not set
# CONFIG_SND_SOC_TFA989X is not setCONFIG_SND_SOC_TLV320ADC3XXX=mCONFIG_SND_SOC_TLV320AIC23=mCONFIG_SND_SOC_TLV320AIC23_I2C=m
# CONFIG_SND_SOC_TLV320AIC23_SPI is not setCONFIG_SND_SOC_TLV320AIC26=mCONFIG_SND_SOC_TLV320AIC31XX=mCONFIG_SND_SOC_TLV320AIC32X4=mCONFIG_SND_SOC_TLV320AIC32X4_I2C=mCONFIG_SND_SOC_TLV320AIC32X4_SPI=mCONFIG_SND_SOC_TLV320AIC3X=mCONFIG_SND_SOC_TLV320AIC3X_I2C=m
# CONFIG_SND_SOC_TLV320AIC3X_SPI is not setCONFIG_SND_SOC_TLV320DAC33=mCONFIG_SND_SOC_TLV320ADCX140=mCONFIG_SND_SOC_TS3A227E=m
# CONFIG_SND_SOC_TSCS42XX is not set
# CONFIG_SND_SOC_TSCS454 is not setCONFIG_SND_SOC_TWL4030=m
# CONFIG_SND_SOC_TWL6040 is not setCONFIG_SND_SOC_UDA1334=mCONFIG_SND_SOC_UDA134X=mCONFIG_SND_SOC_UDA1380=m
# CONFIG_SND_SOC_WCD9335 is not set
# CONFIG_SND_SOC_WCD934X is not set
# CONFIG_SND_SOC_WCD938X_SDW is not setCONFIG_SND_SOC_WL1273=mCONFIG_SND_SOC_WM0010=mCONFIG_SND_SOC_WM1250_EV1=mCONFIG_SND_SOC_WM2000=mCONFIG_SND_SOC_WM2200=mCONFIG_SND_SOC_WM5100=m
# CONFIG_SND_SOC_WM5102 is not set
# CONFIG_SND_SOC_WM5110 is not set
# CONFIG_SND_SOC_WM8350 is not set
# CONFIG_SND_SOC_WM8400 is not setCONFIG_SND_SOC_WM8510=m
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8524 is not setCONFIG_SND_SOC_WM8580=mCONFIG_SND_SOC_WM8711=mCONFIG_SND_SOC_WM8727=m
# CONFIG_SND_SOC_WM8728 is not setCONFIG_SND_SOC_WM8731=m
# CONFIG_SND_SOC_WM8731_I2C is not setCONFIG_SND_SOC_WM8731_SPI=m
# CONFIG_SND_SOC_WM8737 is not setCONFIG_SND_SOC_WM8741=mCONFIG_SND_SOC_WM8750=mCONFIG_SND_SOC_WM8753=mCONFIG_SND_SOC_WM8770=mCONFIG_SND_SOC_WM8776=mCONFIG_SND_SOC_WM8782=mCONFIG_SND_SOC_WM8804=m
# CONFIG_SND_SOC_WM8804_I2C is not setCONFIG_SND_SOC_WM8804_SPI=mCONFIG_SND_SOC_WM8900=mCONFIG_SND_SOC_WM8903=mCONFIG_SND_SOC_WM8904=m
# CONFIG_SND_SOC_WM8940 is not setCONFIG_SND_SOC_WM8955=mCONFIG_SND_SOC_WM8960=mCONFIG_SND_SOC_WM8961=mCONFIG_SND_SOC_WM8962=mCONFIG_SND_SOC_WM8971=m
# CONFIG_SND_SOC_WM8974 is not setCONFIG_SND_SOC_WM8978=mCONFIG_SND_SOC_WM8983=mCONFIG_SND_SOC_WM8985=mCONFIG_SND_SOC_WM8988=mCONFIG_SND_SOC_WM8990=mCONFIG_SND_SOC_WM8991=mCONFIG_SND_SOC_WM8993=mCONFIG_SND_SOC_WM8994=mCONFIG_SND_SOC_WM8995=mCONFIG_SND_SOC_WM8996=m
# CONFIG_SND_SOC_WM8997 is not set
# CONFIG_SND_SOC_WM8998 is not setCONFIG_SND_SOC_WM9081=mCONFIG_SND_SOC_WM9090=mCONFIG_SND_SOC_WM9705=mCONFIG_SND_SOC_WM9712=mCONFIG_SND_SOC_WM9713=m
# CONFIG_SND_SOC_WSA881X is not set
# CONFIG_SND_SOC_WSA883X is not setCONFIG_SND_SOC_ZL38060=mCONFIG_SND_SOC_LM4857=m
# CONFIG_SND_SOC_MAX9759 is not setCONFIG_SND_SOC_MAX9768=mCONFIG_SND_SOC_MAX9877=mCONFIG_SND_SOC_MC13783=mCONFIG_SND_SOC_ML26124=mCONFIG_SND_SOC_MT6351=mCONFIG_SND_SOC_MT6358=mCONFIG_SND_SOC_MT6359=m
# CONFIG_SND_SOC_MT6359_ACCDET is not setCONFIG_SND_SOC_MT6660=mCONFIG_SND_SOC_NAU8315=m
# CONFIG_SND_SOC_NAU8540 is not setCONFIG_SND_SOC_NAU8810=mCONFIG_SND_SOC_NAU8821=mCONFIG_SND_SOC_NAU8822=m
# CONFIG_SND_SOC_NAU8824 is not setCONFIG_SND_SOC_NAU8825=mCONFIG_SND_SOC_TPA6130A2=mCONFIG_SND_SOC_LPASS_MACRO_COMMON=mCONFIG_SND_SOC_LPASS_WSA_MACRO=mCONFIG_SND_SOC_LPASS_VA_MACRO=m
# CONFIG_SND_SOC_LPASS_RX_MACRO is not setCONFIG_SND_SOC_LPASS_TX_MACRO=m
# end of CODEC drivers
CONFIG_SND_SIMPLE_CARD_UTILS=m CONFIG_SND_SIMPLE_CARD=m
# CONFIG_SND_AUDIO_GRAPH_CARD is not set CONFIG_SND_AUDIO_GRAPH_CARD2=m
# CONFIG_SND_AUDIO_GRAPH_CARD2_CUSTOM_SAMPLE is not set CONFIG_SND_TEST_COMPONENT=m
# CONFIG_SND_VIRTIO is not set CONFIG_AC97_BUS=m
#
# HID support
#CONFIG_HID=yCONFIG_HID_BATTERY_STRENGTH=y
# CONFIG_HIDRAW is not set
# CONFIG_UHID is not setCONFIG_HID_GENERIC=m
#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not setCONFIG_HID_ACRUX=yCONFIG_HID_ACRUX_FF=yCONFIG_HID_APPLE=mCONFIG_HID_AUREAL=mCONFIG_HID_BELKIN=y
# CONFIG_HID_CHERRY is not setCONFIG_HID_COUGAR=m
# CONFIG_HID_MACALLY is not setCONFIG_HID_CMEDIA=mCONFIG_HID_CYPRESS=y
# CONFIG_HID_DRAGONRISE is not setCONFIG_HID_EMS_FF=yCONFIG_HID_ELECOM=y
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_GEMBIRD is not setCONFIG_HID_GFRM=yCONFIG_HID_GLORIOUS=m
# CONFIG_HID_VIVALDI is not setCONFIG_HID_KEYTOUCH=mCONFIG_HID_KYE=mCONFIG_HID_WALTOP=mCONFIG_HID_VIEWSONIC=yCONFIG_HID_VRC2=m
# CONFIG_HID_XIAOMI is not setCONFIG_HID_GYRATION=yCONFIG_HID_ICADE=mCONFIG_HID_ITE=mCONFIG_HID_JABRA=mCONFIG_HID_TWINHAN=mCONFIG_HID_KENSINGTON=yCONFIG_HID_LCPOWER=yCONFIG_HID_LED=m
# CONFIG_HID_LENOVO is not set
# CONFIG_HID_MAGICMOUSE is not setCONFIG_HID_MALTRON=mCONFIG_HID_MAYFLASH=y
# CONFIG_HID_REDRAGON is not setCONFIG_HID_MICROSOFT=yCONFIG_HID_MONTEREY=y
# CONFIG_HID_MULTITOUCH is not setCONFIG_HID_NINTENDO=m
# CONFIG_NINTENDO_FF is not setCONFIG_HID_NTI=mCONFIG_HID_ORTEK=yCONFIG_HID_PANTHERLORD=y
# CONFIG_PANTHERLORD_FF is not set
# CONFIG_HID_PETALYNX is not setCONFIG_HID_PICOLCD=y
# CONFIG_HID_PICOLCD_BACKLIGHT is not setCONFIG_HID_PICOLCD_LCD=yCONFIG_HID_PICOLCD_LEDS=y
# CONFIG_HID_PICOLCD_CIR is not setCONFIG_HID_PLANTRONICS=m
# CONFIG_HID_PXRC is not setCONFIG_HID_RAZER=mCONFIG_HID_PRIMAX=yCONFIG_HID_SAITEK=yCONFIG_HID_SEMITEK=y
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEAM is not setCONFIG_HID_STEELSERIES=m
# CONFIG_HID_SUNPLUS is not setCONFIG_HID_RMI=mCONFIG_HID_GREENASIA=yCONFIG_GREENASIA_FF=yCONFIG_HID_SMARTJOYPLUS=mCONFIG_SMARTJOYPLUS_FF=yCONFIG_HID_TIVO=y
# CONFIG_HID_TOPSEED is not setCONFIG_HID_TOPRE=mCONFIG_HID_THINGM=m
# CONFIG_HID_UDRAW_PS3 is not setCONFIG_HID_WIIMOTE=mCONFIG_HID_XINMO=yCONFIG_HID_ZEROPLUS=mCONFIG_ZEROPLUS_FF=yCONFIG_HID_ZYDACRON=y
# CONFIG_HID_SENSOR_HUB is not setCONFIG_HID_ALPS=y
# end of Special HID drivers
#
# I2C HID support
#
# CONFIG_I2C_HID_OF is not setCONFIG_I2C_HID_OF_ELAN=yCONFIG_I2C_HID_OF_GOODIX=y
# end of I2C HID support
CONFIG_I2C_HID_CORE=y
# end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
# CONFIG_USB_SUPPORT is not setCONFIG_MMC=y
# CONFIG_PWRSEQ_EMMC is not set
# CONFIG_PWRSEQ_SIMPLE is not setCONFIG_SDIO_UART=y
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#CONFIG_MMC_DEBUG=yCONFIG_MMC_ARMMMCI=m
# CONFIG_MMC_STM32_SDMMC is not setCONFIG_MMC_SDHCI=yCONFIG_MMC_SDHCI_IO_ACCESSORS=yCONFIG_MMC_SDHCI_PLTFM=m
# CONFIG_MMC_SDHCI_OF_ARASAN is not setCONFIG_MMC_SDHCI_OF_ASPEED=mCONFIG_MMC_SDHCI_OF_ASPEED_TEST=y
# CONFIG_MMC_SDHCI_OF_AT91 is not set
# CONFIG_MMC_SDHCI_OF_ESDHC is not set
# CONFIG_MMC_SDHCI_OF_DWCMSHC is not setCONFIG_MMC_SDHCI_OF_SPARX5=mCONFIG_MMC_SDHCI_CADENCE=m
# CONFIG_MMC_SDHCI_CNS3XXX is not setCONFIG_MMC_SDHCI_ESDHC_IMX=m
# CONFIG_MMC_SDHCI_DOVE is not setCONFIG_MMC_SDHCI_TEGRA=mCONFIG_MMC_SDHCI_S3C=yCONFIG_MMC_SDHCI_PXAV3=mCONFIG_MMC_SDHCI_PXAV2=mCONFIG_MMC_SDHCI_SPEAR=y
# CONFIG_MMC_SDHCI_S3C_DMA is not set
# CONFIG_MMC_SDHCI_BCM_KONA is not setCONFIG_MMC_SDHCI_F_SDH30=mCONFIG_MMC_SDHCI_MILBEAUT=m
# CONFIG_MMC_SDHCI_IPROC is not set
# CONFIG_MMC_MESON_GX is not setCONFIG_MMC_MESON_MX_SDHC=y
# CONFIG_MMC_MESON_MX_SDIO is not set
# CONFIG_MMC_MOXART is not setCONFIG_MMC_SDHCI_ST=mCONFIG_MMC_OMAP_HS=mCONFIG_MMC_SDHCI_MSM=m
# CONFIG_MMC_DAVINCI is not setCONFIG_MMC_SPI=mCONFIG_MMC_S3C=y
# CONFIG_MMC_S3C_HW_SDIO_IRQ is not setCONFIG_MMC_S3C_PIO=y
# CONFIG_MMC_S3C_DMA is not setCONFIG_MMC_SDHCI_SPRD=mCONFIG_MMC_TMIO_CORE=y
# CONFIG_MMC_TMIO is not set
# CONFIG_MMC_SDHI is not setCONFIG_MMC_UNIPHIER=y
# CONFIG_MMC_DW is not setCONFIG_MMC_SH_MMCIF=mCONFIG_MMC_USDHI6ROL0=yCONFIG_MMC_CQHCI=mCONFIG_MMC_HSQ=mCONFIG_MMC_BCM2835=mCONFIG_MMC_MTK=mCONFIG_MMC_SDHCI_XENON=mCONFIG_MMC_SDHCI_OMAP=mCONFIG_MMC_SDHCI_AM654=mCONFIG_MMC_OWL=mCONFIG_MMC_SDHCI_EXTERNAL_DMA=y
# CONFIG_MMC_LITEX is not setCONFIG_MEMSTICK=yCONFIG_MEMSTICK_DEBUG=y
#
# MemoryStick drivers
#CONFIG_MEMSTICK_UNSAFE_RESUME=y
#
# MemoryStick Host Controller Drivers
#CONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=yCONFIG_LEDS_CLASS_FLASH=y
# CONFIG_LEDS_CLASS_MULTICOLOR is not set
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set
#
# LED drivers
#CONFIG_LEDS_AN30259A=y
# CONFIG_LEDS_ARIEL is not setCONFIG_LEDS_AW2013=mCONFIG_LEDS_BCM6328=mCONFIG_LEDS_BCM6358=mCONFIG_LEDS_CR0014114=yCONFIG_LEDS_EL15203000=mCONFIG_LEDS_LM3530=yCONFIG_LEDS_LM3532=m
# CONFIG_LEDS_LM3642 is not setCONFIG_LEDS_LM3692X=mCONFIG_LEDS_S3C24XX=mCONFIG_LEDS_COBALT_QUBE=y
# CONFIG_LEDS_COBALT_RAQ is not setCONFIG_LEDS_PCA9532=m
# CONFIG_LEDS_PCA9532_GPIO is not setCONFIG_LEDS_GPIO=yCONFIG_LEDS_LP3944=m
# CONFIG_LEDS_LP3952 is not setCONFIG_LEDS_LP50XX=y
# CONFIG_LEDS_LP55XX_COMMON is not set
# CONFIG_LEDS_LP8788 is not set
# CONFIG_LEDS_LP8860 is not setCONFIG_LEDS_PCA955X=mCONFIG_LEDS_PCA955X_GPIO=yCONFIG_LEDS_PCA963X=yCONFIG_LEDS_WM831X_STATUS=y
# CONFIG_LEDS_DA9052 is not setCONFIG_LEDS_DAC124S085=mCONFIG_LEDS_PWM=m
# CONFIG_LEDS_REGULATOR is not setCONFIG_LEDS_BD2802=mCONFIG_LEDS_LT3593=yCONFIG_LEDS_ADP5520=m
# CONFIG_LEDS_MC13783 is not setCONFIG_LEDS_NS2=mCONFIG_LEDS_NETXBIG=m
# CONFIG_LEDS_ASIC3 is not setCONFIG_LEDS_TCA6507=mCONFIG_LEDS_TLC591XX=yCONFIG_LEDS_MAX8997=y
CONFIG_LEDS_LM355x=y
# CONFIG_LEDS_OT200 is not setCONFIG_LEDS_IS31FL319X=yCONFIG_LEDS_IS31FL32XX=m
# CONFIG_LEDS_SC27XX_BLTC is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #CONFIG_LEDS_BLINKM=m
# CONFIG_LEDS_SYSCON is not setCONFIG_LEDS_PM8058=m
# CONFIG_LEDS_MLXREG is not setCONFIG_LEDS_USER=yCONFIG_LEDS_SPI_BYTE=mCONFIG_LEDS_TI_LMU_COMMON=yCONFIG_LEDS_LM3697=mCONFIG_LEDS_LM36274=mCONFIG_LEDS_TPS6105X=yCONFIG_LEDS_IP30=mCONFIG_LEDS_BCM63138=yCONFIG_LEDS_LGM=m
#
# Flash and Torch LED drivers
#
# CONFIG_LEDS_AAT1290 is not set
# CONFIG_LEDS_AS3645A is not setCONFIG_LEDS_KTD2692=yCONFIG_LEDS_LM3601X=y
# CONFIG_LEDS_MAX77693 is not setCONFIG_LEDS_MT6360=mCONFIG_LEDS_RT4505=mCONFIG_LEDS_RT8515=mCONFIG_LEDS_SGM3140=m
#
# RGB LED drivers
#
#
# LED Triggers
#CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
# CONFIG_LEDS_TRIGGER_CPU is not setCONFIG_LEDS_TRIGGER_ACTIVITY=yCONFIG_LEDS_TRIGGER_GPIO=yCONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target) # # CONFIG_LEDS_TRIGGER_TRANSIENT is not set CONFIG_LEDS_TRIGGER_CAMERA=m # CONFIG_LEDS_TRIGGER_PANIC is not set # CONFIG_LEDS_TRIGGER_PATTERN is not set CONFIG_LEDS_TRIGGER_AUDIO=m CONFIG_LEDS_TRIGGER_TTY=m
#
# Simple LED drivers
#CONFIG_ACCESSIBILITY=yCONFIG_A11Y_BRAILLE_CONSOLE=y
#
# Speakup console speech
#CONFIG_SPEAKUP=yCONFIG_SPEAKUP_SERIALIO=y
# CONFIG_SPEAKUP_SYNTH_ACNTSA is not setCONFIG_SPEAKUP_SYNTH_ACNTPC=m
# CONFIG_SPEAKUP_SYNTH_APOLLO is not set
# CONFIG_SPEAKUP_SYNTH_AUDPTR is not setCONFIG_SPEAKUP_SYNTH_BNS=y
# CONFIG_SPEAKUP_SYNTH_DECTLK is not setCONFIG_SPEAKUP_SYNTH_DECEXT=y
# CONFIG_SPEAKUP_SYNTH_DECPC is not set
# CONFIG_SPEAKUP_SYNTH_DTLK is not setCONFIG_SPEAKUP_SYNTH_KEYPC=yCONFIG_SPEAKUP_SYNTH_LTLK=mCONFIG_SPEAKUP_SYNTH_SOFT=yCONFIG_SPEAKUP_SYNTH_SPKOUT=m
# CONFIG_SPEAKUP_SYNTH_TXPRT is not setCONFIG_SPEAKUP_SYNTH_DUMMY=m
# end of Speakup console speech
CONFIG_EDAC_SUPPORT=yCONFIG_EDAC=yCONFIG_EDAC_LEGACY_SYSFS=yCONFIG_EDAC_DEBUG=yCONFIG_EDAC_AL_MC=mCONFIG_EDAC_LAYERSCAPE=mCONFIG_EDAC_XGENE=m
# CONFIG_EDAC_BLUEFIELD is not set
# CONFIG_EDAC_DMC520 is not set
# CONFIG_RTC_CLASS is not setCONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#CONFIG_ASYNC_TX_ENABLE_CHANNEL_SWITCH=yCONFIG_DMA_ENGINE=yCONFIG_DMA_VIRTUAL_CHANNELS=yCONFIG_DMA_OF=yCONFIG_ALTERA_MSGDMA=yCONFIG_AMBA_PL08X=y
# CONFIG_APPLE_ADMAC is not setCONFIG_AXI_DMAC=m
# CONFIG_DMA_BCM2835 is not set
# CONFIG_DMA_JZ4780 is not setCONFIG_DMA_SA11X0=mCONFIG_DMA_SUN6I=yCONFIG_DW_AXI_DMAC=m
# CONFIG_EP93XX_DMA is not set
# CONFIG_FSL_EDMA is not setCONFIG_FSL_QDMA=mCONFIG_IMG_MDC_DMA=m
# CONFIG_INTEL_IDMA64 is not set
# CONFIG_INTEL_IOP_ADMA is not setCONFIG_K3_DMA=y
# CONFIG_LPC18XX_DMAMUX is not setCONFIG_MCF_EDMA=m
# CONFIG_MILBEAUT_HDMAC is not setCONFIG_MILBEAUT_XDMAC=yCONFIG_MMP_PDMA=m
# CONFIG_MMP_TDMA is not set
# CONFIG_MV_XOR is not setCONFIG_MV_XOR_V2=yCONFIG_MXS_DMA=y
# CONFIG_NBPFAXI_DMA is not setCONFIG_PL330_DMA=m
# CONFIG_STM32_DMA is not set
# CONFIG_STM32_DMAMUX is not set
# CONFIG_STM32_MDMA is not set
# CONFIG_SPRD_DMA is not setCONFIG_S3C24XX_DMAC=yCONFIG_TEGRA186_GPC_DMA=m
# CONFIG_TEGRA20_APB_DMA is not setCONFIG_TEGRA210_ADMA=m
# CONFIG_TIMB_DMA is not setCONFIG_UNIPHIER_MDMAC=yCONFIG_UNIPHIER_XDMAC=mCONFIG_XGENE_DMA=mCONFIG_XILINX_DMA=yCONFIG_XILINX_ZYNQMP_DMA=m
# CONFIG_XILINX_ZYNQMP_DPDMA is not setCONFIG_MTK_HSDMA=mCONFIG_MTK_CQDMA=m
# CONFIG_MTK_UART_APDMA is not setCONFIG_QCOM_HIDMA_MGMT=yCONFIG_QCOM_HIDMA=yCONFIG_DW_DMAC_CORE=yCONFIG_DW_DMAC=yCONFIG_RZN1_DMAMUX=yCONFIG_SF_PDMA=mCONFIG_RENESAS_DMA=yCONFIG_SH_DMAE_BASE=y
# CONFIG_SH_DMAE is not setCONFIG_RCAR_DMAC=yCONFIG_RENESAS_USB_DMAC=yCONFIG_RZ_DMAC=yCONFIG_TI_EDMA=m
# CONFIG_DMA_OMAP is not setCONFIG_TI_K3_UDMA=y
# CONFIG_TI_K3_UDMA_GLUE_LAYER is not setCONFIG_TI_K3_PSIL=yCONFIG_TI_DMA_CROSSBAR=y
# CONFIG_INTEL_LDMA is not set
#
# DMA Clients
#
# CONFIG_ASYNC_TX_DMA is not setCONFIG_DMATEST=yCONFIG_DMA_ENGINE_RAID=y
#
# DMABUF options
#CONFIG_SYNC_FILE=yCONFIG_SW_SYNC=y
# CONFIG_UDMABUF is not setCONFIG_DMABUF_MOVE_NOTIFY=yCONFIG_DMABUF_DEBUG=y
# CONFIG_DMABUF_SELFTESTS is not setCONFIG_DMABUF_HEAPS=y
# CONFIG_DMABUF_SYSFS_STATS is not set
# CONFIG_DMABUF_HEAPS_SYSTEM is not set
# CONFIG_DMABUF_HEAPS_CMA is not set
# end of DMABUF options
CONFIG_AUXDISPLAY=yCONFIG_CHARLCD=yCONFIG_LINEDISP=yCONFIG_HD44780_COMMON=yCONFIG_HD44780=mCONFIG_IMG_ASCII_LCD=yCONFIG_HT16K33=mCONFIG_LCD2S=yCONFIG_PARPORT_PANEL=yCONFIG_PANEL_PARPORT=0CONFIG_PANEL_PROFILE=5CONFIG_PANEL_CHANGE_MESSAGE=yCONFIG_PANEL_BOOT_MESSAGE=""
# CONFIG_CHARLCD_BL_OFF is not set
# CONFIG_CHARLCD_BL_ON is not setCONFIG_CHARLCD_BL_FLASH=yCONFIG_PANEL=yCONFIG_UIO=yCONFIG_UIO_PDRV_GENIRQ=yCONFIG_UIO_DMEM_GENIRQ=yCONFIG_UIO_PRUSS=mCONFIG_VFIO=mCONFIG_VFIO_IOMMU_TYPE1=mCONFIG_VFIO_VIRQFD=m
# CONFIG_VFIO_NOIOMMU is not setCONFIG_VFIO_PLATFORM=m
# CONFIG_VFIO_AMBA is not setCONFIG_VFIO_PLATFORM_CALXEDAXGMAC_RESET=m
# CONFIG_VFIO_PLATFORM_AMDXGBE_RESET is not setCONFIG_VFIO_PLATFORM_BCMFLEXRM_RESET=mCONFIG_VFIO_MDEV=mCONFIG_VIRT_DRIVERS=yCONFIG_VIRTIO_ANCHOR=yCONFIG_VIRTIO=yCONFIG_VIRTIO_MENU=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_INPUT is not setCONFIG_VIRTIO_MMIO=mCONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=yCONFIG_VHOST_MENU=y
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
#
# Microsoft Hyper-V guest support
#
# end of Microsoft Hyper-V guest support
# CONFIG_GREYBUS is not setCONFIG_COMEDI=yCONFIG_COMEDI_DEBUG=yCONFIG_COMEDI_DEFAULT_BUF_SIZE_KB=2048CONFIG_COMEDI_DEFAULT_BUF_MAXSIZE_KB=20480CONFIG_COMEDI_MISC_DRIVERS=yCONFIG_COMEDI_BOND=mCONFIG_COMEDI_TEST=yCONFIG_COMEDI_PARPORT=yCONFIG_COMEDI_SSV_DNP=yCONFIG_COMEDI_ISA_DRIVERS=yCONFIG_COMEDI_PCL711=mCONFIG_COMEDI_PCL724=yCONFIG_COMEDI_PCL726=yCONFIG_COMEDI_PCL730=yCONFIG_COMEDI_PCL812=yCONFIG_COMEDI_PCL816=mCONFIG_COMEDI_PCL818=yCONFIG_COMEDI_PCM3724=yCONFIG_COMEDI_AMPLC_DIO200_ISA=y
# CONFIG_COMEDI_AMPLC_PC236_ISA is not set
# CONFIG_COMEDI_AMPLC_PC263_ISA is not set
# CONFIG_COMEDI_RTI800 is not setCONFIG_COMEDI_RTI802=mCONFIG_COMEDI_DAC02=mCONFIG_COMEDI_DAS16M1=y
# CONFIG_COMEDI_DAS08_ISA is not setCONFIG_COMEDI_DAS16=yCONFIG_COMEDI_DAS800=yCONFIG_COMEDI_DAS1800=mCONFIG_COMEDI_DAS6402=m
# CONFIG_COMEDI_DT2801 is not setCONFIG_COMEDI_DT2811=y
# CONFIG_COMEDI_DT2814 is not set
# CONFIG_COMEDI_DT2815 is not setCONFIG_COMEDI_DT2817=m
# CONFIG_COMEDI_DT282X is not set
# CONFIG_COMEDI_DMM32AT is not setCONFIG_COMEDI_FL512=m
# CONFIG_COMEDI_AIO_AIO12_8 is not setCONFIG_COMEDI_AIO_IIRO_16=yCONFIG_COMEDI_II_PCI20KC=mCONFIG_COMEDI_C6XDIGIO=mCONFIG_COMEDI_MPC624=yCONFIG_COMEDI_ADQ12B=mCONFIG_COMEDI_NI_AT_A2150=yCONFIG_COMEDI_NI_AT_AO=mCONFIG_COMEDI_NI_ATMIO=mCONFIG_COMEDI_NI_ATMIO16D=m
# CONFIG_COMEDI_NI_LABPC_ISA is not setCONFIG_COMEDI_PCMAD=yCONFIG_COMEDI_PCMDA12=mCONFIG_COMEDI_PCMMIO=yCONFIG_COMEDI_PCMUIO=m
# CONFIG_COMEDI_MULTIQ3 is not set
# CONFIG_COMEDI_S526 is not setCONFIG_COMEDI_8254=yCONFIG_COMEDI_8255=yCONFIG_COMEDI_8255_SA=mCONFIG_COMEDI_KCOMEDILIB=mCONFIG_COMEDI_AMPLC_DIO200=yCONFIG_COMEDI_NI_TIO=mCONFIG_COMEDI_NI_ROUTING=mCONFIG_COMEDI_TESTS=yCONFIG_COMEDI_TESTS_EXAMPLE=y
# CONFIG_COMEDI_TESTS_NI_ROUTES is not set
# CONFIG_STAGING is not set
# CONFIG_GOLDFISH is not set
# CONFIG_CHROME_PLATFORMS is not set
# CONFIG_MELLANOX_PLATFORM is not set
# CONFIG_OLPC_XO175 is not set
# CONFIG_SURFACE_PLATFORMS is not setCONFIG_HAVE_CLK=yCONFIG_HAVE_CLK_PREPARE=yCONFIG_COMMON_CLK=yCONFIG_COMMON_CLK_WM831X=m
#
# Clock driver for ARM Reference designs
#CONFIG_CLK_ICST=y
# CONFIG_CLK_SP810 is not setCONFIG_CLK_VEXPRESS_OSC=m
# end of Clock driver for ARM Reference designs
# CONFIG_CLK_HSDK is not setCONFIG_LMK04832=y
# CONFIG_COMMON_CLK_APPLE_NCO is not set
# CONFIG_COMMON_CLK_MAX77686 is not setCONFIG_COMMON_CLK_MAX9485=y
# CONFIG_COMMON_CLK_RK808 is not set
# CONFIG_COMMON_CLK_HI655X is not setCONFIG_COMMON_CLK_SCMI=mCONFIG_COMMON_CLK_SCPI=yCONFIG_COMMON_CLK_SI5341=yCONFIG_COMMON_CLK_SI5351=y
# CONFIG_COMMON_CLK_SI514 is not set
# CONFIG_COMMON_CLK_SI544 is not setCONFIG_COMMON_CLK_SI570=m
# CONFIG_COMMON_CLK_BM1880 is not set
# CONFIG_COMMON_CLK_CDCE706 is not set
# CONFIG_COMMON_CLK_TPS68470 is not set
# CONFIG_COMMON_CLK_CDCE925 is not setCONFIG_COMMON_CLK_CS2000_CP=yCONFIG_COMMON_CLK_EN7523=yCONFIG_COMMON_CLK_FSL_FLEXSPI=mCONFIG_COMMON_CLK_FSL_SAI=y
# CONFIG_COMMON_CLK_GEMINI is not set
# CONFIG_COMMON_CLK_LAN966X is not setCONFIG_COMMON_CLK_ASPEED=y
# CONFIG_COMMON_CLK_S2MPS11 is not setCONFIG_COMMON_CLK_AXI_CLKGEN=mCONFIG_CLK_QORIQ=y
# CONFIG_CLK_LS1028A_PLLDIG is not setCONFIG_COMMON_CLK_XGENE=y
# CONFIG_COMMON_CLK_PWM is not setCONFIG_COMMON_CLK_OXNAS=yCONFIG_COMMON_CLK_RS9_PCIE=yCONFIG_COMMON_CLK_VC5=y
# CONFIG_COMMON_CLK_VC7 is not setCONFIG_COMMON_CLK_MMP2_AUDIO=yCONFIG_COMMON_CLK_BD718XX=m
# CONFIG_COMMON_CLK_FIXED_MMIO is not set
# CONFIG_CLK_ACTIONS is not set
# CONFIG_CLK_BAIKAL_T1 is not setCONFIG_CLK_BCM2711_DVP=yCONFIG_CLK_BCM2835=y
# CONFIG_CLK_BCM_63XX is not setCONFIG_CLK_BCM_63XX_GATE=yCONFIG_CLK_BCM_KONA=yCONFIG_COMMON_CLK_IPROC=y
# CONFIG_CLK_BCM_CYGNUS is not set
# CONFIG_CLK_BCM_HR2 is not set
# CONFIG_CLK_BCM_NSP is not setCONFIG_CLK_BCM_NS2=yCONFIG_CLK_BCM_SR=yCONFIG_CLK_RASPBERRYPI=m
# CONFIG_COMMON_CLK_HI3516CV300 is not setCONFIG_COMMON_CLK_HI3519=y
# CONFIG_COMMON_CLK_HI3559A is not set
# CONFIG_COMMON_CLK_HI3660 is not set
# CONFIG_COMMON_CLK_HI3670 is not setCONFIG_COMMON_CLK_HI3798CV200=y
# CONFIG_COMMON_CLK_HI6220 is not setCONFIG_RESET_HISI=yCONFIG_STUB_CLK_HI6220=y
# CONFIG_STUB_CLK_HI3660 is not setCONFIG_COMMON_CLK_BOSTON=yCONFIG_MXC_CLK=y
# CONFIG_CLK_IMX8MM is not set
# CONFIG_CLK_IMX8MN is not setCONFIG_CLK_IMX8MP=yCONFIG_CLK_IMX8MQ=yCONFIG_CLK_IMX8ULP=yCONFIG_CLK_IMX93=m
#
# Ingenic SoCs drivers
#CONFIG_INGENIC_CGU_COMMON=yCONFIG_INGENIC_CGU_JZ4740=yCONFIG_INGENIC_CGU_JZ4725B=y
# CONFIG_INGENIC_CGU_JZ4760 is not setCONFIG_INGENIC_CGU_JZ4770=y
# CONFIG_INGENIC_CGU_JZ4780 is not setCONFIG_INGENIC_CGU_X1000=y
# CONFIG_INGENIC_CGU_X1830 is not set
# CONFIG_INGENIC_TCU_CLK is not set
# end of Ingenic SoCs drivers
# CONFIG_COMMON_CLK_KEYSTONE is not setCONFIG_TI_SCI_CLK=m
# CONFIG_TI_SCI_CLK_PROBE_FROM_FW is not set
# CONFIG_TI_SYSCON_CLK is not set
#
# Clock driver for MediaTek SoC
#CONFIG_COMMON_CLK_MEDIATEK=y
# CONFIG_COMMON_CLK_MT2701 is not set
# CONFIG_COMMON_CLK_MT2712 is not setCONFIG_COMMON_CLK_MT6765=y
# CONFIG_COMMON_CLK_MT6765_AUDIOSYS is not setCONFIG_COMMON_CLK_MT6765_CAMSYS=yCONFIG_COMMON_CLK_MT6765_GCESYS=y
# CONFIG_COMMON_CLK_MT6765_MMSYS is not set
# CONFIG_COMMON_CLK_MT6765_IMGSYS is not set
# CONFIG_COMMON_CLK_MT6765_VCODECSYS is not setCONFIG_COMMON_CLK_MT6765_MFGSYS=yCONFIG_COMMON_CLK_MT6765_MIPI0ASYS=yCONFIG_COMMON_CLK_MT6765_MIPI0BSYS=yCONFIG_COMMON_CLK_MT6765_MIPI1ASYS=yCONFIG_COMMON_CLK_MT6765_MIPI1BSYS=y
# CONFIG_COMMON_CLK_MT6765_MIPI2ASYS is not set
# CONFIG_COMMON_CLK_MT6765_MIPI2BSYS is not setCONFIG_COMMON_CLK_MT6779=mCONFIG_COMMON_CLK_MT6779_MMSYS=m
# CONFIG_COMMON_CLK_MT6779_IMGSYS is not setCONFIG_COMMON_CLK_MT6779_IPESYS=mCONFIG_COMMON_CLK_MT6779_CAMSYS=mCONFIG_COMMON_CLK_MT6779_VDECSYS=mCONFIG_COMMON_CLK_MT6779_VENCSYS=mCONFIG_COMMON_CLK_MT6779_MFGCFG=mCONFIG_COMMON_CLK_MT6779_AUDSYS=mCONFIG_COMMON_CLK_MT6795=y
# CONFIG_COMMON_CLK_MT6795_MFGCFG is not setCONFIG_COMMON_CLK_MT6795_MMSYS=mCONFIG_COMMON_CLK_MT6795_VDECSYS=yCONFIG_COMMON_CLK_MT6795_VENCSYS=m
# CONFIG_COMMON_CLK_MT6797 is not set
# CONFIG_COMMON_CLK_MT7622 is not setCONFIG_COMMON_CLK_MT7629=y
# CONFIG_COMMON_CLK_MT7629_ETHSYS is not set
# CONFIG_COMMON_CLK_MT7629_HIFSYS is not setCONFIG_COMMON_CLK_MT7986=y
# CONFIG_COMMON_CLK_MT7986_ETHSYS is not setCONFIG_COMMON_CLK_MT8135=y
# CONFIG_COMMON_CLK_MT8167 is not setCONFIG_COMMON_CLK_MT8173=yCONFIG_COMMON_CLK_MT8173_MMSYS=yCONFIG_COMMON_CLK_MT8183=y
# CONFIG_COMMON_CLK_MT8183_AUDIOSYS is not set
# CONFIG_COMMON_CLK_MT8183_CAMSYS is not set
# CONFIG_COMMON_CLK_MT8183_IMGSYS is not setCONFIG_COMMON_CLK_MT8183_IPU_CORE0=yCONFIG_COMMON_CLK_MT8183_IPU_CORE1=y
# CONFIG_COMMON_CLK_MT8183_IPU_ADL is not set
# CONFIG_COMMON_CLK_MT8183_IPU_CONN is not setCONFIG_COMMON_CLK_MT8183_MFGCFG=yCONFIG_COMMON_CLK_MT8183_MMSYS=yCONFIG_COMMON_CLK_MT8183_VDECSYS=y
# CONFIG_COMMON_CLK_MT8183_VENCSYS is not set
# CONFIG_COMMON_CLK_MT8186 is not set
# CONFIG_COMMON_CLK_MT8192 is not setCONFIG_COMMON_CLK_MT8195=y
# CONFIG_COMMON_CLK_MT8365 is not setCONFIG_COMMON_CLK_MT8516=yCONFIG_COMMON_CLK_MT8516_AUDSYS=y
# end of Clock driver for MediaTek SoC
#
# Clock support for Amlogic platforms
#CONFIG_COMMON_CLK_MESON_REGMAP=yCONFIG_COMMON_CLK_MESON_DUALDIV=yCONFIG_COMMON_CLK_MESON_MPLL=yCONFIG_COMMON_CLK_MESON_PHASE=yCONFIG_COMMON_CLK_MESON_PLL=yCONFIG_COMMON_CLK_MESON_SCLK_DIV=yCONFIG_COMMON_CLK_MESON_VID_PLL_DIV=yCONFIG_COMMON_CLK_MESON_AO_CLKC=yCONFIG_COMMON_CLK_MESON_EE_CLKC=yCONFIG_COMMON_CLK_MESON_CPU_DYNDIV=y
# CONFIG_COMMON_CLK_GXBB is not setCONFIG_COMMON_CLK_AXG=mCONFIG_COMMON_CLK_AXG_AUDIO=yCONFIG_COMMON_CLK_G12A=y
# end of Clock support for Amlogic platforms
CONFIG_MSTAR_MSC313_MPLL=yCONFIG_MCHP_CLK_MPFS=yCONFIG_ARMADA_AP_CP_HELPER=yCONFIG_ARMADA_37XX_CLK=yCONFIG_ARMADA_AP806_SYSCON=yCONFIG_ARMADA_CP110_SYSCON=y
# CONFIG_COMMON_CLK_PISTACHIO is not setCONFIG_QCOM_GDSC=yCONFIG_COMMON_CLK_QCOM=m
# CONFIG_QCOM_A53PLL is not set
# CONFIG_QCOM_A7PLL is not setCONFIG_QCOM_CLK_APCS_MSM8916=m
# CONFIG_QCOM_CLK_APCC_MSM8996 is not setCONFIG_QCOM_CLK_APCS_SDX55=m
# CONFIG_QCOM_CLK_SMD_RPM is not setCONFIG_APQ_GCC_8084=m
# CONFIG_APQ_MMCC_8084 is not setCONFIG_IPQ_APSS_PLL=mCONFIG_IPQ_APSS_6018=m
# CONFIG_IPQ_GCC_4019 is not setCONFIG_IPQ_GCC_6018=mCONFIG_IPQ_GCC_806X=mCONFIG_IPQ_LCC_806X=mCONFIG_IPQ_GCC_8074=m
# CONFIG_MSM_GCC_8660 is not setCONFIG_MSM_GCC_8909=m
# CONFIG_MSM_GCC_8916 is not setCONFIG_MSM_GCC_8939=mCONFIG_MSM_GCC_8960=m
# CONFIG_MSM_LCC_8960 is not setCONFIG_MDM_GCC_9607=mCONFIG_MDM_GCC_9615=m
# CONFIG_MDM_LCC_9615 is not setCONFIG_MSM_MMCC_8960=m
# CONFIG_MSM_GCC_8953 is not setCONFIG_MSM_GCC_8974=m
# CONFIG_MSM_MMCC_8974 is not setCONFIG_MSM_GCC_8976=mCONFIG_MSM_MMCC_8994=mCONFIG_MSM_GCC_8994=mCONFIG_MSM_GCC_8996=m
# CONFIG_MSM_MMCC_8996 is not set
# CONFIG_MSM_GCC_8998 is not set
# CONFIG_MSM_GPUCC_8998 is not set
# CONFIG_MSM_MMCC_8998 is not setCONFIG_QCM_GCC_2290=m
# CONFIG_QCM_DISPCC_2290 is not setCONFIG_QCS_GCC_404=m
# CONFIG_SC_CAMCC_7180 is not set
# CONFIG_SC_CAMCC_7280 is not setCONFIG_SC_DISPCC_7180=mCONFIG_SC_DISPCC_7280=mCONFIG_SC_GCC_7180=mCONFIG_SC_GCC_7280=mCONFIG_SC_GCC_8180X=mCONFIG_SC_GCC_8280XP=mCONFIG_SC_GPUCC_7180=m
# CONFIG_SC_GPUCC_7280 is not setCONFIG_SC_GPUCC_8280XP=mCONFIG_SC_LPASSCC_7280=mCONFIG_SC_LPASS_CORECC_7180=m
# CONFIG_SC_LPASS_CORECC_7280 is not set
# CONFIG_SC_MSS_7180 is not setCONFIG_SC_VIDEOCC_7180=mCONFIG_SC_VIDEOCC_7280=m
# CONFIG_SDM_CAMCC_845 is not setCONFIG_SDM_GCC_660=mCONFIG_SDM_MMCC_660=mCONFIG_SDM_GPUCC_660=m
# CONFIG_QCS_TURING_404 is not setCONFIG_QCS_Q6SSTOP_404=mCONFIG_SDM_GCC_845=m
# CONFIG_SDM_GPUCC_845 is not setCONFIG_SDM_VIDEOCC_845=m
# CONFIG_SDM_DISPCC_845 is not set
# CONFIG_SDM_LPASSCC_845 is not setCONFIG_SDX_GCC_55=mCONFIG_SDX_GCC_65=mCONFIG_SM_CAMCC_8250=mCONFIG_SM_CAMCC_8450=mCONFIG_SM_DISPCC_6125=m
# CONFIG_SM_DISPCC_8250 is not setCONFIG_SM_DISPCC_6350=mCONFIG_SM_DISPCC_8450=m
# CONFIG_SM_GCC_6115 is not setCONFIG_SM_GCC_6125=mCONFIG_SM_GCC_6350=mCONFIG_SM_GCC_6375=mCONFIG_SM_GCC_8150=mCONFIG_SM_GCC_8250=m
# CONFIG_SM_GCC_8350 is not setCONFIG_SM_GCC_8450=mCONFIG_SM_GPUCC_6350=mCONFIG_SM_GPUCC_8150=mCONFIG_SM_GPUCC_8250=m
# CONFIG_SM_GPUCC_8350 is not setCONFIG_SM_VIDEOCC_8150=mCONFIG_SM_VIDEOCC_8250=mCONFIG_SPMI_PMIC_CLKDIV=mCONFIG_QCOM_HFPLL=mCONFIG_KPSS_XCC=mCONFIG_CLK_GFM_LPASS_SM8250=m
# CONFIG_CLK_MT7621 is not setCONFIG_CLK_RENESAS=y
# CONFIG_CLK_EMEV2 is not setCONFIG_CLK_RZA1=yCONFIG_CLK_R7S9210=y
# CONFIG_CLK_R8A73A4 is not setCONFIG_CLK_R8A7740=y
# CONFIG_CLK_R8A7742 is not set
# CONFIG_CLK_R8A7743 is not setCONFIG_CLK_R8A7745=yCONFIG_CLK_R8A77470=yCONFIG_CLK_R8A774A1=yCONFIG_CLK_R8A774B1=yCONFIG_CLK_R8A774C0=yCONFIG_CLK_R8A774E1=yCONFIG_CLK_R8A7778=yCONFIG_CLK_R8A7779=yCONFIG_CLK_R8A7790=yCONFIG_CLK_R8A7791=y
# CONFIG_CLK_R8A7792 is not set
# CONFIG_CLK_R8A7794 is not setCONFIG_CLK_R8A7795=yCONFIG_CLK_R8A77960=yCONFIG_CLK_R8A77961=y
# CONFIG_CLK_R8A77965 is not setCONFIG_CLK_R8A77970=y
# CONFIG_CLK_R8A77980 is not setCONFIG_CLK_R8A77990=yCONFIG_CLK_R8A77995=yCONFIG_CLK_R8A779A0=yCONFIG_CLK_R8A779F0=yCONFIG_CLK_R8A779G0=y
# CONFIG_CLK_R9A06G032 is not setCONFIG_CLK_R9A07G043=yCONFIG_CLK_R9A07G044=yCONFIG_CLK_R9A07G054=yCONFIG_CLK_R9A09G011=yCONFIG_CLK_SH73A0=yCONFIG_CLK_RCAR_CPG_LIB=yCONFIG_CLK_RCAR_GEN2_CPG=yCONFIG_CLK_RCAR_GEN3_CPG=yCONFIG_CLK_RCAR_GEN4_CPG=y
# CONFIG_CLK_RCAR_USB2_CLOCK_SEL is not setCONFIG_CLK_RZG2L=yCONFIG_CLK_RENESAS_CPG_MSSR=yCONFIG_CLK_RENESAS_CPG_MSTP=yCONFIG_CLK_RENESAS_DIV6=yCONFIG_COMMON_CLK_SAMSUNG=yCONFIG_S3C64XX_COMMON_CLK=y
# CONFIG_S5PV210_COMMON_CLK is not setCONFIG_EXYNOS_3250_COMMON_CLK=yCONFIG_EXYNOS_4_COMMON_CLK=y
# CONFIG_EXYNOS_5250_COMMON_CLK is not set
# CONFIG_EXYNOS_5260_COMMON_CLK is not setCONFIG_EXYNOS_5410_COMMON_CLK=y
# CONFIG_EXYNOS_5420_COMMON_CLK is not setCONFIG_EXYNOS_ARM64_COMMON_CLK=y
# CONFIG_EXYNOS_AUDSS_CLK_CON is not setCONFIG_EXYNOS_CLKOUT=mCONFIG_S3C2410_COMMON_CLK=y
# CONFIG_S3C2412_COMMON_CLK is not set
# CONFIG_S3C2443_COMMON_CLK is not set
# CONFIG_TESLA_FSD_COMMON_CLK is not setCONFIG_CLK_SIFIVE=y
# CONFIG_CLK_SIFIVE_PRCI is not setCONFIG_CLK_INTEL_SOCFPGA=yCONFIG_CLK_INTEL_SOCFPGA32=y
# CONFIG_CLK_INTEL_SOCFPGA64 is not set
# CONFIG_SPRD_COMMON_CLK is not setCONFIG_CLK_STARFIVE_JH7100=yCONFIG_CLK_STARFIVE_JH7100_AUDIO=mCONFIG_CLK_SUNXI=y
# CONFIG_CLK_SUNXI_CLOCKS is not setCONFIG_CLK_SUNXI_PRCM_SUN6I=yCONFIG_CLK_SUNXI_PRCM_SUN8I=yCONFIG_CLK_SUNXI_PRCM_SUN9I=y
# CONFIG_SUNXI_CCU is not setCONFIG_COMMON_CLK_TI_ADPLL=m
# CONFIG_CLK_UNIPHIER is not setCONFIG_COMMON_CLK_VISCONTI=y
# CONFIG_CLK_LGM_CGU is not set
# CONFIG_XILINX_VCU is not setCONFIG_COMMON_CLK_XLNX_CLKWZRD=yCONFIG_COMMON_CLK_ZYNQMP=y
# CONFIG_CLK_KUNIT_TEST is not setCONFIG_CLK_GATE_KUNIT_TEST=m
# CONFIG_HWSPINLOCK is not set
#
# Clock Source drivers
#CONFIG_TIMER_OF=yCONFIG_TIMER_PROBE=yCONFIG_CLKSRC_MMIO=y
# CONFIG_BCM2835_TIMER is not set
# CONFIG_BCM_KONA_TIMER is not set
# CONFIG_DAVINCI_TIMER is not set
# CONFIG_DIGICOLOR_TIMER is not setCONFIG_OMAP_DM_TIMER=y
# CONFIG_DW_APB_TIMER is not set
# CONFIG_FTTMR010_TIMER is not set
# CONFIG_IXP4XX_TIMER is not set
# CONFIG_ROCKCHIP_TIMER is not set
# CONFIG_MESON6_TIMER is not set
# CONFIG_OWL_TIMER is not set
# CONFIG_RDA_TIMER is not setCONFIG_SUN4I_TIMER=yCONFIG_SUN5I_HSTIMER=y
# CONFIG_TEGRA_TIMER is not set
# CONFIG_VT8500_TIMER is not setCONFIG_NPCM7XX_TIMER=y
# CONFIG_CADENCE_TTC_TIMER is not set
# CONFIG_ASM9260_TIMER is not setCONFIG_CLKSRC_DBX500_PRCMU=yCONFIG_CLPS711X_TIMER=yCONFIG_MXS_TIMER=yCONFIG_NSPIRE_TIMER=y
# CONFIG_KEYSTONE_TIMER is not set
# CONFIG_INTEGRATOR_AP_TIMER is not setCONFIG_CLKSRC_PISTACHIO=y
# CONFIG_CLKSRC_TI_32K is not setCONFIG_CLKSRC_STM32_LP=y
# CONFIG_CLKSRC_MPS2 is not set
# CONFIG_ARC_TIMERS is not setCONFIG_ARM_ARCH_TIMER=yCONFIG_ARM_ARCH_TIMER_EVTSTREAM=yCONFIG_ARM_ARCH_TIMER_OOL_WORKAROUND=yCONFIG_FSL_ERRATUM_A008585=y
# CONFIG_HISILICON_ERRATUM_161010101 is not set
# CONFIG_ARM64_ERRATUM_858921 is not setCONFIG_SUN50I_ERRATUM_UNKNOWN1=yCONFIG_ARM_TIMER_SP804=y
# CONFIG_ARMV7M_SYSTICK is not setCONFIG_ATMEL_PIT=y
# CONFIG_ATMEL_ST is not setCONFIG_CLKSRC_EXYNOS_MCT=yCONFIG_CLKSRC_SAMSUNG_PWM=y
# CONFIG_FSL_FTM_TIMER is not setCONFIG_OXNAS_RPS_TIMER=yCONFIG_SYS_SUPPORTS_SH_CMT=yCONFIG_MTK_TIMER=yCONFIG_SPRD_TIMER=yCONFIG_SYS_SUPPORTS_SH_TMU=y
# CONFIG_CLKSRC_JCORE_PIT is not setCONFIG_SH_TIMER_CMT=yCONFIG_SH_TIMER_MTU2=y
# CONFIG_RENESAS_OSTM is not set
# CONFIG_SH_TIMER_TMU is not setCONFIG_EM_TIMER_STI=yCONFIG_CLKSRC_VERSATILE=yCONFIG_CLKSRC_PXA=y
# CONFIG_CLKSRC_IMX_GPT is not setCONFIG_CLKSRC_IMX_TPM=y
# CONFIG_TIMER_IMX_SYS_CTR is not setCONFIG_CLKSRC_ST_LPC=yCONFIG_GXP_TIMER=yCONFIG_MSC313E_TIMER=y
# CONFIG_INGENIC_TIMER is not setCONFIG_INGENIC_SYSOST=yCONFIG_INGENIC_OST=y
# CONFIG_MICROCHIP_PIT64B is not set
# end of Clock Source drivers
CONFIG_MAILBOX=yCONFIG_APPLE_MAILBOX=y
# CONFIG_ARM_MHU is not setCONFIG_ARM_MHU_V2=y
# CONFIG_IMX_MBOX is not setCONFIG_PLATFORM_MHU=mCONFIG_PL320_MBOX=yCONFIG_ARMADA_37XX_RWTM_MBOX=mCONFIG_OMAP2PLUS_MBOX=yCONFIG_OMAP_MBOX_KFIFO_SIZE=256CONFIG_ROCKCHIP_MBOX=yCONFIG_ALTERA_MBOX=m
# CONFIG_BCM2835_MBOX is not setCONFIG_TI_MESSAGE_MANAGER=yCONFIG_HI3660_MBOX=mCONFIG_HI6220_MBOX=m
# CONFIG_MAILBOX_TEST is not set
# CONFIG_POLARFIRE_SOC_MAILBOX is not setCONFIG_QCOM_APCS_IPC=mCONFIG_BCM_PDC_MBOX=y
# CONFIG_BCM_FLEXRM_MBOX is not setCONFIG_STM32_IPCC=m
# CONFIG_MTK_ADSP_MBOX is not setCONFIG_MTK_CMDQ_MBOX=yCONFIG_SUN6I_MSGBOX=y
# CONFIG_SPRD_MBOX is not set
# CONFIG_QCOM_IPCC is not setCONFIG_IOMMU_IOVA=yCONFIG_IOMMU_API=yCONFIG_IOMMU_SUPPORT=y
#
# Generic IOMMU Pagetable Support
#CONFIG_IOMMU_IO_PGTABLE=y CONFIG_IOMMU_IO_PGTABLE_LPAE=y
# CONFIG_IOMMU_IO_PGTABLE_LPAE_SELFTEST is not set CONFIG_IOMMU_IO_PGTABLE_ARMV7S=y
# CONFIG_IOMMU_IO_PGTABLE_ARMV7S_SELFTEST is not set CONFIG_IOMMU_IO_PGTABLE_DART=y
# end of Generic IOMMU Pagetable Support
# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_IOMMU_DEFAULT_DMA_STRICT is not set CONFIG_IOMMU_DEFAULT_DMA_LAZY=y
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set CONFIG_OF_IOMMU=yCONFIG_IOMMU_DMA=yCONFIG_OMAP_IOMMU=yCONFIG_OMAP_IOMMU_DEBUG=y
# CONFIG_ROCKCHIP_IOMMU is not set CONFIG_SUN50I_IOMMU=yCONFIG_IPMMU_VMSA=y
# CONFIG_APPLE_DART is not set CONFIG_ARM_SMMU=y CONFIG_ARM_SMMU_LEGACY_DT_BINDINGS=y
# CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT is not set CONFIG_ARM_SMMU_V3=y
# CONFIG_ARM_SMMU_V3_SVA is not set CONFIG_S390_CCW_IOMMU=y CONFIG_S390_AP_IOMMU=yCONFIG_MTK_IOMMU=y
# CONFIG_QCOM_IOMMU is not set CONFIG_VIRTIO_IOMMU=mCONFIG_SPRD_IOMMU=m
#
# Remoteproc drivers
#CONFIG_REMOTEPROC=y
# CONFIG_REMOTEPROC_CDEV is not set
# CONFIG_INGENIC_VPU_RPROC is not set
# CONFIG_MTK_SCP is not set
# CONFIG_MESON_MX_AO_ARC_REMOTEPROC is not setCONFIG_RCAR_REMOTEPROC=mCONFIG_TI_K3_DSP_REMOTEPROC=yCONFIG_TI_K3_R5_REMOTEPROC=m
# end of Remoteproc drivers
#
# Rpmsg drivers
#CONFIG_RPMSG=yCONFIG_RPMSG_CTRL=yCONFIG_RPMSG_NS=mCONFIG_RPMSG_QCOM_GLINK=yCONFIG_RPMSG_QCOM_GLINK_RPM=y
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers
# CONFIG_SOUNDWIRE is not set
#
# SOC (System On Chip) specific Drivers
#
# CONFIG_OWL_PM_DOMAINS is not set
#
# Amlogic SoC drivers
#CONFIG_MESON_CANVAS=yCONFIG_MESON_CLK_MEASURE=y
# CONFIG_MESON_GX_SOCINFO is not setCONFIG_MESON_GX_PM_DOMAINS=mCONFIG_MESON_EE_PM_DOMAINS=m
# CONFIG_MESON_SECURE_PM_DOMAINS is not set
# CONFIG_MESON_MX_SOCINFO is not set
# end of Amlogic SoC drivers
#
# Apple SoC drivers
#CONFIG_APPLE_PMGR_PWRSTATE=y
# CONFIG_APPLE_RTKIT is not setCONFIG_APPLE_SART=y
# end of Apple SoC drivers
#
# ASPEED SoC drivers
#
# CONFIG_ASPEED_LPC_CTRL is not setCONFIG_ASPEED_LPC_SNOOP=mCONFIG_ASPEED_UART_ROUTING=m
# CONFIG_ASPEED_P2A_CTRL is not set
# CONFIG_ASPEED_SOCINFO is not set
# end of ASPEED SoC drivers
# CONFIG_AT91_SOC_ID is not setCONFIG_AT91_SOC_SFR=y
#
# Broadcom SoC drivers
#CONFIG_BCM2835_POWER=yCONFIG_SOC_BCM63XX=yCONFIG_SOC_BRCMSTB=yCONFIG_BCM63XX_POWER=y
# CONFIG_BCM_PMB is not set
# end of Broadcom SoC drivers
#
# NXP/Freescale QorIQ SoC drivers
#
# CONFIG_FSL_DPAA is not setCONFIG_QUICC_ENGINE=yCONFIG_UCC_SLOW=yCONFIG_UCC=y
# CONFIG_DPAA2_CONSOLE is not set
# end of NXP/Freescale QorIQ SoC drivers
#
# fujitsu SoC drivers # # end of fujitsu SoC drivers
#
# i.MX SoC drivers
#CONFIG_IMX_GPCV2_PM_DOMAINS=y
# CONFIG_SOC_IMX8M is not set
# CONFIG_SOC_IMX9 is not set
# end of i.MX SoC drivers
#
# IXP4xx SoC drivers
#CONFIG_IXP4XX_QMGR=y
# CONFIG_IXP4XX_NPE is not set
# end of IXP4xx SoC drivers
#
# Enable LiteX SoC Builder specific drivers
#CONFIG_LITEX=yCONFIG_LITEX_SOC_CONTROLLER=y
# end of Enable LiteX SoC Builder specific drivers
#
# MediaTek SoC drivers
#CONFIG_MTK_CMDQ=mCONFIG_MTK_DEVAPC=mCONFIG_MTK_INFRACFG=yCONFIG_MTK_PMIC_WRAP=yCONFIG_MTK_SCPSYS=y
# CONFIG_MTK_SCPSYS_PM_DOMAINS is not setCONFIG_MTK_MMSYS=yCONFIG_MTK_SVS=y
# end of MediaTek SoC drivers
#
# Qualcomm SoC drivers
#CONFIG_QCOM_AOSS_QMP=mCONFIG_QCOM_COMMAND_DB=y
# CONFIG_QCOM_GENI_SE is not set
# CONFIG_QCOM_GSBI is not setCONFIG_QCOM_LLCC=y
# CONFIG_QCOM_RPMH is not setCONFIG_QCOM_RPMPD=mCONFIG_QCOM_SMD_RPM=mCONFIG_QCOM_SPM=y
# CONFIG_QCOM_WCNSS_CTRL is not set
# CONFIG_QCOM_ICC_BWMON is not set
# end of Qualcomm SoC drivers
CONFIG_SOC_RENESAS=yCONFIG_ARCH_RCAR_GEN3=yCONFIG_ARCH_RZG2L=y
# CONFIG_ARCH_R8A77995 is not setCONFIG_ARCH_R8A77990=yCONFIG_ARCH_R8A77950=yCONFIG_ARCH_R8A77951=y
# CONFIG_ARCH_R8A77965 is not setCONFIG_ARCH_R8A77960=yCONFIG_ARCH_R8A77961=yCONFIG_ARCH_R8A779F0=y
# CONFIG_ARCH_R8A77980 is not set
# CONFIG_ARCH_R8A77970 is not setCONFIG_ARCH_R8A779A0=yCONFIG_ARCH_R8A779G0=y
# CONFIG_ARCH_R8A774C0 is not setCONFIG_ARCH_R8A774E1=yCONFIG_ARCH_R8A774A1=y
# CONFIG_ARCH_R8A774B1 is not setCONFIG_ARCH_R9A07G043=yCONFIG_ARCH_R9A07G044=y
# CONFIG_ARCH_R9A07G054 is not setCONFIG_ARCH_R9A09G011=yCONFIG_RST_RCAR=yCONFIG_SYSC_RCAR=yCONFIG_SYSC_RCAR_GEN4=yCONFIG_SYSC_R8A77995=yCONFIG_SYSC_R8A7794=yCONFIG_SYSC_R8A77990=y
# CONFIG_SYSC_R8A7779 is not setCONFIG_SYSC_R8A7790=yCONFIG_SYSC_R8A7795=yCONFIG_SYSC_R8A7791=yCONFIG_SYSC_R8A77965=yCONFIG_SYSC_R8A77960=yCONFIG_SYSC_R8A77961=yCONFIG_SYSC_R8A779F0=yCONFIG_SYSC_R8A7792=y
# CONFIG_SYSC_R8A77980 is not set
# CONFIG_SYSC_R8A77970 is not setCONFIG_SYSC_R8A779A0=yCONFIG_SYSC_R8A779G0=y
# CONFIG_SYSC_RMOBILE is not set
# CONFIG_SYSC_R8A77470 is not set
# CONFIG_SYSC_R8A7745 is not setCONFIG_SYSC_R8A7742=y
# CONFIG_SYSC_R8A7743 is not set
# CONFIG_SYSC_R8A774C0 is not setCONFIG_SYSC_R8A774E1=yCONFIG_SYSC_R8A774A1=yCONFIG_SYSC_R8A774B1=yCONFIG_ROCKCHIP_GRF=y
# CONFIG_ROCKCHIP_IODOMAIN is not set
# CONFIG_ROCKCHIP_PM_DOMAINS is not set
# CONFIG_ROCKCHIP_DTPM is not setCONFIG_SOC_SAMSUNG=yCONFIG_EXYNOS_ASV_ARM=yCONFIG_EXYNOS_CHIPID=yCONFIG_EXYNOS_USI=mCONFIG_EXYNOS_PMU=y
# CONFIG_EXYNOS_PMU_ARM_DRIVERS is not setCONFIG_EXYNOS_PM_DOMAINS=y
# CONFIG_EXYNOS_REGULATOR_COUPLER is not setCONFIG_SUNXI_MBUS=yCONFIG_SUNXI_SRAM=yCONFIG_SOC_TEGRA20_VOLTAGE_COUPLER=yCONFIG_SOC_TEGRA30_VOLTAGE_COUPLER=yCONFIG_SOC_TI=yCONFIG_TI_SCI_PM_DOMAINS=yCONFIG_TI_K3_RINGACC=yCONFIG_TI_K3_SOCINFO=y
# CONFIG_TI_PRUSS is not setCONFIG_TI_SCI_INTA_MSI_DOMAIN=y
# CONFIG_UX500_SOC_ID is not set
#
# Xilinx SoC drivers
#
# end of Xilinx SoC drivers # end of SOC (System On Chip) specific Drivers
CONFIG_PM_DEVFREQ=y
#
# DEVFREQ Governors
#CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=yCONFIG_DEVFREQ_GOV_PERFORMANCE=m
# CONFIG_DEVFREQ_GOV_POWERSAVE is not setCONFIG_DEVFREQ_GOV_USERSPACE=yCONFIG_DEVFREQ_GOV_PASSIVE=y
#
# DEVFREQ Drivers
#CONFIG_ARM_EXYNOS_BUS_DEVFREQ=mCONFIG_ARM_IMX_BUS_DEVFREQ=yCONFIG_ARM_IMX8M_DDRC_DEVFREQ=yCONFIG_ARM_TEGRA_DEVFREQ=y
# CONFIG_ARM_MEDIATEK_CCI_DEVFREQ is not setCONFIG_ARM_RK3399_DMC_DEVFREQ=m
# CONFIG_ARM_SUN8I_A33_MBUS_DEVFREQ is not setCONFIG_PM_DEVFREQ_EVENT=yCONFIG_DEVFREQ_EVENT_EXYNOS_NOCP=yCONFIG_DEVFREQ_EVENT_EXYNOS_PPMU=yCONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI=mCONFIG_EXTCON=y
#
# Extcon Device Drivers
#CONFIG_EXTCON_ADC_JACK=mCONFIG_EXTCON_FSA9480=yCONFIG_EXTCON_GPIO=m
# CONFIG_EXTCON_MAX3355 is not setCONFIG_EXTCON_MAX77693=y
# CONFIG_EXTCON_MAX8997 is not setCONFIG_EXTCON_PTN5150=mCONFIG_EXTCON_QCOM_SPMI_MISC=mCONFIG_EXTCON_RT8973A=m
# CONFIG_EXTCON_SM5502 is not set
# CONFIG_EXTCON_USB_GPIO is not setCONFIG_MEMORY=yCONFIG_DDR=yCONFIG_ARM_PL172_MPMC=y
# CONFIG_ATMEL_SDRAMC is not set
# CONFIG_ATMEL_EBI is not setCONFIG_BRCMSTB_DPFE=yCONFIG_BRCMSTB_MEMC=m
# CONFIG_BT1_L2_CTL is not set
# CONFIG_TI_AEMIF is not setCONFIG_TI_EMIF=yCONFIG_OMAP_GPMC=yCONFIG_OMAP_GPMC_DEBUG=yCONFIG_MVEBU_DEVBUS=yCONFIG_FSL_CORENET_CF=y
# CONFIG_FSL_IFC is not set
# CONFIG_JZ4780_NEMC is not setCONFIG_MTK_SMI=yCONFIG_DA8XX_DDRCTL=yCONFIG_PL353_SMC=mCONFIG_RENESAS_RPCIF=mCONFIG_STM32_FMC2_EBI=mCONFIG_SAMSUNG_MC=yCONFIG_EXYNOS5422_DMC=y
# CONFIG_EXYNOS_SROM is not setCONFIG_TEGRA_MC=yCONFIG_TEGRA20_EMC=yCONFIG_TEGRA30_EMC=yCONFIG_TEGRA124_EMC=yCONFIG_TEGRA210_EMC_TABLE=yCONFIG_TEGRA210_EMC=mCONFIG_IIO=yCONFIG_IIO_BUFFER=yCONFIG_IIO_BUFFER_CB=yCONFIG_IIO_BUFFER_DMA=yCONFIG_IIO_BUFFER_DMAENGINE=mCONFIG_IIO_BUFFER_HW_CONSUMER=yCONFIG_IIO_KFIFO_BUF=yCONFIG_IIO_TRIGGERED_BUFFER=yCONFIG_IIO_CONFIGFS=yCONFIG_IIO_TRIGGER=yCONFIG_IIO_CONSUMERS_PER_TRIGGER=2
# CONFIG_IIO_SW_DEVICE is not setCONFIG_IIO_SW_TRIGGER=yCONFIG_IIO_TRIGGERED_EVENT=m
#
# Accelerometers
#CONFIG_ADIS16201=yCONFIG_ADIS16209=yCONFIG_ADXL313=y
# CONFIG_ADXL313_I2C is not setCONFIG_ADXL313_SPI=yCONFIG_ADXL345=yCONFIG_ADXL345_I2C=mCONFIG_ADXL345_SPI=yCONFIG_ADXL355=yCONFIG_ADXL355_I2C=yCONFIG_ADXL355_SPI=mCONFIG_ADXL367=yCONFIG_ADXL367_SPI=yCONFIG_ADXL367_I2C=yCONFIG_ADXL372=yCONFIG_ADXL372_SPI=yCONFIG_ADXL372_I2C=yCONFIG_BMA180=y
# CONFIG_BMA220 is not setCONFIG_BMA400=mCONFIG_BMA400_I2C=mCONFIG_BMA400_SPI=mCONFIG_BMC150_ACCEL=yCONFIG_BMC150_ACCEL_I2C=yCONFIG_BMC150_ACCEL_SPI=yCONFIG_BMI088_ACCEL=yCONFIG_BMI088_ACCEL_SPI=yCONFIG_DA280=mCONFIG_DA311=m
# CONFIG_DMARD06 is not setCONFIG_DMARD09=y
# CONFIG_DMARD10 is not setCONFIG_FXLS8962AF=m
# CONFIG_FXLS8962AF_I2C is not setCONFIG_FXLS8962AF_SPI=mCONFIG_IIO_ST_ACCEL_3AXIS=mCONFIG_IIO_ST_ACCEL_I2C_3AXIS=mCONFIG_IIO_ST_ACCEL_SPI_3AXIS=mCONFIG_KXSD9=mCONFIG_KXSD9_SPI=m
# CONFIG_KXSD9_I2C is not setCONFIG_KXCJK1013=yCONFIG_MC3230=mCONFIG_MMA7455=mCONFIG_MMA7455_I2C=mCONFIG_MMA7455_SPI=mCONFIG_MMA7660=m
# CONFIG_MMA8452 is not setCONFIG_MMA9551_CORE=m
# CONFIG_MMA9551 is not setCONFIG_MMA9553=mCONFIG_MSA311=m
# CONFIG_MXC4005 is not setCONFIG_MXC6255=yCONFIG_SCA3000=m
# CONFIG_SCA3300 is not set
# CONFIG_STK8312 is not setCONFIG_STK8BA50=m
# end of Accelerometers
#
# Analog to digital converters
#CONFIG_AD_SIGMA_DELTA=yCONFIG_AD7091R5=y
# CONFIG_AD7124 is not set
# CONFIG_AD7192 is not setCONFIG_AD7266=yCONFIG_AD7280=mCONFIG_AD7291=mCONFIG_AD7292=yCONFIG_AD7298=mCONFIG_AD7476=yCONFIG_AD7606=mCONFIG_AD7606_IFACE_PARALLEL=mCONFIG_AD7606_IFACE_SPI=mCONFIG_AD7766=m
# CONFIG_AD7768_1 is not setCONFIG_AD7780=yCONFIG_AD7791=mCONFIG_AD7793=yCONFIG_AD7887=mCONFIG_AD7923=mCONFIG_AD7949=yCONFIG_AD799X=y
# CONFIG_ADI_AXI_ADC is not setCONFIG_ASPEED_ADC=yCONFIG_AT91_ADC=yCONFIG_AT91_SAMA5D2_ADC=m
# CONFIG_AXP20X_ADC is not set
# CONFIG_AXP288_ADC is not setCONFIG_BCM_IPROC_ADC=m
# CONFIG_BERLIN2_ADC is not setCONFIG_CC10001_ADC=yCONFIG_DA9150_GPADC=mCONFIG_ENVELOPE_DETECTOR=yCONFIG_EXYNOS_ADC=m
# CONFIG_MXS_LRADC_ADC is not setCONFIG_FSL_MX25_ADC=m
# CONFIG_HI8435 is not set
# CONFIG_HX711 is not set
# CONFIG_INA2XX_ADC is not setCONFIG_INGENIC_ADC=y
# CONFIG_IMX7D_ADC is not setCONFIG_IMX8QXP_ADC=y
# CONFIG_LP8788_ADC is not setCONFIG_LPC18XX_ADC=yCONFIG_LPC32XX_ADC=mCONFIG_LTC2471=mCONFIG_LTC2485=y
# CONFIG_LTC2496 is not setCONFIG_LTC2497=y
# CONFIG_MAX1027 is not setCONFIG_MAX11100=m
# CONFIG_MAX1118 is not set
# CONFIG_MAX11205 is not setCONFIG_MAX1241=m
# CONFIG_MAX1363 is not setCONFIG_MAX9611=yCONFIG_MCP320X=yCONFIG_MCP3422=mCONFIG_MCP3911=mCONFIG_MEDIATEK_MT6360_ADC=mCONFIG_MEDIATEK_MT6577_AUXADC=mCONFIG_MEN_Z188_ADC=y
# CONFIG_MESON_SARADC is not set
# CONFIG_MP2629_ADC is not setCONFIG_NAU7802=yCONFIG_NPCM_ADC=yCONFIG_QCOM_VADC_COMMON=m
# CONFIG_QCOM_PM8XXX_XOADC is not set
# CONFIG_QCOM_SPMI_IADC is not setCONFIG_QCOM_SPMI_VADC=mCONFIG_QCOM_SPMI_ADC5=mCONFIG_RCAR_GYRO_ADC=mCONFIG_ROCKCHIP_SARADC=m
# CONFIG_RICHTEK_RTQ6056 is not setCONFIG_RZG2L_ADC=m
# CONFIG_SC27XX_ADC is not set
# CONFIG_SPEAR_ADC is not set
# CONFIG_SD_ADC_MODULATOR is not setCONFIG_STM32_ADC_CORE=yCONFIG_STM32_ADC=mCONFIG_STM32_DFSDM_CORE=m
# CONFIG_STM32_DFSDM_ADC is not setCONFIG_STMPE_ADC=mCONFIG_SUN4I_GPADC=mCONFIG_TI_ADC081C=m
# CONFIG_TI_ADC0832 is not setCONFIG_TI_ADC084S021=yCONFIG_TI_ADC12138=yCONFIG_TI_ADC108S102=y
# CONFIG_TI_ADC128S052 is not set
# CONFIG_TI_ADC161S626 is not setCONFIG_TI_ADS1015=yCONFIG_TI_ADS7950=y
# CONFIG_TI_ADS8344 is not setCONFIG_TI_ADS8688=yCONFIG_TI_ADS124S08=mCONFIG_TI_ADS131E08=yCONFIG_TI_TLC4541=yCONFIG_TI_TSC2046=yCONFIG_TWL4030_MADC=mCONFIG_TWL6030_GPADC=yCONFIG_VF610_ADC=yCONFIG_XILINX_XADC=mCONFIG_XILINX_AMS=y
# end of Analog to digital converters
#
# Analog to digital and digital to analog converters #CONFIG_AD74413R=y
# end of Analog to digital and digital to analog converters
#
# Analog Front Ends
#
# CONFIG_IIO_RESCALE is not set
# end of Analog Front Ends
#
# Amplifiers
#CONFIG_AD8366=mCONFIG_ADA4250=yCONFIG_HMC425=y
# end of Amplifiers
#
# Capacitance to digital converters
#CONFIG_AD7150=m
# CONFIG_AD7746 is not set
# end of Capacitance to digital converters
#
# Chemical Sensors
#
# CONFIG_ATLAS_PH_SENSOR is not set
# CONFIG_ATLAS_EZO_SENSOR is not set
# CONFIG_BME680 is not set
# CONFIG_CCS811 is not setCONFIG_IAQCORE=yCONFIG_PMS7003=m
# CONFIG_SCD30_CORE is not setCONFIG_SCD4X=mCONFIG_SENSIRION_SGP30=mCONFIG_SENSIRION_SGP40=mCONFIG_SPS30=mCONFIG_SPS30_I2C=mCONFIG_SPS30_SERIAL=m
# CONFIG_SENSEAIR_SUNRISE_CO2 is not setCONFIG_VZ89X=y
# end of Chemical Sensors
#
# Hid Sensor IIO Common
#
# end of Hid Sensor IIO Common
CONFIG_IIO_MS_SENSORS_I2C=y
#
# IIO SCMI Sensors
#
# CONFIG_IIO_SCMI is not set
# end of IIO SCMI Sensors
#
# SSP Sensor Common
#CONFIG_IIO_SSP_SENSORS_COMMONS=mCONFIG_IIO_SSP_SENSORHUB=m
# end of SSP Sensor Common
CONFIG_IIO_ST_SENSORS_I2C=mCONFIG_IIO_ST_SENSORS_SPI=mCONFIG_IIO_ST_SENSORS_CORE=m
#
# Digital to analog converters
#CONFIG_AD3552R=m
# CONFIG_AD5064 is not setCONFIG_AD5360=yCONFIG_AD5380=yCONFIG_AD5421=m
# CONFIG_AD5446 is not set
# CONFIG_AD5449 is not setCONFIG_AD5592R_BASE=yCONFIG_AD5592R=yCONFIG_AD5593R=m
# CONFIG_AD5504 is not setCONFIG_AD5624R_SPI=m
# CONFIG_LTC2688 is not setCONFIG_AD5686=m
# CONFIG_AD5686_SPI is not setCONFIG_AD5696_I2C=m
# CONFIG_AD5755 is not set
# CONFIG_AD5758 is not setCONFIG_AD5761=y
# CONFIG_AD5764 is not set
# CONFIG_AD5766 is not setCONFIG_AD5770R=mCONFIG_AD5791=mCONFIG_AD7293=mCONFIG_AD7303=y
# CONFIG_AD8801 is not set
# CONFIG_DPOT_DAC is not set
# CONFIG_DS4424 is not set
# CONFIG_LPC18XX_DAC is not setCONFIG_LTC1660=y
# CONFIG_LTC2632 is not setCONFIG_M62332=mCONFIG_MAX517=mCONFIG_MAX5821=mCONFIG_MCP4725=y
# CONFIG_MCP4922 is not setCONFIG_STM32_DAC=mCONFIG_STM32_DAC_CORE=m
# CONFIG_TI_DAC082S085 is not setCONFIG_TI_DAC5571=mCONFIG_TI_DAC7311=yCONFIG_TI_DAC7612=yCONFIG_VF610_DAC=y
# end of Digital to analog converters
#
# IIO dummy driver
#
# end of IIO dummy driver
#
# Filters
#CONFIG_ADMV8818=m
# end of Filters
#
# Frequency Synthesizers DDS/PLL
#
#
# Clock Generator/Distribution
#
# CONFIG_AD9523 is not set
# end of Clock Generator/Distribution
#
# Phase-Locked Loop (PLL) frequency synthesizers
#CONFIG_ADF4350=mCONFIG_ADF4371=yCONFIG_ADMV1013=m
# CONFIG_ADMV1014 is not setCONFIG_ADMV4420=y
# CONFIG_ADRF6780 is not set
# end of Phase-Locked Loop (PLL) frequency synthesizers # end of Frequency Synthesizers DDS/PLL
#
# Digital gyroscope sensors
#CONFIG_ADIS16080=yCONFIG_ADIS16130=mCONFIG_ADIS16136=mCONFIG_ADIS16260=yCONFIG_ADXRS290=yCONFIG_ADXRS450=mCONFIG_BMG160=mCONFIG_BMG160_I2C=mCONFIG_BMG160_SPI=mCONFIG_FXAS21002C=mCONFIG_FXAS21002C_I2C=mCONFIG_FXAS21002C_SPI=mCONFIG_MPU3050=yCONFIG_MPU3050_I2C=yCONFIG_IIO_ST_GYRO_3AXIS=mCONFIG_IIO_ST_GYRO_I2C_3AXIS=m
# CONFIG_IIO_ST_GYRO_SPI_3AXIS is not set
# CONFIG_ITG3200 is not set
# end of Digital gyroscope sensors
#
# Health Sensors
#
#
# Heart Rate Monitors
#CONFIG_AFE4403=mCONFIG_AFE4404=m
# CONFIG_MAX30100 is not setCONFIG_MAX30102=m
# end of Heart Rate Monitors # end of Health Sensors
#
# Humidity sensors
#
# CONFIG_AM2315 is not setCONFIG_DHT11=y
# CONFIG_HDC100X is not setCONFIG_HDC2010=yCONFIG_HTS221=yCONFIG_HTS221_I2C=yCONFIG_HTS221_SPI=y
# CONFIG_HTU21 is not setCONFIG_SI7005=yCONFIG_SI7020=y
# end of Humidity sensors
#
# Inertial measurement units
#
# CONFIG_ADIS16400 is not set
# CONFIG_ADIS16460 is not setCONFIG_ADIS16475=yCONFIG_ADIS16480=yCONFIG_BMI160=yCONFIG_BMI160_I2C=y
# CONFIG_BMI160_SPI is not setCONFIG_BOSCH_BNO055=mCONFIG_BOSCH_BNO055_SERIAL=m
# CONFIG_BOSCH_BNO055_I2C is not setCONFIG_FXOS8700=yCONFIG_FXOS8700_I2C=yCONFIG_FXOS8700_SPI=mCONFIG_KMX61=mCONFIG_INV_ICM42600=mCONFIG_INV_ICM42600_I2C=mCONFIG_INV_ICM42600_SPI=mCONFIG_INV_MPU6050_IIO=yCONFIG_INV_MPU6050_I2C=yCONFIG_INV_MPU6050_SPI=m
# CONFIG_IIO_ST_LSM6DSX is not setCONFIG_IIO_ST_LSM9DS0=mCONFIG_IIO_ST_LSM9DS0_I2C=m
# CONFIG_IIO_ST_LSM9DS0_SPI is not set
# end of Inertial measurement units
CONFIG_IIO_ADIS_LIB=yCONFIG_IIO_ADIS_LIB_BUFFER=y
1,398 lines not shown · raw message
Part of this message is not shown here. View the raw message.
Re: [PATCH 2/9] KVM: arm64: Add helper for creating removed stage2 subtrees
In reply to Ricardo KollerQuoted 24 lines · Ricardo Koller
Add a stage2 helper,
kvm_pgtable_stage2_create_removed(), for creating removed tables (the opposite ofkvm_pgtable_stage2_free_removed()). Creating a removed table is useful for splitting block PTEs into subtrees of 4K PTEs. For example, a 1G block PTE can be split into 4K PTEs by first creating a fully populated tree, and then use it to replace the 1G PTE in a single step. This will be used in a subsequent commit for eager huge-page splitting (a dirty-logging optimization).No functional change intended. This new function will be used in a subsequent commit.
Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_pgtable.h | 25 +++++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 47 ++++++++++++++++++++++++++++ 2 files changed, 72 insertions(+)arch/arm64/include/asm/kvm_pgtable.h +0
-0
arch/arm64/include/asm/kvm_pgtable.h void kvm_pgtable_stage2_destroy(struct kvm_pgtable *pgt); · line 456
Quoted 7 lines
arch/arm64/include/asm/kvm_pgtable.h +4
-0@@ -450,6 +450,31 @@ void kvm_pgtable_stage2_destroy(struct kvm_pgtable *pgt);*/ void kvm_pgtable_stage2_free_removed (struct kvm_pgtable_mm_ops *mm_ops,void *pgtable,u32 level); +/** +* kvm_pgtable_stage2_free_removed() - Create a removed stage-2 paging structure. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @new: Unlinked stage-2 paging structure to be created.
Oh, I see so the "removed" page table is actually a new page table that has never been part of the paging structure. In that case I would find it much more intuitive to call it "unlinked" or similar.
Quoted 85 lines
arch/arm64/include/asm/kvm_pgtable.h +21
-0+* @phys: Physical address of the memory to map. +* @level: Level of the stage-2 paging structure to be created. +* @prot: Permissions and attributes for the mapping. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* Create a removed page-table tree of PAGE_SIZE leaf PTEs under *new. +* This new page-table tree is not reachable (i.e., it is removed) from the +* root pgd and it's therefore unreachableby the hardware page-table +* walker. No TLB invalidation or CMOs are performed. +* +* If device attributes are not explicitly requested in @prot, then the +* mapping will be normal, cacheable. +* +* Return: 0 only if a fully populated tree was created, negative error +* code on failure. No partially-populated table can be returned. +*/ +int kvm_pgtable_stage2_create_removed (struct kvm_pgtable *pgt, +kvm_pte_t *new,u64 phys,u32 level, +enum kvm_pgtable_prot prot,void *mc); +/** * kvm_pgtable_stage2_map() - Install a mapping in a guest stage-2 page-table. * @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). arch/arm64/kvm/hyp/pgtable.c +47
-1@@ -1181,6 +1181,53 @@ int kvm_pgtable_stage2_flush(struct kvm_pgtable *pgt, u64 addr, u64 size)return kvm_pgtable_walk (pgt, addr, size, &walker); } +/* +* map_data->force_pte is true in order to force creating PAGE_SIZE PTEs. +* data->addr is 0 because the IPA is irrelevant for a removed table. +*/ +int kvm_pgtable_stage2_create_removed (struct kvm_pgtable *pgt, +kvm_pte_t *new,u64 phys,u32 level, +enum kvm_pgtable_prot prot,void *mc) +{ +struct stage2_map_data map_data = { + .phys = phys, + .mmu = pgt->mmu, + .memcache = mc, + .force_pte = true, + }; +struct kvm_pgtable_walker walker = { + .cb = stage2_map_walker, + .flags =KVM_PGTABLE_WALK_LEAF | +KVM_PGTABLE_WALK_REMOVED , + .arg = &map_data, + }; +struct kvm_pgtable_walk_data data = { + .walker = &walker, + .addr =0 , + .end =kvm_granule_size (level), + }; +struct kvm_pgtable_mm_ops *mm_ops = pgt->mm_ops; +kvm_pte_t *pgtable; +int ret; + + ret =stage2_set_prot_attr (pgt, prot, &map_data.attr); +if (ret) +return ret; + + pgtable = mm_ops->zalloc_page (mc); +if (!pgtable) +return -ENOMEM ; + + ret =__kvm_pgtable_walk (&data, mm_ops, pgtable, level +1 ); +if (ret) { +kvm_pgtable_stage2_free_removed (mm_ops, pgtable, level); + mm_ops->put_page (pgtable); +return ret; + } + + *new =kvm_init_table_pte (pgtable, mm_ops); +return 0 ; +} int __kvm_pgtable_stage2_init(struct kvm_pgtable *pgt, struct kvm_s2_mmu *mmu, struct kvm_pgtable_mm_ops *mm_ops, --2.39.0.314.g84b9a713c41-goog
Re: [PATCH 2/9] KVM: arm64: Add helper for creating removed stage2 subtrees
Quoted 28 lines · Ben Gardon
Quoted 27 lines · Ricardo Koller
Add a stage2 helper,
kvm_pgtable_stage2_create_removed(), for creating removed tables (the opposite ofkvm_pgtable_stage2_free_removed()). Creating a removed table is useful for splitting block PTEs into subtrees of 4K PTEs. For example, a 1G block PTE can be split into 4K PTEs by first creating a fully populated tree, and then use it to replace the 1G PTE in a single step. This will be used in a subsequent commit for eager huge-page splitting (a dirty-logging optimization).No functional change intended. This new function will be used in a subsequent commit.
Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_pgtable.h | 25 +++++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 47 ++++++++++++++++++++++++++++ 2 files changed, 72 insertions(+)arch/arm64/include/asm/kvm_pgtable.h +0
-0@@ -450,6 +450,31 @@ void kvm_pgtable_stage2_destroy(struct kvm_pgtable *pgt);*/ void kvm_pgtable_stage2_free_removed (struct kvm_pgtable_mm_ops *mm_ops,void *pgtable,u32 level);
Quoted 9 lines
arch/arm64/include/asm/kvm_pgtable.h void kvm_pgtable_stage2_destroy(struct kvm_pgtable *pgt); · line 456
Quoted 4 lines
arch/arm64/include/asm/kvm_pgtable.h +4
-0+/** +* kvm_pgtable_stage2_free_removed() - Create a removed stage-2 paging structure. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @new: Unlinked stage-2 paging structure to be created. Oh, I see so the "removed" page table is actually a new page table that has never been part of the paging structure. In that case I would find it much more intuitive to call it "unlinked" or similar.
Sounds good, I like "unlinked".
Oliver, are you OK if I rename free_removed() as well? just to keep them symmetric.
Quoted 85 lines
Quoted 85 lines
arch/arm64/include/asm/kvm_pgtable.h +21
-0+* @phys: Physical address of the memory to map. +* @level: Level of the stage-2 paging structure to be created. +* @prot: Permissions and attributes for the mapping. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* Create a removed page-table tree of PAGE_SIZE leaf PTEs under *new. +* This new page-table tree is not reachable (i.e., it is removed) from the +* root pgd and it's therefore unreachableby the hardware page-table +* walker. No TLB invalidation or CMOs are performed. +* +* If device attributes are not explicitly requested in @prot, then the +* mapping will be normal, cacheable. +* +* Return: 0 only if a fully populated tree was created, negative error +* code on failure. No partially-populated table can be returned. +*/ +int kvm_pgtable_stage2_create_removed (struct kvm_pgtable *pgt, +kvm_pte_t *new,u64 phys,u32 level, +enum kvm_pgtable_prot prot,void *mc); +/** * kvm_pgtable_stage2_map() - Install a mapping in a guest stage-2 page-table. * @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). arch/arm64/kvm/hyp/pgtable.c +47
-1@@ -1181,6 +1181,53 @@ int kvm_pgtable_stage2_flush(struct kvm_pgtable *pgt, u64 addr, u64 size)return kvm_pgtable_walk (pgt, addr, size, &walker); } +/* +* map_data->force_pte is true in order to force creating PAGE_SIZE PTEs. +* data->addr is 0 because the IPA is irrelevant for a removed table. +*/ +int kvm_pgtable_stage2_create_removed (struct kvm_pgtable *pgt, +kvm_pte_t *new,u64 phys,u32 level, +enum kvm_pgtable_prot prot,void *mc) +{ +struct stage2_map_data map_data = { + .phys = phys, + .mmu = pgt->mmu, + .memcache = mc, + .force_pte = true, + }; +struct kvm_pgtable_walker walker = { + .cb = stage2_map_walker, + .flags =KVM_PGTABLE_WALK_LEAF | +KVM_PGTABLE_WALK_REMOVED , + .arg = &map_data, + }; +struct kvm_pgtable_walk_data data = { + .walker = &walker, + .addr =0 , + .end =kvm_granule_size (level), + }; +struct kvm_pgtable_mm_ops *mm_ops = pgt->mm_ops; +kvm_pte_t *pgtable; +int ret; + + ret =stage2_set_prot_attr (pgt, prot, &map_data.attr); +if (ret) +return ret; + + pgtable = mm_ops->zalloc_page (mc); +if (!pgtable) +return -ENOMEM ; + + ret =__kvm_pgtable_walk (&data, mm_ops, pgtable, level +1 ); +if (ret) { +kvm_pgtable_stage2_free_removed (mm_ops, pgtable, level); + mm_ops->put_page (pgtable); +return ret; + } + + *new =kvm_init_table_pte (pgtable, mm_ops); +return 0 ; +} int __kvm_pgtable_stage2_init(struct kvm_pgtable *pgt, struct kvm_s2_mmu *mmu, struct kvm_pgtable_mm_ops *mm_ops, --2.39.0.314.g84b9a713c41-goog
Re: [PATCH 2/9] KVM: arm64: Add helper for creating removed stage2 subtrees
Quoted 1 line · Ricardo Koller
On Mon, Jan 23, 2023 at 04:55:40PM -0800, Ben Gardon wrote:
[...]
Quoted 10 lines
Quoted 9 lines
Quoted 4 lines
+/**
+ *kvm_pgtable_stage2_free_removed()- Create a removed stage-2 paging structure.
+ * @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*().
+ * @new: Unlinked stage-2 paging structure to be created.Oh, I see so the "removed" page table is actually a new page table that has never been part of the paging structure. In that case I would find it much more intuitive to call it "unlinked" or similar.
Quoted 4 lines
Sounds good, I like "unlinked".
Oliver, are you OK if I rename
free_removed()as well? just to keep them symmetric.
Fine by me, and sorry for the silly naming :)
--
Thanks,
Oliver
PATCH 3/9 KVM: arm64: Add kvm_pgtable_stage2_split()
In reply to Ricardo KollerAdd a new stage2 function, kvm_pgtable_stage2_split(), for splitting a range of huge pages. This will be used for eager-splitting huge pages into PAGE_SIZE pages. The goal is to avoid having to split huge pages on write-protection faults, and instead use this function to do it ahead of time for large ranges (e.g., all guest memory in 1G chunks at a time).
No functional change intended. This new function will be used in a subsequent commit.
--- arch/arm64/include/asm/kvm_pgtable.h | 29 ++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 67 ++++++++++++++++++++++++++++ 2 files changed, 96 insertions(+)
arch/arm64/include/asm/kvm_pgtable.h +29 -0
@@ -644,6 +644,35 @@ bool kvm_pgtable_stage2_is_young(struct kvm_pgtable *pgt, u64 addr);*/ int kvm_pgtable_stage2_flush (struct kvm_pgtable *pgt,u64 addr,u64 size); +/** +* kvm_pgtable_stage2_split() - Split a range of huge pages into leaf PTEs pointing +* to PAGE_SIZE guest pages. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @addr: Intermediate physical address from which to split. +* @size: Size of the range. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* @addr and the end (@addr + @size) are effectively aligned down and up to +* the top level huge-page block size. This is an exampe using 1GB +* huge-pages and 4KB granules. +* +* [---input range---] +* : : +* [--1G block pte--][--1G block pte--][--1G block pte--][--1G block pte--] +* : : +* [--2MB--][--2MB--][--2MB--][--2MB--] +* : : +* [ ][ ][:][ ][ ][ ][ ][ ][:][ ][ ][ ] +* : : +* +* Return: 0 on success, negative error code on failure. Note that +* kvm_pgtable_stage2_split() is best effort: it tries to break as many +* blocks in the input range as allowed by the size of the memcache. It +* will fail it wasn't able to break any block. +*/ +int kvm_pgtable_stage2_split (struct kvm_pgtable *pgt,u64 addr,u64 size,void *mc); +/** * kvm_pgtable_walk() - Walk a page-table. * @pgt: Page-table structure initialised by kvm_pgtable_*_init().
arch/arm64/kvm/hyp/pgtable.c +67 -0
73 lines not on this page · raw message
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
Quoted 26 lines · Ricardo Koller
Add a new stage2 function,
kvm_pgtable_stage2_split(), for splitting a range of huge pages. This will be used for eager-splitting huge pages intoPAGE_SIZEpages. The goal is to avoid having to split huge pages on write-protection faults, and instead use this function to do it ahead of time for large ranges (e.g., all guest memory in 1G chunks at a time).No functional change intended. This new function will be used in a subsequent commit.
Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_pgtable.h | 29 ++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 67 ++++++++++++++++++++++++++++ 2 files changed, 96 insertions(+)arch/arm64/include/asm/kvm_pgtable.h +1
-0@@ -644,6 +644,35 @@ bool kvm_pgtable_stage2_is_young(struct kvm_pgtable *pgt, u64 addr);*/ int kvm_pgtable_stage2_flush (struct kvm_pgtable *pgt,u64 addr,u64 size); +/**
arch/arm64/include/asm/kvm_pgtable.h bool kvm_pgtable_stage2_is_young(struct kvm_pgtable *pgt, u64 addr); · line 657
Quoted 10 lines
arch/arm64/include/asm/kvm_pgtable.h +10
-0+* kvm_pgtable_stage2_split() - Split a range of huge pages into leaf PTEs pointing +* to PAGE_SIZE guest pages. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @addr: Intermediate physical address from which to split. +* @size: Size of the range. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* @addr and the end (@addr + @size) are effectively aligned down and up to +* the top level huge-page block size. This is an exampe using 1GB
Nit: example
Quoted 37 lines
arch/arm64/include/asm/kvm_pgtable.h +18
-0+* huge-pages and 4KB granules. +* +* [---input range---] +* : : +* [--1G block pte--][--1G block pte--][--1G block pte--][--1G block pte--] +* : : +* [--2MB--][--2MB--][--2MB--][--2MB--] +* : : +* [ ][ ][:][ ][ ][ ][ ][ ][:][ ][ ][ ] +* : : +* +* Return: 0 on success, negative error code on failure. Note that +* kvm_pgtable_stage2_split() is best effort: it tries to break as many +* blocks in the input range as allowed by the size of the memcache. It +* will fail it wasn't able to break any block. +*/ +int kvm_pgtable_stage2_split (struct kvm_pgtable *pgt,u64 addr,u64 size,void *mc); +/** * kvm_pgtable_walk() - Walk a page-table. * @pgt: Page-table structure initialised by kvm_pgtable_*_init(). arch/arm64/kvm/hyp/pgtable.c +8
-0@@ -1229,6 +1229,73 @@ int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt,return 0 ; } +struct stage2_split_data { +struct kvm_s2_mmu *mmu; +void *memcache; +}; + +static int stage2_split_walker (const struct kvm_pgtable_visit_ctx *ctx, +enum kvm_pgtable_walk_flags visit) +{
arch/arm64/kvm/hyp/pgtable.c int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt, · line 1249
Quoted 10 lines
arch/arm64/kvm/hyp/pgtable.c +10
-0+struct stage2_split_data *data = ctx->arg; +struct kvm_pgtable_mm_ops *mm_ops = ctx->mm_ops; +kvm_pte_t pte = ctx->old, new, *childp; +enum kvm_pgtable_prot prot; +void *mc = data->memcache; +u32 level = ctx->level; +u64 phys; +int ret; + +/* Nothing to split at the last level */
Would it be accurate to say:
/* No huge pages can exist at the root level, so there's nothing to split here. */
I think of "last level" as the lowest/leaf/4k level but KVM_PGTABLE_MAX_LEVELS - 1 is 3? Does ARM do the level numbering in reverse order to x86?
Quoted 3 lines
arch/arm64/kvm/hyp/pgtable.c +3
-0+if (level ==KVM_PGTABLE_MAX_LEVELS -1 ) +return 0 ; +
...
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
Quoted 92 lines · Ben Gardon
Quoted 26 lines · Ricardo Koller
Add a new stage2 function,
kvm_pgtable_stage2_split(), for splitting a range of huge pages. This will be used for eager-splitting huge pages intoPAGE_SIZEpages. The goal is to avoid having to split huge pages on write-protection faults, and instead use this function to do it ahead of time for large ranges (e.g., all guest memory in 1G chunks at a time).No functional change intended. This new function will be used in a subsequent commit.
Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_pgtable.h | 29 ++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 67 ++++++++++++++++++++++++++++ 2 files changed, 96 insertions(+)arch/arm64/include/asm/kvm_pgtable.h +1
-0@@ -644,6 +644,35 @@ bool kvm_pgtable_stage2_is_young(struct kvm_pgtable *pgt, u64 addr);*/ int kvm_pgtable_stage2_flush (struct kvm_pgtable *pgt,u64 addr,u64 size); +/** arch/arm64/include/asm/kvm_pgtable.h bool kvm_pgtable_stage2_is_young(struct kvm_pgtable *pgt, u64 addr); · line 657
Quoted 10 lines
arch/arm64/include/asm/kvm_pgtable.h +10
-0+* kvm_pgtable_stage2_split() - Split a range of huge pages into leaf PTEs pointing +* to PAGE_SIZE guest pages. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @addr: Intermediate physical address from which to split. +* @size: Size of the range. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* @addr and the end (@addr + @size) are effectively aligned down and up to +* the top level huge-page block size. This is an exampe using 1GB Nit: example
Quoted 37 lines
arch/arm64/include/asm/kvm_pgtable.h +18
-0+* huge-pages and 4KB granules. +* +* [---input range---] +* : : +* [--1G block pte--][--1G block pte--][--1G block pte--][--1G block pte--] +* : : +* [--2MB--][--2MB--][--2MB--][--2MB--] +* : : +* [ ][ ][:][ ][ ][ ][ ][ ][:][ ][ ][ ] +* : : +* +* Return: 0 on success, negative error code on failure. Note that +* kvm_pgtable_stage2_split() is best effort: it tries to break as many +* blocks in the input range as allowed by the size of the memcache. It +* will fail it wasn't able to break any block. +*/ +int kvm_pgtable_stage2_split (struct kvm_pgtable *pgt,u64 addr,u64 size,void *mc); +/** * kvm_pgtable_walk() - Walk a page-table. * @pgt: Page-table structure initialised by kvm_pgtable_*_init(). arch/arm64/kvm/hyp/pgtable.c +8
-0@@ -1229,6 +1229,73 @@ int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt,return 0 ; } +struct stage2_split_data { +struct kvm_s2_mmu *mmu; +void *memcache; +}; + +static int stage2_split_walker (const struct kvm_pgtable_visit_ctx *ctx, +enum kvm_pgtable_walk_flags visit) +{arch/arm64/kvm/hyp/pgtable.c int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt, · line 1249
Quoted 10 lines
arch/arm64/kvm/hyp/pgtable.c +10
-0+struct stage2_split_data *data = ctx->arg; +struct kvm_pgtable_mm_ops *mm_ops = ctx->mm_ops; +kvm_pte_t pte = ctx->old, new, *childp; +enum kvm_pgtable_prot prot; +void *mc = data->memcache; +u32 level = ctx->level; +u64 phys; +int ret; + +/* Nothing to split at the last level */ Would it be accurate to say:
/* No huge pages can exist at the root level, so there's nothing to split here. */
Quoted 2 lines
I think of "last level" as the lowest/leaf/4k level but
KVM_PGTABLE_MAX_LEVELS- 1 is 3?
Right, this is the 4k level.
Quoted 2 lines
Does ARM do the level numbering in
reverse order to x86?
Yes, it does. Interesting, x86 does
iter->level--;
while arm does:
ret = __kvm_pgtable_walk(data, mm_ops, childp, level + 1);
I don't think this numbering scheme is encoded anywhere in the PTEs, so either architecture could use the other.
Quoted 5 lines
Quoted 4 lines
arch/arm64/kvm/hyp/pgtable.c +3
-0+if (level ==KVM_PGTABLE_MAX_LEVELS -1 ) +return 0 ; +...
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
Quoted 1 line · Ricardo Koller
On Mon, Jan 23, 2023 at 05:03:23PM -0800, Ben Gardon wrote:
[...]
Quoted 14 lines
Quoted 6 lines
Would it be accurate to say:
/* No huge pages can exist at the root level, so there's nothing to split here. */I think of "last level" as the lowest/leaf/4k level but
KVM_PGTABLE_MAX_LEVELS- 1 is 3?Right, this is the 4k level.
Quoted 2 lines
Does ARM do the level numbering in
reverse order to x86?Yes, it does. Interesting, x86 does
Quoted 8 lines
iter->level--;while arm does:
ret = __kvm_pgtable_walk(data, mm_ops, childp, level + 1);I don't think this numbering scheme is encoded anywhere in the PTEs, so either architecture could use the other.
The numbering we use in the page table walkers is deliberate, as it directly matches the Arm ARM. While we can certainly use either scheme I'd prefer we keep aligned with the architecture.
--
Thanks,
Oliver
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
Quoted 24 lines · Oliver Upton
Quoted 1 line · Ricardo Koller
On Mon, Jan 23, 2023 at 05:03:23PM -0800, Ben Gardon wrote:
[...]
Quoted 18 lines
Quoted 6 lines
Would it be accurate to say:
/* No huge pages can exist at the root level, so there's nothing to split here. */I think of "last level" as the lowest/leaf/4k level but
KVM_PGTABLE_MAX_LEVELS- 1 is 3?Right, this is the 4k level.
Quoted 2 lines
Does ARM do the level numbering in
reverse order to x86?Yes, it does. Interesting, x86 does
iter->level--;while arm does:
Quoted 8 lines
Quoted 4 lines
ret = __kvm_pgtable_walk(data, mm_ops, childp, level + 1);I don't think this numbering scheme is encoded anywhere in the PTEs, so either architecture could use the other.
The numbering we use in the page table walkers is deliberate, as it directly matches the Arm ARM. While we can certainly use either scheme I'd prefer we keep aligned with the architecture.
hehe, I was actually subtly suggesting our x86 friends to change their side.
Quoted 4 lines
--
Thanks,
Oliver
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
Quoted 27 lines · Ricardo Koller
Quoted 26 lines · Oliver Upton
Quoted 1 line · Ricardo Koller
On Mon, Jan 23, 2023 at 05:03:23PM -0800, Ben Gardon wrote:
[...]
Quoted 20 lines
Quoted 6 lines
Would it be accurate to say:
/* No huge pages can exist at the root level, so there's nothing to split here. */I think of "last level" as the lowest/leaf/4k level but
KVM_PGTABLE_MAX_LEVELS- 1 is 3?Right, this is the 4k level.
Quoted 2 lines
Does ARM do the level numbering in
reverse order to x86?Yes, it does. Interesting, x86 does
iter->level--;while arm does:
ret = __kvm_pgtable_walk(data, mm_ops, childp, level + 1);
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
I don't think this numbering scheme is encoded anywhere in the PTEs, so either architecture could use the other.
The numbering we use in the page table walkers is deliberate, as it directly matches the Arm ARM. While we can certainly use either scheme I'd prefer we keep aligned with the architecture.
hehe, I was actually subtly suggesting our x86 friends to change their side.
Yeah KVM/x86 and KVM/ARM use basically opposite numbering schemes for page table levels.
Level | KVM/ARM | KVM/x86
----- | ------- | ---------------
pte | 3 | 1 (PG_LEVEL_4K)
pmd | 2 | 2 (PG_LEVEL_2M)
pud | 1 | 3 (PG_LEVEL_1G)
p4d | 0 | 4
| -1 | 5The ARM levels come from the architecture, whereas the x86 levels are arbitrary.
I do think it would be valuable to standardize on one leveling scheme at some point. Otherwise, mixing level schemes is bound to be a source of bugs if and when we are sharing more MMU code across architectures.
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
Quoted 2 lines · David Matlack
Quoted 1 line · Ricardo Koller
On Tue, Jan 24, 2023 at 9:11 AM Oliver Upton <[email protected]> wrote:
[...]
Quoted 17 lines
Quoted 5 lines
Quoted 3 lines
The numbering we use in the page table walkers is deliberate, as it directly matches the Arm ARM. While we can certainly use either scheme I'd prefer we keep aligned with the architecture.
hehe, I was actually subtly suggesting our x86 friends to change their side.
Yeah KVM/x86 and KVM/ARM use basically opposite numbering schemes for page table levels.
Level | KVM/ARM | KVM/x86 ----- | ------- | --------------- pte | 3 | 1 (PG_LEVEL_4K) pmd | 2 | 2 (PG_LEVEL_2M) pud | 1 | 3 (PG_LEVEL_1G) p4d | 0 | 4 | -1 | 5
Quoted 6 lines
The ARM levels come from the architecture, whereas the x86 levels are arbitrary.
I do think it would be valuable to standardize on one leveling scheme at some point. Otherwise, mixing level schemes is bound to be a source of bugs if and when we are sharing more MMU code across architectures.
That could work, so long as the respective ISAs don't depend on any specific numbering scheme. For arm64 the level hints encoded in TLBIs match our numbering scheme, which is quite valuable. We are definitely at odds with RISC-V's numbering scheme (descending order, starting from root), but AFAICT there doesn't appear to be any portion of the ISA that depends on it (yet).
Sure, we could add some glue code to transform KVM's common leveling scheme into an architecture-specific one for these use cases, but I worry that'll be incredibly error-prone.
In any case I'd prefer we not make any changes at this point, as they'd be purely cosmetic.
--
Thanks,
Oliver
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
In reply to Ricardo KollerHi, Ricardo
Quoted 79 lines · Ricardo Koller
Add a new stage2 function,
kvm_pgtable_stage2_split(), for splitting a range of huge pages. This will be used for eager-splitting huge pages intoPAGE_SIZEpages. The goal is to avoid having to split huge pages on write-protection faults, and instead use this function to do it ahead of time for large ranges (e.g., all guest memory in 1G chunks at a time).No functional change intended. This new function will be used in a subsequent commit.
Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_pgtable.h | 29 ++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 67 ++++++++++++++++++++++++++++ 2 files changed, 96 insertions(+)arch/arm64/include/asm/kvm_pgtable.h +29
-0@@ -644,6 +644,35 @@ bool kvm_pgtable_stage2_is_young(struct kvm_pgtable *pgt, u64 addr);*/ int kvm_pgtable_stage2_flush (struct kvm_pgtable *pgt,u64 addr,u64 size); +/** +* kvm_pgtable_stage2_split() - Split a range of huge pages into leaf PTEs pointing +* to PAGE_SIZE guest pages. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @addr: Intermediate physical address from which to split. +* @size: Size of the range. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* @addr and the end (@addr + @size) are effectively aligned down and up to +* the top level huge-page block size. This is an exampe using 1GB +* huge-pages and 4KB granules. +* +* [---input range---] +* : : +* [--1G block pte--][--1G block pte--][--1G block pte--][--1G block pte--] +* : : +* [--2MB--][--2MB--][--2MB--][--2MB--] +* : : +* [ ][ ][:][ ][ ][ ][ ][ ][:][ ][ ][ ] +* : : +* +* Return: 0 on success, negative error code on failure. Note that +* kvm_pgtable_stage2_split() is best effort: it tries to break as many +* blocks in the input range as allowed by the size of the memcache. It +* will fail it wasn't able to break any block. +*/ +int kvm_pgtable_stage2_split (struct kvm_pgtable *pgt,u64 addr,u64 size,void *mc); +/** * kvm_pgtable_walk() - Walk a page-table. * @pgt: Page-table structure initialised by kvm_pgtable_*_init(). arch/arm64/kvm/hyp/pgtable.c +15
-0@@ -1229,6 +1229,73 @@ int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt,return 0 ; } +struct stage2_split_data { +struct kvm_s2_mmu *mmu; +void *memcache; +}; + +static int stage2_split_walker (const struct kvm_pgtable_visit_ctx *ctx, +enum kvm_pgtable_walk_flags visit) +{ +struct stage2_split_data *data = ctx->arg; +struct kvm_pgtable_mm_ops *mm_ops = ctx->mm_ops; +kvm_pte_t pte = ctx->old, new, *childp; +enum kvm_pgtable_prot prot; +void *mc = data->memcache; +u32 level = ctx->level; +u64 phys;
arch/arm64/kvm/hyp/pgtable.c int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt, · line 1256
Quoted 10 lines
arch/arm64/kvm/hyp/pgtable.c +10
-0+int ret; + +/* Nothing to split at the last level */ +if (level ==KVM_PGTABLE_MAX_LEVELS -1 ) +return 0 ; + +/* We only split valid block mappings */ +if (!kvm_pte_valid (pte) ||kvm_pte_table (pte, ctx->level)) +return 0 ; +
IIUC, It should be !kvm_pte_table(pte, ctx->level)?
also, the kvm_pte_table includes the level check and kvm_pte_valid, so, it just be like:
- /* Nothing to split at the last level */
- if (level == KVM_PGTABLE_MAX_LEVELS - 1)
- return 0;
-
- /* We only split valid block mappings */
+ if (!kvm_pte_table(pte, ctx->level))
+ return 0;
Quoted 46 lines
arch/arm64/kvm/hyp/pgtable.c +42
-0+ phys =kvm_pte_to_phys (pte); + prot =kvm_pgtable_stage2_pte_prot (pte); + + ret =kvm_pgtable_stage2_create_removed (data->mmu->pgt, &new, phys, + level, prot, mc); +if (ret) +return ret; + +if (!stage2_try_break_pte (ctx, data->mmu)) { + childp =kvm_pte_follow (new, mm_ops); +kvm_pgtable_stage2_free_removed (mm_ops, childp, level); + mm_ops->put_page (childp); +return -EAGAIN ; + } + +/* +* Note, the contents of the page table are guaranteed to be +* made visible before the new PTE is assigned because +* stage2_make_pte() writes the PTE using smp_store_release(). +*/ +stage2_make_pte (ctx, new); +dsb (ishst); +return 0 ; +} + +int kvm_pgtable_stage2_split (struct kvm_pgtable *pgt, +u64 addr,u64 size,void *mc) +{ +struct stage2_split_data split_data = { + .mmu = pgt->mmu, + .memcache = mc, + }; + +struct kvm_pgtable_walker walker = { + .cb = stage2_split_walker, + .flags =KVM_PGTABLE_WALK_LEAF , + .arg = &split_data, + }; + +return kvm_pgtable_walk (pgt, addr, size, &walker); +} + int __kvm_pgtable_stage2_init(struct kvm_pgtable *pgt, struct kvm_s2_mmu *mmu, struct kvm_pgtable_mm_ops *mm_ops, enum kvm_pgtable_stage2_flags flags,
Signature · 2 lines
Regards. Chuan
Re: [PATCH 3/9] KVM: arm64: Add kvm_pgtable_stage2_split()
Hi Zheng,
Quoted 86 lines · Zheng Chuan
Hi, Ricardo
Quoted 82 lines · Ricardo Koller
Add a new stage2 function,
kvm_pgtable_stage2_split(), for splitting a range of huge pages. This will be used for eager-splitting huge pages intoPAGE_SIZEpages. The goal is to avoid having to split huge pages on write-protection faults, and instead use this function to do it ahead of time for large ranges (e.g., all guest memory in 1G chunks at a time).No functional change intended. This new function will be used in a subsequent commit.
Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_pgtable.h | 29 ++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 67 ++++++++++++++++++++++++++++ 2 files changed, 96 insertions(+)arch/arm64/include/asm/kvm_pgtable.h +29
-0@@ -644,6 +644,35 @@ bool kvm_pgtable_stage2_is_young(struct kvm_pgtable *pgt, u64 addr);*/ int kvm_pgtable_stage2_flush (struct kvm_pgtable *pgt,u64 addr,u64 size); +/** +* kvm_pgtable_stage2_split() - Split a range of huge pages into leaf PTEs pointing +* to PAGE_SIZE guest pages. +* @pgt: Page-table structure initialised by kvm_pgtable_stage2_init*(). +* @addr: Intermediate physical address from which to split. +* @size: Size of the range. +* @mc: Cache of pre-allocated and zeroed memory from which to allocate +* page-table pages. +* +* @addr and the end (@addr + @size) are effectively aligned down and up to +* the top level huge-page block size. This is an exampe using 1GB +* huge-pages and 4KB granules. +* +* [---input range---] +* : : +* [--1G block pte--][--1G block pte--][--1G block pte--][--1G block pte--] +* : : +* [--2MB--][--2MB--][--2MB--][--2MB--] +* : : +* [ ][ ][:][ ][ ][ ][ ][ ][:][ ][ ][ ] +* : : +* +* Return: 0 on success, negative error code on failure. Note that +* kvm_pgtable_stage2_split() is best effort: it tries to break as many +* blocks in the input range as allowed by the size of the memcache. It +* will fail it wasn't able to break any block. +*/ +int kvm_pgtable_stage2_split (struct kvm_pgtable *pgt,u64 addr,u64 size,void *mc); +/** * kvm_pgtable_walk() - Walk a page-table. * @pgt: Page-table structure initialised by kvm_pgtable_*_init(). arch/arm64/kvm/hyp/pgtable.c +18
-0@@ -1229,6 +1229,73 @@ int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt,return 0 ; } +struct stage2_split_data { +struct kvm_s2_mmu *mmu; +void *memcache; +}; + +static int stage2_split_walker (const struct kvm_pgtable_visit_ctx *ctx, +enum kvm_pgtable_walk_flags visit) +{ +struct stage2_split_data *data = ctx->arg; +struct kvm_pgtable_mm_ops *mm_ops = ctx->mm_ops; +kvm_pte_t pte = ctx->old, new, *childp; +enum kvm_pgtable_prot prot; +void *mc = data->memcache; +u32 level = ctx->level; +u64 phys; +int ret; + +/* Nothing to split at the last level */
Quoted 8 lines
arch/arm64/kvm/hyp/pgtable.c int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt, · line 1256
Quoted 7 lines
arch/arm64/kvm/hyp/pgtable.c +7
-0+if (level ==KVM_PGTABLE_MAX_LEVELS -1 ) +return 0 ; + +/* We only split valid block mappings */ +if (!kvm_pte_valid (pte) ||kvm_pte_table (pte, ctx->level)) +return 0 ; +IIUC, It should be !kvm_pte_table(pte,
ctx->level)?
It's the other way around; if the current PTE is a table then there's nothing to split
(it's already a table), and we leave early.
Review
Quoted 8 lines
also, the
kvm_pte_tableincludes the level check andkvm_pte_valid, so, it just be like:(quoted diff) +2
-5- /* Nothing to split at the last level */ - if (level == KVM_PGTABLE_MAX_LEVELS - 1) - return 0; - - /* We only split valid block mappings */ + if (!kvm_pte_table(pte, ctx->level)) + return 0;
Still need the kvm_pte_valid() check because !kvm_pte_table() does not imply that the pte is valid. Same with the level check.
Thanks for taking a look at the patch,
Ricardo
Quoted 52 lines
Quoted 37 lines
arch/arm64/kvm/hyp/pgtable.c +35
-0+ phys =kvm_pte_to_phys (pte); + prot =kvm_pgtable_stage2_pte_prot (pte); + + ret =kvm_pgtable_stage2_create_removed (data->mmu->pgt, &new, phys, + level, prot, mc); +if (ret) +return ret; + +if (!stage2_try_break_pte (ctx, data->mmu)) { + childp =kvm_pte_follow (new, mm_ops); +kvm_pgtable_stage2_free_removed (mm_ops, childp, level); + mm_ops->put_page (childp); +return -EAGAIN ; + } + +/* +* Note, the contents of the page table are guaranteed to be +* made visible before the new PTE is assigned because +* stage2_make_pte() writes the PTE using smp_store_release(). +*/ +stage2_make_pte (ctx, new); +dsb (ishst); +return 0 ; +} + +int kvm_pgtable_stage2_split (struct kvm_pgtable *pgt, +u64 addr,u64 size,void *mc) +{ +struct stage2_split_data split_data = { + .mmu = pgt->mmu, + .memcache = mc, + }; + +struct kvm_pgtable_walker walker = { + .cb = stage2_split_walker,arch/arm64/kvm/hyp/pgtable.c int kvm_pgtable_stage2_create_removed(struct kvm_pgtable *pgt, · line 1301
Quoted 10 lines
arch/arm64/kvm/hyp/pgtable.c +7
-0+ .flags = KVM_PGTABLE_WALK_LEAF, + .arg = &split_data, + }; + +return kvm_pgtable_walk (pgt, addr, size, &walker); +} + int __kvm_pgtable_stage2_init(struct kvm_pgtable *pgt, struct kvm_s2_mmu *mmu, struct kvm_pgtable_mm_ops *mm_ops, enum kvm_pgtable_stage2_flags flags,--
Regards.
Chuan
PATCH 4/9 KVM: arm64: Refactor kvm_arch_commit_memory_region()
In reply to Ricardo KollerRefactor kvm_arch_commit_memory_region() as a preparation for a future commit to look cleaner and more understandable. Also, it looks more like its x86 counterpart (in kvm_mmu_slot_apply_flags()).
No functional change intended.
--- arch/arm64/kvm/mmu.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-)
arch/arm64/kvm/mmu.c +11 -4
@@ -1758,20 +1758,27 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,const struct kvm_memory_slot *new, enum kvm_mr_change change) { + bool log_dirty_pages = new && new->flags & KVM_MEM_LOG_DIRTY_PAGES; +/* * At this point memslot has been committed and there is an * allocated dirty_bitmap[], dirty pages will be tracked while the * memory slot is write protected. */ -if (change !=KVM_MR_DELETE && new->flags &KVM_MEM_LOG_DIRTY_PAGES ) { +if (log_dirty_pages) { + +if (change ==KVM_MR_DELETE ) +return ; +/* * If we're with initial-all-set, we don't need to write * protect any pages because they're all reported as dirty. * Huge pages and normal pages will be write protect gradually. */ -if (!kvm_dirty_log_manual_protect_and_init_set (kvm)) { -kvm_mmu_wp_memory_region (kvm, new->id); - } +if (kvm_dirty_log_manual_protect_and_init_set (kvm)) +return ; + +kvm_mmu_wp_memory_region (kvm, new->id); } }
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
PATCH 5/9 KVM: arm64: Add kvm_uninit_stage2_mmu()
In reply to Ricardo KollerAdd kvm_uninit_stage2_mmu() and move kvm_free_stage2_pgd() into it. A future commit will add some more things to do inside of kvm_uninit_stage2_mmu().
No functional change intended.
--- arch/arm64/include/asm/kvm_mmu.h | 1 + arch/arm64/kvm/mmu.c | 7 ++++++- 2 files changed, 7 insertions(+), 1 deletion(-)
arch/arm64/include/asm/kvm_mmu.h +1 -0
@@ -167,6 +167,7 @@ void free_hyp_pgds(void);void stage2_unmap_vm (struct kvm *kvm);int kvm_init_stage2_mmu (struct kvm *kvm,struct kvm_s2_mmu *mmu,unsigned long type); +void kvm_uninit_stage2_mmu (struct kvm *kvm);void kvm_free_stage2_pgd (struct kvm_s2_mmu *mmu);int kvm_phys_addr_ioremap (struct kvm *kvm,phys_addr_t guest_ipa,phys_addr_t pa,unsigned long size,bool writable);
arch/arm64/kvm/mmu.c +6 -1
@@ -766,6 +766,11 @@ int kvm_init_stage2_mmu(struct kvm *kvm, struct kvm_s2_mmu *mmu, unsigned long treturn err; } +void kvm_uninit_stage2_mmu (struct kvm *kvm) +{ +kvm_free_stage2_pgd (&kvm->arch.mmu); +} +static void stage2_unmap_memslot (struct kvm *kvm,struct kvm_memory_slot *memslot) {
@@ -1852,7 +1857,7 @@ void kvm_arch_memslots_updated(struct kvm *kvm, u64 gen)void kvm_arch_flush_shadow_all (struct kvm *kvm) { -kvm_free_stage2_pgd (&kvm->arch.mmu); +kvm_uninit_stage2_mmu (kvm); } void kvm_arch_flush_shadow_memslot(struct kvm *kvm,
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
PATCH 6/9 KVM: arm64: Split huge pages when dirty logging is enabled
In reply to Ricardo KollerSplit huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the mmu_lock and give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.
The benefits of eager page splitting are the same as in x86, added with commit a3fe5dbda0a4 ("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when running dirty_log_perf_test with 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.
--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)
arch/arm64/include/asm/kvm_host.h +30 -0
@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran; +/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge +* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB). +* +* CACHE_CAPACITY should have enough pages to cover CHUNK_SIZE; for +* example, 1GB requires the following number of PAGE_SIZE-pages: +* - 512 when using 2MB hugepages with 4KB granules (1GB / 2MB). +* - 513 when using 1GB hugepages with 4KB granules (1 + (1GB / 2MB)). +* - 32 when using 32MB hugepages with 16KB granule (1GB / 32MB). +* - 2 when using 512MB hugepages with 64KB granules (1GB / 512MB). +* CACHE_CAPACITY below assumes the worst case: 1GB hugepages with 4KB +* granules. +* +* Protected by kvm->slots_lock. +*/ +#define EAGER_PAGE_SPLIT_CHUNK_SIZE SZ_1G +#define EAGER_PAGE_SPLIT_CACHE_CAPACITY \ + (DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_1G) + \ + DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_2M)) +struct kvm_mmu_memory_cache split_page_cache; +struct kvm_arch *arch; };
arch/arm64/kvm/mmu.c +108 -2
153 lines not on this page · raw message
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 37 lines · Ricardo Koller
Split huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the
mmu_lockand give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.The benefits of eager page splitting are the same as in x86, added with commit
a3fe5dbda0a4("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when runningdirty_log_perf_testwith 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)arch/arm64/include/asm/kvm_host.h +2
-0@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran; +/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge
arch/arm64/include/asm/kvm_host.h struct kvm_s2_mmu { · line 167
Quoted 10 lines
arch/arm64/include/asm/kvm_host.h +10
-0+* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB).
This feels a little fragile to link scheduling decisions into the batch size. (I'm not saying we don't do the same thing on x86, but it's a mistake in either case.) I'd prefer if we could yield more granularly in a way that's not tied to splitting a whole EAGER_PAGE_SPLIT_CHUNK_SIZE worth of pages.
Tuning the chunk size to balance memory overhead with batch performance makes sense, but it becomes more difficult to also balance with the needs of the scheduler. Could we add some yield point in kvm_pgtable_stage2_split or give it an early return path or something?
Quoted 187 lines
arch/arm64/include/asm/kvm_host.h +18
-0+* +* CACHE_CAPACITY should have enough pages to cover CHUNK_SIZE; for +* example, 1GB requires the following number of PAGE_SIZE-pages: +* - 512 when using 2MB hugepages with 4KB granules (1GB / 2MB). +* - 513 when using 1GB hugepages with 4KB granules (1 + (1GB / 2MB)). +* - 32 when using 32MB hugepages with 16KB granule (1GB / 32MB). +* - 2 when using 512MB hugepages with 64KB granules (1GB / 512MB). +* CACHE_CAPACITY below assumes the worst case: 1GB hugepages with 4KB +* granules. +* +* Protected by kvm->slots_lock. +*/ +#define EAGER_PAGE_SPLIT_CHUNK_SIZE SZ_1G +#define EAGER_PAGE_SPLIT_CACHE_CAPACITY \ + (DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_1G) + \ + DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_2M)) +struct kvm_mmu_memory_cache split_page_cache; +struct kvm_arch *arch; };arch/arm64/kvm/mmu.c +108
-3@@ -31,14 +31,24 @@ static phys_addr_t hyp_idmap_vector;static unsigned long io_map_base; -static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +bool __read_mostly eager_page_split = true; +module_param (eager_page_split, bool,0644 ); + +static phys_addr_t __stage2_range_addr_end (phys_addr_t addr,phys_addr_t end, +phys_addr_t size) { -phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL );phys_addr_t boundary =ALIGN_DOWN (addr + size, size);return (boundary -1 < end -1 ) ? boundary : end; } +static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +{ +phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL ); + +return __stage2_range_addr_end (addr, end, size); +} +/* * Release kvm_mmu_lock periodically if the memory region is large. Otherwise, * we may see kernel panics with CONFIG_DETECT_HUNG_TASK, @@ -71,6 +81,64 @@ static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr,return ret; } +static inline bool need_topup (struct kvm_mmu_memory_cache *cache,int min) +{ +return kvm_mmu_memory_cache_nr_free_objects (cache) < min; +} + +static bool need_topup_split_page_cache_or_resched (struct kvm *kvm) +{ +struct kvm_mmu_memory_cache *cache; + +if (need_resched () ||rwlock_needbreak (&kvm->mmu_lock)) +return true; + + cache = &kvm->arch.mmu.split_page_cache; +return need_topup (cache,EAGER_PAGE_SPLIT_CACHE_CAPACITY ); +} + +static int kvm_mmu_split_huge_pages (struct kvm *kvm,phys_addr_t addr, +phys_addr_t end) +{ +struct kvm_mmu_memory_cache *cache; +struct kvm_pgtable *pgt; +int ret; +u64 next; +int cache_capacity =EAGER_PAGE_SPLIT_CACHE_CAPACITY ; + +lockdep_assert_held_write (&kvm->mmu_lock); + +lockdep_assert_held (&kvm->slots_lock); + + cache = &kvm->arch.mmu.split_page_cache; + +do { +if (need_topup_split_page_cache_or_resched (kvm)) { +write_unlock (&kvm->mmu_lock); +cond_resched (); +/* Eager page splitting is best-effort. */ + ret =__kvm_mmu_topup_memory_cache (cache, + cache_capacity, + cache_capacity); +write_lock (&kvm->mmu_lock); +if (ret) +break ; + } + + pgt = kvm->arch.mmu.pgt; +if (!pgt) +return -EINVAL ; + + next =__stage2_range_addr_end (addr, end, +EAGER_PAGE_SPLIT_CHUNK_SIZE ); + ret =kvm_pgtable_stage2_split (pgt, addr, next - addr, cache); +if (ret) +break ; + }while (addr = next, addr != end); + +return ret; +} +#define stage2_apply_range_resched (kvm, addr, end, fn) \ stage2_apply_range(kvm, addr, end, fn, true)@@ -755,6 +823,8 @@ int kvm_init_stage2_mmu(struct kvm *kvm, struct kvm_s2_mmu *mmu, unsigned long tfor_each_possible_cpu (cpu) *per_cpu_ptr (mmu->last_vcpu_ran, cpu) =-1 ; + mmu->split_page_cache.gfp_zero = __GFP_ZERO; + mmu->pgt = pgt; mmu->pgd_phys =__pa (pgt->pgd);return 0 ;@@ -769,6 +839,7 @@ int kvm_init_stage2_mmu(struct kvm *kvm, struct kvm_s2_mmu *mmu, unsigned long tvoid kvm_uninit_stage2_mmu (struct kvm *kvm) {kvm_free_stage2_pgd (&kvm->arch.mmu); +kvm_mmu_free_memory_cache (&kvm->arch.mmu.split_page_cache); } static void stage2_unmap_memslot(struct kvm *kvm,@@ -996,6 +1067,29 @@ static void kvm_mmu_write_protect_pt_masked(struct kvm *kvm,stage2_wp_range (&kvm->arch.mmu, start, end); } +/** +* kvm_mmu_split_memory_region() - split the stage 2 blocks into PAGE_SIZE +* pages for memory slot +* @kvm: The KVM pointer +* @slot: The memory slot to split +* +* Acquires kvm->mmu_lock. Called with kvm->slots_lock mutex acquired, +* serializing operations for VM memory regions. +*/ +static void kvm_mmu_split_memory_region (struct kvm *kvm,int slot) +{ +struct kvm_memslots *slots =kvm_memslots (kvm); +struct kvm_memory_slot *memslot =id_to_memslot (slots, slot); +phys_addr_t start, end; + + start = memslot->base_gfn <<PAGE_SHIFT ; + end = (memslot->base_gfn + memslot->npages) <<PAGE_SHIFT ; + +write_lock (&kvm->mmu_lock); +kvm_mmu_split_huge_pages (kvm, start, end); +write_unlock (&kvm->mmu_lock); +} +/* * kvm_arch_mmu_enable_log_dirty_pt_masked - enable dirty logging for selected * dirty pages. @@ -1783,7 +1877,19 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,if (kvm_dirty_log_manual_protect_and_init_set (kvm))return ; +if (READ_ONCE (eager_page_split)) +kvm_mmu_split_memory_region (kvm, new->id); +kvm_mmu_wp_memory_region (kvm, new->id); + }else { +/* +* Free any leftovers from the eager page splitting cache. Do +* this when deleting, moving, disabling dirty logging, or +* creating the memslot (a nop). Doing it for deletes makes +* sure we don't leak memory, and there's no need to keep the +* cache around for any of the other cases. +*/ +kvm_mmu_free_memory_cache (&kvm->arch.mmu.split_page_cache); } } --2.39.0.314.g84b9a713c41-goog
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 36 lines · Ben Gardon
Quoted 35 lines · Ricardo Koller
Split huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the
mmu_lockand give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.The benefits of eager page splitting are the same as in x86, added with commit
a3fe5dbda0a4("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when runningdirty_log_perf_testwith 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)arch/arm64/include/asm/kvm_host.h +0
-0@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran;
Quoted 15 lines
arch/arm64/include/asm/kvm_host.h struct kvm_s2_mmu { · line 167
Quoted 12 lines
arch/arm64/include/asm/kvm_host.h +12
-0+/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge +* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB). This feels a little fragile to link scheduling decisions into the batch size.
Completely agree.
Quoted 8 lines
(I'm not saying we don't do the same thing on x86, but
it's a mistake in either case.) I'd prefer if we could yield more granularly in a way that's not tied to splitting a wholeEAGER_PAGE_SPLIT_CHUNK_SIZEworth of pages.
Tuning the chunk size to balance memory overhead with batch performance makes sense, but it becomes more difficult to also balance with the needs of the scheduler. Could we add some yield point inkvm_pgtable_stage2_splitor give it an early return path or something?
We definitely need to move in the direction of early returns, but I'd rather not build it purely for the sake of eager page spliting. A better approach would likely be to add it to the core page table walker code such that all walkers that operate on a swath of memory can use it.
In the interest of keeping this series manageable, I'd prefer yielding walkers be done in a separate series.
--
Thanks,
Oliver
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
In reply to Ricardo KollerHi Ricardo,
Quoted 52 lines · Ricardo Koller
Split huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the
mmu_lockand give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.The benefits of eager page splitting are the same as in x86, added with commit
a3fe5dbda0a4("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when runningdirty_log_perf_testwith 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)arch/arm64/include/asm/kvm_host.h +18
-0@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran; +/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge +* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB). +* +* CACHE_CAPACITY should have enough pages to cover CHUNK_SIZE; for +* example, 1GB requires the following number of PAGE_SIZE-pages: +* - 512 when using 2MB hugepages with 4KB granules (1GB / 2MB). +* - 513 when using 1GB hugepages with 4KB granules (1 + (1GB / 2MB)). +* - 32 when using 32MB hugepages with 16KB granule (1GB / 32MB).
arch/arm64/include/asm/kvm_host.h struct kvm_s2_mmu { · line 183
Quoted 10 lines
arch/arm64/include/asm/kvm_host.h +10
-0+* - 2 when using 512MB hugepages with 64KB granules (1GB / 512MB). +* CACHE_CAPACITY below assumes the worst case: 1GB hugepages with 4KB +* granules. +* +* Protected by kvm->slots_lock. +*/ +#define EAGER_PAGE_SPLIT_CHUNK_SIZE SZ_1G +#define EAGER_PAGE_SPLIT_CACHE_CAPACITY \ + (DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_1G) + \ + DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_2M))
Could you instead make use of the existing KVM_PGTABLE_MIN_BLOCK_LEVEL as the batch size? 513 pages across all page sizes is a non-negligible amount of memory that goes largely unused when PAGE_SIZE != 4K.
With that change it is a lot easier to correctly match the cache capacity to the selected page size. Additionally, we continue to have a single set of batching logic that we can improve later on.
Quoted 10 lines
arch/arm64/include/asm/kvm_host.h +2
-0+struct kvm_mmu_memory_cache split_page_cache; +struct kvm_arch *arch; };arch/arm64/kvm/mmu.c +0
-0
arch/arm64/kvm/mmu.c static phys_addr_t hyp_idmap_vector; · line 36
Quoted 7 lines
arch/arm64/kvm/mmu.c +3
-1@@ -31,14 +31,24 @@ static phys_addr_t hyp_idmap_vector;static unsigned long io_map_base; -static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +bool __read_mostly eager_page_split = true; +module_param (eager_page_split, bool,0644 ); +
Unless someone is really begging for it I'd prefer we not add a module parameter for this.
Quoted 20 lines
arch/arm64/kvm/mmu.c +9
-1+static phys_addr_t __stage2_range_addr_end (phys_addr_t addr,phys_addr_t end, +phys_addr_t size) { -phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL );phys_addr_t boundary =ALIGN_DOWN (addr + size, size);return (boundary -1 < end -1 ) ? boundary : end; } +static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +{ +phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL ); + +return __stage2_range_addr_end (addr, end, size); +} +/* * Release kvm_mmu_lock periodically if the memory region is large. Otherwise, * we may see kernel panics with CONFIG_DETECT_HUNG_TASK,
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 87
Quoted 7 lines
arch/arm64/kvm/mmu.c +4
-0@@ -71,6 +81,64 @@ static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr,return ret; } +static inline bool need_topup (struct kvm_mmu_memory_cache *cache,int min) +{ +return kvm_mmu_memory_cache_nr_free_objects (cache) < min; +}
I don't think the helper is adding too much here.
Quoted 11 lines
arch/arm64/kvm/mmu.c +11
-0+static bool need_topup_split_page_cache_or_resched (struct kvm *kvm) +{ +struct kvm_mmu_memory_cache *cache; + +if (need_resched () ||rwlock_needbreak (&kvm->mmu_lock)) +return true; + + cache = &kvm->arch.mmu.split_page_cache; +return need_topup (cache,EAGER_PAGE_SPLIT_CACHE_CAPACITY ); +} +
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 109
Quoted 10 lines
arch/arm64/kvm/mmu.c +10
-0+static int kvm_mmu_split_huge_pages (struct kvm *kvm,phys_addr_t addr, +phys_addr_t end) +{ +struct kvm_mmu_memory_cache *cache; +struct kvm_pgtable *pgt; +int ret; +u64 next; +int cache_capacity =EAGER_PAGE_SPLIT_CACHE_CAPACITY ; + +lockdep_assert_held_write (&kvm->mmu_lock);
Rather than having the caller acquire the lock, can you instead do it here? It would appear that the entire critical section is enclosed within this function.
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 111
Quoted 1 line
arch/arm64/kvm/mmu.c +1
-0+lockdep_assert_held (&kvm->slots_lock);
This function doesn't depend on anything guarded by the slots_lock, can you move this to kvm_mmu_split_memory_region()?
Quoted 18 lines
arch/arm64/kvm/mmu.c +18
-0+ cache = &kvm->arch.mmu.split_page_cache; + + do { + if (need_topup_split_page_cache_or_resched(kvm)) { + write_unlock(&kvm->mmu_lock); + cond_resched(); + /* Eager page splitting is best-effort. */ + ret = __kvm_mmu_topup_memory_cache(cache, + cache_capacity, + cache_capacity); + write_lock(&kvm->mmu_lock); + if (ret) + break; + } + + pgt = kvm->arch.mmu.pgt; + if (!pgt) + return -EINVAL;
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 140
Quoted 10 lines
arch/arm64/kvm/mmu.c +10
-0+ + next =__stage2_range_addr_end (addr, end, +EAGER_PAGE_SPLIT_CHUNK_SIZE ); + ret =kvm_pgtable_stage2_split (pgt, addr, next - addr, cache); +if (ret) +break ; + }while (addr = next, addr != end); + +return ret; +}
--
Thanks,
Oliver
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 62 lines · Oliver Upton
Hi Ricardo,
Quoted 58 lines · Ricardo Koller
Split huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the
mmu_lockand give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.The benefits of eager page splitting are the same as in x86, added with commit
a3fe5dbda0a4("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when runningdirty_log_perf_testwith 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)arch/arm64/include/asm/kvm_host.h +24
-0@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran; +/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge +* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB). +* +* CACHE_CAPACITY should have enough pages to cover CHUNK_SIZE; for +* example, 1GB requires the following number of PAGE_SIZE-pages: +* - 512 when using 2MB hugepages with 4KB granules (1GB / 2MB). +* - 513 when using 1GB hugepages with 4KB granules (1 + (1GB / 2MB)). +* - 32 when using 32MB hugepages with 16KB granule (1GB / 32MB). +* - 2 when using 512MB hugepages with 64KB granules (1GB / 512MB). +* CACHE_CAPACITY below assumes the worst case: 1GB hugepages with 4KB +* granules. +* +* Protected by kvm->slots_lock. +*/
Quoted 9 lines
arch/arm64/include/asm/kvm_host.h struct kvm_s2_mmu { · line 183
Quoted 4 lines
arch/arm64/include/asm/kvm_host.h +4
-0+#define EAGER_PAGE_SPLIT_CHUNK_SIZE SZ_1G +#define EAGER_PAGE_SPLIT_CACHE_CAPACITY \ + (DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_1G) + \ + DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_2M))Could you instead make use of the existing
KVM_PGTABLE_MIN_BLOCK_LEVELas the batch size? 513 pages across all page sizes is a non-negligible amount of memory that goes largely unused whenPAGE_SIZE!= 4K.
Sounds good, will refine this for v2.
Quoted 17 lines
With that change it is a lot easier to correctly match the cache capacity to the selected page size. Additionally, we continue to have a single set of batching logic that we can improve later on.
Quoted 13 lines
arch/arm64/include/asm/kvm_host.h +2
-0+struct kvm_mmu_memory_cache split_page_cache; +struct kvm_arch *arch; };arch/arm64/kvm/mmu.c +0
-0@@ -31,14 +31,24 @@ static phys_addr_t hyp_idmap_vector;static unsigned long io_map_base;
Quoted 7 lines
arch/arm64/kvm/mmu.c static phys_addr_t hyp_idmap_vector; · line 36
Quoted 4 lines
arch/arm64/kvm/mmu.c +3
-1-static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +bool __read_mostly eager_page_split = true; +module_param (eager_page_split, bool,0644 ); +Unless someone is really begging for it I'd prefer we not add a module parameter for this.
It was mainly to match x86 and because it makes perf testing a bit simpler. What do others think?
Quoted 24 lines
Quoted 24 lines
arch/arm64/kvm/mmu.c +9
-1+static phys_addr_t __stage2_range_addr_end (phys_addr_t addr,phys_addr_t end, +phys_addr_t size) { -phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL );phys_addr_t boundary =ALIGN_DOWN (addr + size, size);return (boundary -1 < end -1 ) ? boundary : end; } +static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +{ +phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL ); + +return __stage2_range_addr_end (addr, end, size); +} +/* * Release kvm_mmu_lock periodically if the memory region is large. Otherwise, * we may see kernel panics with CONFIG_DETECT_HUNG_TASK, @@ -71,6 +81,64 @@ static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr,return ret; }
Quoted 6 lines
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 87
Quoted 4 lines
arch/arm64/kvm/mmu.c +4
-0+static inline bool need_topup (struct kvm_mmu_memory_cache *cache,int min) +{ +return kvm_mmu_memory_cache_nr_free_objects (cache) < min; +}I don't think the helper is adding too much here.
Will try how it looks without.
Quoted 18 lines
Quoted 18 lines
arch/arm64/kvm/mmu.c +17
-0+static bool need_topup_split_page_cache_or_resched (struct kvm *kvm) +{ +struct kvm_mmu_memory_cache *cache; + +if (need_resched () ||rwlock_needbreak (&kvm->mmu_lock)) +return true; + + cache = &kvm->arch.mmu.split_page_cache; +return need_topup (cache,EAGER_PAGE_SPLIT_CACHE_CAPACITY ); +} + +static int kvm_mmu_split_huge_pages (struct kvm *kvm,phys_addr_t addr, +phys_addr_t end) +{ +struct kvm_mmu_memory_cache *cache; +struct kvm_pgtable *pgt; +int ret;
Quoted 8 lines
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 109
Quoted 4 lines
arch/arm64/kvm/mmu.c +4
-0+u64 next; +int cache_capacity =EAGER_PAGE_SPLIT_CACHE_CAPACITY ; + +lockdep_assert_held_write (&kvm->mmu_lock);Rather than having the caller acquire the lock, can you instead do it here? It would appear that the entire critical section is enclosed within this function.
Sure. I will first double check things related to perf and correctness just in case.
I'm not sure if the increase of acquire/releases makes any difference in perf. Also, not sure if there's a correctness issue because of releasing the lock between WP and split (I think it should be fine, but not 100% sure).
Quoted 5 lines
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 111
Quoted 2 lines
arch/arm64/kvm/mmu.c +1
-0+lockdep_assert_held (&kvm->slots_lock);This function doesn't depend on anything guarded by the
slots_lock, can you move this tokvm_mmu_split_memory_region()?
kvm_mmu_split_memory_region() takes a memslot.
That works in this case, eager splitting when enabling dirty logging, but won't work in the next commit when spliting on the CLEAR ioctl.
Quoted 33 lines
Quoted 19 lines
arch/arm64/kvm/mmu.c +18
-0+ cache = &kvm->arch.mmu.split_page_cache; + + do { + if (need_topup_split_page_cache_or_resched(kvm)) { + write_unlock(&kvm->mmu_lock); + cond_resched(); + /* Eager page splitting is best-effort. */ + ret = __kvm_mmu_topup_memory_cache(cache, + cache_capacity, + cache_capacity); + write_lock(&kvm->mmu_lock); + if (ret) + break; + } + + pgt = kvm->arch.mmu.pgt; + if (!pgt) + return -EINVAL;arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 140
Quoted 10 lines
arch/arm64/kvm/mmu.c +10
-0+ + next =__stage2_range_addr_end (addr, end, +EAGER_PAGE_SPLIT_CHUNK_SIZE ); + ret =kvm_pgtable_stage2_split (pgt, addr, next - addr, cache); +if (ret) +break ; + }while (addr = next, addr != end); + +return ret; +}--
Thanks,
Oliver
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 171 lines · Ricardo Koller
Quoted 62 lines · Oliver Upton
Hi Ricardo,
Quoted 58 lines · Ricardo Koller
Split huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the
mmu_lockand give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.The benefits of eager page splitting are the same as in x86, added with commit
a3fe5dbda0a4("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when runningdirty_log_perf_testwith 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)arch/arm64/include/asm/kvm_host.h +24
-0@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran; +/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge +* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB). +* +* CACHE_CAPACITY should have enough pages to cover CHUNK_SIZE; for +* example, 1GB requires the following number of PAGE_SIZE-pages: +* - 512 when using 2MB hugepages with 4KB granules (1GB / 2MB). +* - 513 when using 1GB hugepages with 4KB granules (1 + (1GB / 2MB)). +* - 32 when using 32MB hugepages with 16KB granule (1GB / 32MB). +* - 2 when using 512MB hugepages with 64KB granules (1GB / 512MB). +* CACHE_CAPACITY below assumes the worst case: 1GB hugepages with 4KB +* granules. +* +* Protected by kvm->slots_lock. +*/ Quoted 9 lines
arch/arm64/include/asm/kvm_host.h struct kvm_s2_mmu { · line 183
Quoted 4 lines
arch/arm64/include/asm/kvm_host.h +4
-0+#define EAGER_PAGE_SPLIT_CHUNK_SIZE SZ_1G +#define EAGER_PAGE_SPLIT_CACHE_CAPACITY \ + (DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_1G) + \ + DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_2M))Could you instead make use of the existing
KVM_PGTABLE_MIN_BLOCK_LEVELas the batch size? 513 pages across all page sizes is a non-negligible amount of memory that goes largely unused whenPAGE_SIZE!= 4K.Sounds good, will refine this for v2.
Quoted 17 lines
With that change it is a lot easier to correctly match the cache capacity to the selected page size. Additionally, we continue to have a single set of batching logic that we can improve later on.
Quoted 13 lines
arch/arm64/include/asm/kvm_host.h +2
-0+struct kvm_mmu_memory_cache split_page_cache; +struct kvm_arch *arch; };arch/arm64/kvm/mmu.c +0
-0@@ -31,14 +31,24 @@ static phys_addr_t hyp_idmap_vector;static unsigned long io_map_base;Quoted 7 lines
arch/arm64/kvm/mmu.c static phys_addr_t hyp_idmap_vector; · line 36
Quoted 4 lines
arch/arm64/kvm/mmu.c +3
-1-static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +bool __read_mostly eager_page_split = true; +module_param (eager_page_split, bool,0644 ); +Unless someone is really begging for it I'd prefer we not add a module parameter for this.
It was mainly to match x86 and because it makes perf testing a bit simpler. What do others think?
Quoted 24 lines
Quoted 24 lines
arch/arm64/kvm/mmu.c +9
-1+static phys_addr_t __stage2_range_addr_end (phys_addr_t addr,phys_addr_t end, +phys_addr_t size) { -phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL );phys_addr_t boundary =ALIGN_DOWN (addr + size, size);return (boundary -1 < end -1 ) ? boundary : end; } +static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +{ +phys_addr_t size =kvm_granule_size (KVM_PGTABLE_MIN_BLOCK_LEVEL ); + +return __stage2_range_addr_end (addr, end, size); +} +/* * Release kvm_mmu_lock periodically if the memory region is large. Otherwise, * we may see kernel panics with CONFIG_DETECT_HUNG_TASK, @@ -71,6 +81,64 @@ static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr,return ret; }Quoted 6 lines
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 87
Quoted 4 lines
arch/arm64/kvm/mmu.c +4
-0+static inline bool need_topup (struct kvm_mmu_memory_cache *cache,int min) +{ +return kvm_mmu_memory_cache_nr_free_objects (cache) < min; +}I don't think the helper is adding too much here.
Will try how it looks without.
Quoted 18 lines
Quoted 18 lines
arch/arm64/kvm/mmu.c +17
-0+static bool need_topup_split_page_cache_or_resched (struct kvm *kvm) +{ +struct kvm_mmu_memory_cache *cache; + +if (need_resched () ||rwlock_needbreak (&kvm->mmu_lock)) +return true; + + cache = &kvm->arch.mmu.split_page_cache; +return need_topup (cache,EAGER_PAGE_SPLIT_CACHE_CAPACITY ); +} + +static int kvm_mmu_split_huge_pages (struct kvm *kvm,phys_addr_t addr, +phys_addr_t end) +{ +struct kvm_mmu_memory_cache *cache; +struct kvm_pgtable *pgt; +int ret;Quoted 8 lines
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 109
Quoted 4 lines
arch/arm64/kvm/mmu.c +4
-0+u64 next; +int cache_capacity =EAGER_PAGE_SPLIT_CACHE_CAPACITY ; + +lockdep_assert_held_write (&kvm->mmu_lock);Rather than having the caller acquire the lock, can you instead do it here? It would appear that the entire critical section is enclosed within this function.
Sure. I will first double check things related to perf and correctness just in case.
I'm not sure if the increase of acquire/releases makes any difference in perf. Also, not sure if there's a correctness issue because of releasing the lock between WP and split (I think it should be fine, but not 100% sure).Quoted 1 line
Quoted 9 lines
Quoted 4 lines
arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 111
Quoted 1 line
arch/arm64/kvm/mmu.c +1
-0+lockdep_assert_held (&kvm->slots_lock);This function doesn't depend on anything guarded by the
slots_lock, can you move this tokvm_mmu_split_memory_region()?
kvm_mmu_split_memory_region()takes a memslot.
That works in this case, eager splitting when enabling dirty logging, but won't work in the next commit when spliting on the CLEAR ioctl.
Ahh, you meant just the "lockdep" line. Yes, that makes sense. Will do.
Quoted 33 lines
Quoted 33 lines
Quoted 19 lines
arch/arm64/kvm/mmu.c +18
-0+ cache = &kvm->arch.mmu.split_page_cache; + + do { + if (need_topup_split_page_cache_or_resched(kvm)) { + write_unlock(&kvm->mmu_lock); + cond_resched(); + /* Eager page splitting is best-effort. */ + ret = __kvm_mmu_topup_memory_cache(cache, + cache_capacity, + cache_capacity); + write_lock(&kvm->mmu_lock); + if (ret) + break; + } + + pgt = kvm->arch.mmu.pgt; + if (!pgt) + return -EINVAL;arch/arm64/kvm/mmu.c static int stage2_apply_range(struct kvm *kvm, phys_addr_t addr, · line 140
Quoted 10 lines
arch/arm64/kvm/mmu.c +10
-0+ + next =__stage2_range_addr_end (addr, end, +EAGER_PAGE_SPLIT_CHUNK_SIZE ); + ret =kvm_pgtable_stage2_split (pgt, addr, next - addr, cache); +if (ret) +break ; + }while (addr = next, addr != end); + +return ret; +}--
Thanks,
Oliver
Marc Zyngier
maintainerRe: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
In reply to Ricardo KollerQuoted 101 lines · Ricardo Koller
Quoted 62 lines · Oliver Upton
Hi Ricardo,
Quoted 58 lines · Ricardo Koller
Split huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the
mmu_lockand give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.The benefits of eager page splitting are the same as in x86, added with commit
a3fe5dbda0a4("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when runningdirty_log_perf_testwith 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)arch/arm64/include/asm/kvm_host.h +24
-0@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran; +/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge +* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB). +* +* CACHE_CAPACITY should have enough pages to cover CHUNK_SIZE; for +* example, 1GB requires the following number of PAGE_SIZE-pages: +* - 512 when using 2MB hugepages with 4KB granules (1GB / 2MB). +* - 513 when using 1GB hugepages with 4KB granules (1 + (1GB / 2MB)). +* - 32 when using 32MB hugepages with 16KB granule (1GB / 32MB). +* - 2 when using 512MB hugepages with 64KB granules (1GB / 512MB). +* CACHE_CAPACITY below assumes the worst case: 1GB hugepages with 4KB +* granules. +* +* Protected by kvm->slots_lock. +*/ Quoted 9 lines
arch/arm64/include/asm/kvm_host.h struct kvm_s2_mmu { · line 183
Quoted 4 lines
arch/arm64/include/asm/kvm_host.h +4
-0+#define EAGER_PAGE_SPLIT_CHUNK_SIZE SZ_1G +#define EAGER_PAGE_SPLIT_CACHE_CAPACITY \ + (DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_1G) + \ + DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_2M))Could you instead make use of the existing
KVM_PGTABLE_MIN_BLOCK_LEVELas the batch size? 513 pages across all page sizes is a non-negligible amount of memory that goes largely unused whenPAGE_SIZE!= 4K.Sounds good, will refine this for v2.
Quoted 17 lines
With that change it is a lot easier to correctly match the cache capacity to the selected page size. Additionally, we continue to have a single set of batching logic that we can improve later on.
Quoted 13 lines
arch/arm64/include/asm/kvm_host.h +2
-0+struct kvm_mmu_memory_cache split_page_cache; +struct kvm_arch *arch; };arch/arm64/kvm/mmu.c +0
-0@@ -31,14 +31,24 @@ static phys_addr_t hyp_idmap_vector;static unsigned long io_map_base;Quoted 7 lines
arch/arm64/kvm/mmu.c static phys_addr_t hyp_idmap_vector; · line 36
Quoted 4 lines
arch/arm64/kvm/mmu.c +3
-1-static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +bool __read_mostly eager_page_split = true; +module_param (eager_page_split, bool,0644 ); +Unless someone is really begging for it I'd prefer we not add a module parameter for this.
Quoted 2 lines
It was mainly to match x86 and because it makes perf testing a bit simpler. What do others think?
From my PoV this is a no.
If you have a flag because this is an experimental feature (like NV), then this is a kernel option, and you taint the kernel when it is set.
If you have a flag because this is a modal option that makes different use of the HW which cannot be exposed to userspace (like GICv4), then this also is a kernel option.
This is neither.
The one thing that would convince me to make it an option is the amount of memory this thing consumes. 512+ pages is a huge amount, and I'm not overly happy about that. Why can't this be a userspace visible option, selectable on a per VM (or memslot) basis?
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Hi Marc,
Quoted 109 lines · Marc Zyngier
Quoted 101 lines · Ricardo Koller
Quoted 62 lines · Oliver Upton
Hi Ricardo,
Quoted 58 lines · Ricardo Koller
Split huge pages eagerly when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages, which negatively impacts guest performance.
A memslot marked for dirty logging is split in 1GB pieces at a time. This is in order to release the
mmu_lockand give other kernel threads the opportunity to run, and also in order to allocate enough pages to split a 1GB range worth of huge pages (or a single 1GB huge page). Note that these page allocations can fail, so eager page splitting is best-effort. This is not a correctness issue though, as huge pages can still be split on write-faults.The benefits of eager page splitting are the same as in x86, added with commit
a3fe5dbda0a4("KVM: x86/mmu: Split huge pages mapped by the TDP MMU when dirty logging is enabled"). For example, when runningdirty_log_perf_testwith 64 virtual CPUs (Ampere Altra), 1GB per vCPU, 50% reads, and 2MB HugeTLB memory, the time it takes vCPUs to access all of their memory after dirty logging is enabled decreased by 44% from 2.58s to 1.42s.Signed-off-by Ricardo Koller <[email protected]>--- arch/arm64/include/asm/kvm_host.h | 30 ++++++++ arch/arm64/kvm/mmu.c | 110 +++++++++++++++++++++++++++++- 2 files changed, 138 insertions(+), 2 deletions(-)arch/arm64/include/asm/kvm_host.h +24
-0@@ -153,6 +153,36 @@ struct kvm_s2_mmu {/* The last vcpu id that ran on each physical CPU */ int __percpu *last_vcpu_ran; +/* +* Memory cache used to split EAGER_PAGE_SPLIT_CHUNK_SIZE worth of huge +* pages. It is used to allocate stage2 page tables while splitting +* huge pages. Its capacity should be EAGER_PAGE_SPLIT_CACHE_CAPACITY. +* Note that the choice of EAGER_PAGE_SPLIT_CHUNK_SIZE influences both +* the capacity of the split page cache (CACHE_CAPACITY), and how often +* KVM reschedules. Be wary of raising CHUNK_SIZE too high. +* +* A good heuristic to pick CHUNK_SIZE is that it should be larger than +* all the available huge-page sizes, and be a multiple of all the +* other ones; for example, 1GB when all the available huge-page sizes +* are (1GB, 2MB, 32MB, 512MB). +* +* CACHE_CAPACITY should have enough pages to cover CHUNK_SIZE; for +* example, 1GB requires the following number of PAGE_SIZE-pages: +* - 512 when using 2MB hugepages with 4KB granules (1GB / 2MB). +* - 513 when using 1GB hugepages with 4KB granules (1 + (1GB / 2MB)). +* - 32 when using 32MB hugepages with 16KB granule (1GB / 32MB). +* - 2 when using 512MB hugepages with 64KB granules (1GB / 512MB). +* CACHE_CAPACITY below assumes the worst case: 1GB hugepages with 4KB +* granules. +* +* Protected by kvm->slots_lock. +*/ Quoted 9 lines
arch/arm64/include/asm/kvm_host.h struct kvm_s2_mmu { · line 183
Quoted 4 lines
arch/arm64/include/asm/kvm_host.h +4
-0+#define EAGER_PAGE_SPLIT_CHUNK_SIZE SZ_1G +#define EAGER_PAGE_SPLIT_CACHE_CAPACITY \ + (DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_1G) + \ + DIV_ROUND_UP_ULL(EAGER_PAGE_SPLIT_CHUNK_SIZE, SZ_2M))Could you instead make use of the existing
KVM_PGTABLE_MIN_BLOCK_LEVELas the batch size? 513 pages across all page sizes is a non-negligible amount of memory that goes largely unused whenPAGE_SIZE!= 4K.Sounds good, will refine this for v2.
Quoted 17 lines
With that change it is a lot easier to correctly match the cache capacity to the selected page size. Additionally, we continue to have a single set of batching logic that we can improve later on.
Quoted 13 lines
arch/arm64/include/asm/kvm_host.h +2
-0+struct kvm_mmu_memory_cache split_page_cache; +struct kvm_arch *arch; };arch/arm64/kvm/mmu.c +0
-0@@ -31,14 +31,24 @@ static phys_addr_t hyp_idmap_vector;static unsigned long io_map_base;Quoted 7 lines
arch/arm64/kvm/mmu.c static phys_addr_t hyp_idmap_vector; · line 36
Quoted 4 lines
arch/arm64/kvm/mmu.c +3
-1-static phys_addr_t stage2_range_addr_end (phys_addr_t addr,phys_addr_t end) +bool __read_mostly eager_page_split = true; +module_param (eager_page_split, bool,0644 ); +Unless someone is really begging for it I'd prefer we not add a module parameter for this.
Quoted 2 lines
It was mainly to match x86 and because it makes perf testing a bit simpler. What do others think?
From my PoV this is a no.
Quoted 8 lines
If you have a flag because this is an experimental feature (like NV), then this is a kernel option, and you taint the kernel when it is set.
If you have a flag because this is a modal option that makes different use of the HW which cannot be exposed to userspace (like GICv4), then this also is a kernel option.
This is neither.
Ah, I see. Thanks for the explanation.
Quoted 6 lines
The one thing that would convince me to make it an option is the amount of memory this thing consumes. 512+ pages is a huge amount, and I'm not overly happy about that. Why can't this be a userspace visible option, selectable on a per VM (or memslot) basis?
It should be possible. I am exploring a couple of ideas that could help when the hugepages are not 1G (e.g., 2M). However, they add complexity and I'm not sure they help much.
(will be using PAGE_SIZE=4K to make things simpler)
This feature pre-allocates 513 pages before splitting every 1G range. For example, it converts 1G block PTEs into trees made of 513 pages. When not using this feature, the same 513 pages would be allocated, but lazily over a longer period of time.
Eager-splitting pre-allocates those pages in order to split huge-pages into fully populated trees. Which is needed in order to use FEAT_BBM and skipping the expensive TLBI broadcasts. 513 is just the number of pages needed to break a 1G huge-page.
We could optimize for smaller huge-pages, like 2M by splitting 1 huge-page at a time: only preallocate one 4K page at a time. The trick is how to know that we are splitting 2M huge-pages. We could either get the vma pagesize or use hints from userspace. I'm not sure that this is worth it though. The user will most likely want to split big ranges of memory (>1G), so optimizing for smaller huge-pages only converts the left into the right:
alloc 1 page | | alloc 512 pages
split 2M huge-page | | split 2M huge-page
alloc 1 page | | split 2M huge-page
split 2M huge-page | => | split 2M huge-page
...
alloc 1 page | | split 2M huge-page
split 2M huge-page | | split 2M huge-pageStill thinking of what else to do.
Thanks!
Ricardo
Quoted 6 lines
Thanks,
M.--
Without deviation from the norm, progress is not possible.
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 3 lines · Ricardo Koller
Hi Marc,
On Thu, Jan 26, 2023 at 12:10 PM Marc Zyngier <[email protected]> wrote:
[...]
Quoted 39 lines
Quoted 6 lines
The one thing that would convince me to make it an option is the amount of memory this thing consumes. 512+ pages is a huge amount, and I'm not overly happy about that. Why can't this be a userspace visible option, selectable on a per VM (or memslot) basis?
It should be possible. I am exploring a couple of ideas that could help when the hugepages are not 1G (e.g., 2M). However, they add complexity and I'm not sure they help much.
(will be using PAGE_SIZE=4K to make things simpler)
This feature pre-allocates 513 pages before splitting every 1G range. For example, it converts 1G block PTEs into trees made of 513 pages. When not using this feature, the same 513 pages would be allocated, but lazily over a longer period of time.
Eager-splitting pre-allocates those pages in order to split huge-pages into fully populated trees. Which is needed in order to use
FEAT_BBMand skipping the expensive TLBI broadcasts. 513 is just the number of pages needed to break a 1G huge-page.We could optimize for smaller huge-pages, like 2M by splitting 1 huge-page at a time: only preallocate one 4K page at a time. The trick is how to know that we are splitting 2M huge-pages. We could either get the vma pagesize or use hints from userspace. I'm not sure that this is worth it though. The user will most likely want to split big ranges of memory (>1G), so optimizing for smaller huge-pages only converts the left into the right:
alloc 1 page | | alloc 512 pages split 2M huge-page | | split 2M huge-page alloc 1 page | | split 2M huge-page split 2M huge-page | => | split 2M huge-page ... alloc 1 page | | split 2M huge-page split 2M huge-page | | split 2M huge-page
Quoted 1 line
Still thinking of what else to do.
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Signature · 2 lines
Thanks, Oliver
Sean Christopherson
reviewerRe: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 8 lines · Oliver Upton
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Maybe. It's also entirely possible that QoS is never factored in, e.g. if QoS guarantees for all VMs on a system are better met by enabling eager splitting across the board.
There are other reasons to use module/kernel params beyond what Marc listed, e.g. to let the user opt out even when something is on by default. x86's TDP MMU has benefited greatly from downstream users being able to do A/B performance testing this way. I suspect x86's eager_page_split knob was added largely for this reason, e.g. to easily see how a specific workload is affected by eager splitting. That seems like a reasonable fit on the ARM side as well.
IMO, we should try to avoid new uAPI without a proven need, especially if we're considering throwing something into memslots. AFAIK, module params, at least on the x86 side of things, aren't considered immutable ABI (or maybe it's just that we haven't modified/removed one recently that folks care about).
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 14 lines · Sean Christopherson
Quoted 8 lines · Oliver Upton
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Maybe. It's also entirely possible that QoS is never factored in, e.g. if QoS guarantees for all VMs on a system are better met by enabling eager splitting across the board.
Quoted 6 lines
There are other reasons to use module/kernel params beyond what Marc listed, e.g. to let the user opt out even when something is on by default. x86's TDP MMU has benefited greatly from downstream users being able to do A/B performance testing this way. I suspect x86's
eager_page_splitknob was added largely for this reason, e.g. to easily see how a specific workload is affected by eager splitting. That seems like a reasonable fit on the ARM side as well.
There's a rather important distinction here in that we'd allow userspace to select the page split cache size, which should be correctly sized for the backing memory source. Considering the break-before-make rules of the architecture, the only way eager split is performant on arm64 is by replacing a block entry with a fully populated table hierarchy in one operation. AFAICT, you don't have this problem on x86, as the architecture generally permits a direct valid->valid transformation without an intermediate invalidation. Well, ignoring iTLB multihit :)
So, the largest transformation we need to do right now is on a PUD w/ PAGE_SIZE=4K, leading to 513 pages as proposed in the series. Exposing that configuration option in a module parameter is presumptive that all VMs on a host use the exact same memory configuration, which doesn't feel right to me.
--
Thanks,
Oliver
Sean Christopherson
reviewerRe: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 31 lines · Oliver Upton
Quoted 14 lines · Sean Christopherson
Quoted 8 lines · Oliver Upton
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Maybe. It's also entirely possible that QoS is never factored in, e.g. if QoS guarantees for all VMs on a system are better met by enabling eager splitting across the board.
Quoted 6 lines
There are other reasons to use module/kernel params beyond what Marc listed, e.g. to let the user opt out even when something is on by default. x86's TDP MMU has benefited greatly from downstream users being able to do A/B performance testing this way. I suspect x86's
eager_page_splitknob was added largely for this reason, e.g. to easily see how a specific workload is affected by eager splitting. That seems like a reasonable fit on the ARM side as well.There's a rather important distinction here in that we'd allow userspace to select the page split cache size, which should be correctly sized for the backing memory source. Considering the break-before-make rules of the architecture, the only way eager split is performant on arm64 is by replacing a block entry with a fully populated table hierarchy in one operation. AFAICT, you don't have this problem on x86, as the architecture generally permits a direct
valid->validtransformation without an intermediate invalidation. Well, ignoring iTLB multihit :)
Quoted 5 lines
So, the largest transformation we need to do right now is on a PUD w/ PAGE_SIZE=4K, leading to 513 pages as proposed in the series. Exposing that configuration option in a module parameter is presumptive that all VMs on a host use the exact same memory configuration, which doesn't feel right to me.
Can you elaborate on the cache size needing to be tied to the backing source? Do the issues arise if you get to a point where KVM can have PGD-sized hugepages with PAGE_SIZE=4KiB? Or do you want to let userspace optimize _now_ for PMD+4KiB?
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 32 lines · Sean Christopherson
Quoted 31 lines · Oliver Upton
Quoted 14 lines · Sean Christopherson
Quoted 8 lines · Oliver Upton
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Maybe. It's also entirely possible that QoS is never factored in, e.g. if QoS guarantees for all VMs on a system are better met by enabling eager splitting across the board.
Quoted 6 lines
There are other reasons to use module/kernel params beyond what Marc listed, e.g. to let the user opt out even when something is on by default. x86's TDP MMU has benefited greatly from downstream users being able to do A/B performance testing this way. I suspect x86's
eager_page_splitknob was added largely for this reason, e.g. to easily see how a specific workload is affected by eager splitting. That seems like a reasonable fit on the ARM side as well.There's a rather important distinction here in that we'd allow userspace to select the page split cache size, which should be correctly sized for the backing memory source. Considering the break-before-make rules of the architecture, the only way eager split is performant on arm64 is by replacing a block entry with a fully populated table hierarchy in one operation. AFAICT, you don't have this problem on x86, as the architecture generally permits a direct
valid->validtransformation without an intermediate invalidation. Well, ignoring iTLB multihit :)
Quoted 7 lines
Quoted 5 lines
So, the largest transformation we need to do right now is on a PUD w/ PAGE_SIZE=4K, leading to 513 pages as proposed in the series. Exposing that configuration option in a module parameter is presumptive that all VMs on a host use the exact same memory configuration, which doesn't feel right to me.
Can you elaborate on the cache size needing to be tied to the backing source?
The proposed eager split mechanism attempts to replace a block with a a fully populated page table hierarchy (i.e. mapped at PTE granularity) in order to avoid successive break-before-make invalidations. The cache size must be >= the number of pages required to build out that fully mapped page table hierarchy.
Quoted 2 lines
Do the issues arise if you get to a point where KVM can have PGD-sized hugepages with PAGE_SIZE=4KiB?
Those problems when splitting any hugepage larger than a PMD. It just so happens that the only configuration that supports larger mappings is 4K at the moment.
If we were to take the step-down approach to eager page splitting, there will be a lot of knock-on break-before-make operations as we go PUD -> PMD -> PTE.
Quoted 1 line
Or do you want to let userspace optimize _now_ for PMD+4KiB?
The default cache value should probably optimize for PMD splitting and give userspace the option to scale that up for PUD or greater if it sees fit.
Signature · 2 lines
Thanks, Oliver
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
In reply to Oliver UptonQuoted 23 lines · Oliver Upton
Quoted 14 lines · Sean Christopherson
Quoted 8 lines · Oliver Upton
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Maybe. It's also entirely possible that QoS is never factored in, e.g. if QoS guarantees for all VMs on a system are better met by enabling eager splitting across the board.
Quoted 6 lines
There are other reasons to use module/kernel params beyond what Marc listed, e.g. to let the user opt out even when something is on by default. x86's TDP MMU has benefited greatly from downstream users being able to do A/B performance testing this way. I suspect x86's
eager_page_splitknob was added largely for this reason, e.g. to easily see how a specific workload is affected by eager splitting. That seems like a reasonable fit on the ARM side as well.
Quoted 6 lines
There's a rather important distinction here in that we'd allow userspace to select the page split cache size, which should be correctly sized for the backing memory source. Considering the break-before-make rules of the architecture, the only way eager split is performant on arm64 is by replacing a block entry with a fully populated table hierarchy in one operation.
I don't see how this can be true if we are able to tolerate splitting 2M pages. Splitting 2M pages inherently means 512 Break-Before-Make operations per 1GiB region of guest physical memory.
If we had a cache size of 1 and were splitting a 1GiB region, we would then need to do 512+1 BBM per 1GiB region. If we can tolerate 512 per 1GiB, why not 513?
It seems more like the 513 cache size is more to optimize splitting 1GiB pages. I agree it can turn those 513 int 1, but future versions of the architecture also elide BBM requirements which is another way to optimize 1GiB pages.
Quoted 13 lines
AFAICT, you don't have this problem on x86, as the architecture generally permits a direct
valid->validtransformation without an intermediate invalidation. Well, ignoring iTLB multihit :)So, the largest transformation we need to do right now is on a PUD w/ PAGE_SIZE=4K, leading to 513 pages as proposed in the series. Exposing that configuration option in a module parameter is presumptive that all VMs on a host use the exact same memory configuration, which doesn't feel right to me.
--
Thanks,
Oliver
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Quoted 36 lines · David Matlack
Quoted 23 lines · Oliver Upton
Quoted 14 lines · Sean Christopherson
Quoted 8 lines · Oliver Upton
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Maybe. It's also entirely possible that QoS is never factored in, e.g. if QoS guarantees for all VMs on a system are better met by enabling eager splitting across the board.
Quoted 6 lines
There are other reasons to use module/kernel params beyond what Marc listed, e.g. to let the user opt out even when something is on by default. x86's TDP MMU has benefited greatly from downstream users being able to do A/B performance testing this way. I suspect x86's
eager_page_splitknob was added largely for this reason, e.g. to easily see how a specific workload is affected by eager splitting. That seems like a reasonable fit on the ARM side as well.Quoted 6 lines
There's a rather important distinction here in that we'd allow userspace to select the page split cache size, which should be correctly sized for the backing memory source. Considering the break-before-make rules of the architecture, the only way eager split is performant on arm64 is by replacing a block entry with a fully populated table hierarchy in one operation.
I don't see how this can be true if we are able to tolerate splitting 2M pages. Splitting 2M pages inherently means 512 Break-Before-Make operations per 1GiB region of guest physical memory.
Quoted 6 lines
If we had a cache size of 1 and were splitting a 1GiB region, we would then need to do 512+1 BBM per 1GiB region. If we can tolerate 512 per 1GiB, why not 513?
It seems more like the 513 cache size is more to optimize splitting 1GiB pages.
That's correct. Although there's also a slight benefit for the 2M huge-pages case as the 512 huge-pages can be split without having to walk down the tree from the root every time.
Quoted 3 lines
I agree it can turn those 513 int 1, but future versions of the architecture also elide BBM requirements which is another way to optimize 1GiB pages.
There's also the CPU cost needed to walk down the tree from the root 513 times (same as above).
Quoted 15 lines
Quoted 15 lines
AFAICT, you don't have this problem on x86, as the architecture generally permits a direct
valid->validtransformation without an intermediate invalidation. Well, ignoring iTLB multihit :)So, the largest transformation we need to do right now is on a PUD w/ PAGE_SIZE=4K, leading to 513 pages as proposed in the series. Exposing that configuration option in a module parameter is presumptive that all VMs on a host use the exact same memory configuration, which doesn't feel right to me.
--
Thanks,
Oliver
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
In reply to David MatlackQuoted 31 lines · David Matlack
Quoted 23 lines · Oliver Upton
Quoted 14 lines · Sean Christopherson
Quoted 8 lines · Oliver Upton
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Maybe. It's also entirely possible that QoS is never factored in, e.g. if QoS guarantees for all VMs on a system are better met by enabling eager splitting across the board.
Quoted 6 lines
There are other reasons to use module/kernel params beyond what Marc listed, e.g. to let the user opt out even when something is on by default. x86's TDP MMU has benefited greatly from downstream users being able to do A/B performance testing this way. I suspect x86's
eager_page_splitknob was added largely for this reason, e.g. to easily see how a specific workload is affected by eager splitting. That seems like a reasonable fit on the ARM side as well.Quoted 6 lines
There's a rather important distinction here in that we'd allow userspace to select the page split cache size, which should be correctly sized for the backing memory source. Considering the break-before-make rules of the architecture, the only way eager split is performant on arm64 is by replacing a block entry with a fully populated table hierarchy in one operation.
Quoted 3 lines
I don't see how this can be true if we are able to tolerate splitting 2M pages. Splitting 2M pages inherently means 512 Break-Before-Make operations per 1GiB region of guest physical memory.
'Only' was definitely not the right word here.
I fear that there is a rather limited degree of portability for any observation that we derive from a particular system. Assuming the absolute worst of hardware, TLBIs + serialization will become even more of a bounding issue as the number of affected entities on the interconnect scales.
So in that vein I don't believe it is easy to glean what may or may not be tolerable.
Quoted 2 lines
It seems more like the 513 cache size is more to optimize splitting 1GiB pages.
I don't believe anyone is particularly jazzed about this detail, so I would be surprised if we accepted this as the default configuration.
Quoted 3 lines
I agree it can turn those 513 int 1, but future versions of the architecture also elide BBM requirements which is another way to optimize 1GiB pages.
Level 2 break-before-make behavior is helpful but certainly not a panacea. Most worrying is that implementations may generate TLB conflict aborts, at which point the only remediation is to invalidate the entire affected context.
Signature · 2 lines
Thanks, Oliver
Marc Zyngier
maintainerRe: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
In reply to Oliver UptonQuoted 47 lines · Oliver Upton
Quoted 3 lines · Ricardo Koller
Hi Marc,
On Thu, Jan 26, 2023 at 12:10 PM Marc Zyngier <[email protected]> wrote:
[...]
Quoted 39 lines
Quoted 6 lines
The one thing that would convince me to make it an option is the amount of memory this thing consumes. 512+ pages is a huge amount, and I'm not overly happy about that. Why can't this be a userspace visible option, selectable on a per VM (or memslot) basis?
It should be possible. I am exploring a couple of ideas that could help when the hugepages are not 1G (e.g., 2M). However, they add complexity and I'm not sure they help much.
(will be using PAGE_SIZE=4K to make things simpler)
This feature pre-allocates 513 pages before splitting every 1G range. For example, it converts 1G block PTEs into trees made of 513 pages. When not using this feature, the same 513 pages would be allocated, but lazily over a longer period of time.
Eager-splitting pre-allocates those pages in order to split huge-pages into fully populated trees. Which is needed in order to use
FEAT_BBMand skipping the expensive TLBI broadcasts. 513 is just the number of pages needed to break a 1G huge-page.We could optimize for smaller huge-pages, like 2M by splitting 1 huge-page at a time: only preallocate one 4K page at a time. The trick is how to know that we are splitting 2M huge-pages. We could either get the vma pagesize or use hints from userspace. I'm not sure that this is worth it though. The user will most likely want to split big ranges of memory (>1G), so optimizing for smaller huge-pages only converts the left into the right:
alloc 1 page | | alloc 512 pages split 2M huge-page | | split 2M huge-page alloc 1 page | | split 2M huge-page split 2M huge-page | => | split 2M huge-page ... alloc 1 page | | split 2M huge-page split 2M huge-page | | split 2M huge-page
Quoted 5 lines
Quoted 1 line
Still thinking of what else to do.
I think that Marc's suggestion of having userspace configure this is sound. After all, userspace _should_ know the granularity of the backing source it chose for guest memory.
Only if it is not using anonymous memory. That's the important distinction.
Quoted 5 lines
We could also interpret a cache size of 0 to signal that userspace wants to disable eager page split for a VM altogether. It is entirely possible that the user will want a differing QoS between slice-of-hardware and overcommitted VMs.
Absolutely. The overcommited case would suffer from the upfront allocation (these systems are usually very densely packed).
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Marc Zyngier
maintainerRe: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
In reply to Ricardo KollerQuoted 11 lines · Ricardo Koller
Quoted 6 lines
The one thing that would convince me to make it an option is the amount of memory this thing consumes. 512+ pages is a huge amount, and I'm not overly happy about that. Why can't this be a userspace visible option, selectable on a per VM (or memslot) basis?
It should be possible. I am exploring a couple of ideas that could help when the hugepages are not 1G (e.g., 2M). However, they add complexity and I'm not sure they help much.
Quoted 6 lines
(will be using PAGE_SIZE=4K to make things simpler)
This feature pre-allocates 513 pages before splitting every 1G range. For example, it converts 1G block PTEs into trees made of 513 pages. When not using this feature, the same 513 pages would be allocated, but lazily over a longer period of time.
This is an important difference. It avoids the upfront allocation "thermal shock", giving time to the kernel to reclaim memory from somewhere else. Doing it upfront means you *must* have 2MB+ of immediately available memory for each GB of RAM you guest uses.
Quoted 5 lines
Eager-splitting pre-allocates those pages in order to split huge-pages into fully populated trees. Which is needed in order to use
FEAT_BBMand skipping the expensive TLBI broadcasts. 513 is just the number of pages needed to break a 1G huge-page.
I understand that. But it also clear that 1GB huge pages are unlikely to be THPs, and I wonder if we should treat the two differently. Using HugeTLBFS pages is significant here.
Quoted 17 lines
We could optimize for smaller huge-pages, like 2M by splitting 1 huge-page at a time: only preallocate one 4K page at a time. The trick is how to know that we are splitting 2M huge-pages. We could either get the vma pagesize or use hints from userspace. I'm not sure that this is worth it though. The user will most likely want to split big ranges of memory (>1G), so optimizing for smaller huge-pages only converts the left into the right:
alloc 1 page | | alloc 512 pages split 2M huge-page | | split 2M huge-page alloc 1 page | | split 2M huge-page split 2M huge-page | => | split 2M huge-page ... alloc 1 page | | split 2M huge-page split 2M huge-page | | split 2M huge-page
Quoted 1 line
Still thinking of what else to do.
I think the 1G case fits your own use case, but I doubt this covers the majority of the users. Most people rely on the kernel ability to use THPs, which are capped at the first level of block mapping.
2MB (and 32MB for 16kB base pages) are the most likely mappings in my experience (512MB with 64kB pages are vanishingly rare).
Having to pay an upfront cost for HugeTLBFS doesn't shock me, and it fits the model. For THPs, where everything is opportunistic and the user not involved, this is a lot more debatable.
This is why I'd like this behaviour to be a buy-in, either directly (a first class userspace API) or indirectly (the provenance of the memory).
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Re: [PATCH 6/9] KVM: arm64: Split huge pages when dirty logging is enabled
Hi Marc,
Quoted 62 lines · Marc Zyngier
Quoted 11 lines · Ricardo Koller
Quoted 6 lines
The one thing that would convince me to make it an option is the amount of memory this thing consumes. 512+ pages is a huge amount, and I'm not overly happy about that. Why can't this be a userspace visible option, selectable on a per VM (or memslot) basis?
It should be possible. I am exploring a couple of ideas that could help when the hugepages are not 1G (e.g., 2M). However, they add complexity and I'm not sure they help much.
Quoted 6 lines
(will be using PAGE_SIZE=4K to make things simpler)
This feature pre-allocates 513 pages before splitting every 1G range. For example, it converts 1G block PTEs into trees made of 513 pages. When not using this feature, the same 513 pages would be allocated, but lazily over a longer period of time.
This is an important difference. It avoids the upfront allocation "thermal shock", giving time to the kernel to reclaim memory from somewhere else. Doing it upfront means you *must* have 2MB+ of immediately available memory for each GB of RAM you guest uses.
Quoted 5 lines
Eager-splitting pre-allocates those pages in order to split huge-pages into fully populated trees. Which is needed in order to use
FEAT_BBMand skipping the expensive TLBI broadcasts. 513 is just the number of pages needed to break a 1G huge-page.I understand that. But it also clear that 1GB huge pages are unlikely to be THPs, and I wonder if we should treat the two differently. Using HugeTLBFS pages is significant here.
Quoted 17 lines
We could optimize for smaller huge-pages, like 2M by splitting 1 huge-page at a time: only preallocate one 4K page at a time. The trick is how to know that we are splitting 2M huge-pages. We could either get the vma pagesize or use hints from userspace. I'm not sure that this is worth it though. The user will most likely want to split big ranges of memory (>1G), so optimizing for smaller huge-pages only converts the left into the right:
alloc 1 page | | alloc 512 pages split 2M huge-page | | split 2M huge-page alloc 1 page | | split 2M huge-page split 2M huge-page | => | split 2M huge-page ... alloc 1 page | | split 2M huge-page split 2M huge-page | | split 2M huge-pageQuoted 1 line
Still thinking of what else to do.
I think the 1G case fits your own use case, but I doubt this covers the majority of the users. Most people rely on the kernel ability to use THPs, which are capped at the first level of block mapping.
2MB (and 32MB for 16kB base pages) are the most likely mappings in my experience (512MB with 64kB pages are vanishingly rare).
Quoted 7 lines
Having to pay an upfront cost for HugeTLBFS doesn't shock me, and it fits the model. For THPs, where everything is opportunistic and the user not involved, this is a lot more debatable.
This is why I'd like this behaviour to be a buy-in, either directly (a first class userspace API) or indirectly (the provenance of the memory).
This all makes sense, thanks for the explanation. I decided to implement something for both cases: small caches (~1 page) where the PUDs are split one PMD at a time, and bigger caches (>513) where the PUDs can be split with a single replacement. The user specifies the size of the cache via a capability, and size of 0 implies no eager splitting (the feature is off).
Thanks,
Ricardo
Quoted 7 lines
Thanks,
M.--
Without deviation from the norm, progress is not possible.
PATCH 7/9 KVM: arm64: Open-code kvm_mmu_write_protect_pt_masked()
In reply to Ricardo KollerMove the functionality of kvm_mmu_write_protect_pt_masked() into its caller, kvm_arch_mmu_enable_log_dirty_pt_masked(). This will be used in a subsequent commit in order to share some of the code in kvm_arch_mmu_enable_log_dirty_pt_masked().
No functional change intended.
--- arch/arm64/kvm/mmu.c | 42 +++++++++++++++--------------------------- 1 file changed, 15 insertions(+), 27 deletions(-)
arch/arm64/kvm/mmu.c +15 -27
@@ -1045,28 +1045,6 @@ static void kvm_mmu_wp_memory_region(struct kvm *kvm, int slot)kvm_flush_remote_tlbs (kvm); } -/** -* kvm_mmu_write_protect_pt_masked() - write protect dirty pages -* @kvm: The KVM pointer -* @slot: The memory slot associated with mask -* @gfn_offset: The gfn offset in memory slot -* @mask: The mask of dirty pages at offset 'gfn_offset' in this memory -* slot to be write protected -* -* Walks bits set in mask write protects the associated pte's. Caller must -* acquire kvm_mmu_lock. -*/ -static void kvm_mmu_write_protect_pt_masked (struct kvm *kvm, -struct kvm_memory_slot *slot, -gfn_t gfn_offset,unsigned long mask) -{ -phys_addr_t base_gfn = slot->base_gfn + gfn_offset; -phys_addr_t start = (base_gfn +__ffs (mask)) <<PAGE_SHIFT ; -phys_addr_t end = (base_gfn +__fls (mask) +1 ) <<PAGE_SHIFT ; - -stage2_wp_range (&kvm->arch.mmu, start, end); -} -/** * kvm_mmu_split_memory_region() - split the stage 2 blocks into PAGE_SIZE * pages for memory slot
@@ -1091,17 +1069,27 @@ static void kvm_mmu_split_memory_region(struct kvm *kvm, int slot) }/* -* kvm_arch_mmu_enable_log_dirty_pt_masked - enable dirty logging for selected -* dirty pages. +* kvm_arch_mmu_enable_log_dirty_pt_masked() - enable dirty logging for selected pages. +* @kvm: The KVM pointer +* @slot: The memory slot associated with mask +* @gfn_offset: The gfn offset in memory slot +* @mask: The mask of pages at offset 'gfn_offset' in this memory +* slot to enable dirty logging on * -* It calls kvm_mmu_write_protect_pt_masked to write protect selected pages to -* enable dirty logging for them. +* Writes protect selected pages to enable dirty logging for them. Caller must +* acquire kvm->mmu_lock. */ void kvm_arch_mmu_enable_log_dirty_pt_masked (struct kvm *kvm,struct kvm_memory_slot *slot,gfn_t gfn_offset,unsigned long mask) { -kvm_mmu_write_protect_pt_masked (kvm, slot, gfn_offset, mask); +phys_addr_t base_gfn = slot->base_gfn + gfn_offset; +phys_addr_t start = (base_gfn +__ffs (mask)) <<PAGE_SHIFT ; +phys_addr_t end = (base_gfn +__fls (mask) +1 ) <<PAGE_SHIFT ; + +lockdep_assert_held_write (&kvm->mmu_lock); + +stage2_wp_range (&kvm->arch.mmu, start, end); }static void kvm_send_hwpoison_signal (unsigned long address,short lsb)
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
PATCH 8/9 KVM: arm64: Split huge pages during KVM_CLEAR_DIRTY_LOG
In reply to Ricardo KollerThis is the arm64 counterpart of commit cb00a70bd4b7 ("KVM: x86/mmu:
Split huge pages mapped by the TDP MMU during KVM_CLEAR_DIRTY_LOG"), which has the benefit of splitting the cost of splitting a memslot across multiple ioctls.
Split huge pages on the range specified using KVM_CLEAR_DIRTY_LOG. And do not split when enabling dirty logging if KVM_DIRTY_LOG_INITIALLY_SET is set.
--- arch/arm64/kvm/mmu.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
arch/arm64/kvm/mmu.c +13 -3
@@ -1076,8 +1076,8 @@ static void kvm_mmu_split_memory_region(struct kvm *kvm, int slot)* @mask: The mask of pages at offset 'gfn_offset' in this memory * slot to enable dirty logging on * -* Writes protect selected pages to enable dirty logging for them. Caller must -* acquire kvm->mmu_lock. +* Splits selected pages to PAGE_SIZE and then writes protect them to enable +* dirty logging for them. Caller must acquire kvm->mmu_lock. */ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm, struct kvm_memory_slot *slot,
@@ -1090,6 +1090,14 @@ void kvm_arch_mmu_enable_log_dirty_pt_masked(struct kvm *kvm,lockdep_assert_held_write (&kvm->mmu_lock);stage2_wp_range (&kvm->arch.mmu, start, end); + +/* +* If initially-all-set mode is not set, then huge-pages were already +* split when enabling dirty logging: no need to do it again. +*/ +if (kvm_dirty_log_manual_protect_and_init_set (kvm) && +READ_ONCE (eager_page_split)) +kvm_mmu_split_huge_pages (kvm, start, end); }static void kvm_send_hwpoison_signal (unsigned long address,short lsb)
@@ -1875,7 +1883,9 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,* this when deleting, moving, disabling dirty logging, or * creating the memslot (a nop). Doing it for deletes makes * sure we don't leak memory, and there's no need to keep the -* cache around for any of the other cases. +* cache around for any of the other cases. Keeping the cache +* is useful for succesive KVM_CLEAR_DIRTY_LOG calls, which is +* not handled in this function. */ kvm_mmu_free_memory_cache (&kvm->arch.mmu.split_page_cache); }
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
PATCH 9/9 KVM: arm64: Use local TLBI on permission relaxation
In reply to Ricardo KollerFrom: Marc Zyngier <[email protected]>
Broadcasted TLB invalidations (TLBI) are usually less performant than their local variant. In particular, we observed some implementations that take millliseconds to complete parallel broadcasted TLBIs.
It's safe to use local, non-shareable, TLBIs when relaxing permissions on a PTE in the KVM case for a couple of reasons. First, according to the ARM Arm (DDI 0487H.a D5-4913), permission relaxation does not need break-before-make. Second, KVM does not set the VTTBR_EL2.CnP bit, so each PE has its own TLB entry for the same page. KVM could tolerate that when doing permission relaxation (i.e., not having changes broadcasted to all PEs).
--- arch/arm64/include/asm/kvm_asm.h | 4 +++ arch/arm64/kvm/hyp/nvhe/hyp-main.c | 10 ++++++ arch/arm64/kvm/hyp/nvhe/tlb.c | 54 ++++++++++++++++++++++++++++++ arch/arm64/kvm/hyp/pgtable.c | 2 +- arch/arm64/kvm/hyp/vhe/tlb.c | 32 ++++++++++++++++++ 5 files changed, 101 insertions(+), 1 deletion(-)
arch/arm64/include/asm/kvm_asm.h +4 -0
@@ -68,6 +68,7 @@ enum __kvm_host_smccc_func { __KVM_HOST_SMCCC_FUNC___kvm_vcpu_run, __KVM_HOST_SMCCC_FUNC___kvm_flush_vm_context, __KVM_HOST_SMCCC_FUNC___kvm_tlb_flush_vmid_ipa, + __KVM_HOST_SMCCC_FUNC___kvm_tlb_flush_vmid_ipa_nsh, __KVM_HOST_SMCCC_FUNC___kvm_tlb_flush_vmid, __KVM_HOST_SMCCC_FUNC___kvm_flush_cpu_context, __KVM_HOST_SMCCC_FUNC___kvm_timer_set_cntvoff,
@@ -225,6 +226,9 @@ extern void __kvm_flush_vm_context(void);extern void __kvm_flush_cpu_context (struct kvm_s2_mmu *mmu);extern void __kvm_tlb_flush_vmid_ipa (struct kvm_s2_mmu *mmu,phys_addr_t ipa,int level); +extern void __kvm_tlb_flush_vmid_ipa_nsh (struct kvm_s2_mmu *mmu, +phys_addr_t ipa, +int level);extern void __kvm_tlb_flush_vmid (struct kvm_s2_mmu *mmu);extern void __kvm_timer_set_cntvoff (u64 cntvoff);
arch/arm64/kvm/hyp/nvhe/hyp-main.c +10 -0
@@ -125,6 +125,15 @@ static void handle___kvm_tlb_flush_vmid_ipa(struct kvm_cpu_context *host_ctxt)__kvm_tlb_flush_vmid_ipa (kern_hyp_va (mmu), ipa, level); } +static void handle___kvm_tlb_flush_vmid_ipa_nsh (struct kvm_cpu_context *host_ctxt) +{ + DECLARE_REG(struct kvm_s2_mmu *, mmu, host_ctxt, 1); +DECLARE_REG (phys_addr_t, ipa, host_ctxt,2 ); +DECLARE_REG (int, level, host_ctxt,3 ); + +__kvm_tlb_flush_vmid_ipa_nsh (kern_hyp_va (mmu), ipa, level); +} +static void handle___kvm_tlb_flush_vmid (struct kvm_cpu_context *host_ctxt) { DECLARE_REG(struct kvm_s2_mmu *, mmu, host_ctxt, 1);
@@ -315,6 +324,7 @@ static const hcall_t host_hcall[] = {HANDLE_FUNC (__kvm_vcpu_run),HANDLE_FUNC (__kvm_flush_vm_context),HANDLE_FUNC (__kvm_tlb_flush_vmid_ipa), +HANDLE_FUNC (__kvm_tlb_flush_vmid_ipa_nsh),HANDLE_FUNC (__kvm_tlb_flush_vmid),HANDLE_FUNC (__kvm_flush_cpu_context), HANDLE_FUNC(__kvm_timer_set_cntvoff),
arch/arm64/kvm/hyp/nvhe/tlb.c +54 -0
60 lines not on this page · raw message
arch/arm64/kvm/hyp/pgtable.c +1 -1
@@ -1148,7 +1148,7 @@ int kvm_pgtable_stage2_relax_perms(struct kvm_pgtable *pgt, u64 addr, ret =stage2_update_leaf_attrs (pgt, addr,1 , set, clr,NULL , &level,KVM_PGTABLE_WALK_SHARED );if (!ret) -kvm_call_hyp (__kvm_tlb_flush_vmid_ipa, pgt->mmu, addr, level); +kvm_call_hyp (__kvm_tlb_flush_vmid_ipa_nsh, pgt->mmu, addr, level);return ret; }
arch/arm64/kvm/hyp/vhe/tlb.c +32 -0
@@ -111,6 +111,38 @@ void __kvm_tlb_flush_vmid_ipa(struct kvm_s2_mmu *mmu,__tlb_switch_to_host (&cxt); } +void __kvm_tlb_flush_vmid_ipa_nsh (struct kvm_s2_mmu *mmu, +phys_addr_t ipa,int level) +{ +struct tlb_inv_context cxt; + +dsb (nshst); + +/* Switch to requested VMID */ +__tlb_switch_to_guest (mmu, &cxt); + +/* +* We could do so much better if we had the VA as well. +* Instead, we invalidate Stage-2 for this IPA, and the +* whole of Stage-1. Weep... +*/ + ipa >>=12 ; +__tlbi_level (ipas2e1, ipa, level); + +/* +* We have to ensure completion of the invalidation at Stage-2, +* since a table walk on another CPU could refill a TLB with a +* complete (S1 + S2) walk based on the old Stage-2 mapping if +* the Stage-1 invalidation happened first. +*/ +dsb (nsh); +__tlbi (vmalle1); +dsb (nsh); +isb (); + +__tlb_switch_to_host (&cxt); +} +void __kvm_tlb_flush_vmid (struct kvm_s2_mmu *mmu) {struct tlb_inv_context cxt;
Signature · 1 line
2.39.0.314.g84b9a713c41-goog
Quoted 86 lines · Ricardo Koller
Implement Eager Page Splitting for ARM.
Eager Page Splitting improves the performance of dirty-logging (used in live migrations) when guest memory is backed by huge-pages. It's an optimization used in Google Cloud since 2016 on x86, and for the last couple of months on ARM.
Background and motivation
=========================
Dirty logging is typically used for live-migration iterative copying. KVM implements dirty-logging at thePAGE_SIZEgranularity (will refer to 4K pages from now on). It does it by faulting on write-protected 4K pages. Therefore, enabling dirty-logging on a huge-page requires breaking it into 4K pages in the first place. KVM does this breaking on fault, and because it's in the critical path it only maps the 4K page that faulted; every other 4K page is left unmapped. This is not great for performance on ARM for a couple of reasons:- Splitting on fault can halt vcpus for milliseconds in some implementations. Splitting a block PTE requires using a broadcasted TLB invalidation (TLBI) for every huge-page (due to the break-before-make requirement). Note that x86 doesn't need this. We observed some implementations that take millliseconds to complete broadcasted TLBIs when done in parallel from multiple vcpus. And that's exactly what happens when doing it on fault: multiple vcpus fault at the same time triggering TLBIs in parallel.
- Read intensive guest workloads end up paying for dirty-logging. Only mapping the faulting 4K page means that all the other pages that were part of the huge-page will now be unmapped. The effect is that any access, including reads, now has to fault.
Eager Page Splitting (on ARM)
=============================
Eager Page Splitting fixes the above two issues by eagerly splitting huge-pages when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages. This is what the TDP MMU does for x86 [0], except that x86 does it for different reasons: to avoid grabbing the MMU lock on fault. Note that taking care of write-protection faults still requires grabbing the MMU lock on ARM, but not on x86 (with thefast_page_faultpath).An additional benefit of eagerly splitting huge-pages is that it can be done in a controlled way (e.g., via an IOCTL). This series provides two knobs for doing it, just like its x86 counterpart: when enabling dirty logging, and when using the
KVM_CLEAR_DIRTY_LOGioctl. The benefit of doing it onKVM_CLEAR_DIRTY_LOGis that this ioctl takes ranges, and not complete memslots like when enabling dirty logging. This means that the cost of splitting (mainly broadcasted TLBIs) can be throttled: split a range, wait for a bit, split another range, etc. The benefits of this approach were presented by Oliver Upton at KVM Forum 2022 [1].Implementation
==============
Patches 1-3 add a pgtable utility function for splitting huge block
PTEs:kvm_pgtable_stage2_split(). Patches 4-8 add support for eagerly splitting huge-pages when enabling dirty-logging and when using theKVM_CLEAR_DIRTY_LOGioctl. Note that this is just like what x86 does, and the code is actually based on it. And finally, patch 9:KVM: arm64: Use local TLBI on permission relaxation
adds support for using local TLBIs instead of broadcasts when doing permission relaxation. This last patch is key to achieving good performance during dirty-logging, as eagerly breaking huge-pages replaces mapping new pages with permission relaxation. Got this patch (indirectly) from Marc Z. and took the liberty of adding a commit message.
Note: this applies on top of 6.2-rc3.
Performance evaluation
======================
The performance benefits were tested using thedirty_log_perf_testselftest with 2M huge-pages.The first test uses a write-only sequential workload where the stride is 2M instead of 4K [2]. The idea with this experiment is to emulate a random access pattern writing a different huge-page at every access. Observe that the benefit increases with the number of vcpus: up to 5.76x for 152 vcpus.
./dirty_log_perf_test_sparse -s
anonymous_hugetlb_2mb-b 1G -v $i -i 3 -m 2
Quoted 14 lines
+-------+----------+------------------+
| vCPUs | 6.2-rc3 | 6.2-rc3 + series |
| | (ms) | (ms) |
+-------+----------+------------------+
| 1 | 2.63 | 1.66 |
| 2 | 2.95 | 1.70 |
| 4 | 3.21 | 1.71 |
| 8 | 4.97 | 1.78 |
| 16 | 9.51 | 1.82 |
| 32 | 20.15 | 3.03 |
| 64 | 40.09 | 5.80 |
| 128 | 80.08 | 12.24 |
| 152 | 109.81 | 15.14 |
+-------+----------+------------------+This is the average pass time I assume? Or the total or last? Or whole test runtime?
Was this run with MANUAL_PROTECT or do the split during the CLEAR IOCTL or with the splitting at enable time?
Quoted 67 lines
This second test measures the benefit of eager page splitting on read intensive workloads (1 write for every 10 reads). As in the other test, the benefit increases with the number of vcpus, up to 8.82x for 152 vcpus.
./dirty_log_perf_test -s
anonymous_hugetlb_2mb-b 1G -v $i -i 3 -m 2 -f 10+-------+----------+------------------+ | vCPUs | 6.2-rc3 | 6.2-rc3 + series | | | (sec) | (sec) | +-------+----------+------------------+ | 1 | 0.65 | 0.07 | | 2 | 0.70 | 0.08 | | 4 | 0.71 | 0.08 | | 8 | 0.72 | 0.08 | | 16 | 0.76 | 0.08 | | 32 | 1.61 | 0.14 | | 64 | 3.46 | 0.30 | | 128 | 5.49 | 0.64 | | 152 | 6.44 | 0.63 | +-------+----------+------------------+Changes from the RFC:
https://lore.kernel.org/kvmarm/[email protected]/
- dropped the changes to split on POST visits. No visible perf benefit.
- changed thekvm_pgtable_stage2_free_removed()implementation to reuse the stage2 mapper.
- dropped theFEAT_BBMchanges and optimization. Will send this on a different series.Thanks,
Ricardo[0] https://lore.kernel.org/kvm/[email protected]/
[1] https://kvmforum2022.sched.com/event/15jJq/kvmarm-at-scale-improvements-to-the-mmu-in-the-face-of-hardware-growing-pains-oliver-upton-google
[2] https://github.com/ricarkol/linux/commit/f78e9102b2bff4fb7f30bee810d7d611a537b46d
[3] https://lore.kernel.org/kvmarm/[email protected]/Marc Zyngier (1):
KVM: arm64: Use local TLBI on permission relaxationRicardo Koller (8):
KVM: arm64: AddKVM_PGTABLE_WALK_REMOVEDintoctx->flags
KVM: arm64: Add helper for creating removed stage2 subtrees
KVM: arm64: Addkvm_pgtable_stage2_split()
KVM: arm64: Refactorkvm_arch_commit_memory_region()
KVM: arm64: Addkvm_uninit_stage2_mmu()
KVM: arm64: Split huge pages when dirty logging is enabled
KVM: arm64: Open-codekvm_mmu_write_protect_pt_masked()
KVM: arm64: Split huge pages duringKVM_CLEAR_DIRTY_LOGarch/arm64/include/asm/kvm_asm.h | 4 + arch/arm64/include/asm/kvm_host.h | 30 +++++ arch/arm64/include/asm/kvm_mmu.h | 1 + arch/arm64/include/asm/kvm_pgtable.h | 62 ++++++++++ arch/arm64/kvm/hyp/nvhe/hyp-main.c | 10 ++ arch/arm64/kvm/hyp/nvhe/tlb.c | 54 +++++++++ arch/arm64/kvm/hyp/pgtable.c | 143 +++++++++++++++++++++-- arch/arm64/kvm/hyp/vhe/tlb.c | 32 +++++ arch/arm64/kvm/mmu.c | 168 ++++++++++++++++++++++----- 9 files changed, 466 insertions(+), 38 deletions(-)--
2.39.0.314.g84b9a713c41-goog
Quoted 102 lines · Ben Gardon
Quoted 86 lines · Ricardo Koller
Implement Eager Page Splitting for ARM.
Eager Page Splitting improves the performance of dirty-logging (used in live migrations) when guest memory is backed by huge-pages. It's an optimization used in Google Cloud since 2016 on x86, and for the last couple of months on ARM.
Background and motivation
=========================
Dirty logging is typically used for live-migration iterative copying. KVM implements dirty-logging at thePAGE_SIZEgranularity (will refer to 4K pages from now on). It does it by faulting on write-protected 4K pages. Therefore, enabling dirty-logging on a huge-page requires breaking it into 4K pages in the first place. KVM does this breaking on fault, and because it's in the critical path it only maps the 4K page that faulted; every other 4K page is left unmapped. This is not great for performance on ARM for a couple of reasons:- Splitting on fault can halt vcpus for milliseconds in some implementations. Splitting a block PTE requires using a broadcasted TLB invalidation (TLBI) for every huge-page (due to the break-before-make requirement). Note that x86 doesn't need this. We observed some implementations that take millliseconds to complete broadcasted TLBIs when done in parallel from multiple vcpus. And that's exactly what happens when doing it on fault: multiple vcpus fault at the same time triggering TLBIs in parallel.
- Read intensive guest workloads end up paying for dirty-logging. Only mapping the faulting 4K page means that all the other pages that were part of the huge-page will now be unmapped. The effect is that any access, including reads, now has to fault.
Eager Page Splitting (on ARM)
=============================
Eager Page Splitting fixes the above two issues by eagerly splitting huge-pages when enabling dirty logging. The goal is to avoid doing it while faulting on write-protected pages. This is what the TDP MMU does for x86 [0], except that x86 does it for different reasons: to avoid grabbing the MMU lock on fault. Note that taking care of write-protection faults still requires grabbing the MMU lock on ARM, but not on x86 (with thefast_page_faultpath).An additional benefit of eagerly splitting huge-pages is that it can be done in a controlled way (e.g., via an IOCTL). This series provides two knobs for doing it, just like its x86 counterpart: when enabling dirty logging, and when using the
KVM_CLEAR_DIRTY_LOGioctl. The benefit of doing it onKVM_CLEAR_DIRTY_LOGis that this ioctl takes ranges, and not complete memslots like when enabling dirty logging. This means that the cost of splitting (mainly broadcasted TLBIs) can be throttled: split a range, wait for a bit, split another range, etc. The benefits of this approach were presented by Oliver Upton at KVM Forum 2022 [1].Implementation
==============
Patches 1-3 add a pgtable utility function for splitting huge block
PTEs:kvm_pgtable_stage2_split(). Patches 4-8 add support for eagerly splitting huge-pages when enabling dirty-logging and when using theKVM_CLEAR_DIRTY_LOGioctl. Note that this is just like what x86 does, and the code is actually based on it. And finally, patch 9:KVM: arm64: Use local TLBI on permission relaxation
adds support for using local TLBIs instead of broadcasts when doing permission relaxation. This last patch is key to achieving good performance during dirty-logging, as eagerly breaking huge-pages replaces mapping new pages with permission relaxation. Got this patch (indirectly) from Marc Z. and took the liberty of adding a commit message.
Note: this applies on top of 6.2-rc3.
Performance evaluation
======================
The performance benefits were tested using thedirty_log_perf_testselftest with 2M huge-pages.The first test uses a write-only sequential workload where the stride is 2M instead of 4K [2]. The idea with this experiment is to emulate a random access pattern writing a different huge-page at every access. Observe that the benefit increases with the number of vcpus: up to 5.76x for 152 vcpus.
./dirty_log_perf_test_sparse -s
anonymous_hugetlb_2mb-b 1G -v $i -i 3 -m 2Quoted 14 lines
+-------+----------+------------------+ | vCPUs | 6.2-rc3 | 6.2-rc3 + series | | | (ms) | (ms) | +-------+----------+------------------+ | 1 | 2.63 | 1.66 | | 2 | 2.95 | 1.70 | | 4 | 3.21 | 1.71 | | 8 | 4.97 | 1.78 | | 16 | 9.51 | 1.82 | | 32 | 20.15 | 3.03 | | 64 | 40.09 | 5.80 | | 128 | 80.08 | 12.24 | | 152 | 109.81 | 15.14 | +-------+----------+------------------+
Quoted 2 lines
This is the average pass time I assume? Or the total or last? Or whole test runtime?
Oops, forgot to provide any detail, sorry for that. This is the length of the first guest pass ("Iteration 2 dirty memory time").
Quoted 2 lines
Was this run with
MANUAL_PROTECTor do the split during the CLEAR IOCTL or with the splitting at enable time?
The CLEAR IOCTL (with MANUAL_PROTECT). Just to double check, without the '-g' argument.
Quoted 68 lines
Quoted 68 lines
This second test measures the benefit of eager page splitting on read intensive workloads (1 write for every 10 reads). As in the other test, the benefit increases with the number of vcpus, up to 8.82x for 152 vcpus.
./dirty_log_perf_test -s
anonymous_hugetlb_2mb-b 1G -v $i -i 3 -m 2 -f 10+-------+----------+------------------+ | vCPUs | 6.2-rc3 | 6.2-rc3 + series | | | (sec) | (sec) | +-------+----------+------------------+ | 1 | 0.65 | 0.07 | | 2 | 0.70 | 0.08 | | 4 | 0.71 | 0.08 | | 8 | 0.72 | 0.08 | | 16 | 0.76 | 0.08 | | 32 | 1.61 | 0.14 | | 64 | 3.46 | 0.30 | | 128 | 5.49 | 0.64 | | 152 | 6.44 | 0.63 | +-------+----------+------------------+Changes from the RFC:
https://lore.kernel.org/kvmarm/[email protected]/
- dropped the changes to split on POST visits. No visible perf benefit.
- changed thekvm_pgtable_stage2_free_removed()implementation to reuse the stage2 mapper.
- dropped theFEAT_BBMchanges and optimization. Will send this on a different series.Thanks,
Ricardo[0] https://lore.kernel.org/kvm/[email protected]/
[1] https://kvmforum2022.sched.com/event/15jJq/kvmarm-at-scale-improvements-to-the-mmu-in-the-face-of-hardware-growing-pains-oliver-upton-google
[2] https://github.com/ricarkol/linux/commit/f78e9102b2bff4fb7f30bee810d7d611a537b46d
[3] https://lore.kernel.org/kvmarm/[email protected]/Marc Zyngier (1):
KVM: arm64: Use local TLBI on permission relaxationRicardo Koller (8):
KVM: arm64: AddKVM_PGTABLE_WALK_REMOVEDintoctx->flags
KVM: arm64: Add helper for creating removed stage2 subtrees
KVM: arm64: Addkvm_pgtable_stage2_split()
KVM: arm64: Refactorkvm_arch_commit_memory_region()
KVM: arm64: Addkvm_uninit_stage2_mmu()
KVM: arm64: Split huge pages when dirty logging is enabled
KVM: arm64: Open-codekvm_mmu_write_protect_pt_masked()
KVM: arm64: Split huge pages duringKVM_CLEAR_DIRTY_LOGarch/arm64/include/asm/kvm_asm.h | 4 + arch/arm64/include/asm/kvm_host.h | 30 +++++ arch/arm64/include/asm/kvm_mmu.h | 1 + arch/arm64/include/asm/kvm_pgtable.h | 62 ++++++++++ arch/arm64/kvm/hyp/nvhe/hyp-main.c | 10 ++ arch/arm64/kvm/hyp/nvhe/tlb.c | 54 +++++++++ arch/arm64/kvm/hyp/pgtable.c | 143 +++++++++++++++++++++-- arch/arm64/kvm/hyp/vhe/tlb.c | 32 +++++ arch/arm64/kvm/mmu.c | 168 ++++++++++++++++++++++----- 9 files changed, 466 insertions(+), 38 deletions(-)--
2.39.0.314.g84b9a713c41-goog