mm / virtio: Provide support for unused page reporting
Subsystems (8)
v11 cover mm / virtio: Provide support for unused page reporting
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.
In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "reported_boundary" pointer. This pointer is used by the get_unreported_pages iterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modified add_to_free_list_tail so that it will not insert pages behind the reported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.
If another process needs to perform a massive manipulation of the free list, such as compaction, it can either reset a given individual boundary which will push the boundary back to the list_head, or it can clear the bit indicating the zone is actively processing which will result in the reporting process resetting all of the boundaries for a given zone.
I am leaving a number of things hard-coded such as limiting the lowest order processed to pageblock_order, and have left it up to the guest to determine what the limit is on how many pages it wants to allocate to process the hints. The upper limit for this is based on the size of the queue used to store the scatterlist.
I wanted to avoid gaming the performance testing for this. As far as possible gain a significant performance improvement should be visible in cases where guests are forced to write/read from swap. As such, testing it would be more of a benchmark of copying a page from swap versus just allocating a zero page. I have been verifying that the memory is being freed using memhog to allocate all the memory on the guest, and then watching /proc/meminfo to verify the host sees the memory returned after the test completes.
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16 vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
For info on earlier versions you will need to follow the links provided with the respective versions.
Changes from v9:
https://lore.kernel.org/lkml/[email protected]/
Updated cover page
Dropped per-cpu page randomization entropy patch
Added "to_tail" boolean value to __free_one_page to improve readability Renamed __shuffle_pick_tail to shuffle_pick_tail, avoiding extra inline function Dropped arm64 HUGLE_TLB_ORDER movement patch since it is no longer needed Significant rewrite of page reporting functionality
Updated logic to support interruptions from compaction get_unreported_page will now walk through reported sections
Moved free_list manipulators out of mmzone.h and into page_alloc.c Removed page_reporting.h include from mmzone.h
Split page_reporting.h between include/linux/ and mm/
Added #include <asm/pgtable.h>" to mm/page_reporting.h
Renamed page_reporting_startup/shutdown to page_reporting_register/unregister
Updated comments related to virtio page poison tracking feature
Changes from v10:
https://lore.kernel.org/lkml/[email protected]/
Rebased on "Add linux-next specific files for 20190930"
Added page_is_reported() macro to prevent unneeded testing of PageReported bit Fixed several spots where comments referred to older aeration naming Set upper limit for phdev->capacity to page reporting high water mark Updated virtio page poison detection logic to also cover init_on_free Tweaked page_reporting_notify_free to reduce code size
Removed dead code in non-reporting path
---
Alexander Duyck (6):
mm: Adjust shuffle code to allow for future coalescing
mm: Use zone and order instead of free area in free_list manipulators
mm: Introduce Reported pages
mm: Add device side and notifier for unused page reporting
virtio-balloon: Pull page poisoning config out of free page hinting
virtio-balloon: Add support for providing unused page reports to host
drivers/virtio/Kconfig | 1 drivers/virtio/virtio_balloon.c | 88 ++++++++- include/linux/mmzone.h | 60 ++---- include/linux/page-flags.h | 11 + include/linux/page_reporting.h | 31 +++ include/uapi/linux/virtio_balloon.h | 1 mm/Kconfig | 11 + mm/Makefile | 1 mm/compaction.c | 5 + mm/memory_hotplug.c | 2 mm/page_alloc.c | 194 +++++++++++++++---- mm/page_reporting.c | 350 +++++++++++++++++++++++++++++++++++ mm/page_reporting.h | 225 +++++++++++++++++++++++ mm/shuffle.c | 12 + mm/shuffle.h | 6 + 15 files changed, 896 insertions(+), 102 deletions(-) create mode 100644 include/linux/page_reporting.h create mode 100644 mm/page_reporting.c create mode 100644 mm/page_reporting.h
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH v11 1/6 mm: Adjust shuffle code to allow for future coalescing
From: Alexander Duyck <[email protected]>
Move the head/tail adding logic out of the shuffle code and into the __free_one_page function since ultimately that is where it is really needed anyway. By doing this we should be able to reduce the overhead and can consolidate all of the list addition bits in one spot.
--- include/linux/mmzone.h | 12 -------- mm/page_alloc.c | 71 ++++++++++++++++++++++++++++-------------------- mm/shuffle.c | 12 ++++---- mm/shuffle.h | 6 ++++ 4 files changed, 54 insertions(+), 47 deletions(-)
include/linux/mmzone.h +0 -12
@@ -116,18 +116,6 @@ static inline void add_to_free_area_tail(struct page *page, struct free_area *ar area->nr_free++; } -#ifdef CONFIG_SHUFFLE_PAGE_ALLOCATOR -/* Used to preserve page allocation order entropy */ -void add_to_free_area_random (struct page *page,struct free_area *area, -int migratetype); -#else -static inline void add_to_free_area_random (struct page *page, -struct free_area *area,int migratetype) -{ -add_to_free_area (page, area, migratetype); -} -#endif -/* Used for pages which are on another list */ static inline void move_to_free_area (struct page *page,struct free_area *area,int migratetype)
mm/page_alloc.c +42 -29
94 lines not on this page · raw message
mm/shuffle.c +6 -6
@@ -183,11 +183,11 @@ void __meminit __shuffle_free_memory(pg_data_t *pgdat)shuffle_zone (z); } -void add_to_free_area_random (struct page *page,struct free_area *area, -int migratetype) +bool shuffle_pick_tail (void ) {static u64 rand;static u8 rand_bits; +bool ret;/* * The lack of locking is deliberate. If 2 threads race to
@@ -198,10 +198,10 @@ void add_to_free_area_random(struct page *page, struct free_area *area, rand =get_random_u64 (); } -if (rand &1 ) -add_to_free_area (page, area, migratetype); -else -add_to_free_area_tail (page, area, migratetype); + ret = rand &1 ; + rand_bits--; rand >>=1 ; + +return ret; }
mm/shuffle.h +6 -0
@@ -22,6 +22,7 @@ enum mm_shuffle_ctl {DECLARE_STATIC_KEY_FALSE (page_alloc_shuffle_key);extern void page_alloc_shuffle (enum mm_shuffle_ctl ctl);extern void __shuffle_free_memory (pg_data_t *pgdat); +extern bool shuffle_pick_tail (void );static inline void shuffle_free_memory (pg_data_t *pgdat) {if (!static_branch_unlikely (&page_alloc_shuffle_key))
@@ -44,6 +45,11 @@ static inline bool is_shuffle_order(int order) return order >= SHUFFLE_ORDER; }#else +static inline bool shuffle_pick_tail (void ) +{ +return false; +} +static inline void shuffle_free_memory (pg_data_t *pgdat) { }
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH v11 2/6 mm: Use zone and order instead of free area in free_list manipulators
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
In order to enable the use of the zone from the list manipulator functions I will need access to the zone pointer. As it turns out most of the accessors were always just being directly passed &zone->free_area[order] anyway so it would make sense to just fold that into the function itself and pass the zone and order as arguments instead of the free area.
In order to be able to reference the zone we need to move the declaration of the functions down so that we have the zone defined before we define the list manipulation functions. Since the functions are only used in the file mm/page_alloc.c we can just move them there to reduce noise in the header.
--- include/linux/mmzone.h | 32 ----------------------- mm/page_alloc.c | 68 +++++++++++++++++++++++++++++++++++------------- 2 files changed, 49 insertions(+), 51 deletions(-)
include/linux/mmzone.h +0 -32
@@ -100,29 +100,6 @@ struct free_area {unsigned long nr_free; }; -/* Used for pages not on another list */ -static inline void add_to_free_area (struct page *page,struct free_area *area, -int migratetype) -{ -list_add (&page->lru, &area->free_list[migratetype]); - area->nr_free++; -} - -/* Used for pages not on another list */ -static inline void add_to_free_area_tail (struct page *page,struct free_area *area, -int migratetype) -{ -list_add_tail (&page->lru, &area->free_list[migratetype]); - area->nr_free++; -} - -/* Used for pages which are on another list */ -static inline void move_to_free_area (struct page *page,struct free_area *area, -int migratetype) -{ -list_move (&page->lru, &area->free_list[migratetype]); -} -static inline struct page *get_page_from_free_area (struct free_area *area,int migratetype) {
@@ -130,15 +107,6 @@ static inline struct page *get_page_from_free_area(struct free_area *area, struct page, lru); } -static inline void del_page_from_free_area (struct page *page, -struct free_area *area) -{ -list_del (&page->lru); -__ClearPageBuddy (page); -set_page_private (page,0 ); - area->nr_free--; -} -static inline bool free_area_empty (struct free_area *area,int migratetype) {return list_empty (&area->free_list[migratetype]);
mm/page_alloc.c +49 -19
163 lines not on this page · raw message
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
kernel test robot
build bot[mm] 2eca680594: will-it-scale.per_process_ops -2.5% regression
FYI, we noticed a -2.5% regression of will-it-scale.per_process_ops due to commit:
Greeting,
FYI, we noticed a -2.5% regression of will-it-scale.per_process_ops due to commit:
commit: 2eca680594818153ac6a1be3ad8e964184169bf2 ("[PATCH v11 2/6] mm: Use zone and order instead of free area in free_list manipulators")
url: https://github.com/0day-ci/linux/commits/Alexander-Duyck/mm-virtio-Provide-support-for-unused-page-reporting/20191002-024207
in testcase: will-it-scale
on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 128G memory with following parameters:
nr_task: 100% mode: process test: page_fault2 cpufreq_governor: performance ucode: 0xb000038
test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two.
test-url: https://github.com/antonblanchard/will-it-scale
If you fix the issue, kindly add following tag
Details are as below:
-------------------------------------------------------------------------------------------------->
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
=========================================================================================
compiler/cpufreq_governor/kconfig/mode/nr_task/rootfs/tbox_group/test/testcase/ucode:
gcc-7/performance/x86_64-rhel-7.6/process/100%/debian-x86_64-2019-09-23.cgz/lkp-bdw-ep6/page_fault2/will-it-scale/0xb000038
commit:
2f16feee6a ("mm: Adjust shuffle code to allow for future coalescing") 2eca680594 ("mm: Use zone and order instead of free area in free_list manipulators")
2f16feee6a912d6b 2eca680594818153ac6a1be3ad8
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
3:4 -2% 2:4 perf-profile.self.cycles-pp.error_entry
%stddev %change %stddev
\ | \
84981 -2.5% 82888 will-it-scale.per_process_ops
7478397 -2.5% 7294217 will-it-scale.workload
614224 ± 3% -8.7% 560976 ± 4% meminfo.DirectMap4k
0.00 ± 86% +0.0 0.00 ± 27% mpstat.cpu.all.soft%
8560 ± 99% -99.4% 51.25 ± 13% numa-numastat.node1.other_node
1331 ± 45% +791.3% 11867 ± 87% turbostat.C1
43.50 +3.1% 44.85 boot-time.boot
3387 +4.0% 3523 boot-time.idle
109720 ± 11% +237.3% 370072 ± 95% cpuidle.C1.time
5131 ± 10% +178.3% 14281 ± 76% cpuidle.C1.usage
13736 ± 3% -7.7% 12672 numa-vmstat.node0.nr_slab_reclaimable
10240 ± 5% +10.2% 11280 numa-vmstat.node1.nr_slab_reclaimable
54947 ± 3% -7.8% 50687 ± 2% numa-meminfo.node0.KReclaimable
54947 ± 3% -7.8% 50687 ± 2% numa-meminfo.node0.SReclaimable
40956 ± 5% +10.2% 45122 numa-meminfo.node1.KReclaimable
40956 ± 5% +10.2% 45122 numa-meminfo.node1.SReclaimable
2.256e+09 -2.4% 2.202e+09 proc-vmstat.numa_hit
2.256e+09 -2.4% 2.202e+09 proc-vmstat.numa_local
2.258e+09 -2.4% 2.203e+09 proc-vmstat.pgalloc_normal
2.249e+09 -2.4% 2.195e+09 proc-vmstat.pgfault
2.255e+09 -2.4% 2.202e+09 proc-vmstat.pgfree
148.70 ± 8% -23.7% 113.47 ± 12% sched_debug.cfs_rq:/.nr_spread_over.stddev
-62259 -195.9% 59734 ± 38% sched_debug.cfs_rq:/.spread0.avg
68724 ± 31% +174.2% 188414 ± 12% sched_debug.cfs_rq:/.spread0.max
650.62 ± 13% +21.0% 787.54 ± 6% sched_debug.cfs_rq:/.util_avg.min
77.78 ± 21% -31.8% 53.07 ± 9% sched_debug.cfs_rq:/.util_avg.stddev
40.08 ± 36% -66.7% 13.33 ±107% sched_debug.cfs_rq:/.util_est_enqueued.min
266102 ± 49% -60.6% 104930 ± 2% sched_debug.cpu.avg_idle.stddev
22597 ± 8% -27.9% 16297 ± 10% sched_debug.cpu.nr_switches.max
3715 ± 2% -19.5% 2992 ± 7% sched_debug.cpu.nr_switches.stddev
19360 ± 10% -31.3% 13306 ± 9% sched_debug.cpu.sched_count.max
3208 ± 4% -24.6% 2420 ± 9% sched_debug.cpu.sched_count.stddev
2.21 ± 84% +117.0% 4.79 ± 14% sched_debug.cpu.sched_goidle.min
9763 ± 13% -37.4% 6112 ± 13% sched_debug.cpu.ttwu_count.max
1549 ± 5% -27.3% 1126 ± 10% sched_debug.cpu.ttwu_count.stddev
9112 ± 10% -37.9% 5657 ± 14% sched_debug.cpu.ttwu_local.max
1443 ± 3% -29.6% 1015 ± 12% sched_debug.cpu.ttwu_local.stddev
199.25 ± 22% +34.6% 268.25 ± 36% interrupts.36:IR-PCI-MSI.1572867-edge.eth0-TxRx-2
199.25 ± 22% +34.6% 268.25 ± 36% interrupts.CPU15.36:IR-PCI-MSI.1572867-edge.eth0-TxRx-2
47.25 ± 59% +475.1% 271.75 ± 48% interrupts.CPU17.RES:Rescheduling_interrupts
59.75 ± 61% +148.1% 148.25 ± 31% interrupts.CPU18.RES:Rescheduling_interrupts
35.00 ± 93% +406.4% 177.25 ± 47% interrupts.CPU19.RES:Rescheduling_interrupts
2910 ± 3% +9.7% 3192 ± 8% interrupts.CPU2.CAL:Function_call_interrupts
33.50 ±115% +410.4% 171.00 ± 58% interrupts.CPU21.RES:Rescheduling_interrupts
3033 ± 4% +17.3% 3557 ± 8% interrupts.CPU22.CAL:Function_call_interrupts
2965 ± 6% +13.9% 3379 ± 5% interrupts.CPU27.CAL:Function_call_interrupts
202.75 ± 34% -50.8% 99.75 ± 49% interrupts.CPU28.RES:Rescheduling_interrupts
134.00 ± 32% +243.8% 460.75 ± 92% interrupts.CPU31.RES:Rescheduling_interrupts
90.25 ±108% +467.6% 512.25 ± 91% interrupts.CPU44.RES:Rescheduling_interrupts
454.75 ± 74% -78.4% 98.25 ± 82% interrupts.CPU49.RES:Rescheduling_interrupts
4916 ± 34% +60.4% 7885 interrupts.CPU55.NMI:Non-maskable_interrupts
4916 ± 34% +60.4% 7885 interrupts.CPU55.PMI:Performance_monitoring_interrupts
33.25 ±110% +273.7% 124.25 ± 27% interrupts.CPU61.RES:Rescheduling_interrupts
8.00 ± 81% +2500.0% 208.00 ± 97% interrupts.CPU65.RES:Rescheduling_interrupts
105.25 ±114% +368.2% 492.75 ± 64% interrupts.CPU69.RES:Rescheduling_interrupts
224.00 ± 50% -76.2% 53.25 ±121% interrupts.CPU70.RES:Rescheduling_interrupts
41976580 -4.3% 40191219 perf-stat.i.branch-misses
4.657e+08 -3.1% 4.511e+08 ± 2% perf-stat.i.cache-misses
1.446e+09 -3.3% 1.398e+09 perf-stat.i.cache-references
540.00 +203.9% 1641 ±114% perf-stat.i.cycles-between-cache-misses
72449681 -3.7% 69791647 ± 2% perf-stat.i.dTLB-store-misses
6.748e+09 -3.7% 6.499e+09 perf-stat.i.dTLB-stores
15000441 -3.3% 14499685 perf-stat.i.iTLB-load-misses
48416 ± 8% -30.9% 33446 ± 36% perf-stat.i.iTLB-loads
7390548 -3.4% 7136366 ± 2% perf-stat.i.minor-faults
1.31e+08 -4.1% 1.256e+08 perf-stat.i.node-loads
866429 -5.4% 819527 perf-stat.i.node-store-misses
32410281 -5.1% 30770659 perf-stat.i.node-stores
7390641 -3.4% 7136212 ± 2% perf-stat.i.page-faults
21.34 -2.1% 20.90 perf-stat.overall.MPKI
0.28 -0.0 0.27 perf-stat.overall.branch-miss-rate%
521.95 +2.1% 532.97 perf-stat.overall.cycles-between-cache-misses
4515 +2.1% 4612 perf-stat.overall.instructions-per-iTLB-miss
2752428 +2.3% 2816574 perf-stat.overall.path-length
41829479 -4.2% 40062021 perf-stat.ps.branch-misses
4.641e+08 -3.1% 4.498e+08 perf-stat.ps.cache-misses
1.441e+09 -3.3% 1.394e+09 perf-stat.ps.cache-references
72196133 -3.6% 69580505 ± 2% perf-stat.ps.dTLB-store-misses
6.724e+09 -3.6% 6.479e+09 perf-stat.ps.dTLB-stores
14947871 -3.3% 14455433 perf-stat.ps.iTLB-load-misses
48333 ± 7% -31.0% 33349 ± 36% perf-stat.ps.iTLB-loads
7365449 -3.4% 7115485 perf-stat.ps.minor-faults
1.305e+08 -4.0% 1.253e+08 perf-stat.ps.node-loads
863374 -5.4% 817033 perf-stat.ps.node-store-misses
32297524 -5.0% 30677371 perf-stat.ps.node-stores
7365171 -3.4% 7115053 perf-stat.ps.page-faults
8.09 -1.3 6.82 perf-profile.calltrace.cycles-pp.finish_fault.__handle_mm_fault.handle_mm_fault.__do_page_fault.do_page_fault
7.99 -1.3 6.73 perf-profile.calltrace.cycles-pp.alloc_set_pte.finish_fault.__handle_mm_fault.handle_mm_fault.__do_page_fault
5.97 -1.2 4.74 perf-profile.calltrace.cycles-pp.__lru_cache_add.alloc_set_pte.finish_fault.__handle_mm_fault.handle_mm_fault
5.87 -1.2 4.64 perf-profile.calltrace.cycles-pp.pagevec_lru_move_fn.__lru_cache_add.alloc_set_pte.finish_fault.__handle_mm_fault
4.59 -1.2 3.40 ± 2% perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock_irqsave.pagevec_lru_move_fn.__lru_cache_add.alloc_set_pte
4.62 -1.2 3.44 perf-profile.calltrace.cycles-pp._raw_spin_lock_irqsave.pagevec_lru_move_fn.__lru_cache_add.alloc_set_pte.finish_fault
56.80 -0.7 56.09 perf-profile.calltrace.cycles-pp.__do_page_fault.do_page_fault.page_fault
55.72 -0.7 55.02 perf-profile.calltrace.cycles-pp.handle_mm_fault.__do_page_fault.do_page_fault.page_fault
57.16 -0.7 56.45 perf-profile.calltrace.cycles-pp.do_page_fault.page_fault
57.26 -0.7 56.56 perf-profile.calltrace.cycles-pp.page_fault
55.27 -0.7 54.57 perf-profile.calltrace.cycles-pp.__handle_mm_fault.handle_mm_fault.__do_page_fault.do_page_fault.page_fault
2.15 ± 2% -0.5 1.65 ± 3% perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock_irqsave.release_pages.tlb_flush_mmu.unmap_page_range
2.16 ± 2% -0.5 1.67 ± 3% perf-profile.calltrace.cycles-pp._raw_spin_lock_irqsave.release_pages.tlb_flush_mmu.unmap_page_range.unmap_vmas
8.78 -0.2 8.59 perf-profile.calltrace.cycles-pp.copy_user_highpage.__handle_mm_fault.handle_mm_fault.__do_page_fault.do_page_fault
8.66 -0.2 8.48 perf-profile.calltrace.cycles-pp.copy_page.copy_user_highpage.__handle_mm_fault.handle_mm_fault.__do_page_fault
0.93 -0.0 0.90 perf-profile.calltrace.cycles-pp.__pagevec_lru_add_fn.pagevec_lru_move_fn.__lru_cache_add.alloc_set_pte.finish_fault
4.11 +0.1 4.17 perf-profile.calltrace.cycles-pp.release_pages.tlb_flush_mmu.tlb_finish_mmu.unmap_region.__do_munmap
4.15 +0.1 4.22 perf-profile.calltrace.cycles-pp.tlb_finish_mmu.unmap_region.__do_munmap.__vm_munmap.__x64_sys_munmap
4.13 +0.1 4.20 perf-profile.calltrace.cycles-pp.tlb_flush_mmu.tlb_finish_mmu.unmap_region.__do_munmap.__vm_munmap
3.72 +0.1 3.85 perf-profile.calltrace.cycles-pp.free_unref_page_list.release_pages.tlb_flush_mmu.tlb_finish_mmu.unmap_region
3.66 +0.1 3.79 perf-profile.calltrace.cycles-pp.free_pcppages_bulk.free_unref_page_list.release_pages.tlb_flush_mmu.tlb_finish_mmu
33.34 +0.7 34.03 perf-profile.calltrace.cycles-pp.unmap_vmas.unmap_region.__do_munmap.__vm_munmap.__x64_sys_munmap
33.34 +0.7 34.02 perf-profile.calltrace.cycles-pp.unmap_page_range.unmap_vmas.unmap_region.__do_munmap.__vm_munmap
32.04 +0.7 32.76 perf-profile.calltrace.cycles-pp.tlb_flush_mmu.unmap_page_range.unmap_vmas.unmap_region.__do_munmap
31.80 +0.7 32.52 perf-profile.calltrace.cycles-pp.release_pages.tlb_flush_mmu.unmap_page_range.unmap_vmas.unmap_region
37.53 +0.8 38.28 perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe
37.53 +0.8 38.28 perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe
37.50 +0.8 38.26 perf-profile.calltrace.cycles-pp.unmap_region.__do_munmap.__vm_munmap.__x64_sys_munmap.do_syscall_64
37.50 +0.8 38.26 perf-profile.calltrace.cycles-pp.__x64_sys_munmap.do_syscall_64.entry_SYSCALL_64_after_hwframe
37.50 +0.8 38.26 perf-profile.calltrace.cycles-pp.__do_munmap.__vm_munmap.__x64_sys_munmap.do_syscall_64.entry_SYSCALL_64_after_hwframe
37.50 +0.8 38.26 perf-profile.calltrace.cycles-pp.__vm_munmap.__x64_sys_munmap.do_syscall_64.entry_SYSCALL_64_after_hwframe
35.45 +0.8 36.22 perf-profile.calltrace.cycles-pp.alloc_pages_vma.__handle_mm_fault.handle_mm_fault.__do_page_fault.do_page_fault
34.73 +0.8 35.50 perf-profile.calltrace.cycles-pp.get_page_from_freelist.__alloc_pages_nodemask.alloc_pages_vma.__handle_mm_fault.handle_mm_fault
35.13 +0.8 35.91 perf-profile.calltrace.cycles-pp.__alloc_pages_nodemask.alloc_pages_vma.__handle_mm_fault.handle_mm_fault.__do_page_fault
32.89 +0.8 33.70 perf-profile.calltrace.cycles-pp._raw_spin_lock.get_page_from_freelist.__alloc_pages_nodemask.alloc_pages_vma.__handle_mm_fault
32.80 +0.8 33.61 perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock.get_page_from_freelist.__alloc_pages_nodemask.alloc_pages_vma
28.87 +1.2 30.10 perf-profile.calltrace.cycles-pp.free_unref_page_list.release_pages.tlb_flush_mmu.unmap_page_range.unmap_vmas
28.36 +1.2 29.61 perf-profile.calltrace.cycles-pp.free_pcppages_bulk.free_unref_page_list.release_pages.tlb_flush_mmu.unmap_page_range
30.85 +1.4 32.26 perf-profile.calltrace.cycles-pp._raw_spin_lock.free_pcppages_bulk.free_unref_page_list.release_pages.tlb_flush_mmu
30.77 +1.4 32.18 perf-profile.calltrace.cycles-pp.native_queued_spin_lock_slowpath._raw_spin_lock.free_pcppages_bulk.free_unref_page_list.release_pages
7.09 -1.8 5.33 ± 2% perf-profile.children.cycles-pp._raw_spin_lock_irqsave
8.09 -1.3 6.83 perf-profile.children.cycles-pp.finish_fault
8.03 -1.3 6.77 perf-profile.children.cycles-pp.alloc_set_pte
5.89 -1.2 4.65 perf-profile.children.cycles-pp.pagevec_lru_move_fn
5.98 -1.2 4.75 perf-profile.children.cycles-pp.__lru_cache_add
56.83 -0.7 56.11 perf-profile.children.cycles-pp.__do_page_fault
55.76 -0.7 55.05 perf-profile.children.cycles-pp.handle_mm_fault
57.16 -0.7 56.46 perf-profile.children.cycles-pp.do_page_fault
57.30 -0.7 56.60 perf-profile.children.cycles-pp.page_fault
55.30 -0.7 54.60 perf-profile.children.cycles-pp.__handle_mm_fault
8.78 -0.2 8.59 perf-profile.children.cycles-pp.copy_user_highpage
8.69 -0.2 8.51 perf-profile.children.cycles-pp.copy_page
0.41 -0.0 0.39 perf-profile.children.cycles-pp.__mod_lruvec_state
4.16 +0.1 4.22 perf-profile.children.cycles-pp.tlb_finish_mmu
70.71 +0.5 71.19 perf-profile.children.cycles-pp.native_queued_spin_lock_slowpath
33.34 +0.7 34.03 perf-profile.children.cycles-pp.unmap_vmas
33.34 +0.7 34.03 perf-profile.children.cycles-pp.unmap_page_range
37.61 +0.7 38.36 perf-profile.children.cycles-pp.entry_SYSCALL_64_after_hwframe
37.61 +0.7 38.36 perf-profile.children.cycles-pp.do_syscall_64
37.50 +0.8 38.26 perf-profile.children.cycles-pp.__do_munmap
37.50 +0.8 38.26 perf-profile.children.cycles-pp.__vm_munmap
37.50 +0.8 38.26 perf-profile.children.cycles-pp.unmap_region
37.50 +0.8 38.26 perf-profile.children.cycles-pp.__x64_sys_munmap
35.47 +0.8 36.25 perf-profile.children.cycles-pp.alloc_pages_vma
34.87 +0.8 35.65 perf-profile.children.cycles-pp.get_page_from_freelist
36.18 +0.8 36.96 perf-profile.children.cycles-pp.tlb_flush_mmu
36.03 +0.8 36.82 perf-profile.children.cycles-pp.release_pages
35.25 +0.8 36.04 perf-profile.children.cycles-pp.__alloc_pages_nodemask
32.62 +1.4 34.00 perf-profile.children.cycles-pp.free_unref_page_list
32.04 +1.4 33.44 perf-profile.children.cycles-pp.free_pcppages_bulk
64.81 +2.2 67.01 perf-profile.children.cycles-pp._raw_spin_lock
8.65 -0.2 8.46 perf-profile.self.cycles-pp.copy_page
0.94 -0.0 0.89 perf-profile.self.cycles-pp.get_page_from_freelist
1.13 -0.0 1.10 perf-profile.self.cycles-pp._raw_spin_lock
70.71 +0.5 71.19 perf-profile.self.cycles-pp.native_queued_spin_lock_slowpathwill-it-scale.per_process_ops
90000 +-+-----------------------------------------------------------------+
O..O.O..O.O..O..O.O..O..O.O..O O O..O O O.O O O.O..O..O.O..O.+..|
80000 +-+ : : : : : : |
70000 +-+ : : : : : : |
| : : : : : : |
60000 +-+ : : : : : : |
50000 +-+ : : : : : : |
| : : : : : : |
40000 +-+ : : : : : : |
30000 +-+ : : : : : : |
| : : : : : : |
20000 +-+ :: :: : : |
10000 +-+ : : : |
| : : : |
0 +-+-----------------------------------------------------------------+
will-it-scale.workload 8e+06 +-+-----------------------------------------------------------------+
O..O.O..O.O..O..O.O..O..O.O..O O O..O O O.O O O.O..O..O.O..O.+..|
7e+06 +-+ : : : : : : |
6e+06 +-+ : : : : : : |
| : : : : : : |
5e+06 +-+ : : : : : : |
| : : : : : : |
4e+06 +-+ : : : : : : |
| : : : : : : |
3e+06 +-+ : : : : : : |
2e+06 +-+ : : : : : : |
| :: :: : : |
1e+06 +-+ : : : |
| : : : |
0 +-+-----------------------------------------------------------------+ [*] bisect-good sample
[O] bisect-bad sample
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided for informational purposes only. Any difference in system hardware or software design or configuration may affect actual performance.
Thanks,
Rong Chen
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 5.4.0-rc1 Kernel Configuration
#
#
# Compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
#CONFIG_CC_IS_GCC=yCONFIG_GCC_VERSION=70400CONFIG_CLANG_VERSION=0CONFIG_CC_CAN_LINK=yCONFIG_CC_HAS_ASM_GOTO=yCONFIG_CC_HAS_ASM_INLINE=yCONFIG_CC_HAS_WARN_MAYBE_UNINITIALIZED=yCONFIG_IRQ_WORK=yCONFIG_BUILDTIME_EXTABLE_SORT=yCONFIG_THREAD_INFO_IN_TASK=y
#
# General setup
#CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
# CONFIG_HEADER_TEST is not setCONFIG_LOCALVERSION=""CONFIG_LOCALVERSION_AUTO=yCONFIG_BUILD_SALT=""CONFIG_HAVE_KERNEL_GZIP=yCONFIG_HAVE_KERNEL_BZIP2=yCONFIG_HAVE_KERNEL_LZMA=yCONFIG_HAVE_KERNEL_XZ=yCONFIG_HAVE_KERNEL_LZO=yCONFIG_HAVE_KERNEL_LZ4=yCONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not setCONFIG_DEFAULT_HOSTNAME="(none)"CONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSVIPC_SYSCTL=yCONFIG_POSIX_MQUEUE=yCONFIG_POSIX_MQUEUE_SYSCTL=yCONFIG_CROSS_MEMORY_ATTACH=yCONFIG_USELIB=yCONFIG_AUDIT=yCONFIG_HAVE_ARCH_AUDITSYSCALL=yCONFIG_AUDITSYSCALL=y
#
# IRQ subsystem
#CONFIG_GENERIC_IRQ_PROBE=yCONFIG_GENERIC_IRQ_SHOW=yCONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=yCONFIG_GENERIC_PENDING_IRQ=yCONFIG_GENERIC_IRQ_MIGRATION=yCONFIG_IRQ_DOMAIN=yCONFIG_IRQ_SIM=yCONFIG_IRQ_DOMAIN_HIERARCHY=yCONFIG_GENERIC_MSI_IRQ=yCONFIG_GENERIC_MSI_IRQ_DOMAIN=yCONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=yCONFIG_GENERIC_IRQ_RESERVATION_MODE=yCONFIG_IRQ_FORCED_THREADING=yCONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem
CONFIG_CLOCKSOURCE_WATCHDOG=yCONFIG_ARCH_CLOCKSOURCE_DATA=yCONFIG_ARCH_CLOCKSOURCE_INIT=yCONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=yCONFIG_GENERIC_TIME_VSYSCALL=yCONFIG_GENERIC_CLOCKEVENTS=yCONFIG_GENERIC_CLOCKEVENTS_BROADCAST=yCONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=yCONFIG_GENERIC_CMOS_UPDATE=y
#
# Timers subsystem
#CONFIG_TICK_ONESHOT=yCONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
# CONFIG_NO_HZ_IDLE is not setCONFIG_NO_HZ_FULL=yCONFIG_CONTEXT_TRACKING=y
# CONFIG_CONTEXT_TRACKING_FORCE is not setCONFIG_NO_HZ=yCONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem
# CONFIG_PREEMPT_NONE is not setCONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not setCONFIG_PREEMPT_COUNT=y
#
# 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=yCONFIG_BSD_PROCESS_ACCT=yCONFIG_BSD_PROCESS_ACCT_V3=yCONFIG_TASKSTATS=yCONFIG_TASK_DELAY_ACCT=yCONFIG_TASK_XACCT=yCONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
CONFIG_CPU_ISOLATION=y
#
# RCU Subsystem
#CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not setCONFIG_SRCU=yCONFIG_TREE_SRCU=yCONFIG_TASKS_RCU=yCONFIG_RCU_STALL_COMMON=yCONFIG_RCU_NEED_SEGCBLIST=yCONFIG_RCU_NOCB_CPU=y
# end of RCU Subsystem
CONFIG_BUILD_BIN2C=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS is not setCONFIG_LOG_BUF_SHIFT=20CONFIG_LOG_CPU_MAX_BUF_SHIFT=12CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
#
# Scheduler features
#
# end of Scheduler features
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=yCONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=yCONFIG_ARCH_SUPPORTS_INT128=yCONFIG_NUMA_BALANCING=yCONFIG_NUMA_BALANCING_DEFAULT_ENABLED=yCONFIG_CGROUPS=yCONFIG_PAGE_COUNTER=yCONFIG_MEMCG=yCONFIG_MEMCG_SWAP=yCONFIG_MEMCG_SWAP_ENABLED=yCONFIG_MEMCG_KMEM=yCONFIG_BLK_CGROUP=yCONFIG_CGROUP_WRITEBACK=yCONFIG_CGROUP_SCHED=yCONFIG_FAIR_GROUP_SCHED=yCONFIG_CFS_BANDWIDTH=yCONFIG_RT_GROUP_SCHED=yCONFIG_CGROUP_PIDS=yCONFIG_CGROUP_RDMA=yCONFIG_CGROUP_FREEZER=yCONFIG_CGROUP_HUGETLB=yCONFIG_CPUSETS=yCONFIG_PROC_PID_CPUSET=yCONFIG_CGROUP_DEVICE=yCONFIG_CGROUP_CPUACCT=yCONFIG_CGROUP_PERF=yCONFIG_CGROUP_BPF=y
# CONFIG_CGROUP_DEBUG is not setCONFIG_SOCK_CGROUP_DATA=yCONFIG_NAMESPACES=yCONFIG_UTS_NS=yCONFIG_IPC_NS=yCONFIG_USER_NS=yCONFIG_PID_NS=yCONFIG_NET_NS=yCONFIG_CHECKPOINT_RESTORE=yCONFIG_SCHED_AUTOGROUP=y
# CONFIG_SYSFS_DEPRECATED is not setCONFIG_RELAY=yCONFIG_BLK_DEV_INITRD=yCONFIG_INITRAMFS_SOURCE=""CONFIG_RD_GZIP=yCONFIG_RD_BZIP2=yCONFIG_RD_LZMA=yCONFIG_RD_XZ=yCONFIG_RD_LZO=yCONFIG_RD_LZ4=yCONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_SYSCTL=yCONFIG_HAVE_UID16=yCONFIG_SYSCTL_EXCEPTION_TRACE=yCONFIG_HAVE_PCSPKR_PLATFORM=yCONFIG_BPF=yCONFIG_EXPERT=yCONFIG_UID16=yCONFIG_MULTIUSER=yCONFIG_SGETMASK_SYSCALL=yCONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not setCONFIG_FHANDLE=yCONFIG_POSIX_TIMERS=yCONFIG_PRINTK=yCONFIG_PRINTK_NMI=yCONFIG_BUG=yCONFIG_ELF_CORE=yCONFIG_PCSPKR_PLATFORM=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_FUTEX_PI=yCONFIG_EPOLL=yCONFIG_SIGNALFD=yCONFIG_TIMERFD=yCONFIG_EVENTFD=yCONFIG_SHMEM=yCONFIG_AIO=yCONFIG_IO_URING=yCONFIG_ADVISE_SYSCALLS=yCONFIG_MEMBARRIER=yCONFIG_KALLSYMS=yCONFIG_KALLSYMS_ALL=yCONFIG_KALLSYMS_ABSOLUTE_PERCPU=yCONFIG_KALLSYMS_BASE_RELATIVE=yCONFIG_BPF_SYSCALL=yCONFIG_BPF_JIT_ALWAYS_ON=yCONFIG_USERFAULTFD=yCONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=yCONFIG_RSEQ=y
# CONFIG_DEBUG_RSEQ is not setCONFIG_EMBEDDED=yCONFIG_HAVE_PERF_EVENTS=y
# CONFIG_PC104 is not set
#
# Kernel Performance Events And Counters
#CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters
CONFIG_VM_EVENT_COUNTERS=yCONFIG_SLUB_DEBUG=y
# CONFIG_SLUB_MEMCG_SYSFS_ON is not set
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not setCONFIG_SLUB=y
# CONFIG_SLOB is not setCONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not setCONFIG_SLUB_CPU_PARTIAL=yCONFIG_SYSTEM_DATA_VERIFICATION=yCONFIG_PROFILING=yCONFIG_TRACEPOINTS=y
# end of General setup
CONFIG_64BIT=yCONFIG_X86_64=yCONFIG_X86=yCONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=yCONFIG_MMU=yCONFIG_ARCH_MMAP_RND_BITS_MIN=28 CONFIG_ARCH_MMAP_RND_BITS_MAX=32 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_FILTER_PGPROT=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=yCONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_HAVE_INTEL_TXT=yCONFIG_X86_64_SMP=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_DYNAMIC_PHYSICAL_MASK=y CONFIG_PGTABLE_LEVELS=5 CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
#
# Processor type and features
#CONFIG_ZONE_DMA=yCONFIG_SMP=yCONFIG_X86_FEATURE_NAMES=yCONFIG_X86_X2APIC=yCONFIG_X86_MPPARSE=y
# CONFIG_GOLDFISH is not setCONFIG_RETPOLINE=yCONFIG_X86_CPU_RESCTRL=yCONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_NUMACHIP is not set
# CONFIG_X86_VSMP is not setCONFIG_X86_UV=y
# CONFIG_X86_GOLDFISH is not set
# CONFIG_X86_INTEL_MID is not setCONFIG_X86_INTEL_LPSS=yCONFIG_X86_AMD_PLATFORM_DEVICE=yCONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not setCONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not setCONFIG_HYPERVISOR_GUEST=yCONFIG_PARAVIRT=yCONFIG_PARAVIRT_XXL=y
# CONFIG_PARAVIRT_DEBUG is not setCONFIG_PARAVIRT_SPINLOCKS=yCONFIG_X86_HV_CALLBACK_VECTOR=yCONFIG_XEN=yCONFIG_XEN_PV=yCONFIG_XEN_PV_SMP=y
# CONFIG_XEN_DOM0 is not setCONFIG_XEN_PVHVM=yCONFIG_XEN_PVHVM_SMP=yCONFIG_XEN_512GB=yCONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
# CONFIG_XEN_PVH is not setCONFIG_KVM_GUEST=yCONFIG_ARCH_CPUIDLE_HALTPOLL=y
# CONFIG_PVH is not set
# CONFIG_KVM_DEBUG_FS is not setCONFIG_PARAVIRT_TIME_ACCOUNTING=yCONFIG_PARAVIRT_CLOCK=y
# CONFIG_JAILHOUSE_GUEST is not set
# CONFIG_ACRN_GUEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not setCONFIG_GENERIC_CPU=yCONFIG_X86_INTERNODE_CACHE_SHIFT=6CONFIG_X86_L1_CACHE_SHIFT=6CONFIG_X86_TSC=yCONFIG_X86_CMPXCHG64=yCONFIG_X86_CMOV=yCONFIG_X86_MINIMUM_CPU_FAMILY=64CONFIG_X86_DEBUGCTLMSR=y
# CONFIG_PROCESSOR_SELECT is not setCONFIG_CPU_SUP_INTEL=yCONFIG_CPU_SUP_AMD=yCONFIG_CPU_SUP_HYGON=yCONFIG_CPU_SUP_CENTAUR=yCONFIG_CPU_SUP_ZHAOXIN=yCONFIG_HPET_TIMER=yCONFIG_HPET_EMULATE_RTC=yCONFIG_DMI=yCONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not setCONFIG_MAXSMP=yCONFIG_NR_CPUS_RANGE_BEGIN=8192CONFIG_NR_CPUS_RANGE_END=8192CONFIG_NR_CPUS_DEFAULT=8192CONFIG_NR_CPUS=8192CONFIG_SCHED_SMT=yCONFIG_SCHED_MC=yCONFIG_SCHED_MC_PRIO=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=yCONFIG_X86_MCE=yCONFIG_X86_MCELOG_LEGACY=yCONFIG_X86_MCE_INTEL=yCONFIG_X86_MCE_AMD=yCONFIG_X86_MCE_THRESHOLD=yCONFIG_X86_MCE_INJECT=mCONFIG_X86_THERMAL_VECTOR=y
#
# Performance monitoring
#CONFIG_PERF_EVENTS_INTEL_UNCORE=yCONFIG_PERF_EVENTS_INTEL_RAPL=yCONFIG_PERF_EVENTS_INTEL_CSTATE=y
# CONFIG_PERF_EVENTS_AMD_POWER is not set
# end of Performance monitoring
CONFIG_X86_16BIT=yCONFIG_X86_ESPFIX64=y CONFIG_X86_VSYSCALL_EMULATION=yCONFIG_I8K=mCONFIG_MICROCODE=yCONFIG_MICROCODE_INTEL=yCONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=yCONFIG_X86_CPUID=yCONFIG_X86_5LEVEL=yCONFIG_X86_DIRECT_GBPAGES=y
# CONFIG_X86_CPA_STATISTICS is not set CONFIG_AMD_MEM_ENCRYPT=y
# CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is not set CONFIG_NUMA=yCONFIG_AMD_NUMA=yCONFIG_X86_64_ACPI_NUMA=y CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set CONFIG_NODES_SHIFT=10 CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_MEMORY_PROBE=y CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_X86_PMEM_LEGACY_DEVICE=y CONFIG_X86_PMEM_LEGACY=m CONFIG_X86_CHECK_BIOS_CORRUPTION=y
# CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set CONFIG_X86_RESERVE_LOW=64CONFIG_MTRR=yCONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=yCONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_ARCH_RANDOM=yCONFIG_X86_SMAP=yCONFIG_X86_INTEL_UMIP=yCONFIG_X86_INTEL_MPX=y CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y CONFIG_EFI=yCONFIG_EFI_STUB=yCONFIG_EFI_MIXED=yCONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not setCONFIG_HZ_1000=yCONFIG_HZ=1000CONFIG_SCHED_HRTICK=yCONFIG_KEXEC=yCONFIG_KEXEC_FILE=y CONFIG_ARCH_HAS_KEXEC_PURGATORY=y
# CONFIG_KEXEC_SIG is not set CONFIG_CRASH_DUMP=yCONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x1000000 CONFIG_RELOCATABLE=yCONFIG_RANDOMIZE_BASE=yCONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_DYNAMIC_MEMORY_LAYOUT=y CONFIG_RANDOMIZE_MEMORY=y CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0xa CONFIG_HOTPLUG_CPU=y CONFIG_BOOTPARAM_HOTPLUG_CPU0=y
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set CONFIG_LEGACY_VSYSCALL_EMULATE=y
# CONFIG_LEGACY_VSYSCALL_XONLY is not set
# CONFIG_LEGACY_VSYSCALL_NONE is not set
# CONFIG_CMDLINE_BOOL is not set CONFIG_MODIFY_LDT_SYSCALL=y CONFIG_HAVE_LIVEPATCH=yCONFIG_LIVEPATCH=y
# end of Processor type and features
CONFIG_ARCH_HAS_ADD_PAGES=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=yCONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=yCONFIG_USE_PERCPU_NUMA_NODE_ID=yCONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=yCONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=yCONFIG_ARCH_ENABLE_THP_MIGRATION=y
#
# Power management and ACPI options
#CONFIG_ARCH_HIBERNATION_HEADER=yCONFIG_SUSPEND=yCONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not setCONFIG_HIBERNATE_CALLBACKS=yCONFIG_HIBERNATION=yCONFIG_PM_STD_PARTITION=""CONFIG_PM_SLEEP=yCONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not setCONFIG_PM=yCONFIG_PM_DEBUG=yCONFIG_PM_ADVANCED_DEBUG=y
# CONFIG_PM_TEST_SUSPEND is not setCONFIG_PM_SLEEP_DEBUG=y
# CONFIG_DPM_WATCHDOG is not setCONFIG_PM_TRACE=yCONFIG_PM_TRACE_RTC=yCONFIG_PM_CLK=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
# CONFIG_ENERGY_MODEL is not setCONFIG_ARCH_SUPPORTS_ACPI=yCONFIG_ACPI=yCONFIG_ACPI_LEGACY_TABLES_LOOKUP=yCONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=yCONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
# CONFIG_ACPI_DEBUGGER is not setCONFIG_ACPI_SPCR_TABLE=yCONFIG_ACPI_LPIT=yCONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS_POWER is not setCONFIG_ACPI_REV_OVERRIDE_POSSIBLE=yCONFIG_ACPI_EC_DEBUGFS=mCONFIG_ACPI_AC=yCONFIG_ACPI_BATTERY=yCONFIG_ACPI_BUTTON=yCONFIG_ACPI_VIDEO=mCONFIG_ACPI_FAN=y
# CONFIG_ACPI_TAD is not setCONFIG_ACPI_DOCK=yCONFIG_ACPI_CPU_FREQ_PSS=yCONFIG_ACPI_PROCESSOR_CSTATE=yCONFIG_ACPI_PROCESSOR_IDLE=yCONFIG_ACPI_CPPC_LIB=yCONFIG_ACPI_PROCESSOR=yCONFIG_ACPI_IPMI=mCONFIG_ACPI_HOTPLUG_CPU=yCONFIG_ACPI_PROCESSOR_AGGREGATOR=mCONFIG_ACPI_THERMAL=yCONFIG_ACPI_NUMA=yCONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=yCONFIG_ACPI_TABLE_UPGRADE=y
# CONFIG_ACPI_DEBUG is not setCONFIG_ACPI_PCI_SLOT=yCONFIG_ACPI_CONTAINER=yCONFIG_ACPI_HOTPLUG_MEMORY=yCONFIG_ACPI_HOTPLUG_IOAPIC=yCONFIG_ACPI_SBS=mCONFIG_ACPI_HED=yCONFIG_ACPI_CUSTOM_METHOD=mCONFIG_ACPI_BGRT=y
# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not setCONFIG_ACPI_NFIT=m
# CONFIG_NFIT_SECURITY_DEBUG is not set
# CONFIG_ACPI_HMAT is not setCONFIG_HAVE_ACPI_APEI=yCONFIG_HAVE_ACPI_APEI_NMI=yCONFIG_ACPI_APEI=yCONFIG_ACPI_APEI_GHES=yCONFIG_ACPI_APEI_PCIEAER=yCONFIG_ACPI_APEI_MEMORY_FAILURE=yCONFIG_ACPI_APEI_EINJ=mCONFIG_ACPI_APEI_ERST_DEBUG=y
# CONFIG_DPTF_POWER is not setCONFIG_ACPI_WATCHDOG=yCONFIG_ACPI_EXTLOG=mCONFIG_ACPI_ADXL=y
# CONFIG_PMIC_OPREGION is not set
# CONFIG_ACPI_CONFIGFS is not setCONFIG_X86_PM_TIMER=yCONFIG_SFI=y
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_ATTR_SET=y CONFIG_CPU_FREQ_GOV_COMMON=y
# CONFIG_CPU_FREQ_STAT is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
# CONFIG_CPU_FREQ_GOV_SCHEDUTIL is not set
#
# CPU frequency scaling drivers
#CONFIG_X86_INTEL_PSTATE=yCONFIG_X86_PCC_CPUFREQ=mCONFIG_X86_ACPI_CPUFREQ=mCONFIG_X86_ACPI_CPUFREQ_CPB=yCONFIG_X86_POWERNOW_K8=mCONFIG_X86_AMD_FREQ_SENSITIVITY=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not setCONFIG_X86_P4_CLOCKMOD=m
#
# shared options # CONFIG_X86_SPEEDSTEP_LIB=m # end of CPU Frequency scaling
#
# CPU Idle
#CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not setCONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
# CONFIG_CPU_IDLE_GOV_HALTPOLL is not setCONFIG_HALTPOLL_CPUIDLE=y
# end of CPU Idle
CONFIG_INTEL_IDLE=y
# end of Power management and ACPI options
#
# Bus options (PCI etc.)
#CONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_XEN=yCONFIG_MMCONF_FAM10H=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
# CONFIG_ISA_BUS is not setCONFIG_ISA_DMA_API=yCONFIG_AMD_NB=y
# CONFIG_X86_SYSFB is not set
# end of Bus options (PCI etc.)
#
# Binary Emulations
#CONFIG_IA32_EMULATION=y
# CONFIG_X86_X32 is not setCONFIG_COMPAT_32=yCONFIG_COMPAT=yCONFIG_COMPAT_FOR_U64_ALIGNMENT=yCONFIG_SYSVIPC_COMPAT=y
# end of Binary Emulations
CONFIG_X86_DEV_DMA_OPS=y
#
# Firmware Drivers
#CONFIG_EDD=m
# CONFIG_EDD_OFF is not setCONFIG_FIRMWARE_MEMMAP=yCONFIG_DMIID=yCONFIG_DMI_SYSFS=yCONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=yCONFIG_ISCSI_IBFT_FIND=yCONFIG_ISCSI_IBFT=mCONFIG_FW_CFG_SYSFS=y
# CONFIG_FW_CFG_SYSFS_CMDLINE is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# EFI (Extensible Firmware Interface) Support
#CONFIG_EFI_VARS=yCONFIG_EFI_ESRT=yCONFIG_EFI_VARS_PSTORE=yCONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=yCONFIG_EFI_RUNTIME_MAP=y
# CONFIG_EFI_FAKE_MEMMAP is not setCONFIG_EFI_RUNTIME_WRAPPERS=y
# CONFIG_EFI_BOOTLOADER_CONTROL is not set
# CONFIG_EFI_CAPSULE_LOADER is not set
# CONFIG_EFI_TEST is not setCONFIG_APPLE_PROPERTIES=y
# CONFIG_RESET_ATTACK_MITIGATION is not set
# CONFIG_EFI_RCI2_TABLE is not set
# end of EFI (Extensible Firmware Interface) Support
CONFIG_UEFI_CPER=yCONFIG_UEFI_CPER_X86=yCONFIG_EFI_DEV_PATH_PARSER=yCONFIG_EFI_EARLYCON=y
#
# Tegra firmware driver
#
# end of Tegra firmware driver # end of Firmware Drivers
CONFIG_HAVE_KVM=yCONFIG_HAVE_KVM_IRQCHIP=yCONFIG_HAVE_KVM_IRQFD=yCONFIG_HAVE_KVM_IRQ_ROUTING=yCONFIG_HAVE_KVM_EVENTFD=yCONFIG_KVM_MMIO=yCONFIG_KVM_ASYNC_PF=yCONFIG_HAVE_KVM_MSI=yCONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=yCONFIG_KVM_VFIO=yCONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=yCONFIG_KVM_COMPAT=yCONFIG_HAVE_KVM_IRQ_BYPASS=yCONFIG_HAVE_KVM_NO_POLL=yCONFIG_VIRTUALIZATION=yCONFIG_KVM=mCONFIG_KVM_INTEL=mCONFIG_KVM_AMD=mCONFIG_KVM_AMD_SEV=yCONFIG_KVM_MMU_AUDIT=yCONFIG_VHOST_NET=m
# CONFIG_VHOST_SCSI is not setCONFIG_VHOST_VSOCK=mCONFIG_VHOST=m
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
#
# General architecture-dependent options
#CONFIG_CRASH_CORE=yCONFIG_KEXEC_CORE=yCONFIG_HOTPLUG_SMT=yCONFIG_OPROFILE=mCONFIG_OPROFILE_EVENT_MULTIPLEX=yCONFIG_HAVE_OPROFILE=yCONFIG_OPROFILE_NMI_TIMER=yCONFIG_KPROBES=yCONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not setCONFIG_OPTPROBES=yCONFIG_KPROBES_ON_FTRACE=yCONFIG_UPROBES=yCONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=yCONFIG_ARCH_USE_BUILTIN_BSWAP=yCONFIG_KRETPROBES=yCONFIG_USER_RETURN_NOTIFIER=yCONFIG_HAVE_IOREMAP_PROT=yCONFIG_HAVE_KPROBES=yCONFIG_HAVE_KRETPROBES=yCONFIG_HAVE_OPTPROBES=yCONFIG_HAVE_KPROBES_ON_FTRACE=yCONFIG_HAVE_FUNCTION_ERROR_INJECTION=yCONFIG_HAVE_NMI=yCONFIG_HAVE_ARCH_TRACEHOOK=yCONFIG_HAVE_DMA_CONTIGUOUS=yCONFIG_GENERIC_SMP_IDLE_THREAD=yCONFIG_ARCH_HAS_FORTIFY_SOURCE=yCONFIG_ARCH_HAS_SET_MEMORY=yCONFIG_ARCH_HAS_SET_DIRECT_MAP=yCONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=yCONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=yCONFIG_HAVE_ASM_MODVERSIONS=yCONFIG_HAVE_REGS_AND_STACK_ACCESS_API=yCONFIG_HAVE_RSEQ=yCONFIG_HAVE_FUNCTION_ARG_ACCESS_API=yCONFIG_HAVE_CLK=yCONFIG_HAVE_HW_BREAKPOINT=yCONFIG_HAVE_MIXED_BREAKPOINTS_REGS=yCONFIG_HAVE_USER_RETURN_NOTIFIER=yCONFIG_HAVE_PERF_EVENTS_NMI=yCONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=yCONFIG_HAVE_PERF_REGS=yCONFIG_HAVE_PERF_USER_STACK_DUMP=yCONFIG_HAVE_ARCH_JUMP_LABEL=yCONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=yCONFIG_HAVE_RCU_TABLE_FREE=yCONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=yCONFIG_HAVE_ALIGNED_STRUCT_PAGE=yCONFIG_HAVE_CMPXCHG_LOCAL=yCONFIG_HAVE_CMPXCHG_DOUBLE=yCONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=yCONFIG_ARCH_WANT_OLD_COMPAT_IPC=yCONFIG_HAVE_ARCH_SECCOMP_FILTER=yCONFIG_SECCOMP_FILTER=yCONFIG_HAVE_ARCH_STACKLEAK=yCONFIG_HAVE_STACKPROTECTOR=yCONFIG_CC_HAS_STACKPROTECTOR_NONE=yCONFIG_STACKPROTECTOR=yCONFIG_STACKPROTECTOR_STRONG=yCONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=yCONFIG_HAVE_CONTEXT_TRACKING=yCONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=yCONFIG_HAVE_IRQ_TIME_ACCOUNTING=yCONFIG_HAVE_MOVE_PMD=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=yCONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=yCONFIG_HAVE_ARCH_HUGE_VMAP=yCONFIG_ARCH_WANT_HUGE_PMD_SHARE=yCONFIG_HAVE_ARCH_SOFT_DIRTY=yCONFIG_HAVE_MOD_ARCH_SPECIFIC=yCONFIG_MODULES_USE_ELF_RELA=yCONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=yCONFIG_ARCH_HAS_ELF_RANDOMIZE=yCONFIG_HAVE_ARCH_MMAP_RND_BITS=yCONFIG_HAVE_EXIT_THREAD=yCONFIG_ARCH_MMAP_RND_BITS=28CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=yCONFIG_ARCH_MMAP_RND_COMPAT_BITS=8CONFIG_HAVE_ARCH_COMPAT_MMAP_BASES=yCONFIG_HAVE_COPY_THREAD_TLS=yCONFIG_HAVE_STACK_VALIDATION=yCONFIG_HAVE_RELIABLE_STACKTRACE=yCONFIG_OLD_SIGSUSPEND3=yCONFIG_COMPAT_OLD_SIGACTION=yCONFIG_64BIT_TIME=yCONFIG_COMPAT_32BIT_TIME=yCONFIG_HAVE_ARCH_VMAP_STACK=yCONFIG_VMAP_STACK=yCONFIG_ARCH_HAS_STRICT_KERNEL_RWX=yCONFIG_STRICT_KERNEL_RWX=yCONFIG_ARCH_HAS_STRICT_MODULE_RWX=yCONFIG_STRICT_MODULE_RWX=yCONFIG_ARCH_HAS_REFCOUNT=y
# CONFIG_REFCOUNT_FULL is not setCONFIG_HAVE_ARCH_PREL32_RELOCATIONS=yCONFIG_ARCH_USE_MEMREMAP_PROT=y
# CONFIG_LOCK_EVENT_COUNTS is not setCONFIG_ARCH_HAS_MEM_ENCRYPT=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not setCONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling
CONFIG_PLUGIN_HOSTCC="g++"CONFIG_HAVE_GCC_PLUGINS=yCONFIG_GCC_PLUGINS=y
#
# GCC plugins
#
# CONFIG_GCC_PLUGIN_CYC_COMPLEXITY is not set
# CONFIG_GCC_PLUGIN_LATENT_ENTROPY is not set
# CONFIG_GCC_PLUGIN_RANDSTRUCT is not set
# end of GCC plugins # end of General architecture-dependent options
CONFIG_RT_MUTEXES=yCONFIG_BASE_SMALL=0CONFIG_MODULE_SIG_FORMAT=yCONFIG_MODULES=yCONFIG_MODULE_FORCE_LOAD=yCONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set CONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set CONFIG_MODULE_SIG_HASH="sha256"
# CONFIG_MODULE_COMPRESS is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set # CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_TRIM_UNUSED_KSYMS is not set CONFIG_MODULES_TREE_LOOKUP=yCONFIG_BLOCK=yCONFIG_BLK_SCSI_REQUEST=yCONFIG_BLK_DEV_BSG=yCONFIG_BLK_DEV_BSGLIB=y CONFIG_BLK_DEV_INTEGRITY=yCONFIG_BLK_DEV_ZONED=y CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
# CONFIG_BLK_CMDLINE_PARSER is not set
# CONFIG_BLK_WBT is not set
# CONFIG_BLK_CGROUP_IOLATENCY is not set
# CONFIG_BLK_CGROUP_IOCOST is not set CONFIG_BLK_DEBUG_FS=yCONFIG_BLK_DEBUG_FS_ZONED=y
# CONFIG_BLK_SED_OPAL is not set
#
# Partition Types
#CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not setCONFIG_OSF_PARTITION=yCONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not setCONFIG_MAC_PARTITION=yCONFIG_MSDOS_PARTITION=yCONFIG_BSD_DISKLABEL=yCONFIG_MINIX_SUBPARTITION=yCONFIG_SOLARIS_X86_PARTITION=yCONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not setCONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not setCONFIG_SUN_PARTITION=yCONFIG_KARMA_PARTITION=yCONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set
# end of Partition Types
CONFIG_BLOCK_COMPAT=yCONFIG_BLK_MQ_PCI=yCONFIG_BLK_MQ_VIRTIO=yCONFIG_BLK_PM=y
#
# IO Schedulers
#CONFIG_MQ_IOSCHED_DEADLINE=yCONFIG_MQ_IOSCHED_KYBER=y
# CONFIG_IOSCHED_BFQ is not set
# end of IO Schedulers
CONFIG_PREEMPT_NOTIFIERS=yCONFIG_PADATA=yCONFIG_ASN1=yCONFIG_INLINE_SPIN_UNLOCK_IRQ=yCONFIG_INLINE_READ_UNLOCK=yCONFIG_INLINE_READ_UNLOCK_IRQ=yCONFIG_INLINE_WRITE_UNLOCK=yCONFIG_INLINE_WRITE_UNLOCK_IRQ=yCONFIG_ARCH_SUPPORTS_ATOMIC_RMW=yCONFIG_MUTEX_SPIN_ON_OWNER=yCONFIG_RWSEM_SPIN_ON_OWNER=yCONFIG_LOCK_SPIN_ON_OWNER=yCONFIG_ARCH_USE_QUEUED_SPINLOCKS=yCONFIG_QUEUED_SPINLOCKS=yCONFIG_ARCH_USE_QUEUED_RWLOCKS=yCONFIG_QUEUED_RWLOCKS=yCONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=yCONFIG_ARCH_HAS_SYSCALL_WRAPPER=yCONFIG_FREEZER=y
#
# Executable file formats
#CONFIG_BINFMT_ELF=yCONFIG_COMPAT_BINFMT_ELF=yCONFIG_ELFCORE=yCONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=yCONFIG_BINFMT_SCRIPT=yCONFIG_BINFMT_MISC=mCONFIG_COREDUMP=y
# end of Executable file formats
#
# Memory Management options
#CONFIG_SELECT_MEMORY_MODEL=yCONFIG_SPARSEMEM_MANUAL=yCONFIG_SPARSEMEM=yCONFIG_NEED_MULTIPLE_NODES=yCONFIG_HAVE_MEMORY_PRESENT=yCONFIG_SPARSEMEM_EXTREME=yCONFIG_SPARSEMEM_VMEMMAP_ENABLE=yCONFIG_SPARSEMEM_VMEMMAP=yCONFIG_HAVE_MEMBLOCK_NODE_MAP=yCONFIG_HAVE_FAST_GUP=yCONFIG_MEMORY_ISOLATION=yCONFIG_HAVE_BOOTMEM_INFO_NODE=yCONFIG_MEMORY_HOTPLUG=yCONFIG_MEMORY_HOTPLUG_SPARSE=y
# CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is not setCONFIG_MEMORY_HOTREMOVE=yCONFIG_SPLIT_PTLOCK_CPUS=4CONFIG_MEMORY_BALLOON=yCONFIG_BALLOON_COMPACTION=yCONFIG_COMPACTION=yCONFIG_MIGRATION=yCONFIG_CONTIG_ALLOC=yCONFIG_PHYS_ADDR_T_64BIT=yCONFIG_BOUNCE=yCONFIG_VIRT_TO_BUS=yCONFIG_MMU_NOTIFIER=yCONFIG_KSM=yCONFIG_DEFAULT_MMAP_MIN_ADDR=4096CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=yCONFIG_MEMORY_FAILURE=yCONFIG_HWPOISON_INJECT=mCONFIG_TRANSPARENT_HUGEPAGE=yCONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
# CONFIG_TRANSPARENT_HUGEPAGE_MADVISE is not setCONFIG_ARCH_WANTS_THP_SWAP=yCONFIG_THP_SWAP=yCONFIG_TRANSPARENT_HUGE_PAGECACHE=yCONFIG_CLEANCACHE=yCONFIG_FRONTSWAP=yCONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not setCONFIG_CMA_AREAS=7CONFIG_MEM_SOFT_DIRTY=yCONFIG_ZSWAP=yCONFIG_ZPOOL=yCONFIG_ZBUD=y
# CONFIG_Z3FOLD is not setCONFIG_ZSMALLOC=y
# CONFIG_PGTABLE_MAPPING is not set
# CONFIG_ZSMALLOC_STAT is not setCONFIG_GENERIC_EARLY_IOREMAP=yCONFIG_DEFERRED_STRUCT_PAGE_INIT=yCONFIG_IDLE_PAGE_TRACKING=yCONFIG_ARCH_HAS_PTE_DEVMAP=yCONFIG_ZONE_DEVICE=yCONFIG_DEV_PAGEMAP_OPS=y
# CONFIG_DEVICE_PRIVATE is not setCONFIG_FRAME_VECTOR=yCONFIG_ARCH_USES_HIGH_VMA_FLAGS=yCONFIG_ARCH_HAS_PKEYS=y
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_BENCHMARK is not set
# CONFIG_READ_ONLY_THP_FOR_FS is not setCONFIG_ARCH_HAS_PTE_SPECIAL=y
# end of Memory Management options
CONFIG_NET=yCONFIG_COMPAT_NETLINK_MESSAGES=yCONFIG_NET_INGRESS=yCONFIG_NET_EGRESS=yCONFIG_SKB_EXTENSIONS=y
#
# Networking options
#CONFIG_PACKET=yCONFIG_PACKET_DIAG=mCONFIG_UNIX=yCONFIG_UNIX_SCM=yCONFIG_UNIX_DIAG=m
# CONFIG_TLS is not setCONFIG_XFRM=yCONFIG_XFRM_ALGO=yCONFIG_XFRM_USER=y
# CONFIG_XFRM_INTERFACE is not setCONFIG_XFRM_SUB_POLICY=yCONFIG_XFRM_MIGRATE=yCONFIG_XFRM_STATISTICS=yCONFIG_XFRM_IPCOMP=mCONFIG_NET_KEY=mCONFIG_NET_KEY_MIGRATE=y
# CONFIG_XDP_SOCKETS is not setCONFIG_INET=yCONFIG_IP_MULTICAST=yCONFIG_IP_ADVANCED_ROUTER=yCONFIG_IP_FIB_TRIE_STATS=yCONFIG_IP_MULTIPLE_TABLES=yCONFIG_IP_ROUTE_MULTIPATH=yCONFIG_IP_ROUTE_VERBOSE=yCONFIG_IP_ROUTE_CLASSID=yCONFIG_IP_PNP=yCONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not setCONFIG_NET_IPIP=mCONFIG_NET_IPGRE_DEMUX=mCONFIG_NET_IP_TUNNEL=mCONFIG_NET_IPGRE=mCONFIG_NET_IPGRE_BROADCAST=yCONFIG_IP_MROUTE_COMMON=yCONFIG_IP_MROUTE=yCONFIG_IP_MROUTE_MULTIPLE_TABLES=yCONFIG_IP_PIMSM_V1=yCONFIG_IP_PIMSM_V2=yCONFIG_SYN_COOKIES=yCONFIG_NET_IPVTI=mCONFIG_NET_UDP_TUNNEL=mCONFIG_NET_FOU=mCONFIG_NET_FOU_IP_TUNNELS=yCONFIG_INET_AH=mCONFIG_INET_ESP=m
# CONFIG_INET_ESP_OFFLOAD is not setCONFIG_INET_IPCOMP=mCONFIG_INET_XFRM_TUNNEL=mCONFIG_INET_TUNNEL=mCONFIG_INET_DIAG=mCONFIG_INET_TCP_DIAG=mCONFIG_INET_UDP_DIAG=m
# CONFIG_INET_RAW_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not setCONFIG_TCP_CONG_ADVANCED=yCONFIG_TCP_CONG_BIC=mCONFIG_TCP_CONG_CUBIC=yCONFIG_TCP_CONG_WESTWOOD=mCONFIG_TCP_CONG_HTCP=mCONFIG_TCP_CONG_HSTCP=mCONFIG_TCP_CONG_HYBLA=mCONFIG_TCP_CONG_VEGAS=m
# CONFIG_TCP_CONG_NV is not setCONFIG_TCP_CONG_SCALABLE=mCONFIG_TCP_CONG_LP=mCONFIG_TCP_CONG_VENO=mCONFIG_TCP_CONG_YEAH=mCONFIG_TCP_CONG_ILLINOIS=mCONFIG_TCP_CONG_DCTCP=m
# CONFIG_TCP_CONG_CDG is not set
# CONFIG_TCP_CONG_BBR is not setCONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not setCONFIG_DEFAULT_TCP_CONG="cubic"CONFIG_TCP_MD5SIG=yCONFIG_IPV6=yCONFIG_IPV6_ROUTER_PREF=yCONFIG_IPV6_ROUTE_INFO=yCONFIG_IPV6_OPTIMISTIC_DAD=yCONFIG_INET6_AH=mCONFIG_INET6_ESP=m
# CONFIG_INET6_ESP_OFFLOAD is not setCONFIG_INET6_IPCOMP=mCONFIG_IPV6_MIP6=m
# CONFIG_IPV6_ILA is not setCONFIG_INET6_XFRM_TUNNEL=mCONFIG_INET6_TUNNEL=mCONFIG_IPV6_VTI=mCONFIG_IPV6_SIT=mCONFIG_IPV6_SIT_6RD=yCONFIG_IPV6_NDISC_NODETYPE=yCONFIG_IPV6_TUNNEL=mCONFIG_IPV6_GRE=mCONFIG_IPV6_FOU=mCONFIG_IPV6_FOU_TUNNEL=mCONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not setCONFIG_IPV6_MROUTE=yCONFIG_IPV6_MROUTE_MULTIPLE_TABLES=yCONFIG_IPV6_PIMSM_V2=yCONFIG_IPV6_SEG6_LWTUNNEL=y
# CONFIG_IPV6_SEG6_HMAC is not setCONFIG_IPV6_SEG6_BPF=yCONFIG_NETLABEL=yCONFIG_NETWORK_SECMARK=yCONFIG_NET_PTP_CLASSIFY=yCONFIG_NETWORK_PHY_TIMESTAMPING=yCONFIG_NETFILTER=yCONFIG_NETFILTER_ADVANCED=yCONFIG_BRIDGE_NETFILTER=m
#
# Core Netfilter Configuration
#CONFIG_NETFILTER_INGRESS=yCONFIG_NETFILTER_NETLINK=mCONFIG_NETFILTER_FAMILY_BRIDGE=yCONFIG_NETFILTER_FAMILY_ARP=yCONFIG_NETFILTER_NETLINK_ACCT=mCONFIG_NETFILTER_NETLINK_QUEUE=mCONFIG_NETFILTER_NETLINK_LOG=mCONFIG_NETFILTER_NETLINK_OSF=mCONFIG_NF_CONNTRACK=mCONFIG_NF_LOG_COMMON=m
# CONFIG_NF_LOG_NETDEV is not setCONFIG_NETFILTER_CONNCOUNT=mCONFIG_NF_CONNTRACK_MARK=yCONFIG_NF_CONNTRACK_SECMARK=yCONFIG_NF_CONNTRACK_ZONES=yCONFIG_NF_CONNTRACK_PROCFS=yCONFIG_NF_CONNTRACK_EVENTS=yCONFIG_NF_CONNTRACK_TIMEOUT=yCONFIG_NF_CONNTRACK_TIMESTAMP=yCONFIG_NF_CONNTRACK_LABELS=yCONFIG_NF_CT_PROTO_DCCP=yCONFIG_NF_CT_PROTO_GRE=yCONFIG_NF_CT_PROTO_SCTP=yCONFIG_NF_CT_PROTO_UDPLITE=yCONFIG_NF_CONNTRACK_AMANDA=mCONFIG_NF_CONNTRACK_FTP=mCONFIG_NF_CONNTRACK_H323=mCONFIG_NF_CONNTRACK_IRC=mCONFIG_NF_CONNTRACK_BROADCAST=mCONFIG_NF_CONNTRACK_NETBIOS_NS=mCONFIG_NF_CONNTRACK_SNMP=mCONFIG_NF_CONNTRACK_PPTP=mCONFIG_NF_CONNTRACK_SANE=mCONFIG_NF_CONNTRACK_SIP=mCONFIG_NF_CONNTRACK_TFTP=mCONFIG_NF_CT_NETLINK=mCONFIG_NF_CT_NETLINK_TIMEOUT=m
# CONFIG_NETFILTER_NETLINK_GLUE_CT is not setCONFIG_NF_NAT=mCONFIG_NF_NAT_AMANDA=mCONFIG_NF_NAT_FTP=mCONFIG_NF_NAT_IRC=mCONFIG_NF_NAT_SIP=mCONFIG_NF_NAT_TFTP=mCONFIG_NF_NAT_REDIRECT=yCONFIG_NF_NAT_MASQUERADE=yCONFIG_NETFILTER_SYNPROXY=mCONFIG_NF_TABLES=m
# CONFIG_NF_TABLES_SET is not set
# CONFIG_NF_TABLES_INET is not set
# CONFIG_NF_TABLES_NETDEV is not set
# CONFIG_NFT_NUMGEN is not setCONFIG_NFT_CT=mCONFIG_NFT_COUNTER=m
# CONFIG_NFT_CONNLIMIT is not setCONFIG_NFT_LOG=mCONFIG_NFT_LIMIT=mCONFIG_NFT_MASQ=mCONFIG_NFT_REDIR=m
# CONFIG_NFT_TUNNEL is not set
# CONFIG_NFT_OBJREF is not setCONFIG_NFT_QUEUE=m
# CONFIG_NFT_QUOTA is not setCONFIG_NFT_REJECT=mCONFIG_NFT_COMPAT=mCONFIG_NFT_HASH=m
# CONFIG_NFT_XFRM is not set
# CONFIG_NFT_SOCKET is not set
# CONFIG_NFT_OSF is not set
# CONFIG_NFT_TPROXY is not set
# CONFIG_NFT_SYNPROXY is not set
# CONFIG_NF_FLOW_TABLE is not setCONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#CONFIG_NETFILTER_XT_MARK=mCONFIG_NETFILTER_XT_CONNMARK=mCONFIG_NETFILTER_XT_SET=m
#
# Xtables targets
#CONFIG_NETFILTER_XT_TARGET_AUDIT=mCONFIG_NETFILTER_XT_TARGET_CHECKSUM=mCONFIG_NETFILTER_XT_TARGET_CLASSIFY=mCONFIG_NETFILTER_XT_TARGET_CONNMARK=mCONFIG_NETFILTER_XT_TARGET_CONNSECMARK=mCONFIG_NETFILTER_XT_TARGET_CT=mCONFIG_NETFILTER_XT_TARGET_DSCP=mCONFIG_NETFILTER_XT_TARGET_HL=mCONFIG_NETFILTER_XT_TARGET_HMARK=mCONFIG_NETFILTER_XT_TARGET_IDLETIMER=mCONFIG_NETFILTER_XT_TARGET_LED=mCONFIG_NETFILTER_XT_TARGET_LOG=mCONFIG_NETFILTER_XT_TARGET_MARK=mCONFIG_NETFILTER_XT_NAT=mCONFIG_NETFILTER_XT_TARGET_NETMAP=mCONFIG_NETFILTER_XT_TARGET_NFLOG=mCONFIG_NETFILTER_XT_TARGET_NFQUEUE=mCONFIG_NETFILTER_XT_TARGET_NOTRACK=mCONFIG_NETFILTER_XT_TARGET_RATEEST=mCONFIG_NETFILTER_XT_TARGET_REDIRECT=mCONFIG_NETFILTER_XT_TARGET_MASQUERADE=mCONFIG_NETFILTER_XT_TARGET_TEE=mCONFIG_NETFILTER_XT_TARGET_TPROXY=mCONFIG_NETFILTER_XT_TARGET_TRACE=mCONFIG_NETFILTER_XT_TARGET_SECMARK=mCONFIG_NETFILTER_XT_TARGET_TCPMSS=mCONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
#
# Xtables matches
#CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=mCONFIG_NETFILTER_XT_MATCH_BPF=mCONFIG_NETFILTER_XT_MATCH_CGROUP=mCONFIG_NETFILTER_XT_MATCH_CLUSTER=mCONFIG_NETFILTER_XT_MATCH_COMMENT=mCONFIG_NETFILTER_XT_MATCH_CONNBYTES=mCONFIG_NETFILTER_XT_MATCH_CONNLABEL=mCONFIG_NETFILTER_XT_MATCH_CONNLIMIT=mCONFIG_NETFILTER_XT_MATCH_CONNMARK=mCONFIG_NETFILTER_XT_MATCH_CONNTRACK=mCONFIG_NETFILTER_XT_MATCH_CPU=mCONFIG_NETFILTER_XT_MATCH_DCCP=mCONFIG_NETFILTER_XT_MATCH_DEVGROUP=mCONFIG_NETFILTER_XT_MATCH_DSCP=mCONFIG_NETFILTER_XT_MATCH_ECN=mCONFIG_NETFILTER_XT_MATCH_ESP=mCONFIG_NETFILTER_XT_MATCH_HASHLIMIT=mCONFIG_NETFILTER_XT_MATCH_HELPER=mCONFIG_NETFILTER_XT_MATCH_HL=m
# CONFIG_NETFILTER_XT_MATCH_IPCOMP is not setCONFIG_NETFILTER_XT_MATCH_IPRANGE=mCONFIG_NETFILTER_XT_MATCH_IPVS=mCONFIG_NETFILTER_XT_MATCH_L2TP=mCONFIG_NETFILTER_XT_MATCH_LENGTH=mCONFIG_NETFILTER_XT_MATCH_LIMIT=mCONFIG_NETFILTER_XT_MATCH_MAC=mCONFIG_NETFILTER_XT_MATCH_MARK=mCONFIG_NETFILTER_XT_MATCH_MULTIPORT=mCONFIG_NETFILTER_XT_MATCH_NFACCT=mCONFIG_NETFILTER_XT_MATCH_OSF=mCONFIG_NETFILTER_XT_MATCH_OWNER=mCONFIG_NETFILTER_XT_MATCH_POLICY=mCONFIG_NETFILTER_XT_MATCH_PHYSDEV=mCONFIG_NETFILTER_XT_MATCH_PKTTYPE=mCONFIG_NETFILTER_XT_MATCH_QUOTA=mCONFIG_NETFILTER_XT_MATCH_RATEEST=mCONFIG_NETFILTER_XT_MATCH_REALM=mCONFIG_NETFILTER_XT_MATCH_RECENT=mCONFIG_NETFILTER_XT_MATCH_SCTP=mCONFIG_NETFILTER_XT_MATCH_SOCKET=mCONFIG_NETFILTER_XT_MATCH_STATE=mCONFIG_NETFILTER_XT_MATCH_STATISTIC=mCONFIG_NETFILTER_XT_MATCH_STRING=mCONFIG_NETFILTER_XT_MATCH_TCPMSS=mCONFIG_NETFILTER_XT_MATCH_TIME=mCONFIG_NETFILTER_XT_MATCH_U32=m
# end of Core Netfilter Configuration
CONFIG_IP_SET=mCONFIG_IP_SET_MAX=256CONFIG_IP_SET_BITMAP_IP=mCONFIG_IP_SET_BITMAP_IPMAC=mCONFIG_IP_SET_BITMAP_PORT=mCONFIG_IP_SET_HASH_IP=mCONFIG_IP_SET_HASH_IPMARK=mCONFIG_IP_SET_HASH_IPPORT=mCONFIG_IP_SET_HASH_IPPORTIP=mCONFIG_IP_SET_HASH_IPPORTNET=mCONFIG_IP_SET_HASH_IPMAC=mCONFIG_IP_SET_HASH_MAC=mCONFIG_IP_SET_HASH_NETPORTNET=mCONFIG_IP_SET_HASH_NET=mCONFIG_IP_SET_HASH_NETNET=mCONFIG_IP_SET_HASH_NETPORT=mCONFIG_IP_SET_HASH_NETIFACE=mCONFIG_IP_SET_LIST_SET=mCONFIG_IP_VS=mCONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not setCONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#CONFIG_IP_VS_PROTO_TCP=yCONFIG_IP_VS_PROTO_UDP=yCONFIG_IP_VS_PROTO_AH_ESP=yCONFIG_IP_VS_PROTO_ESP=yCONFIG_IP_VS_PROTO_AH=yCONFIG_IP_VS_PROTO_SCTP=y
#
# IPVS scheduler
#CONFIG_IP_VS_RR=mCONFIG_IP_VS_WRR=mCONFIG_IP_VS_LC=mCONFIG_IP_VS_WLC=m
# CONFIG_IP_VS_FO is not set
# CONFIG_IP_VS_OVF is not setCONFIG_IP_VS_LBLC=mCONFIG_IP_VS_LBLCR=mCONFIG_IP_VS_DH=mCONFIG_IP_VS_SH=m
# CONFIG_IP_VS_MH is not setCONFIG_IP_VS_SED=mCONFIG_IP_VS_NQ=m
#
# IPVS SH scheduler
#CONFIG_IP_VS_SH_TAB_BITS=8
#
# IPVS MH scheduler
#CONFIG_IP_VS_MH_TAB_INDEX=12
#
# IPVS application helper
#CONFIG_IP_VS_FTP=mCONFIG_IP_VS_NFCT=yCONFIG_IP_VS_PE_SIP=m
#
# IP: Netfilter Configuration
#CONFIG_NF_DEFRAG_IPV4=mCONFIG_NF_SOCKET_IPV4=mCONFIG_NF_TPROXY_IPV4=m
# CONFIG_NF_TABLES_IPV4 is not set
# CONFIG_NF_TABLES_ARP is not setCONFIG_NF_DUP_IPV4=m
# CONFIG_NF_LOG_ARP is not setCONFIG_NF_LOG_IPV4=mCONFIG_NF_REJECT_IPV4=mCONFIG_NF_NAT_SNMP_BASIC=mCONFIG_NF_NAT_PPTP=mCONFIG_NF_NAT_H323=mCONFIG_IP_NF_IPTABLES=mCONFIG_IP_NF_MATCH_AH=mCONFIG_IP_NF_MATCH_ECN=mCONFIG_IP_NF_MATCH_RPFILTER=mCONFIG_IP_NF_MATCH_TTL=mCONFIG_IP_NF_FILTER=mCONFIG_IP_NF_TARGET_REJECT=mCONFIG_IP_NF_TARGET_SYNPROXY=mCONFIG_IP_NF_NAT=mCONFIG_IP_NF_TARGET_MASQUERADE=mCONFIG_IP_NF_TARGET_NETMAP=mCONFIG_IP_NF_TARGET_REDIRECT=mCONFIG_IP_NF_MANGLE=mCONFIG_IP_NF_TARGET_CLUSTERIP=mCONFIG_IP_NF_TARGET_ECN=mCONFIG_IP_NF_TARGET_TTL=mCONFIG_IP_NF_RAW=mCONFIG_IP_NF_SECURITY=mCONFIG_IP_NF_ARPTABLES=mCONFIG_IP_NF_ARPFILTER=mCONFIG_IP_NF_ARP_MANGLE=m
# end of IP: Netfilter Configuration
#
# IPv6: Netfilter Configuration
#CONFIG_NF_SOCKET_IPV6=mCONFIG_NF_TPROXY_IPV6=m
# CONFIG_NF_TABLES_IPV6 is not setCONFIG_NF_DUP_IPV6=mCONFIG_NF_REJECT_IPV6=mCONFIG_NF_LOG_IPV6=mCONFIG_IP6_NF_IPTABLES=mCONFIG_IP6_NF_MATCH_AH=mCONFIG_IP6_NF_MATCH_EUI64=mCONFIG_IP6_NF_MATCH_FRAG=mCONFIG_IP6_NF_MATCH_OPTS=mCONFIG_IP6_NF_MATCH_HL=mCONFIG_IP6_NF_MATCH_IPV6HEADER=mCONFIG_IP6_NF_MATCH_MH=mCONFIG_IP6_NF_MATCH_RPFILTER=mCONFIG_IP6_NF_MATCH_RT=m
# CONFIG_IP6_NF_MATCH_SRH is not setCONFIG_IP6_NF_TARGET_HL=mCONFIG_IP6_NF_FILTER=mCONFIG_IP6_NF_TARGET_REJECT=mCONFIG_IP6_NF_TARGET_SYNPROXY=mCONFIG_IP6_NF_MANGLE=mCONFIG_IP6_NF_RAW=mCONFIG_IP6_NF_SECURITY=mCONFIG_IP6_NF_NAT=mCONFIG_IP6_NF_TARGET_MASQUERADE=mCONFIG_IP6_NF_TARGET_NPT=m
# end of IPv6: Netfilter Configuration
CONFIG_NF_DEFRAG_IPV6=m
# CONFIG_NF_TABLES_BRIDGE is not set
# CONFIG_NF_CONNTRACK_BRIDGE is not setCONFIG_BRIDGE_NF_EBTABLES=mCONFIG_BRIDGE_EBT_BROUTE=mCONFIG_BRIDGE_EBT_T_FILTER=mCONFIG_BRIDGE_EBT_T_NAT=mCONFIG_BRIDGE_EBT_802_3=mCONFIG_BRIDGE_EBT_AMONG=mCONFIG_BRIDGE_EBT_ARP=mCONFIG_BRIDGE_EBT_IP=mCONFIG_BRIDGE_EBT_IP6=mCONFIG_BRIDGE_EBT_LIMIT=mCONFIG_BRIDGE_EBT_MARK=mCONFIG_BRIDGE_EBT_PKTTYPE=mCONFIG_BRIDGE_EBT_STP=mCONFIG_BRIDGE_EBT_VLAN=mCONFIG_BRIDGE_EBT_ARPREPLY=mCONFIG_BRIDGE_EBT_DNAT=mCONFIG_BRIDGE_EBT_MARK_T=mCONFIG_BRIDGE_EBT_REDIRECT=mCONFIG_BRIDGE_EBT_SNAT=mCONFIG_BRIDGE_EBT_LOG=mCONFIG_BRIDGE_EBT_NFLOG=m
# CONFIG_BPFILTER is not setCONFIG_IP_DCCP=mCONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not setCONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not setCONFIG_IP_DCCP_TFRC_LIB=y
# end of DCCP CCIDs Configuration
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
# end of DCCP Kernel Hacking
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5 is not set CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set CONFIG_SCTP_COOKIE_HMAC_MD5=y CONFIG_SCTP_COOKIE_HMAC_SHA1=y CONFIG_INET_SCTP_DIAG=m
# CONFIG_RDS is not set
# CONFIG_TIPC is not setCONFIG_ATM=mCONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_L2TP=mCONFIG_L2TP_DEBUGFS=mCONFIG_L2TP_V3=yCONFIG_L2TP_IP=mCONFIG_L2TP_ETH=mCONFIG_STP=mCONFIG_GARP=mCONFIG_MRP=mCONFIG_BRIDGE=m CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_BRIDGE_VLAN_FILTERING=y CONFIG_HAVE_NET_DSA=y
# CONFIG_NET_DSA is not set CONFIG_VLAN_8021Q=mCONFIG_VLAN_8021Q_GVRP=y CONFIG_VLAN_8021Q_MVRP=y
# CONFIG_DECNET is not setCONFIG_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not setCONFIG_6LOWPAN=m
# CONFIG_6LOWPAN_DEBUGFS is not set CONFIG_6LOWPAN_NHC=m CONFIG_6LOWPAN_NHC_DEST=m CONFIG_6LOWPAN_NHC_FRAGMENT=m CONFIG_6LOWPAN_NHC_HOP=m CONFIG_6LOWPAN_NHC_IPV6=m CONFIG_6LOWPAN_NHC_MOBILITY=m CONFIG_6LOWPAN_NHC_ROUTING=m CONFIG_6LOWPAN_NHC_UDP=m
# CONFIG_6LOWPAN_GHC_EXT_HDR_HOP is not set # CONFIG_6LOWPAN_GHC_UDP is not set
# CONFIG_6LOWPAN_GHC_ICMPV6 is not set
# CONFIG_6LOWPAN_GHC_EXT_HDR_DEST is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_FRAG is not set # CONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE is not set CONFIG_IEEE802154=m
# CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set CONFIG_IEEE802154_SOCKET=m CONFIG_IEEE802154_6LOWPAN=m CONFIG_MAC802154=mCONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#CONFIG_NET_SCH_CBQ=mCONFIG_NET_SCH_HTB=mCONFIG_NET_SCH_HFSC=mCONFIG_NET_SCH_ATM=mCONFIG_NET_SCH_PRIO=mCONFIG_NET_SCH_MULTIQ=mCONFIG_NET_SCH_RED=mCONFIG_NET_SCH_SFB=mCONFIG_NET_SCH_SFQ=mCONFIG_NET_SCH_TEQL=mCONFIG_NET_SCH_TBF=m
# CONFIG_NET_SCH_CBS is not set
# CONFIG_NET_SCH_ETF is not set
# CONFIG_NET_SCH_TAPRIO is not setCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=mCONFIG_NET_SCH_NETEM=mCONFIG_NET_SCH_DRR=mCONFIG_NET_SCH_MQPRIO=m
# CONFIG_NET_SCH_SKBPRIO is not setCONFIG_NET_SCH_CHOKE=mCONFIG_NET_SCH_QFQ=mCONFIG_NET_SCH_CODEL=mCONFIG_NET_SCH_FQ_CODEL=m
# CONFIG_NET_SCH_CAKE is not setCONFIG_NET_SCH_FQ=m
# CONFIG_NET_SCH_HHF is not set
# CONFIG_NET_SCH_PIE is not setCONFIG_NET_SCH_INGRESS=mCONFIG_NET_SCH_PLUG=m
# CONFIG_NET_SCH_DEFAULT is not set
#
# Classification
#CONFIG_NET_CLS=yCONFIG_NET_CLS_BASIC=mCONFIG_NET_CLS_TCINDEX=mCONFIG_NET_CLS_ROUTE4=mCONFIG_NET_CLS_FW=mCONFIG_NET_CLS_U32=mCONFIG_CLS_U32_PERF=yCONFIG_CLS_U32_MARK=yCONFIG_NET_CLS_RSVP=mCONFIG_NET_CLS_RSVP6=mCONFIG_NET_CLS_FLOW=mCONFIG_NET_CLS_CGROUP=yCONFIG_NET_CLS_BPF=mCONFIG_NET_CLS_FLOWER=mCONFIG_NET_CLS_MATCHALL=mCONFIG_NET_EMATCH=yCONFIG_NET_EMATCH_STACK=32CONFIG_NET_EMATCH_CMP=mCONFIG_NET_EMATCH_NBYTE=mCONFIG_NET_EMATCH_U32=mCONFIG_NET_EMATCH_META=mCONFIG_NET_EMATCH_TEXT=m
# CONFIG_NET_EMATCH_CANID is not setCONFIG_NET_EMATCH_IPSET=m
# CONFIG_NET_EMATCH_IPT is not setCONFIG_NET_CLS_ACT=yCONFIG_NET_ACT_POLICE=mCONFIG_NET_ACT_GACT=mCONFIG_GACT_PROB=yCONFIG_NET_ACT_MIRRED=mCONFIG_NET_ACT_SAMPLE=mCONFIG_NET_ACT_IPT=mCONFIG_NET_ACT_NAT=mCONFIG_NET_ACT_PEDIT=mCONFIG_NET_ACT_SIMP=mCONFIG_NET_ACT_SKBEDIT=mCONFIG_NET_ACT_CSUM=m
# CONFIG_NET_ACT_MPLS is not setCONFIG_NET_ACT_VLAN=m
# CONFIG_NET_ACT_BPF is not setCONFIG_NET_ACT_CONNMARK=m
# CONFIG_NET_ACT_CTINFO is not setCONFIG_NET_ACT_SKBMOD=m
# CONFIG_NET_ACT_IFE is not setCONFIG_NET_ACT_TUNNEL_KEY=m
# CONFIG_NET_ACT_CT is not set
# CONFIG_NET_TC_SKB_EXT is not setCONFIG_NET_SCH_FIFO=yCONFIG_DCB=yCONFIG_DNS_RESOLVER=m
# CONFIG_BATMAN_ADV is not setCONFIG_OPENVSWITCH=mCONFIG_OPENVSWITCH_GRE=mCONFIG_OPENVSWITCH_VXLAN=mCONFIG_OPENVSWITCH_GENEVE=mCONFIG_VSOCKETS=mCONFIG_VSOCKETS_DIAG=mCONFIG_VMWARE_VMCI_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS=mCONFIG_VIRTIO_VSOCKETS_COMMON=mCONFIG_HYPERV_VSOCKETS=mCONFIG_NETLINK_DIAG=mCONFIG_MPLS=yCONFIG_NET_MPLS_GSO=yCONFIG_MPLS_ROUTING=mCONFIG_MPLS_IPTUNNEL=mCONFIG_NET_NSH=m
# CONFIG_HSR is not setCONFIG_NET_SWITCHDEV=yCONFIG_NET_L3_MASTER_DEV=y
# CONFIG_NET_NCSI is not setCONFIG_RPS=yCONFIG_RFS_ACCEL=yCONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not setCONFIG_CGROUP_NET_CLASSID=yCONFIG_NET_RX_BUSY_POLL=yCONFIG_BQL=yCONFIG_BPF_JIT=yCONFIG_BPF_STREAM_PARSER=yCONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#CONFIG_NET_PKTGEN=mCONFIG_NET_DROP_MONITOR=y
# end of Network testing # end of Networking options
# CONFIG_HAMRADIO is not setCONFIG_CAN=mCONFIG_CAN_RAW=mCONFIG_CAN_BCM=mCONFIG_CAN_GW=m
# CONFIG_CAN_J1939 is not set
#
# CAN Device Drivers
#CONFIG_CAN_VCAN=m
# CONFIG_CAN_VXCAN is not setCONFIG_CAN_SLCAN=mCONFIG_CAN_DEV=mCONFIG_CAN_CALC_BITTIMING=y
# CONFIG_CAN_KVASER_PCIEFD is not setCONFIG_CAN_C_CAN=mCONFIG_CAN_C_CAN_PLATFORM=mCONFIG_CAN_C_CAN_PCI=mCONFIG_CAN_CC770=m
# CONFIG_CAN_CC770_ISA is not setCONFIG_CAN_CC770_PLATFORM=m
# CONFIG_CAN_IFI_CANFD is not set
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_PEAK_PCIEFD is not setCONFIG_CAN_SJA1000=mCONFIG_CAN_EMS_PCI=m
# CONFIG_CAN_F81601 is not setCONFIG_CAN_KVASER_PCI=mCONFIG_CAN_PEAK_PCI=mCONFIG_CAN_PEAK_PCIEC=yCONFIG_CAN_PLX_PCI=m
# CONFIG_CAN_SJA1000_ISA is not setCONFIG_CAN_SJA1000_PLATFORM=mCONFIG_CAN_SOFTING=m
#
# CAN SPI interfaces
#
# CONFIG_CAN_HI311X is not set
# CONFIG_CAN_MCP251X is not set
# end of CAN SPI interfaces
#
# CAN USB interfaces
#CONFIG_CAN_8DEV_USB=mCONFIG_CAN_EMS_USB=mCONFIG_CAN_ESD_USB2=m
# CONFIG_CAN_GS_USB is not setCONFIG_CAN_KVASER_USB=m
# CONFIG_CAN_MCBA_USB is not setCONFIG_CAN_PEAK_USB=m
# CONFIG_CAN_UCAN is not set
# end of CAN USB interfaces
# CONFIG_CAN_DEBUG_DEVICES is not set
# end of CAN Device Drivers
CONFIG_BT=mCONFIG_BT_BREDR=yCONFIG_BT_RFCOMM=mCONFIG_BT_RFCOMM_TTY=yCONFIG_BT_BNEP=mCONFIG_BT_BNEP_MC_FILTER=yCONFIG_BT_BNEP_PROTO_FILTER=yCONFIG_BT_CMTP=mCONFIG_BT_HIDP=mCONFIG_BT_HS=yCONFIG_BT_LE=y
# CONFIG_BT_6LOWPAN is not set
# CONFIG_BT_LEDS is not set
# CONFIG_BT_SELFTEST is not setCONFIG_BT_DEBUGFS=y
#
# Bluetooth device drivers
#CONFIG_BT_INTEL=mCONFIG_BT_BCM=mCONFIG_BT_RTL=mCONFIG_BT_HCIBTUSB=m
# CONFIG_BT_HCIBTUSB_AUTOSUSPEND is not setCONFIG_BT_HCIBTUSB_BCM=y
# CONFIG_BT_HCIBTUSB_MTK is not setCONFIG_BT_HCIBTUSB_RTL=yCONFIG_BT_HCIBTSDIO=mCONFIG_BT_HCIUART=mCONFIG_BT_HCIUART_H4=yCONFIG_BT_HCIUART_BCSP=yCONFIG_BT_HCIUART_ATH3K=y
# CONFIG_BT_HCIUART_INTEL is not set
# CONFIG_BT_HCIUART_AG6XX is not setCONFIG_BT_HCIBCM203X=mCONFIG_BT_HCIBPA10X=mCONFIG_BT_HCIBFUSB=mCONFIG_BT_HCIVHCI=mCONFIG_BT_MRVL=mCONFIG_BT_MRVL_SDIO=mCONFIG_BT_ATH3K=m
# CONFIG_BT_MTKSDIO is not set
# end of Bluetooth device drivers
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not setCONFIG_STREAM_PARSER=yCONFIG_FIB_RULES=yCONFIG_WIRELESS=yCONFIG_WIRELESS_EXT=yCONFIG_WEXT_CORE=yCONFIG_WEXT_PROC=yCONFIG_WEXT_PRIV=yCONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not setCONFIG_CFG80211_REQUIRE_SIGNED_REGDB=yCONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=yCONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not setCONFIG_CFG80211_CRDA_SUPPORT=yCONFIG_CFG80211_WEXT=yCONFIG_LIB80211=m
# CONFIG_LIB80211_DEBUG is not setCONFIG_MAC80211=mCONFIG_MAC80211_HAS_RC=yCONFIG_MAC80211_RC_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT_MINSTREL=yCONFIG_MAC80211_RC_DEFAULT="minstrel_ht"CONFIG_MAC80211_MESH=yCONFIG_MAC80211_LEDS=yCONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not setCONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_WIMAX is not setCONFIG_RFKILL=mCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not setCONFIG_NET_9P=yCONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_XEN is not set
# CONFIG_NET_9P_DEBUG is not set
# CONFIG_CAIF is not setCONFIG_CEPH_LIB=m
# CONFIG_CEPH_LIB_PRETTYDEBUG is not setCONFIG_CEPH_LIB_USE_DNS_RESOLVER=y
# CONFIG_NFC is not setCONFIG_PSAMPLE=m
# CONFIG_NET_IFE is not setCONFIG_LWTUNNEL=yCONFIG_LWTUNNEL_BPF=yCONFIG_DST_CACHE=yCONFIG_GRO_CELLS=yCONFIG_NET_SOCK_MSG=yCONFIG_NET_DEVLINK=yCONFIG_PAGE_POOL=yCONFIG_FAILOVER=mCONFIG_HAVE_EBPF_JIT=y
#
# Device Drivers
#CONFIG_HAVE_EISA=y
# CONFIG_EISA is not setCONFIG_HAVE_PCI=yCONFIG_PCI=yCONFIG_PCI_DOMAINS=yCONFIG_PCIEPORTBUS=yCONFIG_HOTPLUG_PCI_PCIE=yCONFIG_PCIEAER=yCONFIG_PCIEAER_INJECT=mCONFIG_PCIE_ECRC=yCONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not setCONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not setCONFIG_PCIE_PME=y
# CONFIG_PCIE_DPC is not set
# CONFIG_PCIE_PTM is not set
# CONFIG_PCIE_BW is not setCONFIG_PCI_MSI=yCONFIG_PCI_MSI_IRQ_DOMAIN=yCONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not setCONFIG_PCI_STUB=y
# CONFIG_PCI_PF_STUB is not set
# CONFIG_XEN_PCIDEV_FRONTEND is not setCONFIG_PCI_ATS=yCONFIG_PCI_LOCKLESS_CONFIG=yCONFIG_PCI_IOV=yCONFIG_PCI_PRI=yCONFIG_PCI_PASID=y
# CONFIG_PCI_P2PDMA is not setCONFIG_PCI_LABEL=yCONFIG_PCI_HYPERV=mCONFIG_HOTPLUG_PCI=yCONFIG_HOTPLUG_PCI_ACPI=yCONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not setCONFIG_HOTPLUG_PCI_SHPC=y
#
# PCI controller drivers
#
#
# Cadence PCIe controllers support
#
# end of Cadence PCIe controllers support
CONFIG_VMD=yCONFIG_PCI_HYPERV_INTERFACE=m
#
# DesignWare PCI Core Support
#
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCI_MESON is not set
# end of DesignWare PCI Core Support # end of PCI controller drivers
#
# PCI Endpoint
#
# CONFIG_PCI_ENDPOINT is not set
# end of PCI Endpoint
#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers
CONFIG_PCCARD=y
# CONFIG_PCMCIA is not setCONFIG_CARDBUS=y
#
# PC-card bridges
#CONFIG_YENTA=mCONFIG_YENTA_O2=yCONFIG_YENTA_RICOH=yCONFIG_YENTA_TI=yCONFIG_YENTA_ENE_TUNE=yCONFIG_YENTA_TOSHIBA=y
# CONFIG_RAPIDIO is not set
#
# Generic Driver Options
#CONFIG_UEVENT_HELPER=yCONFIG_UEVENT_HELPER_PATH=""CONFIG_DEVTMPFS=yCONFIG_DEVTMPFS_MOUNT=yCONFIG_STANDALONE=yCONFIG_PREVENT_FIRMWARE_BUILD=y
#
# Firmware loader
#CONFIG_FW_LOADER=y CONFIG_FW_LOADER_PAGED_BUF=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set # CONFIG_FW_LOADER_COMPRESS is not set
# end of Firmware loader
CONFIG_WANT_DEV_COREDUMP=yCONFIG_ALLOW_DEV_COREDUMP=yCONFIG_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not setCONFIG_SYS_HYPERVISOR=yCONFIG_GENERIC_CPU_AUTOPROBE=yCONFIG_GENERIC_CPU_VULNERABILITIES=yCONFIG_REGMAP=yCONFIG_REGMAP_I2C=yCONFIG_REGMAP_SPI=yCONFIG_REGMAP_IRQ=yCONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set
# end of Generic Driver Options
#
# Bus devices
#
# end of Bus devices
CONFIG_CONNECTOR=yCONFIG_PROC_EVENTS=y
# CONFIG_GNSS is not setCONFIG_MTD=m
# CONFIG_MTD_TESTS is not set
#
# Partition parsers
#
# CONFIG_MTD_AR7_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# end of Partition parsers
#
# User Modules And Translation Layers
#CONFIG_MTD_BLKDEVS=mCONFIG_MTD_BLOCK=m
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set
#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not setCONFIG_MTD_MAP_BANK_WIDTH_1=yCONFIG_MTD_MAP_BANK_WIDTH_2=yCONFIG_MTD_MAP_BANK_WIDTH_4=yCONFIG_MTD_CFI_I1=yCONFIG_MTD_CFI_I2=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# end of RAM/ROM/Flash chip drivers
#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set
# end of Mapping drivers for chip access
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_MCHP23K256 is not set
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set
# end of Self-contained MTD device drivers
# CONFIG_MTD_ONENAND is not set
# CONFIG_MTD_RAW_NAND is not set
# CONFIG_MTD_SPI_NAND is not set
#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set
# end of LPDDR & LPDDR2 PCM memory drivers
# CONFIG_MTD_SPI_NOR is not setCONFIG_MTD_UBI=mCONFIG_MTD_UBI_WL_THRESHOLD=4096CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
# CONFIG_MTD_UBI_BLOCK is not set
# CONFIG_MTD_HYPERBUS is not set
# CONFIG_OF is not setCONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=yCONFIG_PARPORT=mCONFIG_PARPORT_PC=mCONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AX88796 is not setCONFIG_PARPORT_1284=yCONFIG_PARPORT_NOT_PC=yCONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set
#
# Protocols
#CONFIG_PNPACPI=yCONFIG_BLK_DEV=yCONFIG_BLK_DEV_NULL_BLK=mCONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION=yCONFIG_BLK_DEV_FD=mCONFIG_CDROM=m
# CONFIG_PARIDE is not setCONFIG_BLK_DEV_PCIESSD_MTIP32XX=m
# CONFIG_ZRAM is not set
# CONFIG_BLK_DEV_UMEM is not setCONFIG_BLK_DEV_LOOP=mCONFIG_BLK_DEV_LOOP_MIN_COUNT=0
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not setCONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SKD is not setCONFIG_BLK_DEV_SX8=mCONFIG_BLK_DEV_RAM=mCONFIG_BLK_DEV_RAM_COUNT=16CONFIG_BLK_DEV_RAM_SIZE=16384CONFIG_CDROM_PKTCDVD=mCONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not setCONFIG_ATA_OVER_ETH=mCONFIG_XEN_BLKDEV_FRONTEND=mCONFIG_VIRTIO_BLK=y
# CONFIG_VIRTIO_BLK_SCSI is not setCONFIG_BLK_DEV_RBD=m
# CONFIG_BLK_DEV_RSXX is not set
#
# NVME Support
#CONFIG_NVME_CORE=mCONFIG_BLK_DEV_NVME=mCONFIG_NVME_MULTIPATH=yCONFIG_NVME_FABRICS=mCONFIG_NVME_FC=m
# CONFIG_NVME_TCP is not setCONFIG_NVME_TARGET=mCONFIG_NVME_TARGET_LOOP=mCONFIG_NVME_TARGET_FC=mCONFIG_NVME_TARGET_FCLOOP=m
# CONFIG_NVME_TARGET_TCP is not set
# end of NVME Support
#
# Misc devices
#CONFIG_SENSORS_LIS3LV02D=m
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not setCONFIG_TIFM_CORE=mCONFIG_TIFM_7XX1=m
# CONFIG_ICS932S401 is not setCONFIG_ENCLOSURE_SERVICES=mCONFIG_SGI_XP=mCONFIG_HP_ILO=mCONFIG_SGI_GRU=m
# CONFIG_SGI_GRU_DEBUG is not setCONFIG_APDS9802ALS=mCONFIG_ISL29003=mCONFIG_ISL29020=mCONFIG_SENSORS_TSL2550=mCONFIG_SENSORS_BH1770=mCONFIG_SENSORS_APDS990X=m
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not setCONFIG_VMWARE_BALLOON=m
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_PCI_ENDPOINT_TEST is not set
# CONFIG_XILINX_SDFEC is not setCONFIG_PVPANIC=y
# CONFIG_C2PORT is not set
#
# EEPROM support
#CONFIG_EEPROM_AT24=m
# CONFIG_EEPROM_AT25 is not setCONFIG_EEPROM_LEGACY=mCONFIG_EEPROM_MAX6875=mCONFIG_EEPROM_93CX6=m
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_IDT_89HPESX is not set
# CONFIG_EEPROM_EE1004 is not set
# end of EEPROM support
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not setCONFIG_CB710_DEBUG_ASSUMPTIONS=y
#
# Texas Instruments shared transport line discipline #
# CONFIG_TI_ST is not set
# end of Texas Instruments shared transport line discipline
CONFIG_SENSORS_LIS3_I2C=mCONFIG_ALTERA_STAPL=mCONFIG_INTEL_MEI=mCONFIG_INTEL_MEI_ME=m
# CONFIG_INTEL_MEI_TXE is not set
# CONFIG_INTEL_MEI_HDCP is not setCONFIG_VMWARE_VMCI=m
#
# Intel MIC & related support
#
#
# Intel MIC Bus Driver
#
# CONFIG_INTEL_MIC_BUS is not set
#
# SCIF Bus Driver
#
# CONFIG_SCIF_BUS is not set
#
# VOP Bus Driver
#
# CONFIG_VOP_BUS is not set
#
# Intel MIC Host Driver
#
#
# Intel MIC Card Driver
#
#
# SCIF Driver
#
#
# Intel MIC Coprocessor State Management (COSM) Drivers #
#
# VOP Driver
#
# end of Intel MIC & related support
# CONFIG_GENWQE is not set
# CONFIG_ECHO is not set
# CONFIG_MISC_ALCOR_PCI is not set
# CONFIG_MISC_RTSX_PCI is not set
# CONFIG_MISC_RTSX_USB is not set
# CONFIG_HABANA_AI is not set
# end of Misc devices
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#CONFIG_SCSI_MOD=yCONFIG_RAID_ATTRS=mCONFIG_SCSI=yCONFIG_SCSI_DMA=yCONFIG_SCSI_NETLINK=yCONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#CONFIG_BLK_DEV_SD=mCONFIG_CHR_DEV_ST=mCONFIG_BLK_DEV_SR=mCONFIG_BLK_DEV_SR_VENDOR=yCONFIG_CHR_DEV_SG=mCONFIG_CHR_DEV_SCH=mCONFIG_SCSI_ENCLOSURE=mCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_LOGGING=yCONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#CONFIG_SCSI_SPI_ATTRS=mCONFIG_SCSI_FC_ATTRS=mCONFIG_SCSI_ISCSI_ATTRS=mCONFIG_SCSI_SAS_ATTRS=mCONFIG_SCSI_SAS_LIBSAS=mCONFIG_SCSI_SAS_ATA=yCONFIG_SCSI_SAS_HOST_SMP=yCONFIG_SCSI_SRP_ATTRS=m
# end of SCSI Transports
CONFIG_SCSI_LOWLEVEL=yCONFIG_ISCSI_TCP=mCONFIG_ISCSI_BOOT_SYSFS=mCONFIG_SCSI_CXGB3_ISCSI=mCONFIG_SCSI_CXGB4_ISCSI=mCONFIG_SCSI_BNX2_ISCSI=mCONFIG_SCSI_BNX2X_FCOE=mCONFIG_BE2ISCSI=m
# CONFIG_BLK_DEV_3W_XXXX_RAID is not setCONFIG_SCSI_HPSA=mCONFIG_SCSI_3W_9XXX=mCONFIG_SCSI_3W_SAS=m
# CONFIG_SCSI_ACARD is not setCONFIG_SCSI_AACRAID=m
# CONFIG_SCSI_AIC7XXX is not setCONFIG_SCSI_AIC79XX=mCONFIG_AIC79XX_CMDS_PER_DEVICE=4CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_DEBUG_ENABLE is not setCONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC94XX is not setCONFIG_SCSI_MVSAS=m
# CONFIG_SCSI_MVSAS_DEBUG is not setCONFIG_SCSI_MVSAS_TASKLET=yCONFIG_SCSI_MVUMI=m
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not setCONFIG_SCSI_ARCMSR=m
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not setCONFIG_MEGARAID_SAS=mCONFIG_SCSI_MPT3SAS=mCONFIG_SCSI_MPT2SAS_MAX_SGE=128CONFIG_SCSI_MPT3SAS_MAX_SGE=128CONFIG_SCSI_MPT2SAS=m
# CONFIG_SCSI_SMARTPQI is not setCONFIG_SCSI_UFSHCD=mCONFIG_SCSI_UFSHCD_PCI=m
# CONFIG_SCSI_UFS_DWC_TC_PCI is not set
# CONFIG_SCSI_UFSHCD_PLATFORM is not set
# CONFIG_SCSI_UFS_BSG is not setCONFIG_SCSI_HPTIOP=m
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not setCONFIG_VMWARE_PVSCSI=m
# CONFIG_XEN_SCSI_FRONTEND is not setCONFIG_HYPERV_STORAGE=mCONFIG_LIBFC=mCONFIG_LIBFCOE=mCONFIG_FCOE=mCONFIG_FCOE_FNIC=m
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FDOMAIN_PCI is not set
# CONFIG_SCSI_GDTH is not setCONFIG_SCSI_ISCI=m
# CONFIG_SCSI_IPS is not setCONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not setCONFIG_SCSI_STEX=m
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not setCONFIG_SCSI_QLA_FC=mCONFIG_TCM_QLA2XXX=m
# CONFIG_TCM_QLA2XXX_DEBUG is not setCONFIG_SCSI_QLA_ISCSI=m
# CONFIG_QEDI is not set
# CONFIG_QEDF is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_WD719X is not setCONFIG_SCSI_DEBUG=mCONFIG_SCSI_PMCRAID=mCONFIG_SCSI_PM8001=m
# CONFIG_SCSI_BFA_FC is not setCONFIG_SCSI_VIRTIO=m
# CONFIG_SCSI_CHELSIO_FCOE is not setCONFIG_SCSI_DH=yCONFIG_SCSI_DH_RDAC=yCONFIG_SCSI_DH_HP_SW=yCONFIG_SCSI_DH_EMC=yCONFIG_SCSI_DH_ALUA=y
# end of SCSI device support
CONFIG_ATA=mCONFIG_ATA_VERBOSE_ERROR=yCONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not setCONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#CONFIG_SATA_AHCI=mCONFIG_SATA_MOBILE_LPM_POLICY=0CONFIG_SATA_AHCI_PLATFORM=m
# CONFIG_SATA_INIC162X is not setCONFIG_SATA_ACARD_AHCI=mCONFIG_SATA_SIL24=mCONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#CONFIG_PDC_ADMA=mCONFIG_SATA_QSTOR=mCONFIG_SATA_SX4=mCONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#CONFIG_ATA_PIIX=m
# CONFIG_SATA_DWC is not setCONFIG_SATA_MV=mCONFIG_SATA_NV=mCONFIG_SATA_PROMISE=mCONFIG_SATA_SIL=mCONFIG_SATA_SIS=mCONFIG_SATA_SVW=mCONFIG_SATA_ULI=mCONFIG_SATA_VIA=mCONFIG_SATA_VITESSE=m
#
# PATA SFF controllers with BMDMA
#CONFIG_PATA_ALI=mCONFIG_PATA_AMD=mCONFIG_PATA_ARTOP=mCONFIG_PATA_ATIIXP=mCONFIG_PATA_ATP867X=mCONFIG_PATA_CMD64X=m
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not setCONFIG_PATA_HPT366=mCONFIG_PATA_HPT37X=mCONFIG_PATA_HPT3X2N=mCONFIG_PATA_HPT3X3=m
# CONFIG_PATA_HPT3X3_DMA is not setCONFIG_PATA_IT8213=mCONFIG_PATA_IT821X=mCONFIG_PATA_JMICRON=mCONFIG_PATA_MARVELL=mCONFIG_PATA_NETCELL=mCONFIG_PATA_NINJA32=m
# CONFIG_PATA_NS87415 is not setCONFIG_PATA_OLDPIIX=m
# CONFIG_PATA_OPTIDMA is not setCONFIG_PATA_PDC2027X=mCONFIG_PATA_PDC_OLD=m
# CONFIG_PATA_RADISYS is not setCONFIG_PATA_RDC=mCONFIG_PATA_SCH=mCONFIG_PATA_SERVERWORKS=mCONFIG_PATA_SIL680=mCONFIG_PATA_SIS=mCONFIG_PATA_TOSHIBA=m
# CONFIG_PATA_TRIFLEX is not setCONFIG_PATA_VIA=m
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#CONFIG_PATA_ACPI=mCONFIG_ATA_GENERIC=m
# CONFIG_PATA_LEGACY is not set CONFIG_MD=yCONFIG_BLK_DEV_MD=yCONFIG_MD_AUTODETECT=yCONFIG_MD_LINEAR=mCONFIG_MD_RAID0=mCONFIG_MD_RAID1=mCONFIG_MD_RAID10=mCONFIG_MD_RAID456=mCONFIG_MD_MULTIPATH=mCONFIG_MD_FAULTY=m
# CONFIG_MD_CLUSTER is not set
# CONFIG_BCACHE is not set CONFIG_BLK_DEV_DM_BUILTIN=y CONFIG_BLK_DEV_DM=mCONFIG_DM_DEBUG=yCONFIG_DM_BUFIO=m
# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set CONFIG_DM_BIO_PRISON=m CONFIG_DM_PERSISTENT_DATA=m
# CONFIG_DM_UNSTRIPED is not set CONFIG_DM_CRYPT=mCONFIG_DM_SNAPSHOT=m CONFIG_DM_THIN_PROVISIONING=m CONFIG_DM_CACHE=mCONFIG_DM_CACHE_SMQ=m
# CONFIG_DM_WRITECACHE is not set CONFIG_DM_ERA=m
# CONFIG_DM_CLONE is not set CONFIG_DM_MIRROR=m CONFIG_DM_LOG_USERSPACE=mCONFIG_DM_RAID=mCONFIG_DM_ZERO=mCONFIG_DM_MULTIPATH=m CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=mCONFIG_DM_DELAY=m
# CONFIG_DM_DUST is not set CONFIG_DM_UEVENT=yCONFIG_DM_FLAKEY=mCONFIG_DM_VERITY=m
# CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG is not set # CONFIG_DM_VERITY_FEC is not set CONFIG_DM_SWITCH=mCONFIG_DM_LOG_WRITES=m
# CONFIG_DM_INTEGRITY is not set
# CONFIG_DM_ZONED is not set CONFIG_TARGET_CORE=mCONFIG_TCM_IBLOCK=mCONFIG_TCM_FILEIO=mCONFIG_TCM_PSCSI=mCONFIG_TCM_USER2=m CONFIG_LOOPBACK_TARGET=mCONFIG_TCM_FC=mCONFIG_ISCSI_TARGET=m CONFIG_ISCSI_TARGET_CXGB4=m
# CONFIG_SBP_TARGET is not set CONFIG_FUSION=yCONFIG_FUSION_SPI=m
# CONFIG_FUSION_FC is not set CONFIG_FUSION_SAS=m CONFIG_FUSION_MAX_SGE=128 CONFIG_FUSION_CTL=m CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#CONFIG_FIREWIRE=mCONFIG_FIREWIRE_OHCI=mCONFIG_FIREWIRE_SBP2=mCONFIG_FIREWIRE_NET=m
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support
CONFIG_MACINTOSH_DRIVERS=yCONFIG_MAC_EMUMOUSEBTN=yCONFIG_NETDEVICES=yCONFIG_MII=yCONFIG_NET_CORE=yCONFIG_BONDING=mCONFIG_DUMMY=m
# CONFIG_EQUALIZER is not setCONFIG_NET_FC=yCONFIG_IFB=mCONFIG_NET_TEAM=mCONFIG_NET_TEAM_MODE_BROADCAST=mCONFIG_NET_TEAM_MODE_ROUNDROBIN=mCONFIG_NET_TEAM_MODE_RANDOM=mCONFIG_NET_TEAM_MODE_ACTIVEBACKUP=mCONFIG_NET_TEAM_MODE_LOADBALANCE=mCONFIG_MACVLAN=mCONFIG_MACVTAP=m
# CONFIG_IPVLAN is not setCONFIG_VXLAN=mCONFIG_GENEVE=m
# CONFIG_GTP is not setCONFIG_MACSEC=yCONFIG_NETCONSOLE=mCONFIG_NETCONSOLE_DYNAMIC=yCONFIG_NETPOLL=yCONFIG_NET_POLL_CONTROLLER=yCONFIG_NTB_NETDEV=mCONFIG_TUN=mCONFIG_TAP=m
# CONFIG_TUN_VNET_CROSS_LE is not setCONFIG_VETH=mCONFIG_VIRTIO_NET=mCONFIG_NLMON=mCONFIG_NET_VRF=yCONFIG_VSOCKMON=m
# CONFIG_ARCNET is not set
# CONFIG_ATM_DRIVERS is not set
#
# CAIF transport drivers
#
#
# Distributed Switch Architecture drivers
#
# end of Distributed Switch Architecture drivers
CONFIG_ETHERNET=yCONFIG_MDIO=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not setCONFIG_NET_VENDOR_AGERE=y
# CONFIG_ET131X is not setCONFIG_NET_VENDOR_ALACRITECH=y
# CONFIG_SLICOSS is not set
# CONFIG_NET_VENDOR_ALTEON is not set
# CONFIG_ALTERA_TSE is not setCONFIG_NET_VENDOR_AMAZON=yCONFIG_ENA_ETHERNET=mCONFIG_NET_VENDOR_AMD=yCONFIG_AMD8111_ETH=mCONFIG_PCNET32=mCONFIG_AMD_XGBE=m
# CONFIG_AMD_XGBE_DCB is not setCONFIG_AMD_XGBE_HAVE_ECC=yCONFIG_NET_VENDOR_AQUANTIA=yCONFIG_AQTION=mCONFIG_NET_VENDOR_ARC=yCONFIG_NET_VENDOR_ATHEROS=yCONFIG_ATL2=mCONFIG_ATL1=mCONFIG_ATL1E=mCONFIG_ATL1C=mCONFIG_ALX=mCONFIG_NET_VENDOR_AURORA=y
# CONFIG_AURORA_NB8800 is not setCONFIG_NET_VENDOR_BROADCOM=yCONFIG_B44=mCONFIG_B44_PCI_AUTOSELECT=yCONFIG_B44_PCICORE_AUTOSELECT=yCONFIG_B44_PCI=y
# CONFIG_BCMGENET is not setCONFIG_BNX2=mCONFIG_CNIC=mCONFIG_TIGON3=yCONFIG_TIGON3_HWMON=yCONFIG_BNX2X=mCONFIG_BNX2X_SRIOV=y
# CONFIG_SYSTEMPORT is not setCONFIG_BNXT=mCONFIG_BNXT_SRIOV=yCONFIG_BNXT_FLOWER_OFFLOAD=yCONFIG_BNXT_DCB=yCONFIG_BNXT_HWMON=yCONFIG_NET_VENDOR_BROCADE=yCONFIG_BNA=mCONFIG_NET_VENDOR_CADENCE=yCONFIG_MACB=mCONFIG_MACB_USE_HWSTAMP=y
# CONFIG_MACB_PCI is not setCONFIG_NET_VENDOR_CAVIUM=y
# CONFIG_THUNDER_NIC_PF is not set
# CONFIG_THUNDER_NIC_VF is not set
# CONFIG_THUNDER_NIC_BGX is not set
# CONFIG_THUNDER_NIC_RGX is not setCONFIG_CAVIUM_PTP=yCONFIG_LIQUIDIO=mCONFIG_LIQUIDIO_VF=mCONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not setCONFIG_CHELSIO_T3=mCONFIG_CHELSIO_T4=m
# CONFIG_CHELSIO_T4_DCB is not setCONFIG_CHELSIO_T4VF=mCONFIG_CHELSIO_LIB=mCONFIG_NET_VENDOR_CISCO=yCONFIG_ENIC=mCONFIG_NET_VENDOR_CORTINA=y
# CONFIG_CX_ECAT is not setCONFIG_DNET=mCONFIG_NET_VENDOR_DEC=yCONFIG_NET_TULIP=yCONFIG_DE2104X=mCONFIG_DE2104X_DSL=0CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not setCONFIG_TULIP_MMIO=y
# CONFIG_TULIP_NAPI is not setCONFIG_DE4X5=mCONFIG_WINBOND_840=mCONFIG_DM9102=mCONFIG_ULI526X=mCONFIG_PCMCIA_XIRCOM=m
# CONFIG_NET_VENDOR_DLINK is not setCONFIG_NET_VENDOR_EMULEX=yCONFIG_BE2NET=mCONFIG_BE2NET_HWMON=yCONFIG_BE2NET_BE2=yCONFIG_BE2NET_BE3=yCONFIG_BE2NET_LANCER=yCONFIG_BE2NET_SKYHAWK=yCONFIG_NET_VENDOR_EZCHIP=yCONFIG_NET_VENDOR_GOOGLE=y
# CONFIG_GVE is not set
# CONFIG_NET_VENDOR_HP is not setCONFIG_NET_VENDOR_HUAWEI=y
# CONFIG_HINIC is not set
# CONFIG_NET_VENDOR_I825XX is not setCONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not setCONFIG_E1000=yCONFIG_E1000E=yCONFIG_E1000E_HWTS=yCONFIG_IGB=yCONFIG_IGB_HWMON=yCONFIG_IGBVF=m
# CONFIG_IXGB is not setCONFIG_IXGBE=yCONFIG_IXGBE_HWMON=yCONFIG_IXGBE_DCB=yCONFIG_IXGBEVF=mCONFIG_I40E=yCONFIG_I40E_DCB=yCONFIG_IAVF=mCONFIG_I40EVF=m
# CONFIG_ICE is not setCONFIG_FM10K=m
# CONFIG_IGC is not setCONFIG_JME=mCONFIG_NET_VENDOR_MARVELL=yCONFIG_MVMDIO=mCONFIG_SKGE=y
# CONFIG_SKGE_DEBUG is not setCONFIG_SKGE_GENESIS=yCONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not setCONFIG_NET_VENDOR_MELLANOX=yCONFIG_MLX4_EN=mCONFIG_MLX4_EN_DCB=yCONFIG_MLX4_CORE=mCONFIG_MLX4_DEBUG=yCONFIG_MLX4_CORE_GEN2=y
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not setCONFIG_NET_VENDOR_MICROSEMI=y
# CONFIG_MSCC_OCELOT_SWITCH is not setCONFIG_NET_VENDOR_MYRI=yCONFIG_MYRI10GE=mCONFIG_MYRI10GE_DCA=y
# CONFIG_FEALNX is not set
# CONFIG_NET_VENDOR_NATSEMI is not setCONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not setCONFIG_NET_VENDOR_NETRONOME=yCONFIG_NFP=mCONFIG_NFP_APP_FLOWER=yCONFIG_NFP_APP_ABM_NIC=y
# CONFIG_NFP_DEBUG is not setCONFIG_NET_VENDOR_NI=y
# CONFIG_NI_XGE_MANAGEMENT_ENET is not set
# CONFIG_NET_VENDOR_NVIDIA is not setCONFIG_NET_VENDOR_OKI=yCONFIG_ETHOC=mCONFIG_NET_VENDOR_PACKET_ENGINES=y
# CONFIG_HAMACHI is not setCONFIG_YELLOWFIN=mCONFIG_NET_VENDOR_PENSANDO=y
# CONFIG_IONIC is not setCONFIG_NET_VENDOR_QLOGIC=yCONFIG_QLA3XXX=mCONFIG_QLCNIC=mCONFIG_QLCNIC_SRIOV=yCONFIG_QLCNIC_DCB=yCONFIG_QLCNIC_HWMON=yCONFIG_NETXEN_NIC=mCONFIG_QED=mCONFIG_QED_SRIOV=yCONFIG_QEDE=mCONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCOM_EMAC is not set
# CONFIG_RMNET is not set
# CONFIG_NET_VENDOR_RDC is not setCONFIG_NET_VENDOR_REALTEK=y
# CONFIG_ATP is not setCONFIG_8139CP=yCONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not setCONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not setCONFIG_R8169=yCONFIG_NET_VENDOR_RENESAS=yCONFIG_NET_VENDOR_ROCKER=yCONFIG_ROCKER=mCONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not set
# CONFIG_NET_VENDOR_SEEQ is not setCONFIG_NET_VENDOR_SOLARFLARE=yCONFIG_SFC=mCONFIG_SFC_MTD=yCONFIG_SFC_MCDI_MON=yCONFIG_SFC_SRIOV=yCONFIG_SFC_MCDI_LOGGING=yCONFIG_SFC_FALCON=mCONFIG_SFC_FALCON_MTD=y
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not setCONFIG_NET_VENDOR_SMSC=yCONFIG_EPIC100=m
# CONFIG_SMSC911X is not setCONFIG_SMSC9420=mCONFIG_NET_VENDOR_SOCIONEXT=y
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not setCONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not set
# CONFIG_NET_VENDOR_TEHUTI is not setCONFIG_NET_VENDOR_TI=y
# CONFIG_TI_CPSW_PHY_SEL is not setCONFIG_TLAN=m
# CONFIG_NET_VENDOR_VIA is not set
# CONFIG_NET_VENDOR_WIZNET is not setCONFIG_NET_VENDOR_XILINX=y
# CONFIG_XILINX_AXI_EMAC is not set
# CONFIG_XILINX_LL_TEMAC is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not setCONFIG_MDIO_DEVICE=yCONFIG_MDIO_BUS=y
# CONFIG_MDIO_BCM_UNIMAC is not setCONFIG_MDIO_BITBANG=m
# CONFIG_MDIO_GPIO is not set
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_THUNDER is not setCONFIG_PHYLIB=yCONFIG_SWPHY=y
# CONFIG_LED_TRIGGER_PHY is not set
#
# MII PHY device drivers
#
# CONFIG_ADIN_PHY is not setCONFIG_AMD_PHY=m
# CONFIG_AQUANTIA_PHY is not set
# CONFIG_AX88796B_PHY is not setCONFIG_AT803X_PHY=m
# CONFIG_BCM7XXX_PHY is not setCONFIG_BCM87XX_PHY=mCONFIG_BCM_NET_PHYLIB=mCONFIG_BROADCOM_PHY=mCONFIG_CICADA_PHY=m
# CONFIG_CORTINA_PHY is not setCONFIG_DAVICOM_PHY=m
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not setCONFIG_FIXED_PHY=yCONFIG_ICPLUS_PHY=m
# CONFIG_INTEL_XWAY_PHY is not setCONFIG_LSI_ET1011C_PHY=mCONFIG_LXT_PHY=mCONFIG_MARVELL_PHY=m
# CONFIG_MARVELL_10G_PHY is not setCONFIG_MICREL_PHY=m
# CONFIG_MICROCHIP_PHY is not set
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not setCONFIG_NATIONAL_PHY=m
# CONFIG_NXP_TJA11XX_PHY is not setCONFIG_QSEMI_PHY=mCONFIG_REALTEK_PHY=y
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not setCONFIG_SMSC_PHY=mCONFIG_STE10XP=m
# CONFIG_TERANETICS_PHY is not setCONFIG_VITESSE_PHY=m
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_MICREL_KS8995MA is not set
# CONFIG_PLIP is not setCONFIG_PPP=mCONFIG_PPP_BSDCOMP=mCONFIG_PPP_DEFLATE=mCONFIG_PPP_FILTER=yCONFIG_PPP_MPPE=mCONFIG_PPP_MULTILINK=yCONFIG_PPPOATM=mCONFIG_PPPOE=mCONFIG_PPTP=mCONFIG_PPPOL2TP=mCONFIG_PPP_ASYNC=mCONFIG_PPP_SYNC_TTY=mCONFIG_SLIP=mCONFIG_SLHC=mCONFIG_SLIP_COMPRESSED=yCONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not setCONFIG_USB_NET_DRIVERS=yCONFIG_USB_CATC=yCONFIG_USB_KAWETH=yCONFIG_USB_PEGASUS=yCONFIG_USB_RTL8150=yCONFIG_USB_RTL8152=m
# CONFIG_USB_LAN78XX is not setCONFIG_USB_USBNET=yCONFIG_USB_NET_AX8817X=yCONFIG_USB_NET_AX88179_178A=mCONFIG_USB_NET_CDCETHER=yCONFIG_USB_NET_CDC_EEM=yCONFIG_USB_NET_CDC_NCM=mCONFIG_USB_NET_HUAWEI_CDC_NCM=mCONFIG_USB_NET_CDC_MBIM=mCONFIG_USB_NET_DM9601=y
# CONFIG_USB_NET_SR9700 is not set
# CONFIG_USB_NET_SR9800 is not setCONFIG_USB_NET_SMSC75XX=yCONFIG_USB_NET_SMSC95XX=yCONFIG_USB_NET_GL620A=yCONFIG_USB_NET_NET1080=yCONFIG_USB_NET_PLUSB=yCONFIG_USB_NET_MCS7830=yCONFIG_USB_NET_RNDIS_HOST=yCONFIG_USB_NET_CDC_SUBSET_ENABLE=yCONFIG_USB_NET_CDC_SUBSET=yCONFIG_USB_ALI_M5632=yCONFIG_USB_AN2720=yCONFIG_USB_BELKIN=yCONFIG_USB_ARMLINUX=yCONFIG_USB_EPSON2888=yCONFIG_USB_KC2190=yCONFIG_USB_NET_ZAURUS=yCONFIG_USB_NET_CX82310_ETH=mCONFIG_USB_NET_KALMIA=mCONFIG_USB_NET_QMI_WWAN=mCONFIG_USB_HSO=mCONFIG_USB_NET_INT51X1=yCONFIG_USB_IPHETH=yCONFIG_USB_SIERRA_NET=yCONFIG_USB_VL600=m
# CONFIG_USB_NET_CH9200 is not set
# CONFIG_USB_NET_AQC111 is not setCONFIG_WLAN=y
# CONFIG_WIRELESS_WDS is not setCONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not setCONFIG_ATH_COMMON=mCONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not setCONFIG_ATH9K_HW=mCONFIG_ATH9K_COMMON=mCONFIG_ATH9K_BTCOEX_SUPPORT=y
# CONFIG_ATH9K is not setCONFIG_ATH9K_HTC=m
# CONFIG_ATH9K_HTC_DEBUGFS is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_WIL6210 is not set
# CONFIG_ATH10K is not set
# CONFIG_WCN36XX is not setCONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not setCONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_BRCMSMAC is not set
# CONFIG_BRCMFMAC is not setCONFIG_WLAN_VENDOR_CISCO=y
# CONFIG_AIRO is not setCONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not setCONFIG_IWLEGACY=mCONFIG_IWL4965=mCONFIG_IWL3945=m
#
# iwl3945 / iwl4965 Debugging Options # CONFIG_IWLEGACY_DEBUG=y CONFIG_IWLEGACY_DEBUGFS=y # end of iwl3945 / iwl4965 Debugging Options
CONFIG_IWLWIFI=mCONFIG_IWLWIFI_LEDS=yCONFIG_IWLDVM=mCONFIG_IWLMVM=mCONFIG_IWLWIFI_OPMODE_MODULAR=y
# CONFIG_IWLWIFI_BCAST_FILTERING is not set
#
# Debugging Options
#
# CONFIG_IWLWIFI_DEBUG is not setCONFIG_IWLWIFI_DEBUGFS=y
# CONFIG_IWLWIFI_DEVICE_TRACING is not set
# end of Debugging Options
CONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_PRISM54 is not setCONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_MWIFIEX is not set
# CONFIG_MWL8K is not setCONFIG_WLAN_VENDOR_MEDIATEK=y
# CONFIG_MT7601U is not set
# CONFIG_MT76x0U is not set
# CONFIG_MT76x0E is not set
# CONFIG_MT76x2E is not set
# CONFIG_MT76x2U is not set
# CONFIG_MT7603E is not set
# CONFIG_MT7615E is not setCONFIG_WLAN_VENDOR_RALINK=y
# CONFIG_RT2X00 is not setCONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
# CONFIG_RTL_CARDS is not set
# CONFIG_RTL8XXXU is not set
# CONFIG_RTW88 is not setCONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not setCONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not setCONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not setCONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not setCONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_QTNFMAC_PCIE is not setCONFIG_MAC80211_HWSIM=m
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_VIRT_WIFI is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers #CONFIG_WAN=y
# CONFIG_LANMEDIA is not setCONFIG_HDLC=mCONFIG_HDLC_RAW=m
# CONFIG_HDLC_RAW_ETH is not set CONFIG_HDLC_CISCO=mCONFIG_HDLC_FR=mCONFIG_HDLC_PPP=m
#
# X.25/LAPB support is disabled
#
# CONFIG_PCI200SYN is not set
# CONFIG_WANXL is not set
# CONFIG_PC300TOO is not set
# CONFIG_FARSYNC is not setCONFIG_DLCI=mCONFIG_DLCI_MAX=8
# CONFIG_SBNI is not setCONFIG_IEEE802154_DRIVERS=mCONFIG_IEEE802154_FAKELB=m
# CONFIG_IEEE802154_AT86RF230 is not set
# CONFIG_IEEE802154_MRF24J40 is not set
# CONFIG_IEEE802154_CC2520 is not set
# CONFIG_IEEE802154_ATUSB is not set
# CONFIG_IEEE802154_ADF7242 is not set
# CONFIG_IEEE802154_CA8210 is not set
# CONFIG_IEEE802154_MCR20A is not set
# CONFIG_IEEE802154_HWSIM is not setCONFIG_XEN_NETDEV_FRONTEND=mCONFIG_VMXNET3=mCONFIG_FUJITSU_ES=mCONFIG_THUNDERBOLT_NET=mCONFIG_HYPERV_NET=mCONFIG_NETDEVSIM=mCONFIG_NET_FAILOVER=mCONFIG_ISDN=yCONFIG_ISDN_CAPI=m
# CONFIG_CAPI_TRACE is not setCONFIG_ISDN_CAPI_CAPI20=mCONFIG_ISDN_CAPI_MIDDLEWARE=yCONFIG_MISDN=mCONFIG_MISDN_DSP=mCONFIG_MISDN_L1OIP=m
#
# mISDN hardware drivers
#CONFIG_MISDN_HFCPCI=mCONFIG_MISDN_HFCMULTI=mCONFIG_MISDN_HFCUSB=mCONFIG_MISDN_AVMFRITZ=mCONFIG_MISDN_SPEEDFAX=mCONFIG_MISDN_INFINEON=mCONFIG_MISDN_W6692=mCONFIG_MISDN_NETJET=mCONFIG_MISDN_HDLC=mCONFIG_MISDN_IPAC=mCONFIG_MISDN_ISAR=mCONFIG_NVM=y
# CONFIG_NVM_PBLK is not set
#
# Input device support
#CONFIG_INPUT=yCONFIG_INPUT_LEDS=yCONFIG_INPUT_FF_MEMLESS=yCONFIG_INPUT_POLLDEV=mCONFIG_INPUT_SPARSEKMAP=m
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not setCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_INPUT_JOYDEV=mCONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADC is not set
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
# CONFIG_KEYBOARD_APPLESPI is not setCONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_XTKBD is not setCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_MOUSE_PS2_ALPS=yCONFIG_MOUSE_PS2_BYD=yCONFIG_MOUSE_PS2_LOGIPS2PP=yCONFIG_MOUSE_PS2_SYNAPTICS=yCONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=yCONFIG_MOUSE_PS2_CYPRESS=yCONFIG_MOUSE_PS2_LIFEBOOK=yCONFIG_MOUSE_PS2_TRACKPOINT=yCONFIG_MOUSE_PS2_ELANTECH=yCONFIG_MOUSE_PS2_ELANTECH_SMBUS=yCONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not setCONFIG_MOUSE_PS2_FOCALTECH=yCONFIG_MOUSE_PS2_VMMOUSE=yCONFIG_MOUSE_PS2_SMBUS=yCONFIG_MOUSE_SERIAL=mCONFIG_MOUSE_APPLETOUCH=mCONFIG_MOUSE_BCM5974=mCONFIG_MOUSE_CYAPA=m
# CONFIG_MOUSE_ELAN_I2C is not setCONFIG_MOUSE_VSXXXAA=m
# CONFIG_MOUSE_GPIO is not setCONFIG_MOUSE_SYNAPTICS_I2C=mCONFIG_MOUSE_SYNAPTICS_USB=m
# CONFIG_INPUT_JOYSTICK is not setCONFIG_INPUT_TABLET=yCONFIG_TABLET_USB_ACECAD=mCONFIG_TABLET_USB_AIPTEK=mCONFIG_TABLET_USB_GTCO=m
# CONFIG_TABLET_USB_HANWANG is not setCONFIG_TABLET_USB_KBTAB=m
# CONFIG_TABLET_USB_PEGASUS is not set
# CONFIG_TABLET_SERIAL_WACOM4 is not setCONFIG_INPUT_TOUCHSCREEN=yCONFIG_TOUCHSCREEN_PROPERTIES=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_ADC is not set
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_BU21029 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8505 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_EXC3000 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_HIDEEP is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_S6SY761 is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_EKTF2127 is not set
# CONFIG_TOUCHSCREEN_ELAN is not setCONFIG_TOUCHSCREEN_ELO=mCONFIG_TOUCHSCREEN_WACOM_W8001=mCONFIG_TOUCHSCREEN_WACOM_I2C=m
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
# CONFIG_TOUCHSCREEN_WM97XX is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_RM_TS is not set
# CONFIG_TOUCHSCREEN_SILEAD is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_STMFTS is not set
# CONFIG_TOUCHSCREEN_SUR40 is not set
# CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZET6223 is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
# CONFIG_TOUCHSCREEN_IQS5XX is not setCONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
# CONFIG_INPUT_MSM_VIBRATOR is not setCONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_MMA8450 is not setCONFIG_INPUT_APANEL=mCONFIG_INPUT_GP2A=m
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_DECODER is not set
# CONFIG_INPUT_GPIO_VIBRA is not setCONFIG_INPUT_ATLAS_BTNS=mCONFIG_INPUT_ATI_REMOTE2=mCONFIG_INPUT_KEYSPAN_REMOTE=m
# CONFIG_INPUT_KXTJ9 is not setCONFIG_INPUT_POWERMATE=mCONFIG_INPUT_YEALINK=mCONFIG_INPUT_CM109=mCONFIG_INPUT_UINPUT=m
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_PWM_BEEPER is not set
# CONFIG_INPUT_PWM_VIBRA is not setCONFIG_INPUT_GPIO_ROTARY_ENCODER=m
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_CMA3000 is not setCONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
# CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not setCONFIG_RMI4_CORE=m
# CONFIG_RMI4_I2C is not set
# CONFIG_RMI4_SPI is not setCONFIG_RMI4_SMB=mCONFIG_RMI4_F03=yCONFIG_RMI4_F03_SERIO=mCONFIG_RMI4_2D_SENSOR=yCONFIG_RMI4_F11=yCONFIG_RMI4_F12=yCONFIG_RMI4_F30=y
# CONFIG_RMI4_F34 is not set
# CONFIG_RMI4_F54 is not set
# CONFIG_RMI4_F55 is not set
#
# Hardware I/O ports
#CONFIG_SERIO=yCONFIG_ARCH_MIGHT_HAVE_PC_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=yCONFIG_SERIO_RAW=mCONFIG_SERIO_ALTERA_PS2=m
# CONFIG_SERIO_PS2MULT is not setCONFIG_SERIO_ARC_PS2=mCONFIG_HYPERV_KEYBOARD=m
# CONFIG_SERIO_GPIO_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports # end of Input device support
#
# Character devices
#CONFIG_TTY=yCONFIG_VT=yCONFIG_CONSOLE_TRANSLATIONS=yCONFIG_VT_CONSOLE=yCONFIG_VT_CONSOLE_SLEEP=yCONFIG_HW_CONSOLE=yCONFIG_VT_HW_CONSOLE_BINDING=yCONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not setCONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not setCONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not setCONFIG_SYNCLINK=mCONFIG_SYNCLINKMP=mCONFIG_SYNCLINK_GT=mCONFIG_NOZOMI=m
# CONFIG_ISI is not setCONFIG_N_HDLC=mCONFIG_N_GSM=m
# CONFIG_TRACE_SINK is not set
# CONFIG_NULL_TTY is not setCONFIG_LDISC_AUTOLOAD=yCONFIG_DEVMEM=y
# CONFIG_DEVKMEM is not set
#
# Serial drivers
#CONFIG_SERIAL_EARLYCON=y CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_FINTEK is not set CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_DMA=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_EXAR=y CONFIG_SERIAL_8250_NR_UARTS=32 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y CONFIG_SERIAL_8250_DWLIB=y CONFIG_SERIAL_8250_DW=y
# CONFIG_SERIAL_8250_RT288X is not set CONFIG_SERIAL_8250_LPSS=y CONFIG_SERIAL_8250_MID=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not setCONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_SERIAL_JSM=m
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not setCONFIG_SERIAL_ARC=mCONFIG_SERIAL_ARC_NR_PORTS=1
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=y
# CONFIG_SERIAL_DEV_BUS is not set
# CONFIG_TTY_PRINTK is not setCONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not setCONFIG_PPDEV=mCONFIG_HVC_DRIVER=yCONFIG_HVC_IRQ=yCONFIG_HVC_XEN=yCONFIG_HVC_XEN_FRONTEND=yCONFIG_VIRTIO_CONSOLE=yCONFIG_IPMI_HANDLER=mCONFIG_IPMI_DMI_DECODE=yCONFIG_IPMI_PLAT_DATA=y
# CONFIG_IPMI_PANIC_EVENT is not setCONFIG_IPMI_DEVICE_INTERFACE=mCONFIG_IPMI_SI=mCONFIG_IPMI_SSIF=mCONFIG_IPMI_WATCHDOG=mCONFIG_IPMI_POWEROFF=mCONFIG_HW_RANDOM=yCONFIG_HW_RANDOM_TIMERIOMEM=mCONFIG_HW_RANDOM_INTEL=mCONFIG_HW_RANDOM_AMD=mCONFIG_HW_RANDOM_VIA=mCONFIG_HW_RANDOM_VIRTIO=yCONFIG_NVRAM=y
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not setCONFIG_RAW_DRIVER=yCONFIG_MAX_RAW_DEVS=8192CONFIG_HPET=yCONFIG_HPET_MMAP=y
# CONFIG_HPET_MMAP_DEFAULT is not setCONFIG_HANGCHECK_TIMER=mCONFIG_UV_MMTIMER=mCONFIG_TCG_TPM=yCONFIG_HW_RANDOM_TPM=yCONFIG_TCG_TIS_CORE=yCONFIG_TCG_TIS=y
# CONFIG_TCG_TIS_SPI is not setCONFIG_TCG_TIS_I2C_ATMEL=mCONFIG_TCG_TIS_I2C_INFINEON=mCONFIG_TCG_TIS_I2C_NUVOTON=mCONFIG_TCG_NSC=mCONFIG_TCG_ATMEL=mCONFIG_TCG_INFINEON=m
# CONFIG_TCG_XEN is not setCONFIG_TCG_CRB=y
# CONFIG_TCG_VTPM_PROXY is not setCONFIG_TCG_TIS_ST33ZP24=mCONFIG_TCG_TIS_ST33ZP24_I2C=m
# CONFIG_TCG_TIS_ST33ZP24_SPI is not setCONFIG_TELCLOCK=mCONFIG_DEVPORT=y
# CONFIG_XILLYBUS is not set
# end of Character devices
# CONFIG_RANDOM_TRUST_CPU is not set
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
#
# I2C support
#CONFIG_I2C=yCONFIG_ACPI_I2C_OPREGION=yCONFIG_I2C_BOARDINFO=yCONFIG_I2C_COMPAT=yCONFIG_I2C_CHARDEV=mCONFIG_I2C_MUX=m
#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_REG is not set
# CONFIG_I2C_MUX_MLXCPLD is not set
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=yCONFIG_I2C_SMBUS=mCONFIG_I2C_ALGOBIT=yCONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not setCONFIG_I2C_AMD756=mCONFIG_I2C_AMD756_S4882=mCONFIG_I2C_AMD8111=m
# CONFIG_I2C_AMD_MP2 is not setCONFIG_I2C_I801=mCONFIG_I2C_ISCH=mCONFIG_I2C_ISMT=mCONFIG_I2C_PIIX4=mCONFIG_I2C_NFORCE2=mCONFIG_I2C_NFORCE2_S4985=m
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not setCONFIG_I2C_SIS96X=mCONFIG_I2C_VIA=mCONFIG_I2C_VIAPRO=m
#
# ACPI drivers
#CONFIG_I2C_SCMI=m
#
# I2C system bus drivers (mostly embedded / system-on-chip) #
# CONFIG_I2C_CBUS_GPIO is not set CONFIG_I2C_DESIGNWARE_CORE=m CONFIG_I2C_DESIGNWARE_PLATFORM=m
# CONFIG_I2C_DESIGNWARE_SLAVE is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_DESIGNWARE_BAYTRAIL is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set CONFIG_I2C_PCA_PLATFORM=mCONFIG_I2C_SIMTEC=m
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#CONFIG_I2C_DIOLAN_U2C=mCONFIG_I2C_PARPORT=mCONFIG_I2C_PARPORT_LIGHT=m
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not setCONFIG_I2C_TINY_USB=mCONFIG_I2C_VIPERBOARD=m
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_MLXCPLD is not set
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=m
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# CONFIG_I3C is not setCONFIG_SPI=y
# CONFIG_SPI_DEBUG is not setCONFIG_SPI_MASTER=y
# CONFIG_SPI_MEM is not set
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_NXP_FLEXSPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not set
# CONFIG_SPMI is not set
# CONFIG_HSI is not setCONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set
#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not setCONFIG_PPS_CLIENT_LDISC=mCONFIG_PPS_CLIENT_PARPORT=mCONFIG_PPS_CLIENT_GPIO=m
#
# PPS generators support
#
#
# PTP clock support
#CONFIG_PTP_1588_CLOCK=yCONFIG_DP83640_PHY=mCONFIG_PTP_1588_CLOCK_KVM=m
# end of PTP clock support
CONFIG_PINCTRL=yCONFIG_PINMUX=yCONFIG_PINCONF=yCONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not setCONFIG_PINCTRL_AMD=m
# CONFIG_PINCTRL_MCP23S08 is not set
# CONFIG_PINCTRL_SX150X is not setCONFIG_PINCTRL_BAYTRAIL=y
# CONFIG_PINCTRL_CHERRYVIEW is not setCONFIG_PINCTRL_INTEL=m
# CONFIG_PINCTRL_BROXTON is not setCONFIG_PINCTRL_CANNONLAKE=m
# CONFIG_PINCTRL_CEDARFORK is not setCONFIG_PINCTRL_DENVERTON=mCONFIG_PINCTRL_GEMINILAKE=m
# CONFIG_PINCTRL_ICELAKE is not setCONFIG_PINCTRL_LEWISBURG=mCONFIG_PINCTRL_SUNRISEPOINT=mCONFIG_GPIOLIB=yCONFIG_GPIOLIB_FASTPATH_LIMIT=512CONFIG_GPIO_ACPI=yCONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not setCONFIG_GPIO_SYSFS=yCONFIG_GPIO_GENERIC=m
#
# Memory mapped GPIO drivers
#CONFIG_GPIO_AMDPT=m
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_EXAR is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not setCONFIG_GPIO_ICH=m
# CONFIG_GPIO_LYNXPOINT is not set
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_VX855 is not set
# CONFIG_GPIO_XILINX is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
#
# Port-mapped I/O GPIO drivers
#
# CONFIG_GPIO_F7188X is not set
# CONFIG_GPIO_IT87 is not set
# CONFIG_GPIO_SCH is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_WINBOND is not set
# CONFIG_GPIO_WS16C48 is not set
# end of Port-mapped I/O GPIO drivers
#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders
#
# MFD GPIO expanders
#
# end of MFD GPIO expanders
#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set
# end of PCI GPIO expanders
#
# SPI GPIO expanders
#
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders
#
# USB GPIO expanders
#CONFIG_GPIO_VIPERBOARD=m
# end of USB GPIO expanders
CONFIG_GPIO_MOCKUP=y
# CONFIG_W1 is not set
# CONFIG_POWER_AVS is not setCONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_RESTART is not setCONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not setCONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ25890 is not setCONFIG_CHARGER_SMB347=m
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_CHARGER_RT9455 is not setCONFIG_HWMON=yCONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#CONFIG_SENSORS_ABITUGURU=mCONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not setCONFIG_SENSORS_AD7414=mCONFIG_SENSORS_AD7418=mCONFIG_SENSORS_ADM1021=mCONFIG_SENSORS_ADM1025=mCONFIG_SENSORS_ADM1026=mCONFIG_SENSORS_ADM1029=mCONFIG_SENSORS_ADM1031=mCONFIG_SENSORS_ADM9240=mCONFIG_SENSORS_ADT7X10=m
# CONFIG_SENSORS_ADT7310 is not setCONFIG_SENSORS_ADT7410=mCONFIG_SENSORS_ADT7411=mCONFIG_SENSORS_ADT7462=mCONFIG_SENSORS_ADT7470=mCONFIG_SENSORS_ADT7475=m
# CONFIG_SENSORS_AS370 is not setCONFIG_SENSORS_ASC7621=mCONFIG_SENSORS_K8TEMP=mCONFIG_SENSORS_K10TEMP=mCONFIG_SENSORS_FAM15H_POWER=mCONFIG_SENSORS_APPLESMC=mCONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ASPEED is not setCONFIG_SENSORS_ATXP1=mCONFIG_SENSORS_DS620=mCONFIG_SENSORS_DS1621=mCONFIG_SENSORS_DELL_SMM=mCONFIG_SENSORS_I5K_AMB=mCONFIG_SENSORS_F71805F=mCONFIG_SENSORS_F71882FG=mCONFIG_SENSORS_F75375S=mCONFIG_SENSORS_FSCHMD=m
# CONFIG_SENSORS_FTSTEUTATES is not setCONFIG_SENSORS_GL518SM=mCONFIG_SENSORS_GL520SM=mCONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_HIH6130 is not setCONFIG_SENSORS_IBMAEM=mCONFIG_SENSORS_IBMPEX=m
# CONFIG_SENSORS_IIO_HWMON is not set
# CONFIG_SENSORS_I5500 is not setCONFIG_SENSORS_CORETEMP=mCONFIG_SENSORS_IT87=mCONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not setCONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2990 is not setCONFIG_SENSORS_LTC4151=mCONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not setCONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not setCONFIG_SENSORS_LTC4261=m
# CONFIG_SENSORS_MAX1111 is not setCONFIG_SENSORS_MAX16065=mCONFIG_SENSORS_MAX1619=mCONFIG_SENSORS_MAX1668=mCONFIG_SENSORS_MAX197=m
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX6621 is not setCONFIG_SENSORS_MAX6639=mCONFIG_SENSORS_MAX6642=mCONFIG_SENSORS_MAX6650=mCONFIG_SENSORS_MAX6697=m
# CONFIG_SENSORS_MAX31790 is not setCONFIG_SENSORS_MCP3021=m
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_ADCXX is not setCONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not setCONFIG_SENSORS_LM73=mCONFIG_SENSORS_LM75=mCONFIG_SENSORS_LM77=mCONFIG_SENSORS_LM78=mCONFIG_SENSORS_LM80=mCONFIG_SENSORS_LM83=mCONFIG_SENSORS_LM85=mCONFIG_SENSORS_LM87=mCONFIG_SENSORS_LM90=mCONFIG_SENSORS_LM92=mCONFIG_SENSORS_LM93=mCONFIG_SENSORS_LM95234=mCONFIG_SENSORS_LM95241=mCONFIG_SENSORS_LM95245=mCONFIG_SENSORS_PC87360=mCONFIG_SENSORS_PC87427=mCONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not setCONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not setCONFIG_SENSORS_PCF8591=mCONFIG_PMBUS=mCONFIG_SENSORS_PMBUS=mCONFIG_SENSORS_ADM1275=m
# CONFIG_SENSORS_IBM_CFFPS is not set
# CONFIG_SENSORS_INSPUR_IPSPS is not set
# CONFIG_SENSORS_IR35221 is not set
# CONFIG_SENSORS_IR38064 is not set
# CONFIG_SENSORS_IRPS5401 is not set
# CONFIG_SENSORS_ISL68137 is not setCONFIG_SENSORS_LM25066=mCONFIG_SENSORS_LTC2978=m
# CONFIG_SENSORS_LTC3815 is not setCONFIG_SENSORS_MAX16064=m
# CONFIG_SENSORS_MAX20751 is not set
# CONFIG_SENSORS_MAX31785 is not setCONFIG_SENSORS_MAX34440=mCONFIG_SENSORS_MAX8688=m
# CONFIG_SENSORS_PXE1610 is not set
# CONFIG_SENSORS_TPS40422 is not set
# CONFIG_SENSORS_TPS53679 is not setCONFIG_SENSORS_UCD9000=mCONFIG_SENSORS_UCD9200=mCONFIG_SENSORS_ZL6100=mCONFIG_SENSORS_SHT15=mCONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not setCONFIG_SENSORS_SIS5595=mCONFIG_SENSORS_DME1737=mCONFIG_SENSORS_EMC1403=m
# CONFIG_SENSORS_EMC2103 is not setCONFIG_SENSORS_EMC6W201=mCONFIG_SENSORS_SMSC47M1=mCONFIG_SENSORS_SMSC47M192=mCONFIG_SENSORS_SMSC47B397=mCONFIG_SENSORS_SCH56XX_COMMON=mCONFIG_SENSORS_SCH5627=mCONFIG_SENSORS_SCH5636=m
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not setCONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_ADS7871 is not setCONFIG_SENSORS_AMC6821=mCONFIG_SENSORS_INA209=mCONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not setCONFIG_SENSORS_THMC50=mCONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not setCONFIG_SENSORS_TMP401=mCONFIG_SENSORS_TMP421=mCONFIG_SENSORS_VIA_CPUTEMP=mCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_VT1211=mCONFIG_SENSORS_VT8231=m
# CONFIG_SENSORS_W83773G is not setCONFIG_SENSORS_W83781D=mCONFIG_SENSORS_W83791D=mCONFIG_SENSORS_W83792D=mCONFIG_SENSORS_W83793=mCONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not setCONFIG_SENSORS_W83L785TS=mCONFIG_SENSORS_W83L786NG=mCONFIG_SENSORS_W83627HF=mCONFIG_SENSORS_W83627EHF=m
# CONFIG_SENSORS_XGENE is not set
#
# ACPI drivers
#CONFIG_SENSORS_ACPI_POWER=m CONFIG_SENSORS_ATK0110=mCONFIG_THERMAL=y
# CONFIG_THERMAL_STATISTICS is not set CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0 CONFIG_THERMAL_HWMON=y CONFIG_THERMAL_WRITABLE_TRIPS=y CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set # CONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR is not set CONFIG_THERMAL_GOV_FAIR_SHARE=y CONFIG_THERMAL_GOV_STEP_WISE=y CONFIG_THERMAL_GOV_BANG_BANG=y CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_THERMAL_GOV_POWER_ALLOCATOR is not set # CONFIG_CLOCK_THERMAL is not set
# CONFIG_DEVFREQ_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set
#
# Intel thermal drivers
#CONFIG_INTEL_POWERCLAMP=mCONFIG_X86_PKG_TEMP_THERMAL=mCONFIG_INTEL_SOC_DTS_IOSF_CORE=m
# CONFIG_INTEL_SOC_DTS_THERMAL is not set
#
# ACPI INT340X thermal drivers
#CONFIG_INT340X_THERMAL=mCONFIG_ACPI_THERMAL_REL=m
# CONFIG_INT3406_THERMAL is not setCONFIG_PROC_THERMAL_MMIO_RAPL=y
# end of ACPI INT340X thermal drivers
# CONFIG_INTEL_PCH_THERMAL is not set
# end of Intel thermal drivers
# CONFIG_GENERIC_ADC_THERMAL is not setCONFIG_WATCHDOG=yCONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not setCONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=yCONFIG_WATCHDOG_OPEN_TIMEOUT=0CONFIG_WATCHDOG_SYSFS=y
#
# Watchdog Pretimeout Governors
#
# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set
#
# Watchdog Device Drivers
#CONFIG_SOFT_WATCHDOG=mCONFIG_WDAT_WDT=m
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not setCONFIG_ALIM1535_WDT=mCONFIG_ALIM7101_WDT=m
# CONFIG_EBC_C384_WDT is not setCONFIG_F71808E_WDT=mCONFIG_SP5100_TCO=mCONFIG_SBC_FITPC2_WATCHDOG=m
# CONFIG_EUROTECH_WDT is not setCONFIG_IB700_WDT=mCONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not setCONFIG_I6300ESB_WDT=yCONFIG_IE6XX_WDT=mCONFIG_ITCO_WDT=yCONFIG_ITCO_VENDOR_SUPPORT=yCONFIG_IT8712F_WDT=mCONFIG_IT87_WDT=mCONFIG_HP_WATCHDOG=mCONFIG_HPWDT_NMI_DECODING=y
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not setCONFIG_NV_TCO=m
# CONFIG_60XX_WDT is not set
# CONFIG_CPU5_WDT is not setCONFIG_SMSC_SCH311X_WDT=m
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_TQMX86_WDT is not setCONFIG_VIA_WDT=mCONFIG_W83627HF_WDT=mCONFIG_W83877F_WDT=mCONFIG_W83977F_WDT=mCONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not setCONFIG_INTEL_MEI_WDT=m
# CONFIG_NI903X_WDT is not set
# CONFIG_NIC7018_WDT is not set
# CONFIG_MEN_A21_WDT is not setCONFIG_XEN_WDT=m
#
# PCI-based Watchdog Cards
#CONFIG_PCIPCWATCHDOG=mCONFIG_WDTPCI=m
#
# USB-based Watchdog Cards
#CONFIG_USBPCWATCHDOG=mCONFIG_SSB_POSSIBLE=yCONFIG_SSB=mCONFIG_SSB_SPROM=yCONFIG_SSB_PCIHOST_POSSIBLE=yCONFIG_SSB_PCIHOST=yCONFIG_SSB_SDIOHOST_POSSIBLE=yCONFIG_SSB_SDIOHOST=yCONFIG_SSB_DRIVER_PCICORE_POSSIBLE=yCONFIG_SSB_DRIVER_PCICORE=yCONFIG_SSB_DRIVER_GPIO=yCONFIG_BCMA_POSSIBLE=yCONFIG_BCMA=mCONFIG_BCMA_HOST_PCI_POSSIBLE=yCONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not setCONFIG_BCMA_DRIVER_PCI=yCONFIG_BCMA_DRIVER_GMAC_CMN=yCONFIG_BCMA_DRIVER_GPIO=y
# CONFIG_BCMA_DEBUG is not set
#
# Multifunction device drivers
#CONFIG_MFD_CORE=y
# CONFIG_MFD_AS3711 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_INTEL_QUARK_I2C_GPIO is not setCONFIG_LPC_ICH=mCONFIG_LPC_SCH=m
# CONFIG_INTEL_SOC_PMIC_CHTDC_TI is not setCONFIG_MFD_INTEL_LPSS=yCONFIG_MFD_INTEL_LPSS_ACPI=yCONFIG_MFD_INTEL_LPSS_PCI=y
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not setCONFIG_MFD_VIPERBOARD=m
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_UCB1400_CORE is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not setCONFIG_MFD_SM501=mCONFIG_MFD_SM501_GPIO=y
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_SMSC is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_SYSCON is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TQMX86 is not setCONFIG_MFD_VX855=m
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# end of Multifunction device drivers
# CONFIG_REGULATOR is not setCONFIG_RC_CORE=mCONFIG_RC_MAP=mCONFIG_LIRC=yCONFIG_RC_DECODERS=yCONFIG_IR_NEC_DECODER=mCONFIG_IR_RC5_DECODER=mCONFIG_IR_RC6_DECODER=mCONFIG_IR_JVC_DECODER=mCONFIG_IR_SONY_DECODER=mCONFIG_IR_SANYO_DECODER=mCONFIG_IR_SHARP_DECODER=mCONFIG_IR_MCE_KBD_DECODER=m
# CONFIG_IR_XMP_DECODER is not setCONFIG_IR_IMON_DECODER=m
# CONFIG_IR_RCMM_DECODER is not setCONFIG_RC_DEVICES=yCONFIG_RC_ATI_REMOTE=mCONFIG_IR_ENE=mCONFIG_IR_IMON=m
# CONFIG_IR_IMON_RAW is not setCONFIG_IR_MCEUSB=mCONFIG_IR_ITE_CIR=mCONFIG_IR_FINTEK=mCONFIG_IR_NUVOTON=mCONFIG_IR_REDRAT3=mCONFIG_IR_STREAMZAP=mCONFIG_IR_WINBOND_CIR=m
# CONFIG_IR_IGORPLUGUSB is not setCONFIG_IR_IGUANA=mCONFIG_IR_TTUSBIR=mCONFIG_RC_LOOPBACK=m
# CONFIG_IR_SERIAL is not set
# CONFIG_IR_SIR is not set
# CONFIG_RC_XBOX_DVD is not setCONFIG_MEDIA_SUPPORT=m
#
# Multimedia core support
#CONFIG_MEDIA_CAMERA_SUPPORT=yCONFIG_MEDIA_ANALOG_TV_SUPPORT=yCONFIG_MEDIA_DIGITAL_TV_SUPPORT=yCONFIG_MEDIA_RADIO_SUPPORT=y
# CONFIG_MEDIA_SDR_SUPPORT is not set
# CONFIG_MEDIA_CEC_SUPPORT is not setCONFIG_MEDIA_CONTROLLER=yCONFIG_MEDIA_CONTROLLER_DVB=yCONFIG_VIDEO_DEV=m
# CONFIG_VIDEO_V4L2_SUBDEV_API is not setCONFIG_VIDEO_V4L2=mCONFIG_VIDEO_V4L2_I2C=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not setCONFIG_VIDEO_TUNER=mCONFIG_VIDEOBUF_GEN=mCONFIG_VIDEOBUF_DMA_SG=mCONFIG_VIDEOBUF_VMALLOC=mCONFIG_DVB_CORE=m
# CONFIG_DVB_MMAP is not setCONFIG_DVB_NET=yCONFIG_TTPCI_EEPROM=mCONFIG_DVB_MAX_ADAPTERS=8CONFIG_DVB_DYNAMIC_MINORS=y
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set
#
# Media drivers
#CONFIG_MEDIA_USB_SUPPORT=y
#
# Webcam devices
#CONFIG_USB_VIDEO_CLASS=mCONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=yCONFIG_USB_GSPCA=mCONFIG_USB_M5602=mCONFIG_USB_STV06XX=mCONFIG_USB_GL860=mCONFIG_USB_GSPCA_BENQ=mCONFIG_USB_GSPCA_CONEX=mCONFIG_USB_GSPCA_CPIA1=m
# CONFIG_USB_GSPCA_DTCS033 is not setCONFIG_USB_GSPCA_ETOMS=mCONFIG_USB_GSPCA_FINEPIX=mCONFIG_USB_GSPCA_JEILINJ=mCONFIG_USB_GSPCA_JL2005BCD=m
# CONFIG_USB_GSPCA_KINECT is not setCONFIG_USB_GSPCA_KONICA=mCONFIG_USB_GSPCA_MARS=mCONFIG_USB_GSPCA_MR97310A=mCONFIG_USB_GSPCA_NW80X=mCONFIG_USB_GSPCA_OV519=mCONFIG_USB_GSPCA_OV534=mCONFIG_USB_GSPCA_OV534_9=mCONFIG_USB_GSPCA_PAC207=mCONFIG_USB_GSPCA_PAC7302=mCONFIG_USB_GSPCA_PAC7311=mCONFIG_USB_GSPCA_SE401=mCONFIG_USB_GSPCA_SN9C2028=mCONFIG_USB_GSPCA_SN9C20X=mCONFIG_USB_GSPCA_SONIXB=mCONFIG_USB_GSPCA_SONIXJ=mCONFIG_USB_GSPCA_SPCA500=mCONFIG_USB_GSPCA_SPCA501=mCONFIG_USB_GSPCA_SPCA505=mCONFIG_USB_GSPCA_SPCA506=mCONFIG_USB_GSPCA_SPCA508=mCONFIG_USB_GSPCA_SPCA561=mCONFIG_USB_GSPCA_SPCA1528=mCONFIG_USB_GSPCA_SQ905=mCONFIG_USB_GSPCA_SQ905C=mCONFIG_USB_GSPCA_SQ930X=mCONFIG_USB_GSPCA_STK014=m
# CONFIG_USB_GSPCA_STK1135 is not setCONFIG_USB_GSPCA_STV0680=mCONFIG_USB_GSPCA_SUNPLUS=mCONFIG_USB_GSPCA_T613=mCONFIG_USB_GSPCA_TOPRO=m
# CONFIG_USB_GSPCA_TOUPTEK is not setCONFIG_USB_GSPCA_TV8532=mCONFIG_USB_GSPCA_VC032X=mCONFIG_USB_GSPCA_VICAM=mCONFIG_USB_GSPCA_XIRLINK_CIT=mCONFIG_USB_GSPCA_ZC3XX=mCONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not setCONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_VIDEO_CPIA2 is not setCONFIG_USB_ZR364XX=mCONFIG_USB_STKWEBCAM=mCONFIG_USB_S2255=m
# CONFIG_VIDEO_USBTV is not set
#
# Analog TV USB devices
#CONFIG_VIDEO_PVRUSB2=mCONFIG_VIDEO_PVRUSB2_SYSFS=yCONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not setCONFIG_VIDEO_HDPVR=mCONFIG_VIDEO_USBVISION=m
# CONFIG_VIDEO_STK1160_COMMON is not set
# CONFIG_VIDEO_GO7007 is not set
#
# Analog/digital TV USB devices
#CONFIG_VIDEO_AU0828=mCONFIG_VIDEO_AU0828_V4L2=y
# CONFIG_VIDEO_AU0828_RC is not setCONFIG_VIDEO_CX231XX=mCONFIG_VIDEO_CX231XX_RC=yCONFIG_VIDEO_CX231XX_ALSA=mCONFIG_VIDEO_CX231XX_DVB=mCONFIG_VIDEO_TM6000=mCONFIG_VIDEO_TM6000_ALSA=mCONFIG_VIDEO_TM6000_DVB=m
#
# Digital TV USB devices
#CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not setCONFIG_DVB_USB_DIB3000MC=mCONFIG_DVB_USB_A800=mCONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not setCONFIG_DVB_USB_DIBUSB_MC=mCONFIG_DVB_USB_DIB0700=mCONFIG_DVB_USB_UMT_010=mCONFIG_DVB_USB_CXUSB=m
# CONFIG_DVB_USB_CXUSB_ANALOG is not setCONFIG_DVB_USB_M920X=mCONFIG_DVB_USB_DIGITV=mCONFIG_DVB_USB_VP7045=mCONFIG_DVB_USB_VP702X=mCONFIG_DVB_USB_GP8PSK=mCONFIG_DVB_USB_NOVA_T_USB2=mCONFIG_DVB_USB_TTUSB2=mCONFIG_DVB_USB_DTT200U=mCONFIG_DVB_USB_OPERA1=mCONFIG_DVB_USB_AF9005=mCONFIG_DVB_USB_AF9005_REMOTE=mCONFIG_DVB_USB_PCTV452E=mCONFIG_DVB_USB_DW2102=mCONFIG_DVB_USB_CINERGY_T2=mCONFIG_DVB_USB_DTV5100=mCONFIG_DVB_USB_AZ6027=mCONFIG_DVB_USB_TECHNISAT_USB2=mCONFIG_DVB_USB_V2=mCONFIG_DVB_USB_AF9015=mCONFIG_DVB_USB_AF9035=mCONFIG_DVB_USB_ANYSEE=mCONFIG_DVB_USB_AU6610=mCONFIG_DVB_USB_AZ6007=mCONFIG_DVB_USB_CE6230=mCONFIG_DVB_USB_EC168=mCONFIG_DVB_USB_GL861=mCONFIG_DVB_USB_LME2510=mCONFIG_DVB_USB_MXL111SF=mCONFIG_DVB_USB_RTL28XXU=m
# CONFIG_DVB_USB_DVBSKY is not set
# CONFIG_DVB_USB_ZD1301 is not setCONFIG_DVB_TTUSB_BUDGET=mCONFIG_DVB_TTUSB_DEC=mCONFIG_SMS_USB_DRV=mCONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set
# CONFIG_DVB_AS102 is not set
#
# Webcam, TV (analog/digital) USB devices
#CONFIG_VIDEO_EM28XX=m
# CONFIG_VIDEO_EM28XX_V4L2 is not setCONFIG_VIDEO_EM28XX_ALSA=mCONFIG_VIDEO_EM28XX_DVB=mCONFIG_VIDEO_EM28XX_RC=mCONFIG_MEDIA_PCI_SUPPORT=y
#
# Media capture support
#
# CONFIG_VIDEO_MEYE is not set
# CONFIG_VIDEO_SOLO6X10 is not set
# CONFIG_VIDEO_TW5864 is not set
# CONFIG_VIDEO_TW68 is not set
# CONFIG_VIDEO_TW686X is not set
#
# Media capture/analog TV support
#CONFIG_VIDEO_IVTV=m
# CONFIG_VIDEO_IVTV_DEPRECATED_IOCTLS is not set
# CONFIG_VIDEO_IVTV_ALSA is not setCONFIG_VIDEO_FB_IVTV=m
# CONFIG_VIDEO_FB_IVTV_FORCE_PAT is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DT3155 is not set
#
# Media capture/analog/hybrid TV support
#CONFIG_VIDEO_CX18=mCONFIG_VIDEO_CX18_ALSA=mCONFIG_VIDEO_CX23885=mCONFIG_MEDIA_ALTERA_CI=m
# CONFIG_VIDEO_CX25821 is not setCONFIG_VIDEO_CX88=mCONFIG_VIDEO_CX88_ALSA=mCONFIG_VIDEO_CX88_BLACKBIRD=mCONFIG_VIDEO_CX88_DVB=mCONFIG_VIDEO_CX88_ENABLE_VP3054=yCONFIG_VIDEO_CX88_VP3054=mCONFIG_VIDEO_CX88_MPEG=mCONFIG_VIDEO_BT848=mCONFIG_DVB_BT8XX=mCONFIG_VIDEO_SAA7134=mCONFIG_VIDEO_SAA7134_ALSA=mCONFIG_VIDEO_SAA7134_RC=yCONFIG_VIDEO_SAA7134_DVB=mCONFIG_VIDEO_SAA7164=m
#
# Media digital TV PCI Adapters
#CONFIG_DVB_AV7110_IR=yCONFIG_DVB_AV7110=mCONFIG_DVB_AV7110_OSD=yCONFIG_DVB_BUDGET_CORE=mCONFIG_DVB_BUDGET=mCONFIG_DVB_BUDGET_CI=mCONFIG_DVB_BUDGET_AV=mCONFIG_DVB_BUDGET_PATCH=mCONFIG_DVB_B2C2_FLEXCOP_PCI=m
# CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not setCONFIG_DVB_PLUTO2=mCONFIG_DVB_DM1105=mCONFIG_DVB_PT1=m
# CONFIG_DVB_PT3 is not setCONFIG_MANTIS_CORE=mCONFIG_DVB_MANTIS=mCONFIG_DVB_HOPPER=mCONFIG_DVB_NGENE=mCONFIG_DVB_DDBRIDGE=m
# CONFIG_DVB_DDBRIDGE_MSIENABLE is not set
# CONFIG_DVB_SMIPCIE is not set
# CONFIG_DVB_NETUP_UNIDVB is not set
# CONFIG_V4L_PLATFORM_DRIVERS is not set
# CONFIG_V4L_MEM2MEM_DRIVERS is not set
# CONFIG_V4L_TEST_DRIVERS is not set
# CONFIG_DVB_PLATFORM_DRIVERS is not set
#
# Supported MMC/SDIO adapters
#CONFIG_SMS_SDIO_DRV=mCONFIG_RADIO_ADAPTERS=yCONFIG_RADIO_TEA575X=m
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not set
#
# Texas Instruments WL128x FM driver (ST based)
#
# end of Texas Instruments WL128x FM driver (ST based)
#
# Supported FireWire (IEEE 1394) Adapters
#CONFIG_DVB_FIREDTV=mCONFIG_DVB_FIREDTV_INPUT=yCONFIG_MEDIA_COMMON_OPTIONS=y
#
# common driver options # CONFIG_VIDEO_CX2341X=m CONFIG_VIDEO_TVEEPROM=m CONFIG_CYPRESS_FIRMWARE=m CONFIG_VIDEOBUF2_CORE=m CONFIG_VIDEOBUF2_V4L2=m CONFIG_VIDEOBUF2_MEMOPS=m CONFIG_VIDEOBUF2_VMALLOC=m CONFIG_VIDEOBUF2_DMA_SG=m CONFIG_VIDEOBUF2_DVB=m CONFIG_DVB_B2C2_FLEXCOP=m CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_SMS_SIANO_MDTV=m CONFIG_SMS_SIANO_RC=y # CONFIG_SMS_SIANO_DEBUGFS is not set
#
# Media ancillary drivers (tuners, sensors, i2c, spi, frontends) #CONFIG_MEDIA_SUBDRV_AUTOSELECT=yCONFIG_MEDIA_ATTACH=yCONFIG_VIDEO_IR_I2C=m
#
# I2C Encoders, decoders, sensors and other helper chips #
#
# Audio decoders, processors and mixers
#CONFIG_VIDEO_TVAUDIO=mCONFIG_VIDEO_TDA7432=m
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not setCONFIG_VIDEO_MSP3400=mCONFIG_VIDEO_CS3308=mCONFIG_VIDEO_CS5345=mCONFIG_VIDEO_CS53L32A=m
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_UDA1342 is not setCONFIG_VIDEO_WM8775=mCONFIG_VIDEO_WM8739=mCONFIG_VIDEO_VP27SMPX=m
# CONFIG_VIDEO_SONY_BTF_MPX is not set
#
# RDS decoders
#CONFIG_VIDEO_SAA6588=m
#
# Video decoders
#
# CONFIG_VIDEO_ADV7183 is not set
# CONFIG_VIDEO_BT819 is not set
# CONFIG_VIDEO_BT856 is not set
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_KS0127 is not set
# CONFIG_VIDEO_ML86V7667 is not set
# CONFIG_VIDEO_SAA7110 is not setCONFIG_VIDEO_SAA711X=m
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set
# CONFIG_VIDEO_TVP7002 is not set
# CONFIG_VIDEO_TW2804 is not set
# CONFIG_VIDEO_TW9903 is not set
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_TW9910 is not set
# CONFIG_VIDEO_VPX3220 is not set
#
# Video and audio decoders
#CONFIG_VIDEO_SAA717X=mCONFIG_VIDEO_CX25840=m
#
# Video encoders
#CONFIG_VIDEO_SAA7127=m
# CONFIG_VIDEO_SAA7185 is not set
# CONFIG_VIDEO_ADV7170 is not set
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not set
# CONFIG_VIDEO_ADV7393 is not set
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_THS8200 is not set
#
# Camera sensor devices
#
# CONFIG_VIDEO_OV2640 is not set
# CONFIG_VIDEO_OV2659 is not set
# CONFIG_VIDEO_OV2680 is not set
# CONFIG_VIDEO_OV2685 is not set
# CONFIG_VIDEO_OV6650 is not set
# CONFIG_VIDEO_OV5695 is not set
# CONFIG_VIDEO_OV772X is not set
# CONFIG_VIDEO_OV7640 is not set
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV7740 is not set
# CONFIG_VIDEO_OV9640 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M111 is not set
# CONFIG_VIDEO_MT9T112 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V111 is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_RJ54N1 is not set
#
# Lens drivers
#
# CONFIG_VIDEO_AD5820 is not set
#
# Flash devices
#
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set
#
# Video improvement chips
#CONFIG_VIDEO_UPD64031A=mCONFIG_VIDEO_UPD64083=m
#
# Audio/Video compression chips
#CONFIG_VIDEO_SAA6752HS=m
#
# SDR tuner chips
#
#
# Miscellaneous helper chips
#
# CONFIG_VIDEO_THS7303 is not setCONFIG_VIDEO_M52790=m
# CONFIG_VIDEO_I2C is not set
# end of I2C Encoders, decoders, sensors and other helper chips
#
# SPI helper chips
#
# end of SPI helper chips
#
# Media SPI Adapters
#
# CONFIG_CXD2880_SPI_DRV is not set
# end of Media SPI Adapters
CONFIG_MEDIA_TUNER=m
#
# Customize TV tuners
#CONFIG_MEDIA_TUNER_SIMPLE=mCONFIG_MEDIA_TUNER_TDA18250=mCONFIG_MEDIA_TUNER_TDA8290=mCONFIG_MEDIA_TUNER_TDA827X=mCONFIG_MEDIA_TUNER_TDA18271=mCONFIG_MEDIA_TUNER_TDA9887=mCONFIG_MEDIA_TUNER_TEA5761=mCONFIG_MEDIA_TUNER_TEA5767=m
# CONFIG_MEDIA_TUNER_MSI001 is not setCONFIG_MEDIA_TUNER_MT20XX=mCONFIG_MEDIA_TUNER_MT2060=mCONFIG_MEDIA_TUNER_MT2063=mCONFIG_MEDIA_TUNER_MT2266=mCONFIG_MEDIA_TUNER_MT2131=mCONFIG_MEDIA_TUNER_QT1010=mCONFIG_MEDIA_TUNER_XC2028=mCONFIG_MEDIA_TUNER_XC5000=mCONFIG_MEDIA_TUNER_XC4000=mCONFIG_MEDIA_TUNER_MXL5005S=mCONFIG_MEDIA_TUNER_MXL5007T=mCONFIG_MEDIA_TUNER_MC44S803=mCONFIG_MEDIA_TUNER_MAX2165=mCONFIG_MEDIA_TUNER_TDA18218=mCONFIG_MEDIA_TUNER_FC0011=mCONFIG_MEDIA_TUNER_FC0012=mCONFIG_MEDIA_TUNER_FC0013=mCONFIG_MEDIA_TUNER_TDA18212=mCONFIG_MEDIA_TUNER_E4000=mCONFIG_MEDIA_TUNER_FC2580=mCONFIG_MEDIA_TUNER_M88RS6000T=mCONFIG_MEDIA_TUNER_TUA9001=mCONFIG_MEDIA_TUNER_SI2157=mCONFIG_MEDIA_TUNER_IT913X=mCONFIG_MEDIA_TUNER_R820T=m
# CONFIG_MEDIA_TUNER_MXL301RF is not setCONFIG_MEDIA_TUNER_QM1D1C0042=mCONFIG_MEDIA_TUNER_QM1D1B0004=m
# end of Customize TV tuners
#
# Customise DVB Frontends
#
#
# Multistandard (satellite) frontends
#CONFIG_DVB_STB0899=mCONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=mCONFIG_DVB_STV0910=m
CONFIG_DVB_STV6110x=mCONFIG_DVB_STV6111=mCONFIG_DVB_MXL5XX=mCONFIG_DVB_M88DS3103=m
#
# Multistandard (cable + terrestrial) frontends
#CONFIG_DVB_DRXK=mCONFIG_DVB_TDA18271C2DD=mCONFIG_DVB_SI2165=mCONFIG_DVB_MN88472=mCONFIG_DVB_MN88473=m
#
# DVB-S (satellite) frontends
#CONFIG_DVB_CX24110=mCONFIG_DVB_CX24123=mCONFIG_DVB_MT312=mCONFIG_DVB_ZL10036=mCONFIG_DVB_ZL10039=mCONFIG_DVB_S5H1420=mCONFIG_DVB_STV0288=mCONFIG_DVB_STB6000=mCONFIG_DVB_STV0299=mCONFIG_DVB_STV6110=mCONFIG_DVB_STV0900=mCONFIG_DVB_TDA8083=mCONFIG_DVB_TDA10086=mCONFIG_DVB_TDA8261=mCONFIG_DVB_VES1X93=mCONFIG_DVB_TUNER_ITD1000=mCONFIG_DVB_TUNER_CX24113=mCONFIG_DVB_TDA826X=mCONFIG_DVB_TUA6100=mCONFIG_DVB_CX24116=mCONFIG_DVB_CX24117=mCONFIG_DVB_CX24120=mCONFIG_DVB_SI21XX=mCONFIG_DVB_TS2020=mCONFIG_DVB_DS3000=mCONFIG_DVB_MB86A16=mCONFIG_DVB_TDA10071=m
#
# DVB-T (terrestrial) frontends
#CONFIG_DVB_SP8870=mCONFIG_DVB_SP887X=mCONFIG_DVB_CX22700=mCONFIG_DVB_CX22702=m
# CONFIG_DVB_S5H1432 is not setCONFIG_DVB_DRXD=mCONFIG_DVB_L64781=mCONFIG_DVB_TDA1004X=mCONFIG_DVB_NXT6000=mCONFIG_DVB_MT352=mCONFIG_DVB_ZL10353=mCONFIG_DVB_DIB3000MB=mCONFIG_DVB_DIB3000MC=mCONFIG_DVB_DIB7000M=mCONFIG_DVB_DIB7000P=m
# CONFIG_DVB_DIB9000 is not setCONFIG_DVB_TDA10048=mCONFIG_DVB_AF9013=mCONFIG_DVB_EC100=mCONFIG_DVB_STV0367=mCONFIG_DVB_CXD2820R=mCONFIG_DVB_CXD2841ER=mCONFIG_DVB_RTL2830=mCONFIG_DVB_RTL2832=mCONFIG_DVB_SI2168=m
# CONFIG_DVB_ZD1301_DEMOD is not setCONFIG_DVB_GP8PSK_FE=m
# CONFIG_DVB_CXD2880 is not set
#
# DVB-C (cable) frontends
#CONFIG_DVB_VES1820=mCONFIG_DVB_TDA10021=mCONFIG_DVB_TDA10023=mCONFIG_DVB_STV0297=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends #CONFIG_DVB_NXT200X=mCONFIG_DVB_OR51211=mCONFIG_DVB_OR51132=mCONFIG_DVB_BCM3510=mCONFIG_DVB_LGDT330X=mCONFIG_DVB_LGDT3305=mCONFIG_DVB_LGDT3306A=mCONFIG_DVB_LG2160=mCONFIG_DVB_S5H1409=mCONFIG_DVB_AU8522=mCONFIG_DVB_AU8522_DTV=mCONFIG_DVB_AU8522_V4L=mCONFIG_DVB_S5H1411=m
#
# ISDB-T (terrestrial) frontends
#CONFIG_DVB_S921=mCONFIG_DVB_DIB8000=mCONFIG_DVB_MB86A20S=m
#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends #CONFIG_DVB_TC90522=m
# CONFIG_DVB_MN88443X is not set
#
# Digital terrestrial only tuners/PLL
#CONFIG_DVB_PLL=mCONFIG_DVB_TUNER_DIB0070=mCONFIG_DVB_TUNER_DIB0090=m
#
# SEC control devices for DVB-S
#CONFIG_DVB_DRX39XYJ=mCONFIG_DVB_LNBH25=m
# CONFIG_DVB_LNBH29 is not setCONFIG_DVB_LNBP21=mCONFIG_DVB_LNBP22=mCONFIG_DVB_ISL6405=mCONFIG_DVB_ISL6421=mCONFIG_DVB_ISL6423=mCONFIG_DVB_A8293=m
# CONFIG_DVB_LGS8GL5 is not setCONFIG_DVB_LGS8GXX=mCONFIG_DVB_ATBM8830=m
CONFIG_DVB_TDA665x=mCONFIG_DVB_IX2505V=mCONFIG_DVB_M88RS2000=mCONFIG_DVB_AF9033=m
# CONFIG_DVB_HORUS3A is not set
# CONFIG_DVB_ASCOT2E is not set
# CONFIG_DVB_HELENE is not set
#
# Common Interface (EN50221) controller drivers
#CONFIG_DVB_CXD2099=m
# CONFIG_DVB_SP2 is not set
#
# Tools to develop new frontends
#CONFIG_DVB_DUMMY_FE=m
# end of Customise DVB Frontends
#
# Graphics support
#CONFIG_AGP=yCONFIG_AGP_AMD64=yCONFIG_AGP_INTEL=yCONFIG_AGP_SIS=yCONFIG_AGP_VIA=yCONFIG_INTEL_GTT=yCONFIG_VGA_ARB=yCONFIG_VGA_ARB_MAX_GPUS=64CONFIG_VGA_SWITCHEROO=yCONFIG_DRM=mCONFIG_DRM_MIPI_DSI=yCONFIG_DRM_DP_AUX_CHARDEV=yCONFIG_DRM_DEBUG_SELFTEST=mCONFIG_DRM_KMS_HELPER=mCONFIG_DRM_KMS_FB_HELPER=yCONFIG_DRM_FBDEV_EMULATION=yCONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not setCONFIG_DRM_LOAD_EDID_FIRMWARE=y
# CONFIG_DRM_DP_CEC is not setCONFIG_DRM_TTM=mCONFIG_DRM_VRAM_HELPER=mCONFIG_DRM_GEM_SHMEM_HELPER=y
#
# I2C encoder or helper chips
#CONFIG_DRM_I2C_CH7006=mCONFIG_DRM_I2C_SIL164=m
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_I2C_NXP_TDA9950 is not set
# end of I2C encoder or helper chips
#
# ARM devices
#
# end of ARM devices
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
#
# ACP (Audio CoProcessor) Configuration
#
# end of ACP (Audio CoProcessor) Configuration
# CONFIG_DRM_NOUVEAU is not setCONFIG_DRM_I915=m
# CONFIG_DRM_I915_ALPHA_SUPPORT is not setCONFIG_DRM_I915_FORCE_PROBE=""CONFIG_DRM_I915_CAPTURE_ERROR=yCONFIG_DRM_I915_COMPRESS_ERROR=yCONFIG_DRM_I915_USERPTR=yCONFIG_DRM_I915_GVT=yCONFIG_DRM_I915_GVT_KVMGT=m
#
# drm/i915 Debugging # # CONFIG_DRM_I915_WERROR is not set # CONFIG_DRM_I915_DEBUG is not set # CONFIG_DRM_I915_DEBUG_MMIO is not set # CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set # CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set # CONFIG_DRM_I915_DEBUG_GUC is not set # CONFIG_DRM_I915_SELFTEST is not set # CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set # CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set # CONFIG_DRM_I915_DEBUG_RUNTIME_PM is not set # end of drm/i915 Debugging
#
# drm/i915 Profile Guided Optimisation # CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250 CONFIG_DRM_I915_SPIN_REQUEST=5 # end of drm/i915 Profile Guided Optimisation
CONFIG_DRM_VGEM=m
# CONFIG_DRM_VKMS is not setCONFIG_DRM_VMWGFX=mCONFIG_DRM_VMWGFX_FBCON=yCONFIG_DRM_GMA500=mCONFIG_DRM_GMA600=yCONFIG_DRM_GMA3600=yCONFIG_DRM_UDL=mCONFIG_DRM_AST=mCONFIG_DRM_MGAG200=mCONFIG_DRM_CIRRUS_QEMU=mCONFIG_DRM_QXL=mCONFIG_DRM_BOCHS=mCONFIG_DRM_VIRTIO_GPU=mCONFIG_DRM_PANEL=y
#
# Display Panels
#
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set
# end of Display Panels
CONFIG_DRM_BRIDGE=yCONFIG_DRM_PANEL_BRIDGE=y
#
# Display Interface Bridges
#
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
# end of Display Interface Bridges
# CONFIG_DRM_ETNAVIV is not set
# CONFIG_DRM_GM12U320 is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_ST7586 is not set
# CONFIG_TINYDRM_ST7735R is not set
# CONFIG_DRM_XEN is not set
# CONFIG_DRM_VBOXVIDEO is not set
# CONFIG_DRM_LEGACY is not setCONFIG_DRM_PANEL_ORIENTATION_QUIRKS=yCONFIG_DRM_LIB_RANDOM=y
#
# Frame buffer Devices
#CONFIG_FB_CMDLINE=yCONFIG_FB_NOTIFY=yCONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not setCONFIG_FB_BOOT_VESA_SUPPORT=yCONFIG_FB_CFB_FILLRECT=yCONFIG_FB_CFB_COPYAREA=yCONFIG_FB_CFB_IMAGEBLIT=yCONFIG_FB_SYS_FILLRECT=mCONFIG_FB_SYS_COPYAREA=mCONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not setCONFIG_FB_SYS_FOPS=mCONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_MODE_HELPERS is not setCONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not setCONFIG_FB_VESA=yCONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SM501 is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_XEN_FBDEV_FRONTEND is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not setCONFIG_FB_HYPERV=m
# CONFIG_FB_SIMPLE is not set
# CONFIG_FB_SM712 is not set
# end of Frame buffer Devices
#
# Backlight & LCD device support
#CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not setCONFIG_LCD_PLATFORM=m
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
# CONFIG_LCD_OTM3225A is not setCONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_PWM is not setCONFIG_BACKLIGHT_APPLE=m
# CONFIG_BACKLIGHT_PM8941_WLED is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not setCONFIG_BACKLIGHT_LP855X=m
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# end of Backlight & LCD device support
CONFIG_HDMI=y
#
# Console display driver support
#CONFIG_VGA_CONSOLE=yCONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
# CONFIG_VGACON_SOFT_SCROLLBACK_PERSISTENT_ENABLE_BY_DEFAULT is not set CONFIG_DUMMY_CONSOLE=yCONFIG_DUMMY_CONSOLE_COLUMNS=80CONFIG_DUMMY_CONSOLE_ROWS=25CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
# end of Console display driver support
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not setCONFIG_LOGO_LINUX_CLUT224=y
# end of Graphics support
CONFIG_SOUND=mCONFIG_SOUND_OSS_CORE=yCONFIG_SOUND_OSS_CORE_PRECLAIM=yCONFIG_SND=mCONFIG_SND_TIMER=mCONFIG_SND_PCM=mCONFIG_SND_PCM_ELD=yCONFIG_SND_HWDEP=mCONFIG_SND_SEQ_DEVICE=mCONFIG_SND_RAWMIDI=mCONFIG_SND_COMPRESS_OFFLOAD=mCONFIG_SND_JACK=yCONFIG_SND_JACK_INPUT_DEV=yCONFIG_SND_OSSEMUL=y
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not setCONFIG_SND_PCM_TIMER=yCONFIG_SND_HRTIMER=mCONFIG_SND_DYNAMIC_MINORS=yCONFIG_SND_MAX_CARDS=32
# CONFIG_SND_SUPPORT_OLD_API is not setCONFIG_SND_PROC_FS=yCONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not setCONFIG_SND_VMASTER=yCONFIG_SND_DMA_SGBUF=yCONFIG_SND_SEQUENCER=mCONFIG_SND_SEQ_DUMMY=mCONFIG_SND_SEQUENCER_OSS=mCONFIG_SND_SEQ_HRTIMER_DEFAULT=yCONFIG_SND_SEQ_MIDI_EVENT=mCONFIG_SND_SEQ_MIDI=mCONFIG_SND_SEQ_MIDI_EMUL=mCONFIG_SND_SEQ_VIRMIDI=mCONFIG_SND_MPU401_UART=mCONFIG_SND_OPL3_LIB=mCONFIG_SND_OPL3_LIB_SEQ=mCONFIG_SND_VX_LIB=mCONFIG_SND_AC97_CODEC=mCONFIG_SND_DRIVERS=yCONFIG_SND_PCSP=mCONFIG_SND_DUMMY=mCONFIG_SND_ALOOP=mCONFIG_SND_VIRMIDI=mCONFIG_SND_MTPAV=m
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not setCONFIG_SND_MPU401=m
# CONFIG_SND_PORTMAN2X4 is not setCONFIG_SND_AC97_POWER_SAVE=yCONFIG_SND_AC97_POWER_SAVE_DEFAULT=5CONFIG_SND_PCI=yCONFIG_SND_AD1889=m
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not setCONFIG_SND_ALI5451=mCONFIG_SND_ASIHPI=mCONFIG_SND_ATIIXP=mCONFIG_SND_ATIIXP_MODEM=mCONFIG_SND_AU8810=mCONFIG_SND_AU8820=mCONFIG_SND_AU8830=m
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not setCONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not setCONFIG_SND_CA0106=mCONFIG_SND_CMIPCI=mCONFIG_SND_OXYGEN_LIB=mCONFIG_SND_OXYGEN=m
# CONFIG_SND_CS4281 is not setCONFIG_SND_CS46XX=mCONFIG_SND_CS46XX_NEW_DSP=yCONFIG_SND_CTXFI=mCONFIG_SND_DARLA20=mCONFIG_SND_GINA20=mCONFIG_SND_LAYLA20=mCONFIG_SND_DARLA24=mCONFIG_SND_GINA24=mCONFIG_SND_LAYLA24=mCONFIG_SND_MONA=mCONFIG_SND_MIA=mCONFIG_SND_ECHO3G=mCONFIG_SND_INDIGO=mCONFIG_SND_INDIGOIO=mCONFIG_SND_INDIGODJ=mCONFIG_SND_INDIGOIOX=mCONFIG_SND_INDIGODJX=mCONFIG_SND_EMU10K1=mCONFIG_SND_EMU10K1_SEQ=mCONFIG_SND_EMU10K1X=mCONFIG_SND_ENS1370=mCONFIG_SND_ENS1371=m
# CONFIG_SND_ES1938 is not setCONFIG_SND_ES1968=mCONFIG_SND_ES1968_INPUT=yCONFIG_SND_ES1968_RADIO=y
# CONFIG_SND_FM801 is not setCONFIG_SND_HDSP=mCONFIG_SND_HDSPM=mCONFIG_SND_ICE1712=mCONFIG_SND_ICE1724=mCONFIG_SND_INTEL8X0=mCONFIG_SND_INTEL8X0M=mCONFIG_SND_KORG1212=mCONFIG_SND_LOLA=mCONFIG_SND_LX6464ES=mCONFIG_SND_MAESTRO3=mCONFIG_SND_MAESTRO3_INPUT=yCONFIG_SND_MIXART=m
# CONFIG_SND_NM256 is not setCONFIG_SND_PCXHR=m
# CONFIG_SND_RIPTIDE is not setCONFIG_SND_RME32=mCONFIG_SND_RME96=mCONFIG_SND_RME9652=m
# CONFIG_SND_SONICVIBES is not setCONFIG_SND_TRIDENT=mCONFIG_SND_VIA82XX=mCONFIG_SND_VIA82XX_MODEM=mCONFIG_SND_VIRTUOSO=mCONFIG_SND_VX222=m
# CONFIG_SND_YMFPCI is not set
#
# HD-Audio
#CONFIG_SND_HDA=mCONFIG_SND_HDA_INTEL=m
# CONFIG_SND_HDA_INTEL_DETECT_DMIC is not setCONFIG_SND_HDA_HWDEP=yCONFIG_SND_HDA_RECONFIG=yCONFIG_SND_HDA_INPUT_BEEP=yCONFIG_SND_HDA_INPUT_BEEP_MODE=0CONFIG_SND_HDA_PATCH_LOADER=yCONFIG_SND_HDA_CODEC_REALTEK=mCONFIG_SND_HDA_CODEC_ANALOG=mCONFIG_SND_HDA_CODEC_SIGMATEL=mCONFIG_SND_HDA_CODEC_VIA=mCONFIG_SND_HDA_CODEC_HDMI=mCONFIG_SND_HDA_CODEC_CIRRUS=mCONFIG_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=mCONFIG_SND_HDA_CODEC_SI3054=mCONFIG_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_COMPONENT=yCONFIG_SND_HDA_I915=yCONFIG_SND_HDA_EXT_CORE=mCONFIG_SND_HDA_PREALLOC_SIZE=512CONFIG_SND_INTEL_NHLT=m
# CONFIG_SND_SPI is not setCONFIG_SND_USB=yCONFIG_SND_USB_AUDIO=mCONFIG_SND_USB_AUDIO_USE_MEDIA_CONTROLLER=yCONFIG_SND_USB_UA101=mCONFIG_SND_USB_USX2Y=mCONFIG_SND_USB_CAIAQ=mCONFIG_SND_USB_CAIAQ_INPUT=yCONFIG_SND_USB_US122L=mCONFIG_SND_USB_6FIRE=mCONFIG_SND_USB_HIFACE=mCONFIG_SND_BCD2000=mCONFIG_SND_USB_LINE6=mCONFIG_SND_USB_POD=mCONFIG_SND_USB_PODHD=mCONFIG_SND_USB_TONEPORT=mCONFIG_SND_USB_VARIAX=mCONFIG_SND_FIREWIRE=yCONFIG_SND_FIREWIRE_LIB=m
# CONFIG_SND_DICE is not set
# CONFIG_SND_OXFW is not setCONFIG_SND_ISIGHT=m
# CONFIG_SND_FIREWORKS is not set
# CONFIG_SND_BEBOB is not set
# CONFIG_SND_FIREWIRE_DIGI00X is not set
# CONFIG_SND_FIREWIRE_TASCAM is not set
# CONFIG_SND_FIREWIRE_MOTU is not set
# CONFIG_SND_FIREFACE is not setCONFIG_SND_SOC=mCONFIG_SND_SOC_COMPRESS=yCONFIG_SND_SOC_TOPOLOGY=yCONFIG_SND_SOC_ACPI=m
# CONFIG_SND_SOC_AMD_ACP is not set
# CONFIG_SND_SOC_AMD_ACP3x is not set
# CONFIG_SND_ATMEL_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 set
# CONFIG_SND_SOC_FSL_SAI is not set
# CONFIG_SND_SOC_FSL_AUDMIX is not set
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_FSL_MICFIL is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
# end of SoC Audio for Freescale CPUs
# CONFIG_SND_I2S_HI6210_I2S is not set
# CONFIG_SND_SOC_IMG is not set CONFIG_SND_SOC_INTEL_SST_TOPLEVEL=y CONFIG_SND_SST_IPC=mCONFIG_SND_SST_IPC_ACPI=m CONFIG_SND_SOC_INTEL_SST_ACPI=m CONFIG_SND_SOC_INTEL_SST=m CONFIG_SND_SOC_INTEL_SST_FIRMWARE=m CONFIG_SND_SOC_INTEL_HASWELL=m CONFIG_SND_SST_ATOM_HIFI2_PLATFORM=m
# CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_PCI is not set CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI=m CONFIG_SND_SOC_INTEL_SKYLAKE=m CONFIG_SND_SOC_INTEL_SKL=m CONFIG_SND_SOC_INTEL_APL=m CONFIG_SND_SOC_INTEL_KBL=m CONFIG_SND_SOC_INTEL_GLK=m CONFIG_SND_SOC_INTEL_CNL=m CONFIG_SND_SOC_INTEL_CFL=m
# CONFIG_SND_SOC_INTEL_CML_H is not set
# CONFIG_SND_SOC_INTEL_CML_LP is not set CONFIG_SND_SOC_INTEL_SKYLAKE_FAMILY=m CONFIG_SND_SOC_INTEL_SKYLAKE_SSP_CLK=m
# CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC is not set CONFIG_SND_SOC_INTEL_SKYLAKE_COMMON=m CONFIG_SND_SOC_ACPI_INTEL_MATCH=m CONFIG_SND_SOC_INTEL_MACH=y CONFIG_SND_SOC_INTEL_HASWELL_MACH=m CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH=m CONFIG_SND_SOC_INTEL_BROADWELL_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH=m CONFIG_SND_SOC_INTEL_BYTCR_RT5651_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5672_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_RT5645_MACH=m CONFIG_SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH=m
# CONFIG_SND_SOC_INTEL_CHT_BSW_NAU8824_MACH is not set # CONFIG_SND_SOC_INTEL_BYT_CHT_CX2072X_MACH is not set CONFIG_SND_SOC_INTEL_BYT_CHT_DA7213_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_ES8316_MACH=m CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=m CONFIG_SND_SOC_INTEL_SKL_RT286_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_SSM4567_MACH=m CONFIG_SND_SOC_INTEL_SKL_NAU88L25_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_DA7219_MAX98357A_GENERIC=m CONFIG_SND_SOC_INTEL_BXT_DA7219_MAX98357A_MACH=m CONFIG_SND_SOC_INTEL_BXT_RT298_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_MAX98927_MACH=m CONFIG_SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH=m # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98357A_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_DA7219_MAX98927_MACH is not set # CONFIG_SND_SOC_INTEL_KBL_RT5660_MACH is not set # CONFIG_SND_SOC_INTEL_GLK_RT5682_MAX98357A_MACH is not set # CONFIG_SND_SOC_MTK_BTCVSD is not set
# CONFIG_SND_SOC_SOF_TOPLEVEL is not set
#
# STMicroelectronics STM32 SOC audio support
#
# end of STMicroelectronics STM32 SOC audio support
# CONFIG_SND_SOC_XILINX_I2S is not set
# CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set # CONFIG_SND_SOC_XILINX_SPDIF is not set
# CONFIG_SND_SOC_XTFPGA_I2S is not set
# CONFIG_ZX_TDM is not set CONFIG_SND_SOC_I2C_AND_SPI=m
#
# CODEC drivers
#
# CONFIG_SND_SOC_AC97_CODEC is not set
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_ADAU1761_I2C is not set
# CONFIG_SND_SOC_ADAU1761_SPI is not set
# CONFIG_SND_SOC_ADAU7002 is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4118 is not set
# CONFIG_SND_SOC_AK4458 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not set
# CONFIG_SND_SOC_AK4642 is not set
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_AK5558 is not set
# CONFIG_SND_SOC_ALC5623 is not set
# CONFIG_SND_SOC_BD28623 is not set
# CONFIG_SND_SOC_BT_SCO is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS35L33 is not set
# CONFIG_SND_SOC_CS35L34 is not set
# CONFIG_SND_SOC_CS35L35 is not set
# CONFIG_SND_SOC_CS35L36 is not set
# CONFIG_SND_SOC_CS42L42 is not set
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_CS43130 is not set
# CONFIG_SND_SOC_CS4341 is not set
# CONFIG_SND_SOC_CS4349 is not set
# CONFIG_SND_SOC_CS53L30 is not set
# CONFIG_SND_SOC_CX2072X is not setCONFIG_SND_SOC_DA7213=mCONFIG_SND_SOC_DA7219=mCONFIG_SND_SOC_DMIC=m
# CONFIG_SND_SOC_ES7134 is not set
# CONFIG_SND_SOC_ES7241 is not setCONFIG_SND_SOC_ES8316=m
# CONFIG_SND_SOC_ES8328_I2C is not set
# CONFIG_SND_SOC_ES8328_SPI is not set
# CONFIG_SND_SOC_GTM601 is not setCONFIG_SND_SOC_HDAC_HDMI=m
# CONFIG_SND_SOC_INNO_RK3036 is not set
# CONFIG_SND_SOC_MAX98088 is not setCONFIG_SND_SOC_MAX98090=mCONFIG_SND_SOC_MAX98357A=m
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9867 is not setCONFIG_SND_SOC_MAX98927=m
# CONFIG_SND_SOC_MAX98373 is not set
# CONFIG_SND_SOC_MAX9860 is not set
# CONFIG_SND_SOC_MSM8916_WCD_DIGITAL is not set
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM1789_I2C is not set
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not set
# CONFIG_SND_SOC_PCM186X_I2C is not set
# CONFIG_SND_SOC_PCM186X_SPI is not set
# CONFIG_SND_SOC_PCM3060_I2C is not set
# CONFIG_SND_SOC_PCM3060_SPI is not set
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM3168A_SPI is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
# CONFIG_SND_SOC_RK3328 is not setCONFIG_SND_SOC_RL6231=mCONFIG_SND_SOC_RL6347A=mCONFIG_SND_SOC_RT286=mCONFIG_SND_SOC_RT298=mCONFIG_SND_SOC_RT5514=mCONFIG_SND_SOC_RT5514_SPI=m
# CONFIG_SND_SOC_RT5616 is not set
# CONFIG_SND_SOC_RT5631 is not setCONFIG_SND_SOC_RT5640=mCONFIG_SND_SOC_RT5645=mCONFIG_SND_SOC_RT5651=mCONFIG_SND_SOC_RT5663=mCONFIG_SND_SOC_RT5670=mCONFIG_SND_SOC_RT5677=mCONFIG_SND_SOC_RT5677_SPI=m
# CONFIG_SND_SOC_SGTL5000 is not set
# CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not set
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not set
# CONFIG_SND_SOC_SPDIF is not set
# CONFIG_SND_SOC_SSM2305 is not set
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not setCONFIG_SND_SOC_SSM4567=m
# CONFIG_SND_SOC_STA32X is not set
# CONFIG_SND_SOC_STA350 is not set
# CONFIG_SND_SOC_STI_SAS is not set
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not set
# CONFIG_SND_SOC_TAS5720 is not set
# CONFIG_SND_SOC_TAS6424 is not set
# CONFIG_SND_SOC_TDA7419 is not set
# CONFIG_SND_SOC_TFA9879 is not set
# CONFIG_SND_SOC_TLV320AIC23_I2C is not set
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC32X4_I2C is not set
# CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set
# CONFIG_SND_SOC_TLV320AIC3X is not setCONFIG_SND_SOC_TS3A227E=m
# CONFIG_SND_SOC_TSCS42XX is not set
# CONFIG_SND_SOC_TSCS454 is not set
# CONFIG_SND_SOC_UDA1334 is not set
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8524 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not set
# CONFIG_SND_SOC_WM8753 is not set
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8782 is not set
# CONFIG_SND_SOC_WM8804_I2C is not set
# CONFIG_SND_SOC_WM8804_SPI is not set
# CONFIG_SND_SOC_WM8903 is not set
# CONFIG_SND_SOC_WM8904 is not set
# CONFIG_SND_SOC_WM8960 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8974 is not set
# CONFIG_SND_SOC_WM8978 is not set
# CONFIG_SND_SOC_WM8985 is not set
# CONFIG_SND_SOC_ZX_AUD96P22 is not set
# CONFIG_SND_SOC_MAX9759 is not set
# CONFIG_SND_SOC_MT6351 is not set
# CONFIG_SND_SOC_MT6358 is not set
# CONFIG_SND_SOC_NAU8540 is not set
# CONFIG_SND_SOC_NAU8810 is not set
# CONFIG_SND_SOC_NAU8822 is not setCONFIG_SND_SOC_NAU8824=mCONFIG_SND_SOC_NAU8825=m
# CONFIG_SND_SOC_TPA6130A2 is not set
# end of CODEC drivers
# CONFIG_SND_SIMPLE_CARD is not setCONFIG_SND_X86=yCONFIG_HDMI_LPE_AUDIO=mCONFIG_SND_SYNTH_EMUX=m
# CONFIG_SND_XEN_FRONTEND is not setCONFIG_AC97_BUS=m
#
# HID support
#CONFIG_HID=yCONFIG_HID_BATTERY_STRENGTH=yCONFIG_HIDRAW=yCONFIG_UHID=mCONFIG_HID_GENERIC=y
#
# Special HID drivers
#CONFIG_HID_A4TECH=y
# CONFIG_HID_ACCUTOUCH is not setCONFIG_HID_ACRUX=m
# CONFIG_HID_ACRUX_FF is not setCONFIG_HID_APPLE=yCONFIG_HID_APPLEIR=m
# CONFIG_HID_ASUS is not setCONFIG_HID_AUREAL=mCONFIG_HID_BELKIN=y
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_BIGBEN_FF is not setCONFIG_HID_CHERRY=yCONFIG_HID_CHICONY=y
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_COUGAR is not set
# CONFIG_HID_MACALLY is not setCONFIG_HID_PRODIKEYS=m
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CP2112 is not set
# CONFIG_HID_CREATIVE_SB0540 is not setCONFIG_HID_CYPRESS=yCONFIG_HID_DRAGONRISE=m
# CONFIG_DRAGONRISE_FF is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELAN is not setCONFIG_HID_ELECOM=m
# CONFIG_HID_ELO is not setCONFIG_HID_EZKEY=y
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not setCONFIG_HID_HOLTEK=m
# CONFIG_HOLTEK_FF is not set
# CONFIG_HID_GT683R is not setCONFIG_HID_KEYTOUCH=mCONFIG_HID_KYE=mCONFIG_HID_UCLOGIC=mCONFIG_HID_WALTOP=m
# CONFIG_HID_VIEWSONIC is not setCONFIG_HID_GYRATION=mCONFIG_HID_ICADE=mCONFIG_HID_ITE=y
# CONFIG_HID_JABRA is not setCONFIG_HID_TWINHAN=mCONFIG_HID_KENSINGTON=yCONFIG_HID_LCPOWER=mCONFIG_HID_LED=m
# CONFIG_HID_LENOVO is not setCONFIG_HID_LOGITECH=yCONFIG_HID_LOGITECH_DJ=mCONFIG_HID_LOGITECH_HIDPP=m
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not setCONFIG_HID_MAGICMOUSE=y
# CONFIG_HID_MALTRON is not set
# CONFIG_HID_MAYFLASH is not setCONFIG_HID_REDRAGON=yCONFIG_HID_MICROSOFT=yCONFIG_HID_MONTEREY=yCONFIG_HID_MULTITOUCH=m
# CONFIG_HID_NTI is not setCONFIG_HID_NTRIG=yCONFIG_HID_ORTEK=mCONFIG_HID_PANTHERLORD=m
# CONFIG_PANTHERLORD_FF is not set
# CONFIG_HID_PENMOUNT is not setCONFIG_HID_PETALYNX=mCONFIG_HID_PICOLCD=mCONFIG_HID_PICOLCD_FB=yCONFIG_HID_PICOLCD_BACKLIGHT=yCONFIG_HID_PICOLCD_LCD=yCONFIG_HID_PICOLCD_LEDS=yCONFIG_HID_PICOLCD_CIR=yCONFIG_HID_PLANTRONICS=yCONFIG_HID_PRIMAX=m
# CONFIG_HID_RETRODE is not setCONFIG_HID_ROCCAT=mCONFIG_HID_SAITEK=mCONFIG_HID_SAMSUNG=mCONFIG_HID_SONY=m
# CONFIG_SONY_FF is not setCONFIG_HID_SPEEDLINK=m
# CONFIG_HID_STEAM is not setCONFIG_HID_STEELSERIES=mCONFIG_HID_SUNPLUS=mCONFIG_HID_RMI=mCONFIG_HID_GREENASIA=m
# CONFIG_GREENASIA_FF is not setCONFIG_HID_HYPERV_MOUSE=mCONFIG_HID_SMARTJOYPLUS=m
# CONFIG_SMARTJOYPLUS_FF is not setCONFIG_HID_TIVO=mCONFIG_HID_TOPSEED=mCONFIG_HID_THINGM=mCONFIG_HID_THRUSTMASTER=m
# CONFIG_THRUSTMASTER_FF is not set
# CONFIG_HID_UDRAW_PS3 is not set
# CONFIG_HID_U2FZERO is not setCONFIG_HID_WACOM=mCONFIG_HID_WIIMOTE=m
# CONFIG_HID_XINMO is not setCONFIG_HID_ZEROPLUS=m
# CONFIG_ZEROPLUS_FF is not setCONFIG_HID_ZYDACRON=mCONFIG_HID_SENSOR_HUB=mCONFIG_HID_SENSOR_CUSTOM_SENSOR=mCONFIG_HID_ALPS=m
# end of Special HID drivers
#
# USB HID support
#CONFIG_USB_HID=yCONFIG_HID_PID=yCONFIG_USB_HIDDEV=y
# end of USB HID support
#
# I2C HID support
#CONFIG_I2C_HID=m
# end of I2C HID support
#
# Intel ISH HID support
#CONFIG_INTEL_ISH_HID=y
# CONFIG_INTEL_ISH_FIRMWARE_DOWNLOADER is not set
# end of Intel ISH HID support # end of HID support
CONFIG_USB_OHCI_LITTLE_ENDIAN=yCONFIG_USB_SUPPORT=yCONFIG_USB_COMMON=y
# CONFIG_USB_LED_TRIG is not set
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_CONN_GPIO is not setCONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB=yCONFIG_USB_PCI=yCONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not setCONFIG_USB_LEDS_TRIGGER_USBPORT=mCONFIG_USB_AUTOSUSPEND_DELAY=2CONFIG_USB_MON=y
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not setCONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_DBGCAP is not setCONFIG_USB_XHCI_PCI=y
# CONFIG_USB_XHCI_PLATFORM is not setCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_ROOT_HUB_TT=yCONFIG_USB_EHCI_TT_NEWSCHED=yCONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not setCONFIG_USB_OHCI_HCD=yCONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not setCONFIG_USB_UHCI_HCD=y
# CONFIG_USB_U132_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_SSB is not set
# CONFIG_USB_HCD_TEST_MODE is not set
#
# USB Device Class drivers
#CONFIG_USB_ACM=mCONFIG_USB_PRINTER=mCONFIG_USB_WDM=mCONFIG_USB_TMC=m
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may #
#
# also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_REALTEK=m CONFIG_REALTEK_AUTOPM=y CONFIG_USB_STORAGE_DATAFAB=m CONFIG_USB_STORAGE_FREECOM=m CONFIG_USB_STORAGE_ISD200=m CONFIG_USB_STORAGE_USBAT=m CONFIG_USB_STORAGE_SDDR09=m CONFIG_USB_STORAGE_SDDR55=m CONFIG_USB_STORAGE_JUMPSHOT=m CONFIG_USB_STORAGE_ALAUDA=m CONFIG_USB_STORAGE_ONETOUCH=m CONFIG_USB_STORAGE_KARMA=m CONFIG_USB_STORAGE_CYPRESS_ATACB=m CONFIG_USB_STORAGE_ENE_UB6250=m CONFIG_USB_UAS=m
#
# USB Imaging devices
#CONFIG_USB_MDC800=mCONFIG_USB_MICROTEK=mCONFIG_USBIP_CORE=m
# CONFIG_USBIP_VHCI_HCD is not set
# CONFIG_USBIP_HOST is not set
# CONFIG_USBIP_DEBUG is not set
# CONFIG_USB_CDNS3 is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
# CONFIG_USB_ISP1760 is not set
#
# USB port drivers
#CONFIG_USB_USS720=mCONFIG_USB_SERIAL=yCONFIG_USB_SERIAL_CONSOLE=yCONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_SIMPLE is not setCONFIG_USB_SERIAL_AIRCABLE=mCONFIG_USB_SERIAL_ARK3116=mCONFIG_USB_SERIAL_BELKIN=mCONFIG_USB_SERIAL_CH341=mCONFIG_USB_SERIAL_WHITEHEAT=mCONFIG_USB_SERIAL_DIGI_ACCELEPORT=mCONFIG_USB_SERIAL_CP210X=mCONFIG_USB_SERIAL_CYPRESS_M8=mCONFIG_USB_SERIAL_EMPEG=mCONFIG_USB_SERIAL_FTDI_SIO=mCONFIG_USB_SERIAL_VISOR=mCONFIG_USB_SERIAL_IPAQ=mCONFIG_USB_SERIAL_IR=mCONFIG_USB_SERIAL_EDGEPORT=mCONFIG_USB_SERIAL_EDGEPORT_TI=m
# CONFIG_USB_SERIAL_F81232 is not set
# CONFIG_USB_SERIAL_F8153X is not setCONFIG_USB_SERIAL_GARMIN=mCONFIG_USB_SERIAL_IPW=mCONFIG_USB_SERIAL_IUU=mCONFIG_USB_SERIAL_KEYSPAN_PDA=mCONFIG_USB_SERIAL_KEYSPAN=mCONFIG_USB_SERIAL_KLSI=mCONFIG_USB_SERIAL_KOBIL_SCT=mCONFIG_USB_SERIAL_MCT_U232=m
# CONFIG_USB_SERIAL_METRO is not setCONFIG_USB_SERIAL_MOS7720=mCONFIG_USB_SERIAL_MOS7715_PARPORT=yCONFIG_USB_SERIAL_MOS7840=m
# CONFIG_USB_SERIAL_MXUPORT is not setCONFIG_USB_SERIAL_NAVMAN=mCONFIG_USB_SERIAL_PL2303=mCONFIG_USB_SERIAL_OTI6858=mCONFIG_USB_SERIAL_QCAUX=mCONFIG_USB_SERIAL_QUALCOMM=mCONFIG_USB_SERIAL_SPCP8X5=mCONFIG_USB_SERIAL_SAFE=mCONFIG_USB_SERIAL_SAFE_PADDED=yCONFIG_USB_SERIAL_SIERRAWIRELESS=mCONFIG_USB_SERIAL_SYMBOL=m
# CONFIG_USB_SERIAL_TI is not setCONFIG_USB_SERIAL_CYBERJACK=mCONFIG_USB_SERIAL_XIRCOM=mCONFIG_USB_SERIAL_WWAN=mCONFIG_USB_SERIAL_OPTION=mCONFIG_USB_SERIAL_OMNINET=mCONFIG_USB_SERIAL_OPTICON=mCONFIG_USB_SERIAL_XSENS_MT=m
# CONFIG_USB_SERIAL_WISHBONE is not setCONFIG_USB_SERIAL_SSU100=mCONFIG_USB_SERIAL_QT2=m
# CONFIG_USB_SERIAL_UPD78F0730 is not setCONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#CONFIG_USB_EMI62=mCONFIG_USB_EMI26=mCONFIG_USB_ADUTUX=mCONFIG_USB_SEVSEG=m
# CONFIG_USB_RIO500 is not setCONFIG_USB_LEGOTOWER=mCONFIG_USB_LCD=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not setCONFIG_USB_IDMOUSE=mCONFIG_USB_FTDI_ELAN=mCONFIG_USB_APPLEDISPLAY=mCONFIG_USB_SISUSBVGA=mCONFIG_USB_SISUSBVGA_CON=yCONFIG_USB_LD=m
# CONFIG_USB_TRANCEVIBRATOR is not setCONFIG_USB_IOWARRIOR=m
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not setCONFIG_USB_ISIGHTFW=m
# CONFIG_USB_YUREX is not setCONFIG_USB_EZUSB_FX2=m
# CONFIG_USB_HUB_USB251XB is not setCONFIG_USB_HSIC_USB3503=m
# CONFIG_USB_HSIC_USB4604 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not setCONFIG_USB_ATM=mCONFIG_USB_SPEEDTOUCH=mCONFIG_USB_CXACRU=mCONFIG_USB_UEAGLEATM=mCONFIG_USB_XUSBATM=m
#
# USB Physical Layer drivers
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# end of USB Physical Layer drivers
# CONFIG_USB_GADGET is not setCONFIG_TYPEC=y
# CONFIG_TYPEC_TCPM is not setCONFIG_TYPEC_UCSI=y
# CONFIG_UCSI_CCG is not setCONFIG_UCSI_ACPI=y
# CONFIG_TYPEC_TPS6598X is not set
#
# USB Type-C Multiplexer/DeMultiplexer Switch support #
# CONFIG_TYPEC_MUX_PI3USB30532 is not set
# end of USB Type-C Multiplexer/DeMultiplexer Switch support
#
# USB Type-C Alternate Mode drivers
#
# CONFIG_TYPEC_DP_ALTMODE is not set
# end of USB Type-C Alternate Mode drivers
# CONFIG_USB_ROLE_SWITCH is not setCONFIG_MMC=mCONFIG_MMC_BLOCK=mCONFIG_MMC_BLOCK_MINORS=8CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not setCONFIG_MMC_SDHCI=mCONFIG_MMC_SDHCI_IO_ACCESSORS=yCONFIG_MMC_SDHCI_PCI=mCONFIG_MMC_RICOH_MMC=yCONFIG_MMC_SDHCI_ACPI=mCONFIG_MMC_SDHCI_PLTFM=m
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_WBSD is not setCONFIG_MMC_TIFM_SD=m
# CONFIG_MMC_SPI is not setCONFIG_MMC_CB710=mCONFIG_MMC_VIA_SDMMC=mCONFIG_MMC_VUB300=mCONFIG_MMC_USHC=m
# CONFIG_MMC_USDHI6ROL0 is not setCONFIG_MMC_CQHCI=m
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MMC_SDHCI_XENON is not setCONFIG_MEMSTICK=m
# CONFIG_MEMSTICK_DEBUG is not set
#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not setCONFIG_MSPRO_BLOCK=m
# CONFIG_MS_BLOCK is not set
#
# MemoryStick Host Controller Drivers
#CONFIG_MEMSTICK_TIFM_MS=mCONFIG_MEMSTICK_JMICRON_38X=mCONFIG_MEMSTICK_R592=mCONFIG_NEW_LEDS=yCONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set
#
# LED drivers
#
# CONFIG_LEDS_APU is not setCONFIG_LEDS_LM3530=m
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not setCONFIG_LEDS_LP3944=m
# CONFIG_LEDS_LP3952 is not setCONFIG_LEDS_LP55XX_COMMON=mCONFIG_LEDS_LP5521=mCONFIG_LEDS_LP5523=mCONFIG_LEDS_LP5562=m
# CONFIG_LEDS_LP8501 is not setCONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_BD2802 is not setCONFIG_LEDS_INTEL_SS4200=m
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM) #CONFIG_LEDS_BLINKM=m
# CONFIG_LEDS_MLXCPLD is not set
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_NIC78BX is not set
# CONFIG_LEDS_TI_LMU_COMMON is not set
#
# LED Triggers
#CONFIG_LEDS_TRIGGERS=yCONFIG_LEDS_TRIGGER_TIMER=mCONFIG_LEDS_TRIGGER_ONESHOT=m
# CONFIG_LEDS_TRIGGER_DISK is not set
# CONFIG_LEDS_TRIGGER_MTD is not setCONFIG_LEDS_TRIGGER_HEARTBEAT=mCONFIG_LEDS_TRIGGER_BACKLIGHT=m
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not setCONFIG_LEDS_TRIGGER_GPIO=mCONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target) # CONFIG_LEDS_TRIGGER_TRANSIENT=m CONFIG_LEDS_TRIGGER_CAMERA=m # CONFIG_LEDS_TRIGGER_PANIC is not set # CONFIG_LEDS_TRIGGER_NETDEV is not set # CONFIG_LEDS_TRIGGER_PATTERN is not set CONFIG_LEDS_TRIGGER_AUDIO=m # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set CONFIG_EDAC_ATOMIC_SCRUB=y CONFIG_EDAC_SUPPORT=y CONFIG_EDAC=y CONFIG_EDAC_LEGACY_SYSFS=y # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_DECODE_MCE=m CONFIG_EDAC_GHES=y CONFIG_EDAC_AMD64=m # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set CONFIG_EDAC_E752X=m CONFIG_EDAC_I82975X=m CONFIG_EDAC_I3000=m CONFIG_EDAC_I3200=m CONFIG_EDAC_IE31200=m CONFIG_EDAC_X38=m CONFIG_EDAC_I5400=m CONFIG_EDAC_I7CORE=m CONFIG_EDAC_I5000=m CONFIG_EDAC_I5100=m CONFIG_EDAC_I7300=m CONFIG_EDAC_SBRIDGE=m CONFIG_EDAC_SKX=m # CONFIG_EDAC_I10NM is not set
9 lines not shown · raw message
2,327 lines not shown · raw message
Part of this message is not shown here. View the raw message.
PATCH v11 3/6 mm: Introduce Reported pages
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
In order to pave the way for free page reporting in virtualized environments we will need a way to get pages out of the free lists and identify those pages after they have been returned. To accomplish this, this patch adds the concept of a Reported Buddy, which is essentially meant to just be the Uptodate flag used in conjunction with the Buddy page type.
It adds a set of pointers we shall call "reported_boundary" which represent the upper boundary between the unreported and reported pages. The general idea is that in order for a page to cross from one side of the boundary to the other it will need to verify that it went through the reporting process. Ultimately a free list has been fully processed when the boundary has been moved from the tail all they way up to occupying the first entry in the list. Without this we would have to manually walk the entire page list until we have find a page that hasn't been reported. In my testing this adds as much as 18% additional overhead which would make this unattractive as a solution.
One limitation to this approach is that it is essentially a linear search and in the case of the free lists we can have pages added to either the head or the tail of the list. In order to place limits on this we only allow pages to be added before the reported_boundary instead of adding to the tail itself. An added advantage to this approach is that we should be reducing the overall memory footprint of the guest as it will be more likely to recycle warm pages versus trying to allocate the reported pages that were likely evicted from the guest memory.
Since we will only be reporting one zone at a time we keep the boundary limited to being defined for just the zone we are currently reporting pages from. Doing this we can keep the number of additional pointers needed quite small. To flag that the boundaries are in place we use a single bit in the zone to indicate that reporting and the boundaries are active.
We store the index of the boundary pointer used to track the reported page in the page->index value. Doing this we can avoid unnecessary computation to determine the index value again. There should be no issues with this as the value is unused when the page is in the buddy allocator, and is reset as soon as the page is removed from the free list.
--- include/linux/mmzone.h | 16 ++++ include/linux/page-flags.h | 11 +++ mm/Kconfig | 11 +++ mm/compaction.c | 5 + mm/memory_hotplug.c | 2 + mm/page_alloc.c | 67 +++++++++++++++-- mm/page_reporting.h | 176 ++++++++++++++++++++++++++++++++++++++++++++ 7 files changed, 281 insertions(+), 7 deletions(-) create mode 100644 mm/page_reporting.h
include/linux/mmzone.h +16 -0
@@ -463,6 +463,14 @@ struct zone {seqlock_t span_seqlock;#endif +#ifdef CONFIG_PAGE_REPORTING +/* +* Pointer to reported page tracking statistics array. The size of +* the array is MAX_ORDER - PAGE_REPORTING_MIN_ORDER. NULL when +* unused page reporting is not present. +*/ +unsigned long *reported_pages; +#endif int initialized;/* Write-intensive fields used from the page allocator */
@@ -538,6 +546,14 @@ enum zone_flags {ZONE_BOOSTED_WATERMARK ,/* zone recently boosted watermarks. * Cleared when kswapd is woken. */ +ZONE_PAGE_REPORTING_ACTIVE ,/* zone enabled page reporting and is +* activly flushing the data out of +* higher order pages. +*/ + ZONE_PAGE_REPORTING_REQUESTED, /* zone enabled page reporting and has + * requested flushing the data out of + * higher order pages. + */ };static inline unsigned long zone_managed_pages (struct zone *zone)
include/linux/page-flags.h +11 -0
@@ -163,6 +163,9 @@ enum pageflags {/* non-lru isolated movable page */ PG_isolated = PG_reclaim, + +/* Buddy pages. Used to track which pages have been reported */ + PG_reported = PG_uptodate, };#ifndef __GENERATING_BOUNDS_H
@@ -432,6 +435,14 @@ static inline bool set_hwpoison_free_buddy_page(struct page *page)#endif /* +* PageReported() is used to track reported free pages within the Buddy +* allocator. We can use the non-atomic version of the test and set +* operations as both should be shielded with the zone lock to prevent +* any possible races on the setting or clearing of the bit. +*/ +__PAGEFLAG (Reported, reported,PF_NO_COMPOUND ) + +/* * On an anonymous page mapped into a user virtual memory area, * page->mapping points to its anon_vma, not to a struct address_space; * with the PAGE_MAPPING_ANON bit set to distinguish it. See rmap.h.
mm/Kconfig +11 -0
@@ -237,6 +237,17 @@ config COMPACTION [email protected]. # +# support for unused page reporting +config PAGE_REPORTING + bool "Allow for reporting of unused pages" + def_bool n + help + Unused page reporting allows for the incremental acquisition of + unused pages from the buddy allocator for the purpose of reporting + those pages to another entity, such as a hypervisor, so that the + memory can be freed up for other uses. + +# # support for page migration # config MIGRATION
mm/compaction.c +5 -0
@@ -24,6 +24,7 @@#include <linux/page_owner.h> #include <linux/psi.h> #include "internal.h" +#include "page_reporting.h" #ifdef CONFIG_COMPACTION static inline void count_compact_event (enum vm_event_item item)
@@ -1325,6 +1326,8 @@ static int next_search_order(struct compact_control *cc, int order)continue ;spin_lock_irqsave (&cc->zone->lock, flags); +page_reporting_free_area_release (cc->zone, order, +MIGRATE_MOVABLE ); freelist = &area->free_list[MIGRATE_MOVABLE ];list_for_each_entry_reverse (freepage, freelist, lru) {unsigned long pfn;
@@ -1681,6 +1684,8 @@ static unsigned long fast_find_migrateblock(struct compact_control *cc)continue ;spin_lock_irqsave (&cc->zone->lock, flags); +page_reporting_free_area_release (cc->zone, order, +MIGRATE_MOVABLE ); freelist = &area->free_list[MIGRATE_MOVABLE ];list_for_each_entry (freepage, freelist, lru) {unsigned long free_pfn;
mm/memory_hotplug.c +2 -0
@@ -41,6 +41,7 @@#include "internal.h" #include "shuffle.h" +#include "page_reporting.h" /* * online_page_callback contains pointer to current page onlining function.
@@ -1624,6 +1625,7 @@ static int __ref __offline_pages(unsigned long start_pfn,if (!populated_zone (zone)) {zone_pcp_reset (zone);build_all_zonelists (NULL ); +page_reporting_reset_zone (zone); }else zone_pcp_update (zone);
mm/page_alloc.c +60 -7
122 lines not on this page · raw message
mm/page_reporting.h new file +176 -0
176 lines not on this page · raw message
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH v11 4/6 mm: Add device side and notifier for unused page reporting
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
With this patch we are adding the pieces needed to enable the reporting of pages to a specific device. That device needs to register a page reporting device that can be used to handle notifications that that pages are unused.
Registering the device will in turn enable the notifications and allow page reporting to be active. When the the device is unregistered it will disable page reporting notifications. For now we only allow one page reporting device to be registered at a time.
The determination of when to start reporting is based on the tracking of the number of free pages in a given area versus the number of reported pages in that area. We keep track of the number of reported pages per free_area in a separate zone specific area. We do this to avoid modifying the free_area structure as this can lead to false sharing for the highest order with the zone lock which leads to a noticeable performance degradation.
Once reporting has started get_unreported_pages will use the reported_boundary pointers to track where it should resume processing the free lists. It will go through and either set the index if it finds a reported page, or it will attempt to isolate the page so that it can be reported.
--- include/linux/page_reporting.h | 31 ++++ mm/Makefile | 1 mm/page_alloc.c | 10 + mm/page_reporting.c | 350 ++++++++++++++++++++++++++++++++++++++++ mm/page_reporting.h | 49 ++++++ 5 files changed, 439 insertions(+), 2 deletions(-) create mode 100644 include/linux/page_reporting.h create mode 100644 mm/page_reporting.c
include/linux/page_reporting.h new file +31 -0
@@ -0,0 +1,31 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +#ifndef _LINUX_PAGE_REPORTING_H +#define _LINUX_PAGE_REPORTING_H + +#include <linux/mmzone.h> + +struct page_reporting_dev_info { +/* function that alters pages to make them "reported" */ +void (*report)(struct page_reporting_dev_info *phdev, +unsigned int nents); + +/* scatterlist containing pages to be processed */ +struct scatterlist *sg; + +/* +* Upper limit on the number of pages that the report function +* expects to be placed into the scatterlist to be processed. +*/ +unsigned long capacity; + +/* work struct for processing reports */ +struct delayed_work work; + +/* The number of zones requesting reporting */ +atomic_t refcnt; +}; + +/* Tear-down and bring-up for page reporting devices */ +void page_reporting_unregister (struct page_reporting_dev_info *phdev); +int page_reporting_register (struct page_reporting_dev_info *phdev); +#endif /*_LINUX_PAGE_REPORTING_H */
mm/Makefile +1 -0
@@ -107,3 +107,4 @@ obj-$(CONFIG_PERCPU_STATS) += percpu-stats.o obj-$(CONFIG_ZONE_DEVICE) += memremap.o obj-$(CONFIG_HMM_MIRROR) += hmm.o obj-$(CONFIG_MEMFD_CREATE) += memfd.o +obj-$(CONFIG_PAGE_REPORTING) += page_reporting.o
mm/page_alloc.c +8 -2
@@ -1073,6 +1073,14 @@ static inline void __free_one_page(struct page *page,add_to_free_list_tail (page, zone, order, migratetype); elseadd_to_free_list (page ,zone ,order ,migratetype ); + +/* +* No need to notify on a reported page as the total count of +* unreported pages will not have increased since we have essentially +* merged the reported page with one or more unreported pages. +*/ +if (!reported) +page_reporting_notify_free (zone, order); }/*
@@ -2262,8 +2270,6 @@ struct page *__rmqueue_smallest(struct zone *zone, unsigned int order, }#ifdef CONFIG_PAGE_REPORTING -struct list_head **reported_boundary__read_mostly ; -/** * free_reported_page - Return a now-reported page back where we got it * @page: Page that was reported
mm/page_reporting.c new file +350 -0
350 lines not on this page · raw message
mm/page_reporting.h +49 -0
67 lines not on this page · raw message
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH v11 5/6 virtio-balloon: Pull page poisoning config out of free page hinting
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
Currently the page poisoning setting wasn't being enabled unless free page hinting was enabled. However we will need the page poisoning tracking logic as well for unused page reporting. As such pull it out and make it a separate bit of config in the probe function.
In addition we need to add support for the more recent init_on_free feature which expects a behavior similar to page poisoning in that we expect the page to be pre-zeroed.
--- drivers/virtio/virtio_balloon.c | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-)
drivers/virtio/virtio_balloon.c +17 -6
@@ -842,7 +842,6 @@ static int virtio_balloon_register_shrinker(struct virtio_balloon *vb)static int virtballoon_probe (struct virtio_device *vdev) {struct virtio_balloon *vb; -__u32 poison_val;int err;if (!vdev->config->get) {
@@ -909,11 +908,20 @@ static int virtballoon_probe(struct virtio_device *vdev) VIRTIO_BALLOON_CMD_ID_STOP);spin_lock_init (&vb->free_page_list_lock);INIT_LIST_HEAD (&vb->free_page_list); -if (virtio_has_feature (vdev,VIRTIO_BALLOON_F_PAGE_POISON )) { + } +if (virtio_has_feature (vdev,VIRTIO_BALLOON_F_PAGE_POISON )) { +/* Start with poison val of 0 representing general init */ +__u32 poison_val =0 ; + +/* +* Let the hypervisor know that we are expecting a +* specific value to be written back in unused pages. +*/ +if (!want_init_on_free ())memset (&poison_val,PAGE_POISON ,sizeof (poison_val)); - virtio_cwrite(vb->vdev, struct virtio_balloon_config, - poison_val, &poison_val); - } + + virtio_cwrite(vb->vdev, struct virtio_balloon_config, + poison_val, &poison_val); }/* * We continue to use VIRTIO_BALLOON_F_DEFLATE_ON_OOM to decide if a
@@ -1014,7 +1022,10 @@ static int virtballoon_restore(struct virtio_device *vdev)static int virtballoon_validate (struct virtio_device *vdev) { -if (!page_poisoning_enabled ()) +/* Tell the host whether we care about poisoned pages. */ +if (!want_init_on_free () && + (IS_ENABLED (CONFIG_PAGE_POISONING_NO_SANITY ) || + !page_poisoning_enabled ()))__virtio_clear_bit (vdev,VIRTIO_BALLOON_F_PAGE_POISON );__virtio_clear_bit (vdev,VIRTIO_F_IOMMU_PLATFORM );
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH v11 6/6 virtio-balloon: Add support for providing unused page reports to host
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
Add support for the page reporting feature provided by virtio-balloon. Reporting differs from the regular balloon functionality in that is is much less durable than a standard memory balloon. Instead of creating a list of pages that cannot be accessed the pages are only inaccessible while they are being indicated to the virtio interface. Once the interface has acknowledged them they are placed back into their respective free lists and are once again accessible by the guest system.
--- drivers/virtio/Kconfig | 1 + drivers/virtio/virtio_balloon.c | 65 +++++++++++++++++++++++++++++++++++ include/uapi/linux/virtio_balloon.h | 1 + 3 files changed, 67 insertions(+)
drivers/virtio/Kconfig +1 -0
@@ -58,6 +58,7 @@ config VIRTIO_BALLOON tristate "Virtio balloon driver" depends on VIRTIO select MEMORY_BALLOON + select PAGE_REPORTING ---help--- This driver supports increasing and decreasing the amount of memory within a KVM guest.
drivers/virtio/virtio_balloon.c +65 -0
136 lines not on this page · raw message
include/uapi/linux/virtio_balloon.h +1 -0
@@ -36,6 +36,7 @@#define VIRTIO_BALLOON_F_DEFLATE_ON_OOM 2/* Deflate balloon on OOM */ #define VIRTIO_BALLOON_F_FREE_PAGE_HINT 3/* VQ to report free pages */ #define VIRTIO_BALLOON_F_PAGE_POISON 4/* Guest is using page poisoning */ +#define VIRTIO_BALLOON_F_REPORTING 5/* Page reporting virtqueue */ /* Size of a PFN in the balloon interface. */ #define VIRTIO_BALLOON_PFN_SHIFT 12
PATCH v11 1/3 virtio-ballon: Implement support for page poison tracking feature
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
We need to make certain to advertise support for page poison tracking if we want to actually get data on if the guest will be poisoning pages. So if free page hinting is active we should add page poisoning support and let the guest disable it if it isn't using it.
Page poisoning will result in a page being dirtied on free. As such we cannot really avoid having to copy the page at least one more time since we will need to write the poison value to the destination. As such we can just ignore free page hinting if page poisoning is enabled as it will actually reduce the work we have to do.
--- hw/virtio/virtio-balloon.c | 25 +++++++++++++++++++++---- include/hw/virtio/virtio-balloon.h | 1 + 2 files changed, 22 insertions(+), 4 deletions(-)
hw/virtio/virtio-balloon.c +21 -4
@@ -531,6 +531,15 @@ static void virtio_balloon_free_page_start(VirtIOBalloon *s)return ; } +/* +* If page poisoning is enabled then we probably shouldn't bother with +* the hinting since the poisoning will dirty the page and invalidate +* the work we are doing anyway. +*/ +if (virtio_vdev_has_feature (vdev,VIRTIO_BALLOON_F_PAGE_POISON )) { +return ; + } +if (s->free_page_report_cmd_id ==UINT_MAX ) { s->free_page_report_cmd_id =VIRTIO_BALLOON_FREE_PAGE_REPORT_CMD_ID_MIN ;
@@ -618,12 +627,10 @@ static size_t virtio_balloon_config_size(VirtIOBalloon *s)if (s->qemu_4_0_config_size) {return sizeof (struct virtio_balloon_config ); } -if (virtio_has_feature (features,VIRTIO_BALLOON_F_PAGE_POISON )) { +if (virtio_has_feature (features,VIRTIO_BALLOON_F_PAGE_POISON ) || +virtio_has_feature (features,VIRTIO_BALLOON_F_FREE_PAGE_HINT )) {return sizeof (struct virtio_balloon_config ); } -if (virtio_has_feature (features,VIRTIO_BALLOON_F_FREE_PAGE_HINT )) { -return offsetof(struct virtio_balloon_config , poison_val); - }return offsetof(struct virtio_balloon_config , free_page_report_cmd_id); }
@@ -634,6 +641,7 @@ static void virtio_balloon_get_config(VirtIODevice *vdev, uint8_t *config_data) config.num_pages =cpu_to_le32 (dev->num_pages); config.actual =cpu_to_le32 (dev->actual); + config.poison_val =cpu_to_le32 (dev->poison_val);if (dev->free_page_report_status ==FREE_PAGE_REPORT_S_REQUESTED ) { config.free_page_report_cmd_id =
@@ -697,6 +705,8 @@ static void virtio_balloon_set_config(VirtIODevice *vdev,qapi_event_send_balloon_change (vm_ram_size - ((ram_addr_t ) dev->actual <<VIRTIO_BALLOON_PFN_SHIFT )); } + dev->poison_val =virtio_vdev_has_feature (vdev,VIRTIO_BALLOON_F_PAGE_POISON ) ? +le32_to_cpu (config.poison_val) :0 ;trace_virtio_balloon_set_config (dev->actual, oldactual); }
@@ -706,6 +716,9 @@ static uint64_t virtio_balloon_get_features(VirtIODevice *vdev, uint64_t f,VirtIOBalloon *dev =VIRTIO_BALLOON (vdev); f |= dev->host_features;virtio_add_feature (&f,VIRTIO_BALLOON_F_STATS_VQ ); +if (virtio_has_feature (f,VIRTIO_BALLOON_F_FREE_PAGE_HINT )) { +virtio_add_feature (&f,VIRTIO_BALLOON_F_PAGE_POISON ); + }return f; }
@@ -847,6 +860,8 @@ static void virtio_balloon_device_reset(VirtIODevice *vdev)g_free (s->stats_vq_elem); s->stats_vq_elem =NULL ; } + + s->poison_val =0 ; }static void virtio_balloon_set_status (VirtIODevice *vdev,uint8_t status)
@@ -909,6 +924,8 @@ static Property virtio_balloon_properties[] = { VIRTIO_BALLOON_F_DEFLATE_ON_OOM, false),DEFINE_PROP_BIT ("free-page-hint" , VirtIOBalloon, host_features,VIRTIO_BALLOON_F_FREE_PAGE_HINT , false), +DEFINE_PROP_BIT ("x-page-poison" , VirtIOBalloon, host_features, + VIRTIO_BALLOON_F_PAGE_POISON, false),/* QEMU 4.0 accidentally changed the config size even when free-page-hint * is disabled, resulting in QEMU 3.1 migration incompatibility. This * property retains this quirk for QEMU 4.1 machine types.
include/hw/virtio/virtio-balloon.h +1 -0
@@ -70,6 +70,7 @@ typedef struct VirtIOBalloon {uint32_t host_features;bool qemu_4_0_config_size; + uint32_t poison_val; } VirtIOBalloon;#endif
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH v11 2/3 virtio-balloon: Add bit to notify guest of unused page reporting
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
Add a bit for the page reporting feature provided by virtio-balloon.
This patch should be replaced once the feature is added to the Linux kernel and the bit is backported into this exported kernel header.
--- include/standard-headers/linux/virtio_balloon.h | 1 + 1 file changed, 1 insertion(+)
include/standard-headers/linux/virtio_balloon.h +1 -0
@@ -36,6 +36,7 @@#define VIRTIO_BALLOON_F_DEFLATE_ON_OOM 2/* Deflate balloon on OOM */ #define VIRTIO_BALLOON_F_FREE_PAGE_HINT 3/* VQ to report free pages */ #define VIRTIO_BALLOON_F_PAGE_POISON 4/* Guest is using page poisoning */ +#define VIRTIO_BALLOON_F_REPORTING 5/* Page reporting virtqueue */ /* Size of a PFN in the balloon interface. */ #define VIRTIO_BALLOON_PFN_SHIFT 12
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
PATCH v11 3/3 virtio-balloon: Provide a interface for unused page reporting
In reply to Alexander DuyckFrom: Alexander Duyck <[email protected]>
Add support for what I am referring to as "unused page reporting". Basically the idea is to function very similar to how the balloon works in that we basically end up madvising the page as not being used. However we don't really need to bother with any deflate type logic since the page will be faulted back into the guest when it is read or written to.
This is meant to be a simplification of the existing balloon interface to use for providing hints to what memory needs to be freed. I am assuming this is safe to do as the deflate logic does not actually appear to do very much other than tracking what subpages have been released and which ones haven't.
--- hw/virtio/virtio-balloon.c | 46 ++++++++++++++++++++++++++++++++++-- include/hw/virtio/virtio-balloon.h | 2 +- 2 files changed, 45 insertions(+), 3 deletions(-)
hw/virtio/virtio-balloon.c +44 -2
@@ -321,6 +321,40 @@ static void balloon_stats_set_poll_interval(Object *obj, Visitor *v,balloon_stats_change_timer (s,0 ); } +static void virtio_balloon_handle_report (VirtIODevice *vdev,VirtQueue *vq) +{ +VirtIOBalloon *dev =VIRTIO_BALLOON (vdev); +VirtQueueElement *elem; + +while ((elem =virtqueue_pop (vq,sizeof (VirtQueueElement)))) { +unsigned int i; + +for (i =0 ; i < elem->in_num; i++) { +void *addr = elem->in_sg[i].iov_base; +size_t size = elem->in_sg[i].iov_len; +ram_addr_t ram_offset; +size_t rb_page_size; +RAMBlock *rb; + +if (qemu_balloon_is_inhibited () || dev->poison_val) +continue ; + + rb =qemu_ram_block_from_host (addr, false, &ram_offset); + rb_page_size =qemu_ram_pagesize (rb); + +/* For now we will simply ignore unaligned memory regions */ +if ((ram_offset | size) & (rb_page_size -1 )) +continue ; + +ram_block_discard_range (rb, ram_offset, size); + } + +virtqueue_push (vq, elem,0 ); +virtio_notify (vdev, vq); +g_free (elem); + } +} +static void virtio_balloon_handle_output (VirtIODevice *vdev,VirtQueue *vq) {VirtIOBalloon *s =VIRTIO_BALLOON (vdev);
@@ -628,7 +662,8 @@ static size_t virtio_balloon_config_size(VirtIOBalloon *s)return sizeof (struct virtio_balloon_config ); }if (virtio_has_feature (features,VIRTIO_BALLOON_F_PAGE_POISON ) || -virtio_has_feature (features,VIRTIO_BALLOON_F_FREE_PAGE_HINT )) { +virtio_has_feature (features,VIRTIO_BALLOON_F_FREE_PAGE_HINT ) || +virtio_has_feature (features,VIRTIO_BALLOON_F_REPORTING )) {return sizeof (struct virtio_balloon_config ); }return offsetof(struct virtio_balloon_config , free_page_report_cmd_id);
@@ -716,7 +751,8 @@ static uint64_t virtio_balloon_get_features(VirtIODevice *vdev, uint64_t f,VirtIOBalloon *dev =VIRTIO_BALLOON (vdev); f |= dev->host_features;virtio_add_feature (&f,VIRTIO_BALLOON_F_STATS_VQ ); -if (virtio_has_feature (f,VIRTIO_BALLOON_F_FREE_PAGE_HINT )) { +if (virtio_has_feature (f,VIRTIO_BALLOON_F_FREE_PAGE_HINT ) || +virtio_has_feature (f,VIRTIO_BALLOON_F_REPORTING )) {virtio_add_feature (&f,VIRTIO_BALLOON_F_PAGE_POISON ); }
@@ -806,6 +842,10 @@ static void virtio_balloon_device_realize(DeviceState *dev, Error **errp) s->dvq =virtio_add_queue (vdev,128 , virtio_balloon_handle_output); s->svq =virtio_add_queue (vdev,128 , virtio_balloon_receive_stats); +if (virtio_has_feature (s->host_features,VIRTIO_BALLOON_F_REPORTING )) { + s->rvq =virtio_add_queue (vdev,32 , virtio_balloon_handle_report); + } +if (virtio_has_feature (s->host_features,VIRTIO_BALLOON_F_FREE_PAGE_HINT )) { s->free_page_vq = virtio_add_queue(vdev, VIRTQUEUE_MAX_SIZE,
@@ -932,6 +972,8 @@ static Property virtio_balloon_properties[] = {*/ DEFINE_PROP_BOOL ("qemu-4-0-config-size" , VirtIOBalloon, qemu_4_0_config_size, false), +DEFINE_PROP_BIT ("unused-page-reporting" , VirtIOBalloon, host_features, +VIRTIO_BALLOON_F_REPORTING , true),DEFINE_PROP_LINK ("iothread" , VirtIOBalloon, iothread,TYPE_IOTHREAD , IOThread *), DEFINE_PROP_END_OF_LIST(),
include/hw/virtio/virtio-balloon.h +1 -1
@@ -42,7 +42,7 @@ enum virtio_balloon_free_page_report_status { typedef struct VirtIOBalloon { VirtIODevice parent_obj; - VirtQueue *ivq, *dvq, *svq, *free_page_vq; + VirtQueue *ivq, *dvq, *svq, *free_page_vq, *rvq; uint32_t free_page_report_status; uint32_t num_pages; uint32_t actual;
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 53 lines · Alexander Duyck
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as
MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "
reported_boundary" pointer. This pointer is used by theget_unreported_pagesiterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modifiedadd_to_free_list_tailso that it will not insert pages behind thereported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.If another process needs to perform a massive manipulation of the free list, such as compaction, it can either reset a given individual boundary which will push the boundary back to the
list_head, or it can clear the bit indicating the zone is actively processing which will result in the reporting process resetting all of the boundaries for a given zone.I am leaving a number of things hard-coded such as limiting the lowest order processed to
pageblock_order, and have left it up to the guest to determine what the limit is on how many pages it wants to allocate to process the hints. The upper limit for this is based on the size of the queue used to store the scatterlist.I wanted to avoid gaming the performance testing for this. As far as possible gain a significant performance improvement should be visible in cases where guests are forced to write/read from swap. As such, testing it would be more of a benchmark of copying a page from swap versus just allocating a zero page. I have been verifying that the memory is being freed using memhog to allocate all the memory on the guest, and then watching
/proc/meminfoto verify the host sees the memory returned after the test completes.
Quoted 12 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16 vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
Signature · 7 lines
Thanks, David / dhildenb --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 34 lines · David Hildenbrand
Quoted 33 lines · Alexander Duyck
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as
MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "
reported_boundary" pointer. This pointer is used by theget_unreported_pagesiterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modifiedadd_to_free_list_tailso that it will not insert pages behind thereported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.
<snip>
Quoted 13 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
- Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 11 lines
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
"I would still be happier if the allocator wouldn't really have to bother about somebody snooping its internal state to do its own thing. So make sure to describe why and how much this really matters. [...]
if you gave some rough numbers to quantify how much overhead for different solutions we are talking about here.
"
Could be that I'm misreading Michals comment, but I'd be interested in the "how much" as well.
Quoted 4 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
@Nitesh, is there a working branch?
Signature · 7 lines
Thanks, David / dhildenb --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 18 lines · David Hildenbrand
Quoted 10 lines
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
"I would still be happier if the allocator wouldn't really have to bother about somebody snooping its internal state to do its own thing. So make sure to describe why and how much this really matters. [...]
if you gave some rough numbers to quantify how much overhead for different solutions we are talking about here.
"
Quoted 7 lines
Could be that I'm misreading Michals comment, but I'd be interested in the "how much" as well.
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
@Nitesh, is there a working branch?
For some unknown reason, I received these set of emails just now :) That's why couldn't respond earlier.
Quoted 2 lines
Signature · 6 lines
Thanks Nitesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Michael S. Tsirkin
maintainerQuoted 5 lines · Alexander Duyck
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Something maybe worth adding to the log:
one disadvantage of the tight integration with the mm core is that only a single reporting device is supported. It's not obvious that more than one is useful though.
Signature · 1 line
MST
Quoted 60 lines · Alexander Duyck
Quoted 34 lines · David Hildenbrand
Quoted 33 lines · Alexander Duyck
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as
MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "
reported_boundary" pointer. This pointer is used by theget_unreported_pagesiterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modifiedadd_to_free_list_tailso that it will not insert pages behind thereported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.<snip>
Quoted 12 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.
[1] https://lkml.org/lkml/2019/8/12/593
Quoted 3 lines
- Alex
Signature · 2 lines
Thanks Nitesh
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · David Hildenbrand
On 01.10.19 17:29, Alexander Duyck wrote:
<snip>
Quoted 24 lines
Quoted 24 lines
Quoted 13 lines
Quoted 13 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16 vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 11 lines
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.[1] https://lkml.org/lkml/2019/8/12/593
Quoted 2 lines
- Alex
I haven't tested it. I will pull the patches and give it a try. It works with the same QEMU changes that mine does right? If so we should be able to get an apples-to-apples comparison.
Also, instead of providing lkml.org links to your patches in the future it might be better to provide a link to the lore.kernel.org version of the thread. So for example the v12 set would be:
https://lore.kernel.org/lkml/[email protected]/
The advantage is you can just look up the message ID in your own inbox to figure out the link, and it provides raw access to the email if needed.
Thanks.
- Alex
Quoted 51 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · David Hildenbrand
On 01.10.19 17:29, Alexander Duyck wrote:
<snip>
Quoted 23 lines
Quoted 23 lines
Quoted 12 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 11 lines
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.[1] https://lkml.org/lkml/2019/8/12/593
Quoted 2 lines
- Alex
I haven't tested it. I will pull the patches and give it a try. It works with the same QEMU changes that mine does right? If so we should be able to get an apples-to-apples comparison.
Also, instead of providing lkml.org links to your patches in the future it might be better to provide a link to the lore.kernel.org version of the thread. So for example the v12 set would be:
https://lore.kernel.org/lkml/[email protected]/
Quoted 6 lines
The advantage is you can just look up the message ID in your own inbox to figure out the link, and it provides raw access to the email if needed.
Thanks.
- Alex
So it looks like v12 still has issues. I'm pretty sure you should be using spin_lock_irq(), not spin_lock() in page_reporting.c to avoid the possibility of an IRQ firing and causing lock recursion on the zone lock.
I'm trying to work around it now, but it needs to be addressed for future versions.
Here is the lock-up my guest reported.
[ 127.869086] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 127.872219] rcu: 0-...0: (0 ticks this GP) idle=94e/1/0x4000000000000002 softirq=5354/5354 fqs=15000 [ 127.874915] rcu: 1-...0: (0 ticks this GP) idle=3b6/1/0x4000000000000000 softirq=3359/3359 fqs=15000 [ 127.877616] (detected by 2, t=60004 jiffies, g=8153, q=8) [ 127.879229] Sending NMI from CPU 2 to CPUs 0: [ 127.881523] NMI backtrace for cpu 0 [ 127.881524] CPU: 0 PID: 658 Comm: kworker/0:6 Not tainted 5.3.0-next-20190930nshuffle+ #2 [ 127.881524] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 127.881525] Workqueue: events page_reporting_wq [ 127.881526] RIP: 0010:queued_spin_lock_slowpath+0x21/0x1f0 [ 127.881526] Code: c0 75 ec c3 90 90 90 90 90 0f 1f 44 00 00 0f 1f 44 00 00 ba 01 00 00 00 8b 07 85 c0 75 0a f0 0f b1 17 85 c0 75 f2 f3 c3 f3 90 <eb> ec 81 fe 00 01 00 00 0f 84 44 01 00 00 81 e6 00 ff ff ff 75 3e [ 127.881527] RSP: 0018:ffffb77480003df0 EFLAGS: 00000002 [ 127.881527] RAX: 0000000000000001 RBX: 0000000000000001 RCX: dead000000000122 [ 127.881528] RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff992a3fffd240 [ 127.881528] RBP: 0000000000000006 R08: 0000000000000000 R09: ffffdd9c508cf948 [ 127.881528] R10: 0000000000000000 R11: 0000000000000000 R12: ffff992a3fffcd00 [ 127.881529] R13: ffffdd9c508cf900 R14: ffff992a2fa2e380 R15: 0000000000000001 [ 127.881529] FS: 0000000000000000(0000) GS:ffff992a2fa00000(0000) knlGS:0000000000000000 [ 127.881529] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 127.881530] CR2: 00007ffff7c50000 CR3: 000000042c6b8004 CR4: 0000000000160ef0 [ 127.881530] Call Trace: [ 127.881530] <IRQ> [ 127.881531] free_pcppages_bulk+0x15f/0x7d0 [ 127.881531] free_unref_page+0x54/0x70 [ 127.881531] tlb_remove_table_rcu+0x23/0x40 [ 127.881531] rcu_do_batch+0x139/0x3f0 [ 127.881532] rcu_core+0x1b9/0x2d0 [ 127.881532] __do_softirq+0xe2/0x2bb [ 127.881532] irq_exit+0xd5/0xe0 [ 127.881532] smp_apic_timer_interrupt+0x74/0x140 [ 127.881533] apic_timer_interrupt+0xf/0x20 [ 127.881533] </IRQ> [ 127.881533] RIP: 0010:__list_del_entry_valid+0x31/0x90 [ 127.881534] Code: 00 00 00 00 ad de 48 8b 57 08 48 39 c8 74 26 48 b9 22 01 00 00 00 00 ad de 48 39 ca 74 53 48 8b 12 48 39 d7 75 38 48 8b 50 08 <48> 39 d7 75 1c b8 01 00 00 00 c3 48 89 c2 48 89 fe 31 c0 48 c7 c7 [ 127.881534] RSP: 0018:ffffb774837cfdf8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 [ 127.881535] RAX: ffffdd9c50858008 RBX: ffffdd9c50798000 RCX: dead000000000122 [ 127.881535] RDX: ffffdd9c50798008 RSI: 0000000000000000 RDI: ffffdd9c50798008 [ 127.881536] RBP: ffff992a3fffcd00 R08: 0000000000000000 R09: 00000000003241ad [ 127.881536] R10: 0000000000000000 R11: 00000000000025c4 R12: 0000000000000009 [ 127.881536] R13: fffffffffffffe00 R14: 0000000000000001 R15: ffff992a3fffcd00 [ 127.881537] __isolate_free_page+0xe9/0x1d0 [ 127.881537] page_reporting_wq+0x1ba/0x290 [ 127.881537] process_one_work+0x16c/0x370 [ 127.881538] worker_thread+0x49/0x3e0 [ 127.881538] kthread+0xf8/0x130 [ 127.881538] ? apply_wqattrs_commit+0x100/0x100 [ 127.881538] ? kthread_bind+0x10/0x10 [ 127.881539] ret_from_fork+0x35/0x40 [ 127.881543] Sending NMI from CPU 2 to CPUs 1: [ 127.921299] NMI backtrace for cpu 1 [ 127.921300] CPU: 1 PID: 1257 Comm: page_fault4_pro Not tainted 5.3.0-next-20190930nshuffle+ #2 [ 127.921300] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 127.921300] RIP: 0010:queued_spin_lock_slowpath+0x21/0x1f0 [ 127.921301] Code: c0 75 ec c3 90 90 90 90 90 0f 1f 44 00 00 0f 1f 44 00 00 ba 01 00 00 00 8b 07 85 c0 75 0a f0 0f b1 17 85 c0 75 f2 f3 c3 f3 90 <eb> ec 81 fe 00 01 00 00 0f 84 44 01 00 00 81 e6 00 ff ff ff 75 3e [ 127.921301] RSP: 0000:ffffb7748378bbd8 EFLAGS: 00000002 [ 127.921302] RAX: 0000000000000001 RBX: 0000000000000246 RCX: 0000000000000001 [ 127.921302] RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff992a3fffd240 [ 127.921303] RBP: 0000000000000009 R08: 0000000000000080 R09: 0000000000323dae [ 127.921303] R10: 0000000000000009 R11: 00000000000030d1 R12: 0000000000000081 [ 127.921304] R13: 00000000003c24ca R14: 0000000000000000 R15: ffff992a3fffcd00 [ 127.921304] FS: 00007ffff7c52540(0000) GS:ffff992a2fa40000(0000) knlGS:0000000000000000 [ 127.921304] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 127.921305] CR2: 00007ffff1e00000 CR3: 000000042f17c001 CR4: 0000000000160ee0 [ 127.921305] Call Trace: [ 127.921305] _raw_spin_lock_irqsave+0x35/0x40 [ 127.921305] get_page_from_freelist+0xba0/0x13c0 [ 127.921306] ? prep_new_page+0xad/0xf0 [ 127.921306] __alloc_pages_nodemask+0x197/0x350 [ 127.921306] alloc_pages_vma+0x160/0x1b0 [ 127.921307] do_huge_pmd_anonymous_page+0x123/0x8a0 [ 127.921307] __handle_mm_fault+0xcbe/0x15f0 [ 127.921307] ? do_mmap+0x47b/0x5e0 [ 127.921307] handle_mm_fault+0xe2/0x1f0 [ 127.921308] __do_page_fault+0x234/0x4c0 [ 127.921308] do_page_fault+0x31/0x120 [ 127.921308] async_page_fault+0x3e/0x50 [ 127.921308] RIP: 0033:0x401c30 [ 127.921309] Code: 00 00 00 08 e8 d1 f4 ff ff 48 89 c5 48 83 f8 ff 74 40 ba 0e 00 00 00 be 00 00 00 08 48 89 c7 e8 e6 f5 ff ff 31 c0 0f 1f 40 00 <c6> 44 05 00 00 4c 01 e0 48 83 03 01 48 3d ff ff ff 07 76 ec be 00 [ 127.921309] RSP: 002b:00007fffffffc8f0 EFLAGS: 00010293 [ 127.921310] RAX: 00000000021af000 RBX: 00007ffff7ffb080 RCX: 00007ffff7eaf2eb [ 127.921310] RDX: 000000000000000e RSI: 0000000008000000 RDI: 00007fffefc51000 [ 127.921311] RBP: 00007fffefc51000 R08: 00000000ffffffff R09: 0000000000000000 [ 127.921311] R10: 0000000000000022 R11: 0000000000000213 R12: 0000000000001000 [ 127.921311] R13: 000000000044de20 R14: 000000000040d890 R15: 0000000000408d20
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 3 lines · Alexander Duyck
So it looks like v12 still has issues. I'm pretty sure you should be using
spin_lock_irq(), notspin_lock()inpage_reporting.cto avoid the possibility of an IRQ firing and causing lock recursion on the zone lock.
Lockdep should make all of this a lot easier to find. Is it being used?
Quoted 5 lines · Dave Hansen
Quoted 3 lines · Alexander Duyck
So it looks like v12 still has issues. I'm pretty sure you should be using
spin_lock_irq(), notspin_lock()inpage_reporting.cto avoid the possibility of an IRQ firing and causing lock recursion on the zone lock.Lockdep should make all of this a lot easier to find. Is it being used?
I do have it in the function which returns the pages to the buddy but I missed it in the function that isolates the pages.
I will correct this.
Signature · 2 lines
Thanks Nitesh
Quoted 35 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · David Hildenbrand
On 01.10.19 17:29, Alexander Duyck wrote:
<snip>
Quoted 29 lines
Quoted 23 lines
Quoted 12 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.
Quoted 7 lines
Quoted 4 lines
[1] https://lkml.org/lkml/2019/8/12/593
Quoted 2 lines
- Alex
I haven't tested it. I will pull the patches and give it a try. It works with the same QEMU changes that mine does right? If so we should be able to get an apples-to-apples comparison.
Yes.
Quoted 5 lines
Also, instead of providing lkml.org links to your patches in the future it might be better to provide a link to the lore.kernel.org version of the thread. So for example the v12 set would be:
https://lore.kernel.org/lkml/[email protected]/
I see, I will keep that in mind. Thanks for pointing this out.
Quoted 13 lines
The advantage is you can just look up the message ID in your own inbox to figure out the link, and it provides raw access to the email if needed.
Thanks.
- Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Signature · 6 lines
Thanks Nitesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 63 lines · Nitesh Narayan Lal
Quoted 60 lines · Alexander Duyck
Quoted 34 lines · David Hildenbrand
Quoted 33 lines · Alexander Duyck
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as
MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "
reported_boundary" pointer. This pointer is used by theget_unreported_pagesiterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modifiedadd_to_free_list_tailso that it will not insert pages behind thereported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.<snip>
Quoted 12 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 8 lines
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.
So I tried testing with the spin_lock calls replaced with spin_lock _irq to resolve the IRQ issue. I also had shuffle enabled in order to increase the number of pages being dirtied.
With that setup the bitmap approach is running significantly worse then my approach, even with the boundary removed. Since I had to modify the code to even getting working I am not comfortable posting numbers. My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then. I would prefer not to spend my time fixing and tuning a patch set that I am still not convinced is viable.
Thanks.
- Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 71 lines · Alexander Duyck
Quoted 70 lines · Nitesh Narayan Lal
Quoted 60 lines · Alexander Duyck
Quoted 34 lines · David Hildenbrand
Quoted 33 lines · Alexander Duyck
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as
MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "
reported_boundary" pointer. This pointer is used by theget_unreported_pagesiterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modifiedadd_to_free_list_tailso that it will not insert pages behind thereported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.<snip>
Quoted 12 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.
Quoted 8 lines
Quoted 1 line
So I tried testing with the
spin_lockcalls replaced withspin_lock_irqto resolve the IRQ issue. I also had shuffle enabled in order to increase the number of pages being dirtied.With that setup the bitmap approach is running significantly worse then my approach, even with the boundary removed. Since I had to
It would make sense to share the setup+benchmark+performance indication that you measured. You don't have to share the actual numbers.
Quoted 5 lines
modify the code to even getting working I am not comfortable posting numbers. My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then. I would prefer not to spend my time fixing and tuning a patch set that I am still not convinced is viable.
I agree, I think Nitesh should work on his patch set and try to reproduce what you are seeing.
Also, I think to make a precise statement of "which overhead comes with external tracking", Nitesh should switch to an approach (motivated by Michal) like
1. Sense lockless if a page is still free
2. start_isolate_page_range()
-> Failed? Skip
3. test_pages_isolated()
-> No? undo_isolate_page_range(), skip
4. Repeat for multiple pages + report
5. undo_isolate_page_range()
That is the bare minimum any external tracking will need = some overhead for the tracking data. As a nice side effect, it get's rid of taking the zone lock manually AFAIKS.
But that's unrelated to your series, only to quantify "how much" does external tracking actually cost.
Signature · 7 lines
Thanks, David / dhildenb --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 71 lines · David Hildenbrand
Quoted 70 lines · Alexander Duyck
Quoted 69 lines · Nitesh Narayan Lal
Quoted 60 lines · Alexander Duyck
Quoted 34 lines · David Hildenbrand
Quoted 33 lines · Alexander Duyck
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as
MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "
reported_boundary" pointer. This pointer is used by theget_unreported_pagesiterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modifiedadd_to_free_list_tailso that it will not insert pages behind thereported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.<snip>
Quoted 12 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.
Quoted 8 lines
Quoted 6 lines
So I tried testing with the
spin_lockcalls replaced withspin_lock_irqto resolve the IRQ issue. I also had shuffle enabled in order to increase the number of pages being dirtied.With that setup the bitmap approach is running significantly worse then my approach, even with the boundary removed. Since I had to
It would make sense to share the setup+benchmark+performance indication that you measured. You don't have to share the actual numbers.
+1
Quoted 8 lines
Quoted 6 lines
modify the code to even getting working I am not comfortable posting numbers. My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then. I would prefer not to spend my time fixing and tuning a patch set that I am still not convinced is viable.
I agree, I think Nitesh should work on his patch set and try to reproduce what you are seeing.
Sure.
I am always open to suggestions of different benchmarks/setup where I can run my patch-set.
Quoted 13 lines
Also, I think to make a precise statement of "which overhead comes with external tracking", Nitesh should switch to an approach (motivated by Michal) like
1. Sense lockless if a page is still free
2.start_isolate_page_range()
-> Failed? Skip
3.test_pages_isolated()
-> No?undo_isolate_page_range(), skip
4. Repeat for multiple pages + report
5.undo_isolate_page_range()
Quoted 6 lines
That is the bare minimum any external tracking will need = some overhead for the tracking data. As a nice side effect, it get's rid of taking the zone lock manually AFAIKS.
But that's unrelated to your series, only to quantify "how much" does external tracking actually cost.
Exactly, first, we need to be sure that the overhead caused by bitmap scanning is not significant. If we are fine with the approach, I will certainly look into this as this would be an excellent enhancement.
Signature · 2 lines
Thanks Nitesh
Quoted 70 lines · Alexander Duyck
Quoted 62 lines · Nitesh Narayan Lal
Quoted 60 lines · Alexander Duyck
Quoted 34 lines · David Hildenbrand
Quoted 33 lines · Alexander Duyck
This series provides an asynchronous means of reporting to a hypervisor that a guest page is no longer in use and can have the data associated with it dropped. To do this I have implemented functionality that allows for what I am referring to as unused page reporting. The advantage of unused page reporting is that we can support a significant amount of memory over-commit with improved performance as we can avoid having to write/read memory from swap as the VM will instead actively participate in freeing unused memory so it doesn't have to be written.
The functionality for this is fairly simple. When enabled it will allocate statistics to track the number of reported pages in a given free area. When the number of free pages exceeds this value plus a high water value, currently 32, it will begin performing page reporting which consists of pulling non-reported pages off of the free lists of a given zone and placing them into a scatterlist. The scatterlist is then given to the page reporting device and it will perform the required action to make the pages "reported", in the case of virtio-balloon this results in the pages being madvised as
MADV_DONTNEED. After this they are placed back on their original free list. If they are not merged in freeing an additional bit is set indicating that they are a "reported" buddy page instead of a standard buddy page. The cycle then repeats with additional non-reported pages being pulled until the free areas all consist of reported pages.In order to try and keep the time needed to find a non-reported page to a minimum we maintain a "
reported_boundary" pointer. This pointer is used by theget_unreported_pagesiterator to determine at what point it should resume searching for non-reported pages. In order to guarantee pages do not get past the scan I have modifiedadd_to_free_list_tailso that it will not insert pages behind thereported_boundary. Doing this allows us to keep the overhead to a minimum as re-walking the list without the boundary will result in as much as 18% additional overhead on a 32G VM.<snip>
Quoted 12 lines
Quoted 4 lines
As far as possible regressions I have focused on cases where performing the hinting would be non-optimal, such as cases where the code isn't needed as memory is not over-committed, or the functionality is not in use. I have been using the will-it-scale/page_fault1 test running with 16
Quoted 8 lines
vcpus and have modified it to use Transparent Huge Pages. With this I see almost no difference with the patches applied and the feature disabled. Likewise I see almost no difference with the feature enabled, but the madvise disabled in the hypervisor due to a device being assigned. With the feature fully enabled in both guest and hypervisor I see a regression between -1.86% and -8.84% versus the baseline. I found that most of the overhead was due to the page faulting/zeroing that comes as a result of the pages having been evicted from the guest.
Quoted 5 lines
I think Michal asked for a performance comparison against Nitesh's approach, to evaluate if keeping the reported state + tracking inside the buddy is really worth it. Do you have any such numbers already? (or did my tired eyes miss them in this cover letter? :/)
I thought what Michal was asking for was what was the benefit of using the boundary pointer. I added a bit up above and to the description for patch 3 as on a 32G VM it adds up to about a 18% difference without factoring in the page faulting and zeroing logic that occurs when we actually do the madvise.
Quoted 7 lines
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.
Quoted 8 lines
So I tried testing with the
spin_lockcalls replaced withspin_lock_irqto resolve the IRQ issue. I also had shuffle enabled in order to increase the number of pages being dirtied.With that setup the bitmap approach is running significantly worse then my approach, even with the boundary removed. Since I had to modify the code to even getting working I am not comfortable posting numbers.
I didn't face any issue in getting the code work or compile. Before my v12 posting, I did try your previously suggested test (will-it-scale/page_fault1 for 12 hours on a 60 GB) and didn't see any issues. I think it would help more if you can share the setup which you are running.
Quoted 3 lines
My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then.
Agreed. However, in order to fix an issue I have to reproduce it first.
Quoted 2 lines
I would prefer not to spend my time fixing and
tuning a patch set that I am still not convinced is viable.
You don't have to, I can fix the issues in my patch-set. :)
Quoted 4 lines
Thanks.
- Alex
Signature · 1 line
Nitesh
Quoted 8 lines · Nitesh Narayan Lal
Quoted 5 lines · Alexander Duyck
Quoted 4 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · David Hildenbrand
On 01.10.19 17:29, Alexander Duyck wrote:
<snip>
Quoted 16 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.Quoted 8 lines
So I tried testing with the
spin_lockcalls replaced withspin_lock_irqto resolve the IRQ issue. I also had shuffle enabled in order to increase the number of pages being dirtied.With that setup the bitmap approach is running significantly worse then my approach, even with the boundary removed. Since I had to modify the code to even getting working I am not comfortable posting numbers.
Quoted 4 lines
I didn't face any issue in getting the code work or compile. Before my v12 posting, I did try your previously suggested test (will-it-scale/page_fault1 for 12 hours on a 60 GB) and didn't see any issues. I think it would help more if you can share the setup which you are running.
So one issue with the standard page_fault1 is that it is only operating at the 4K page level. You won't see much impact from you patches with that as the overhead of splitting a MAX_ORDER - 2 page down to a 4K page will end up being the biggest thing you are benchmarking.
I think I have brought it up before but I am running with the page_fault1 modified to use THP. Making the change is pretty straightforward as all you have to do is add an madvise to the test code. All that is needed is to add "madvise(c, MEMSIZE, MADV_HUGEPAGE);" between the assert and the for loop in the page_fault1 code and then rebuild the test. I actually copied page_fault1.c into a file I named page_fault4.c and added the line. As a result it seems like the code will build it as an additional test.
The only other alteration I can think of that might have much impact would be to enable the page shuffling. The idea is that it will cause us to use more pages because half of the pages freed are dumped to the tail of the list so we are constantly churning the memory.
Quoted 5 lines
Quoted 3 lines
My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then.
Agreed. However, in order to fix an issue I have to reproduce it first.
With the tweak I have suggested above it should make it much easier to reproduce. Basically all you need is to have the allocation competing against hinting. Currently the hinting isn't doing this because the allocations are mostly coming out of 4K pages instead of higher order ones.
Alternatively you could just make the suggestion I had proposed about using spin_lock/unlock_irq in your worker thread and that resolved it for me.
Quoted 4 lines
Quoted 2 lines
I would prefer not to spend my time fixing and
tuning a patch set that I am still not convinced is viable.You don't have to, I can fix the issues in my patch-set. :)
Sounds good. Hopefully the stuff I pointed out above helps you to get a reproduction and resolve the issues.
- Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 34 lines · Alexander Duyck
Quoted 6 lines · Nitesh Narayan Lal
Quoted 4 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · David Hildenbrand
On 01.10.19 17:29, Alexander Duyck wrote:
<snip>
Quoted 11 lines
Quoted 11 lines
Quoted 7 lines
Quoted 3 lines
Do we have a working patch set for Nitesh's code? The last time I tried running his patch set I ran into issues with kernel panics. If we have a known working/stable patch set I can give it a try.
Did you try the v12 patch-set [1]?
I remember that you reported the CPU stall issue, which I fixed in the v12.So I tried testing with the
spin_lockcalls replaced withspin_lock_irqto resolve the IRQ issue. I also had shuffle enabled in order to increase the number of pages being dirtied.Quoted 8 lines
Quoted 4 lines
With that setup the bitmap approach is running significantly worse then my approach, even with the boundary removed. Since I had to modify the code to even getting working I am not comfortable posting numbers.
I didn't face any issue in getting the code work or compile. Before my v12 posting, I did try your previously suggested test (will-it-scale/page_fault1 for 12 hours on a 60 GB) and didn't see any issues. I think it would help more if you can share the setup which you are running.
So one issue with the standard
page_fault1is that it is only operating at the 4K page level. You won't see much impact from you patches with that as the overhead of splitting aMAX_ORDER- 2 page down to a 4K page will end up being the biggest thing you are benchmarking.
Quoted 8 lines
I think I have brought it up before but I am running with the
page_fault1modified to use THP. Making the change is pretty straightforward as all you have to do is add an madvise to the test code. All that is needed is to add "madvise(c, MEMSIZE, MADV_HUGEPAGE);" between the assert and the for loop in thepage_fault1code and then rebuild the test. I actually copiedpage_fault1.cinto a file I namedpage_fault4.cand added the line. As a result it seems like the code will build it as an additional test.
Thanks for explaining.
Quoted 9 lines
The only other alteration I can think of that might have much impact would be to enable the page shuffling. The idea is that it will cause us to use more pages because half of the pages freed are dumped to the tail of the list so we are constantly churning the memory.
Quoted 3 lines
Quoted 3 lines
My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then.
Quoted 6 lines
Quoted 1 line
Agreed. However, in order to fix an issue I have to reproduce it first.
With the tweak I have suggested above it should make it much easier to reproduce. Basically all you need is to have the allocation competing against hinting. Currently the hinting isn't doing this because the allocations are mostly coming out of 4K pages instead of higher order ones.
Understood.
Quoted 4 lines
Alternatively you could just make the suggestion I had proposed about using spin_lock/unlock_irq in your worker thread and that resolved it for me.
I will first reproduce as you suggested and then make the change. That will help me to understand the issue in a better way.
Quoted 6 lines
Quoted 4 lines
Quoted 3 lines
I would prefer not to spend my time fixing and
tuning a patch set that I am still not convinced is viable.You don't have to, I can fix the issues in my patch-set. :)
Sounds good. Hopefully the stuff I pointed out above helps you to get a reproduction and resolve the issues.
Indeed, I will try these suggestions and fix this issue. Did you run into any other issues while building or running?
Quoted 2 lines
- Alex
Signature · 7 lines
Thanks Nitesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
On 10/2/19 10:25 AM, Alexander Duyck wrote:
[...]
Quoted 14 lines
Quoted 4 lines
Quoted 3 lines
My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then.
Agreed. However, in order to fix an issue I have to reproduce it first.
With the tweak I have suggested above it should make it much easier to reproduce. Basically all you need is to have the allocation competing against hinting. Currently the hinting isn't doing this because the allocations are mostly coming out of 4K pages instead of higher order ones.
Alternatively you could just make the suggestion I had proposed about using spin_lock/unlock_irq in your worker thread and that resolved it for me.
Quoted 5 lines
Quoted 3 lines
Quoted 2 lines
I would prefer not to spend my time fixing and
tuning a patch set that I am still not convinced is viable.You don't have to, I can fix the issues in my patch-set. :)
Sounds good. Hopefully the stuff I pointed out above helps you to get a reproduction and resolve the issues.
So I did observe a significant drop in running my v12 path-set [1] with the suggested test setup. However, on making certain changes the performance improved significantly.
I used my v12 patch-set which I have posted earlier and made the following changes:
1. Started reporting only (MAX_ORDER - 1) pages and increased the number of pages that can be reported at a time to 32 from 16. The intent of making these changes was to bring my configuration closer to what Alexander is using.
2. I made an additional change in my bitmap scanning logic to prevent acquiring spinlock if the page is already allocated.
Setup:
On a 16 vCPU 30 GB single NUMA guest affined to a single host NUMA, I ran the modified will-it-scale/page_fault number of times and calculated the average of the number of process and threads launched on the 16th core to compare the impact of my patch-set against an unmodified kernel.
Conclusion:
%Drop in number of processes launched on 16th vCPU = 1-2% %Drop in number of threads launched on 16th vCPU = 5-6%
Other observations:
- I also tried running Alexander's latest v11 page-reporting patch set and observe a similar amount of average degradation in the number of processes and threads.
- I didn't include the linear component recorded by will-it-scale because for some reason it was fluctuating too much even when I was using an unmodified kernel. If required I can investigate this further.
Note: If there is a better way to analyze the will-it-scale/page_fault results then please do let me know.
Other setup details:
Following are the configurations which I enabled to run my tests:
- Enabled: CONFIG_SLAB_FREELIST_RANDOM & CONFIG_SHUFFLE_PAGE_ALLOCATOR
- Set host THP to always
- Set guest THP to madvise
- Added the suggested madvise call in page_fault source code. @Alexander please let me know if I missed something.
The current state of my v13:
I still have to look into Michal's suggestion of using page-isolation API's instead of isolating the page. However, I believe at this moment our objective is to decide with which approach we can proceed and that's why I decided to post the numbers by making small required changes in v12 instead of posting a new series.
Following are the changes which I have made on top of my v12:
page_reporting.h change:
-#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 2) -#define PAGE_REPORTING_MAX_PAGES 16 +#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 1) +#define PAGE_REPORTING_MAX_PAGES 32
page_reporting.c change:
@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf,
/* Process only if the page is still online */
page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn);
- if (!page)
+ if (!page || !PageBuddy(page)) {
+ clear_bit(setbit, zone->bitmap);
+ atomic_dec(&zone->free_pages);
continue;
+ }
@Alexander in case you decide to give it a try and find different results, please do let me know.
[1] https://lore.kernel.org/lkml/[email protected]/
Signature · 2 lines
Thanks Nitesh
Quoted 27 lines · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
[...]
Quoted 14 lines
Quoted 4 lines
Quoted 3 lines
My suggestion would be to look at reworking the patch set and post numbers for my patch set versus the bitmap approach and we can look at them then.
Agreed. However, in order to fix an issue I have to reproduce it first.
With the tweak I have suggested above it should make it much easier to reproduce. Basically all you need is to have the allocation competing against hinting. Currently the hinting isn't doing this because the allocations are mostly coming out of 4K pages instead of higher order ones.
Alternatively you could just make the suggestion I had proposed about using spin_lock/unlock_irq in your worker thread and that resolved it for me.
Quoted 5 lines
Quoted 3 lines
Quoted 2 lines
I would prefer not to spend my time fixing and
tuning a patch set that I am still not convinced is viable.You don't have to, I can fix the issues in my patch-set. :)
Sounds good. Hopefully the stuff I pointed out above helps you to get a reproduction and resolve the issues.
So I did observe a significant drop in running my v12 path-set [1] with the suggested test setup. However, on making certain changes the performance improved significantly.
Quoted 6 lines
I used my v12 patch-set which I have posted earlier and made the following changes:
1. Started reporting only (MAX_ORDER- 1) pages and increased the number of pages that can be reported at a time to 32 from 16. The intent of making these changes was to bring my configuration closer to what Alexander is using.
The increase from 16 to 32 is valid. No point in working in too small of batches. However tightening the order to only test for MAX_ORDER - 1 seems like a step in the wrong direction. The bitmap approach doesn't have much value if it can only work with the highest order page. I realize it is probably necessary in order to make the trick for checking on page_buddy work, but it seems very limiting.
Quoted 2 lines
2. I made an additional change in my bitmap scanning logic to prevent acquiring spinlock if the page is already allocated.
Again, not a fan. It basically means you can only work with MAX_ORDER - 1 and there will be no ability to work with anything smaller.
Quoted 11 lines
Setup:
On a 16 vCPU 30 GB single NUMA guest affined to a single host NUMA, I ran the modified will-it-scale/page_fault number of times and calculated the average of the number of process and threads launched on the 16th core to compare the impact of my patch-set against an unmodified kernel.Conclusion:
%Drop in number of processes launched on 16th vCPU = 1-2%
%Drop in number of threads launched on 16th vCPU = 5-6%
These numbers don't make that much sense to me. Are you talking about a fully functioning setup that is madvsing away the memory in the hypervisor? If so I would have expected a much higher difference versus baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.
Quoted 10 lines
Other observations:
- I also tried running Alexander's latest v11 page-reporting patch set and observe a similar amount of average degradation in the number of processes and threads.
- I didn't include the linear component recorded by will-it-scale because for some reason it was fluctuating too much even when I was using an unmodified kernel. If required I can investigate this further.Note: If there is a better way to analyze the will-it-scale/page_fault results then please do let me know.
Honestly I have mostly just focused on the processes performance. There is usually a fair bit of variability but a pattern forms after a few runs so you can generally tell if a configuration is an improvement or not.
Quoted 7 lines
Other setup details:
Following are the configurations which I enabled to run my tests:
- Enabled:CONFIG_SLAB_FREELIST_RANDOM&CONFIG_SHUFFLE_PAGE_ALLOCATOR
- Set host THP to always
- Set guest THP to madvise
- Added the suggested madvise call inpage_faultsource code. @Alexander please let me know if I missed something.
This seems about right.
Quoted 19 lines
The current state of my v13:
I still have to look into Michal's suggestion of using page-isolation API's instead of isolating the page. However, I believe at this moment our objective is to decide with which approach we can proceed and that's why I decided to post the numbers by making small required changes in v12 instead of posting a new series.Following are the changes which I have made on top of my v12:
page_reporting.hchange:(quoted diff) +2
-2-#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 2) -#define PAGE_REPORTING_MAX_PAGES 16 +#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 1) +#define PAGE_REPORTING_MAX_PAGES 32
page_reporting.cchange:(quoted diff) +0
-0@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf,
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 10 lines
(quoted diff) +4
-1/* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue; + }
I suspect the zone->free_pages is going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU increments free_pages it will likely have to take the cache line containing the bitmap pointer as well.
Quoted 6 lines
(quoted diff) +0
-0@Alexander in case you decide to give it a try and find different results,please do let me know.
If I have some free time I will take a look. However one thing that concerns me about this change is that it will limit things much further in terms of how much memory can ultimately be freed since you are now only working with the highest order page and that becomes a hard requirement for your design.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 3 lines · Alexander Duyck
Quoted 2 lines · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
[...]
Quoted 13 lines
Quoted 7 lines
You don't have to, I can fix the issues in my patch-set. :)
Quoted 2 lines
Sounds good. Hopefully the stuff I pointed out above helps you to get a reproduction and resolve the issues.
So I did observe a significant drop in running my v12 path-set [1] with the suggested test setup. However, on making certain changes the performance improved significantly.
Quoted 6 lines
I used my v12 patch-set which I have posted earlier and made the following changes:
1. Started reporting only (MAX_ORDER- 1) pages and increased the number of pages that can be reported at a time to 32 from 16. The intent of making these changes was to bring my configuration closer to what Alexander is using.
Quoted 6 lines
The increase from 16 to 32 is valid. No point in working in too small of batches. However tightening the order to only test for
MAX_ORDER- 1 seems like a step in the wrong direction. The bitmap approach doesn't have much value if it can only work with the highest order page. I realize it is probably necessary in order to make the trick for checking onpage_buddywork, but it seems very limiting.
If using (pageblock_order - 1) is a better way to do this, then I can probably switch to that.
I will agree with the fact that we have to make the reporting order configurable, atleast to an extent.
Quoted 13 lines
Quoted 3 lines
2. I made an additional change in my bitmap scanning logic to prevent acquiring spinlock if the page is already allocated.
Again, not a fan. It basically means you can only work with
MAX_ORDER- 1 and there will be no ability to work with anything smaller.Quoted 7 lines
Setup:
On a 16 vCPU 30 GB single NUMA guest affined to a single host NUMA, I ran the modified will-it-scale/page_fault number of times and calculated the average of the number of process and threads launched on the 16th core to compare the impact of my patch-set against an unmodified kernel.
Quoted 6 lines
Quoted 3 lines
Conclusion:
%Drop in number of processes launched on 16th vCPU = 1-2%
%Drop in number of threads launched on 16th vCPU = 5-6%These numbers don't make that much sense to me. Are you talking about a fully functioning setup that is madvsing away the memory in the hypervisor?
Without making this change I was observing a significant amount of drop in the number of processes and specifically in the number of threads. I did a double-check of the configuration which I have shared.
I was also observing the "AnonHugePages" via meminfo to check the THP usage. Any more suggestions about what else I can do to verify?
I will be more than happy to try them out.
Quoted 6 lines
If so I would have expected a much higher difference versus
baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.
Right now I have a different host-kernel. I can install the same kernel to the host as well and see if that changes anything.
Quoted 9 lines
Quoted 9 lines
Other observations:
- I also tried running Alexander's latest v11 page-reporting patch set and observe a similar amount of average degradation in the number of processes and threads.
- I didn't include the linear component recorded by will-it-scale because for some reason it was fluctuating too much even when I was using an unmodified kernel. If required I can investigate this further.
Quoted 3 lines
Quoted 2 lines
Note: If there is a better way to analyze the will-it-scale/page_fault results then please do let me know.
Honestly I have mostly just focused on the processes performance.
In my observation processes seems to be most consistent in general.
Quoted 3 lines
There is
usually a fair bit of variability but a pattern forms after a few runs so you can generally tell if a configuration is an improvement or not.
Yeah, that's why I thought of taking the average of 5-6 runs.
Quoted 37 lines
Quoted 8 lines
Other setup details:
Following are the configurations which I enabled to run my tests:
- Enabled:CONFIG_SLAB_FREELIST_RANDOM&CONFIG_SHUFFLE_PAGE_ALLOCATOR
- Set host THP to always
- Set guest THP to madvise
- Added the suggested madvise call inpage_faultsource code. @Alexander please let me know if I missed something.This seems about right.
Quoted 27 lines
The current state of my v13:
I still have to look into Michal's suggestion of using page-isolation API's instead of isolating the page. However, I believe at this moment our objective is to decide with which approach we can proceed and that's why I decided to post the numbers by making small required changes in v12 instead of posting a new series.Following are the changes which I have made on top of my v12:
page_reporting.hchange:(quoted diff) +2
-2-#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 2) -#define PAGE_REPORTING_MAX_PAGES 16 +#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 1) +#define PAGE_REPORTING_MAX_PAGES 32
page_reporting.cchange:(quoted diff) +3
-1@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf, /* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue;
Quoted 8 lines
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 2 lines
(quoted diff) +1
-0+ }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
Quoted 8 lines
Quoted 7 lines
(quoted diff) +0
-0@Alexander in case you decide to give it a try and find different results,please do let me know.
If I have some free time I will take a look.
That would be great, thanks.
Quoted 5 lines
However one thing that
concerns me about this change is that it will limit things much further in terms of how much memory can ultimately be freed since you are now only working with the highest order page and that becomes a hard requirement for your design.
I would assume that should be resolved with (pageblock_order - 1).
Quoted 1 line
Signature · 6 lines
Nitesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 25 lines · Nitesh Narayan Lal
Quoted 3 lines · Alexander Duyck
Quoted 2 lines · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
[...]
Quoted 13 lines
Quoted 7 lines
You don't have to, I can fix the issues in my patch-set. :)
Quoted 2 lines
Sounds good. Hopefully the stuff I pointed out above helps you to get a reproduction and resolve the issues.
So I did observe a significant drop in running my v12 path-set [1] with the suggested test setup. However, on making certain changes the performance improved significantly.
Quoted 6 lines
I used my v12 patch-set which I have posted earlier and made the following changes:
1. Started reporting only (MAX_ORDER- 1) pages and increased the number of pages that can be reported at a time to 32 from 16. The intent of making these changes was to bring my configuration closer to what Alexander is using.Quoted 6 lines
The increase from 16 to 32 is valid. No point in working in too small of batches. However tightening the order to only test for
MAX_ORDER- 1 seems like a step in the wrong direction. The bitmap approach doesn't have much value if it can only work with the highest order page. I realize it is probably necessary in order to make the trick for checking onpage_buddywork, but it seems very limiting.
Quoted 4 lines
If using (
pageblock_order- 1) is a better way to do this, then I can probably switch to that.
I will agree with the fact that we have to make the reporting order configurable, atleast to an extent.
I think you mean pageblock_order, not pageblock_order - 1. The problem with pageblock_order - 1 is that it will have a negative impact on performance as it would disable THP.
Quoted 19 lines
Quoted 12 lines
Quoted 2 lines
2. I made an additional change in my bitmap scanning logic to prevent acquiring spinlock if the page is already allocated.
Again, not a fan. It basically means you can only work with
MAX_ORDER- 1 and there will be no ability to work with anything smaller.Quoted 7 lines
Setup:
On a 16 vCPU 30 GB single NUMA guest affined to a single host NUMA, I ran the modified will-it-scale/page_fault number of times and calculated the average of the number of process and threads launched on the 16th core to compare the impact of my patch-set against an unmodified kernel.Quoted 6 lines
Quoted 3 lines
Conclusion:
%Drop in number of processes launched on 16th vCPU = 1-2%
%Drop in number of threads launched on 16th vCPU = 5-6%These numbers don't make that much sense to me. Are you talking about a fully functioning setup that is madvsing away the memory in the hypervisor?
Quoted 6 lines
Without making this change I was observing a significant amount of drop in the number of processes and specifically in the number of threads. I did a double-check of the configuration which I have shared.
I was also observing the "AnonHugePages" via meminfo to check the THP usage. Any more suggestions about what else I can do to verify?
I will be more than happy to try them out.
So what was the size of your guest? One thing that just occurred to me is that you might be running a much smaller guest than I was.
Quoted 9 lines
Quoted 6 lines
If so I would have expected a much higher difference versus
baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.Right now I have a different host-kernel. I can install the same kernel to the host as well and see if that changes anything.
The host kernel will have a fairly significant impact as I recall. For example running a stock CentOS kernel lowered the performance compared to running a linux-next kernel. As a result the numbers looked better since the overall baseline was lower to begin with as the host OS was introducing additional overhead.
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Other observations:
- I also tried running Alexander's latest v11 page-reporting patch set and observe a similar amount of average degradation in the number of processes and threads.
- I didn't include the linear component recorded by will-it-scale because for some reason it was fluctuating too much even when I was using an unmodified kernel. If required I can investigate this further.
Quoted 5 lines
Quoted 3 lines
Quoted 2 lines
Note: If there is a better way to analyze the will-it-scale/page_fault results then please do let me know.
Honestly I have mostly just focused on the processes performance.
In my observation processes seems to be most consistent in general.
Agreed.
Quoted 5 lines
Quoted 3 lines
There is
usually a fair bit of variability but a pattern forms after a few runs so you can generally tell if a configuration is an improvement or not.Yeah, that's why I thought of taking the average of 5-6 runs.
Same here. I am usually running about 5 iterations.
Quoted 45 lines
Quoted 36 lines
Quoted 7 lines
Other setup details:
Following are the configurations which I enabled to run my tests:
- Enabled:CONFIG_SLAB_FREELIST_RANDOM&CONFIG_SHUFFLE_PAGE_ALLOCATOR
- Set host THP to always
- Set guest THP to madvise
- Added the suggested madvise call inpage_faultsource code. @Alexander please let me know if I missed something.This seems about right.
Quoted 27 lines
The current state of my v13:
I still have to look into Michal's suggestion of using page-isolation API's instead of isolating the page. However, I believe at this moment our objective is to decide with which approach we can proceed and that's why I decided to post the numbers by making small required changes in v12 instead of posting a new series.Following are the changes which I have made on top of my v12:
page_reporting.hchange:(quoted diff) +2
-2-#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 2) -#define PAGE_REPORTING_MAX_PAGES 16 +#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 1) +#define PAGE_REPORTING_MAX_PAGES 32
page_reporting.cchange:(quoted diff) +3
-1@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf, /* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue;Quoted 8 lines
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 2 lines
(quoted diff) +1
-0+ }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.
Quoted 3 lines
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
If nothing else you might look at seeing if you can split up the structures so that the bitmap and nr_bits is in a different region somewhere since those are read-mostly values.
Also you are now updating the bitmap and free_pages both inside and outside of the zone lock so that will likely have some impact.
Quoted 10 lines
Quoted 7 lines
Quoted 6 lines
(quoted diff) +0
-0@Alexander in case you decide to give it a try and find different results,please do let me know.
If I have some free time I will take a look.
That would be great, thanks.
Quoted 7 lines
Quoted 5 lines
However one thing that
concerns me about this change is that it will limit things much further in terms of how much memory can ultimately be freed since you are now only working with the highest order page and that becomes a hard requirement for your design.I would assume that should be resolved with (
pageblock_order- 1).
There is no need for the - 1. The pageblock_order value is the lowest you can go before you start causing THP to be disabled. If you cross that threshold the performance will drop significantly.
Quoted 25 lines · Alexander Duyck
Quoted 24 lines · Nitesh Narayan Lal
Quoted 3 lines · Alexander Duyck
Quoted 2 lines · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
[...]
Quoted 19 lines
Quoted 7 lines
You don't have to, I can fix the issues in my patch-set. :)
Quoted 2 lines
Sounds good. Hopefully the stuff I pointed out above helps you to get a reproduction and resolve the issues.
So I did observe a significant drop in running my v12 path-set [1] with the suggested test setup. However, on making certain changes the performance improved significantly.
Quoted 6 lines
I used my v12 patch-set which I have posted earlier and made the following changes:
1. Started reporting only (MAX_ORDER- 1) pages and increased the number of pages that can be reported at a time to 32 from 16. The intent of making these changes was to bring my configuration closer to what Alexander is using.The increase from 16 to 32 is valid. No point in working in too small of batches. However tightening the order to only test for
MAX_ORDER- 1 seems like a step in the wrong direction. The bitmap approach doesn't have much value if it can only work with the highest order page. I realize it is probably necessary in order to make the trick for checking onpage_buddywork, but it seems very limiting.
Quoted 7 lines
Quoted 4 lines
If using (
pageblock_order- 1) is a better way to do this, then I can probably switch to that.
I will agree with the fact that we have to make the reporting order configurable, atleast to an extent.I think you mean
pageblock_order, notpageblock_order- 1. The problem withpageblock_order- 1 is that it will have a negative impact on performance as it would disable THP.
Ah, I see. Yes my bad.
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Quoted 3 lines
2. I made an additional change in my bitmap scanning logic to prevent acquiring spinlock if the page is already allocated.
Again, not a fan. It basically means you can only work with
MAX_ORDER- 1 and there will be no ability to work with anything smaller.Quoted 10 lines
Setup:
On a 16 vCPU 30 GB single NUMA guest affined to a single host NUMA, I ran the modified will-it-scale/page_fault number of times and calculated the average of the number of process and threads launched on the 16th core to compare the impact of my patch-set against an unmodified kernel.Conclusion:
%Drop in number of processes launched on 16th vCPU = 1-2%
%Drop in number of threads launched on 16th vCPU = 5-6%These numbers don't make that much sense to me. Are you talking about a fully functioning setup that is madvsing away the memory in the hypervisor?
Quoted 8 lines
Quoted 6 lines
Without making this change I was observing a significant amount of drop in the number of processes and specifically in the number of threads. I did a double-check of the configuration which I have shared.
I was also observing the "AnonHugePages" via meminfo to check the THP usage. Any more suggestions about what else I can do to verify?
I will be more than happy to try them out.So what was the size of your guest? One thing that just occurred to me is that you might be running a much smaller guest than I was.
I am running a 30 GB guest.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
If so I would have expected a much higher difference versus
baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.
Quoted 7 lines
Quoted 2 lines
Right now I have a different host-kernel. I can install the same kernel to the host as well and see if that changes anything.
The host kernel will have a fairly significant impact as I recall. For example running a stock CentOS kernel lowered the performance compared to running a linux-next kernel. As a result the numbers looked better since the overall baseline was lower to begin with as the host OS was introducing additional overhead.
I see in that case I will try by installing the same guest kernel to the host as well.
Quoted 65 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Other observations:
- I also tried running Alexander's latest v11 page-reporting patch set and observe a similar amount of average degradation in the number of processes and threads.
- I didn't include the linear component recorded by will-it-scale because for some reason it was fluctuating too much even when I was using an unmodified kernel. If required I can investigate this further.Quoted 4 lines
Quoted 3 lines
Quoted 2 lines
Note: If there is a better way to analyze the will-it-scale/page_fault results then please do let me know.
Honestly I have mostly just focused on the processes performance.
In my observation processes seems to be most consistent in general.
Agreed.
Quoted 4 lines
Quoted 3 lines
There is
usually a fair bit of variability but a pattern forms after a few runs so you can generally tell if a configuration is an improvement or not.Yeah, that's why I thought of taking the average of 5-6 runs.
Same here. I am usually running about 5 iterations.
Quoted 44 lines
Quoted 44 lines
Quoted 7 lines
Other setup details:
Following are the configurations which I enabled to run my tests:
- Enabled:CONFIG_SLAB_FREELIST_RANDOM&CONFIG_SHUFFLE_PAGE_ALLOCATOR
- Set host THP to always
- Set guest THP to madvise
- Added the suggested madvise call inpage_faultsource code. @Alexander please let me know if I missed something.This seems about right.
Quoted 19 lines
The current state of my v13:
I still have to look into Michal's suggestion of using page-isolation API's instead of isolating the page. However, I believe at this moment our objective is to decide with which approach we can proceed and that's why I decided to post the numbers by making small required changes in v12 instead of posting a new series.Following are the changes which I have made on top of my v12:
page_reporting.hchange:(quoted diff) +2
-2-#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 2) -#define PAGE_REPORTING_MAX_PAGES 16 +#define PAGE_REPORTING_MIN_ORDER (MAX_ORDER - 1) +#define PAGE_REPORTING_MAX_PAGES 32
page_reporting.cchange:(quoted diff) +0
-0@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf,Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 10 lines
(quoted diff) +4
-1/* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue; + }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.
Quoted 6 lines
Quoted 3 lines
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
If nothing else you might look at seeing if you can split up the structures so that the bitmap and
nr_bitsis in a different region somewhere since those are read-mostly values.
ok, I will try to understand the issue and your suggestion. Thank you for bringing this up.
Quoted 2 lines
Also you are now updating the bitmap and
free_pagesboth inside and outside of the zone lock so that will likely have some impact.
So as per your previous suggestion, I have made the bitmap structure object as a rcu protected pointer. So we are safe from that side. The other downside which I can think of is a race where one page trying to increment free_pages and other trying to decrements it. However, being an atomic variable that should not be a problem. Did I miss anything?
Quoted 15 lines
Quoted 15 lines
Quoted 8 lines
Quoted 7 lines
(quoted diff) +0
-0@Alexander in case you decide to give it a try and find different results,please do let me know.
If I have some free time I will take a look.
That would be great, thanks.
Quoted 5 lines
However one thing that
concerns me about this change is that it will limit things much further in terms of how much memory can ultimately be freed since you are now only working with the highest order page and that becomes a hard requirement for your design.
Quoted 4 lines
Quoted 1 line
I would assume that should be resolved with (
pageblock_order- 1).There is no need for the - 1. The
pageblock_ordervalue is the lowest you can go before you start causing THP to be disabled. If you cross that threshold the performance will drop significantly.
Makes sense.
--
Nitesh
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 7 lines · Nitesh Narayan Lal
Quoted 4 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
<snip>
Quoted 32 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 13 lines
page_reporting.cchange:(quoted diff) +4
-1@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf, /* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue; + }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.Quoted 6 lines
Quoted 3 lines
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
If nothing else you might look at seeing if you can split up the structures so that the bitmap and
nr_bitsis in a different region somewhere since those are read-mostly values.ok, I will try to understand the issue and your suggestion. Thank you for bringing this up.
Quoted 2 lines
Also you are now updating the bitmap and
free_pagesboth inside and outside of the zone lock so that will likely have some impact.
Quoted 6 lines
So as per your previous suggestion, I have made the bitmap structure object as a rcu protected pointer. So we are safe from that side. The other downside which I can think of is a race where one page trying to increment
free_pagesand other trying to decrements it. However, being an atomic variable that should not be a problem. Did I miss anything?
I'm not so much worried about a race as the cache line bouncing effect. Basically your notifier combined within this hinting thread will likely result in more time spent by the thread that holds the lock since it will be trying to access the bitmap to set the bit and the free_pages to report the bit, but at the same time you will have this thread clearing bits and decrementing the free_pages values.
One thing you could consider in your worker thread would be to do reallocate and replace the bitmap every time you plan to walk it. By doing that you would avoid the cacheline bouncing on the bitmap since you would only have to read it, and you would no longer have another thread dirtying it. You could essentially reset the free_pages at the same time you replace the bitmap. It would need to all happen with the zone lock held though when you swap it out.
- Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 52 lines · Alexander Duyck
Quoted 6 lines · Nitesh Narayan Lal
Quoted 4 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
<snip>
Quoted 28 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 13 lines
page_reporting.cchange:(quoted diff) +4
-1@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf, /* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue; + }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.Quoted 6 lines
Quoted 3 lines
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
If nothing else you might look at seeing if you can split up the structures so that the bitmap and
nr_bitsis in a different region somewhere since those are read-mostly values.ok, I will try to understand the issue and your suggestion. Thank you for bringing this up.
Quoted 8 lines
Quoted 2 lines
Also you are now updating the bitmap and
free_pagesboth inside and outside of the zone lock so that will likely have some impact.So as per your previous suggestion, I have made the bitmap structure object as a rcu protected pointer. So we are safe from that side. The other downside which I can think of is a race where one page trying to increment
free_pagesand other trying to decrements it. However, being an atomic variable that should not be a problem. Did I miss anything?I'm not so much worried about a race as the cache line bouncing effect. Basically your notifier combined within this hinting thread will likely result in more time spent by the thread that holds the lock since it will be trying to access the bitmap to set the bit and the
free_pagesto report the bit, but at the same time you will have this thread clearing bits and decrementing thefree_pagesvalues.
Quoted 7 lines
One thing you could consider in your worker thread would be to do reallocate and replace the bitmap every time you plan to walk it. By doing that you would avoid the cacheline bouncing on the bitmap since you would only have to read it, and you would no longer have another thread dirtying it. You could essentially reset the
free_pagesat the same time you replace the bitmap. It would need to all happen with the zone lock held though when you swap it out.
If I am not mistaken then from what you are suggesting, I will have to hold the zone lock for the entire duration of swap & scan which would be costly if the bitmap is large, isn't? Also, we might end up missing free pages that are getting
freed while we are scanning.
As far as free_pages count is concerned, I am thinking if I should replace it with zone->free_area[REPORTING_ORDER].nr_free which is already there (I still need to explore this in a bit more depth).
Quoted 2 lines
- Alex
Signature · 2 lines
Thanks Nitesh
Quoted 60 lines · Nitesh Narayan Lal
Quoted 51 lines · Alexander Duyck
Quoted 5 lines · Nitesh Narayan Lal
Quoted 4 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
<snip>
Quoted 28 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 13 lines
page_reporting.cchange:(quoted diff) +4
-1@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf, /* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue; + }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.Quoted 6 lines
Quoted 3 lines
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
If nothing else you might look at seeing if you can split up the structures so that the bitmap and
nr_bitsis in a different region somewhere since those are read-mostly values.ok, I will try to understand the issue and your suggestion. Thank you for bringing this up.
Quoted 8 lines
Quoted 2 lines
Also you are now updating the bitmap and
free_pagesboth inside and outside of the zone lock so that will likely have some impact.So as per your previous suggestion, I have made the bitmap structure object as a rcu protected pointer. So we are safe from that side. The other downside which I can think of is a race where one page trying to increment
free_pagesand other trying to decrements it. However, being an atomic variable that should not be a problem. Did I miss anything?I'm not so much worried about a race as the cache line bouncing effect. Basically your notifier combined within this hinting thread will likely result in more time spent by the thread that holds the lock since it will be trying to access the bitmap to set the bit and the
free_pagesto report the bit, but at the same time you will have this thread clearing bits and decrementing thefree_pagesvalues.Quoted 7 lines
One thing you could consider in your worker thread would be to do reallocate and replace the bitmap every time you plan to walk it. By doing that you would avoid the cacheline bouncing on the bitmap since you would only have to read it, and you would no longer have another thread dirtying it. You could essentially reset the
free_pagesat the same time you replace the bitmap. It would need to all happen with the zone lock held though when you swap it out.
Quoted 5 lines
If I am not mistaken then from what you are suggesting, I will have to hold the zone lock for the entire duration of swap & scan which would be costly if the bitmap is large, isn't? Also, we might end up missing free pages that are getting
freed while we are scanning.
You would only need to hold the zone lock when you swap the bitmap. Once it is swapped you wouldn't need to worry about the locking again for bitmap access since your worker thread would be the only one holding the current bitmap. Think of it as a batch clearing of the bits.
You already end up missing pages freed while scanning since you are doing it linearly.
Quoted 5 lines
As far as
free_pagescount is concerned, I am thinking if I should replace it with zone->free_area[REPORTING_ORDER].nr_free which is already there (I still need to explore this in a bit more depth).Quoted 1 line
- Alex
So there ends up being two ways you could use nr_free. One is to track it the way I did with the number of reported pages being tracked, however that requires reducing the count when reported pages are pulled from the free_area and identifying reported pages vs unreported ones.
The other option would be to look at converting nr_free into a pair of free running counters, one tracking frees, and another tracking allocations. Then you just need to record a snapshot of the nr_free values when you do something like the bitmap swap, and then you would be able to track churn, but it wouldn't give you an exact count of unreported pages since it is possible to just alloc/free a single page multiple times to make it look like you have freed a number of pages even though you really haven't.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 65 lines · Alexander Duyck
Quoted 59 lines · Nitesh Narayan Lal
Quoted 51 lines · Alexander Duyck
Quoted 5 lines · Nitesh Narayan Lal
Quoted 4 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
<snip>
Quoted 28 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 13 lines
page_reporting.cchange:(quoted diff) +4
-1@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf, /* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue; + }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.Quoted 6 lines
Quoted 3 lines
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
If nothing else you might look at seeing if you can split up the structures so that the bitmap and
nr_bitsis in a different region somewhere since those are read-mostly values.ok, I will try to understand the issue and your suggestion. Thank you for bringing this up.
Quoted 8 lines
Quoted 2 lines
Also you are now updating the bitmap and
free_pagesboth inside and outside of the zone lock so that will likely have some impact.So as per your previous suggestion, I have made the bitmap structure object as a rcu protected pointer. So we are safe from that side. The other downside which I can think of is a race where one page trying to increment
free_pagesand other trying to decrements it. However, being an atomic variable that should not be a problem. Did I miss anything?I'm not so much worried about a race as the cache line bouncing effect. Basically your notifier combined within this hinting thread will likely result in more time spent by the thread that holds the lock since it will be trying to access the bitmap to set the bit and the
free_pagesto report the bit, but at the same time you will have this thread clearing bits and decrementing thefree_pagesvalues.Quoted 7 lines
One thing you could consider in your worker thread would be to do reallocate and replace the bitmap every time you plan to walk it. By doing that you would avoid the cacheline bouncing on the bitmap since you would only have to read it, and you would no longer have another thread dirtying it. You could essentially reset the
free_pagesat the same time you replace the bitmap. It would need to all happen with the zone lock held though when you swap it out.Quoted 5 lines
If I am not mistaken then from what you are suggesting, I will have to hold the zone lock for the entire duration of swap & scan which would be costly if the bitmap is large, isn't? Also, we might end up missing free pages that are getting
freed while we are scanning.
Quoted 4 lines
You would only need to hold the zone lock when you swap the bitmap. Once it is swapped you wouldn't need to worry about the locking again for bitmap access since your worker thread would be the only one holding the current bitmap. Think of it as a batch clearing of the bits.
I see.
Quoted 3 lines
You already end up missing pages freed while scanning since you are doing it linearly.
I was referring to free pages for whom bits will not be set while we are doing the batch clearing of the bits.
Quoted 11 lines
Quoted 6 lines
As far as
free_pagescount is concerned, I am thinking if I should replace it with zone->free_area[REPORTING_ORDER].nr_free which is already there (I still need to explore this in a bit more depth).Quoted 1 line
- Alex
So there ends up being two ways you could use
nr_free. One is to track it the way I did with the number of reported pages being tracked, however that requires reducing the count when reported pages are pulled from thefree_areaand identifying reported pages vs unreported ones.
Quoted 8 lines
The other option would be to look at converting
nr_freeinto a pair of free running counters, one tracking frees, and another tracking allocations. Then you just need to record a snapshot of thenr_freevalues when you do something like the bitmap swap, and then you would be able to track churn, but it wouldn't give you an exact count of unreported pages since it is possible to just alloc/free a single page multiple times to make it look like you have freed a number of pages even though you really haven't.
Yeah possibly. I will think about it a little bit more to see what is the best way to do it.
Signature · 7 lines
Thanks Nitesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 71 lines · Nitesh Narayan Lal
Quoted 65 lines · Alexander Duyck
Quoted 59 lines · Nitesh Narayan Lal
Quoted 51 lines · Alexander Duyck
Quoted 5 lines · Nitesh Narayan Lal
Quoted 4 lines · Alexander Duyck
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · Nitesh Narayan Lal
On 10/2/19 10:25 AM, Alexander Duyck wrote:
<snip>
Quoted 28 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Review static void scan_zone_bitmap(struct page_reporting_config · line 110
Quoted 13 lines
page_reporting.cchange:(quoted diff) +4
-1@@ -101,8 +101,12 @@ static void scan_zone_bitmap(struct page_reporting_config *phconf, /* Process only if the page is still online */ page = pfn_to_online_page((setbit << PAGE_REPORTING_MIN_ORDER) + zone->base_pfn); - if (!page) + if (!page || !PageBuddy(page)) { + clear_bit(setbit, zone->bitmap); + atomic_dec(&zone->free_pages); continue; + }I suspect the
zone->free_pagesis going to be expensive for you to deal with. It is a global atomic value and is going to have the cacheline bouncing that it is contained in. As a result thinks like setting the bitmap with be more expensive as every tome a CPU incrementsfree_pagesit will likely have to take the cache line containing the bitmap pointer as well.Quoted 6 lines
Quoted 3 lines
I see I will have to explore this more. I am wondering if there is a way to measure this If its effect is not visible in will-it-scale/page_fault1. If there is a noticeable amount of degradation, I will have to address this.
If nothing else you might look at seeing if you can split up the structures so that the bitmap and
nr_bitsis in a different region somewhere since those are read-mostly values.ok, I will try to understand the issue and your suggestion. Thank you for bringing this up.
Quoted 8 lines
Quoted 2 lines
Also you are now updating the bitmap and
free_pagesboth inside and outside of the zone lock so that will likely have some impact.So as per your previous suggestion, I have made the bitmap structure object as a rcu protected pointer. So we are safe from that side. The other downside which I can think of is a race where one page trying to increment
free_pagesand other trying to decrements it. However, being an atomic variable that should not be a problem. Did I miss anything?I'm not so much worried about a race as the cache line bouncing effect. Basically your notifier combined within this hinting thread will likely result in more time spent by the thread that holds the lock since it will be trying to access the bitmap to set the bit and the
free_pagesto report the bit, but at the same time you will have this thread clearing bits and decrementing thefree_pagesvalues.Quoted 7 lines
One thing you could consider in your worker thread would be to do reallocate and replace the bitmap every time you plan to walk it. By doing that you would avoid the cacheline bouncing on the bitmap since you would only have to read it, and you would no longer have another thread dirtying it. You could essentially reset the
free_pagesat the same time you replace the bitmap. It would need to all happen with the zone lock held though when you swap it out.Quoted 5 lines
If I am not mistaken then from what you are suggesting, I will have to hold the zone lock for the entire duration of swap & scan which would be costly if the bitmap is large, isn't? Also, we might end up missing free pages that are getting
freed while we are scanning.Quoted 4 lines
You would only need to hold the zone lock when you swap the bitmap. Once it is swapped you wouldn't need to worry about the locking again for bitmap access since your worker thread would be the only one holding the current bitmap. Think of it as a batch clearing of the bits.
Quoted 7 lines
I see.
Quoted 2 lines
You already end up missing pages freed while scanning since you are doing it linearly.
I was referring to free pages for whom bits will not be set while we are doing the batch clearing of the bits.
I think you missed the point. Your notifier is only setting bits while holding the zone lock anyway. So if you do the swap while holding the zone lock then you will miss nothing. An added advantage is that you could switch over to a non-atomic __set_bit instead of having to do atomic set and clear operations.
Thanks.
- Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
On 10/7/19 1:06 PM, Nitesh Narayan Lal wrote:
[...]
Quoted 12 lines
Quoted 2 lines
So what was the size of your guest? One thing that just occurred to me is that you might be running a much smaller guest than I was.
I am running a 30 GB guest.
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
If so I would have expected a much higher difference versus
baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.Right now I have a different host-kernel. I can install the same kernel to the host as well and see if that changes anything.
Quoted 7 lines
Quoted 5 lines
The host kernel will have a fairly significant impact as I recall. For example running a stock CentOS kernel lowered the performance compared to running a linux-next kernel. As a result the numbers looked better since the overall baseline was lower to begin with as the host OS was introducing additional overhead.
I see in that case I will try by installing the same guest kernel to the host as well.
As per your suggestion, I tried replacing the host kernel with an upstream kernel without my patches i.e., my host has a kernel built on top of the upstream kernel's master branch which has Sept 23rd commit and the guest has the same kernel for the no-hinting case and same kernel + my patches for the page reporting case.
With the changes reported earlier on top of v12, I am not seeing any further degradation (other than what I have previously reported).
To be sure that THP is actively used, I did an experiment where I changed the MEMSIZE in the page_fault. On doing so THP usage checked via /proc/meminfo also increased as I expected.
In any case, if you find something else please let me know and I will look into it again.
I am still looking into your suggestion about cache line bouncing and will reply to it, if I have more questions.
[...]
Signature · 7 lines
Thanks Nitesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Quoted 39 lines · Nitesh Narayan Lal
On 10/7/19 1:06 PM, Nitesh Narayan Lal wrote:
[...]Quoted 12 lines
Quoted 2 lines
So what was the size of your guest? One thing that just occurred to me is that you might be running a much smaller guest than I was.
I am running a 30 GB guest.
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
If so I would have expected a much higher difference versus
baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.Right now I have a different host-kernel. I can install the same kernel to the host as well and see if that changes anything.
Quoted 7 lines
Quoted 5 lines
The host kernel will have a fairly significant impact as I recall. For example running a stock CentOS kernel lowered the performance compared to running a linux-next kernel. As a result the numbers looked better since the overall baseline was lower to begin with as the host OS was introducing additional overhead.
I see in that case I will try by installing the same guest kernel to the host as well.
As per your suggestion, I tried replacing the host kernel with an upstream kernel without my patches i.e., my host has a kernel built on top of the upstream kernel's master branch which has Sept 23rd commit and the guest has the same kernel for the no-hinting case and same kernel + my patches for the page reporting case.
With the changes reported earlier on top of v12, I am not seeing any further degradation (other than what I have previously reported).
To be sure that THP is actively used, I did an experiment where I changed the MEMSIZE in the
page_fault. On doing so THP usage checked via/proc/meminfoalso increased as I expected.In any case, if you find something else please let me know and I will look into it again.
Quoted 5 lines
I am still looking into your suggestion about cache line bouncing and will reply to it, if I have more questions.
[...]
I really feel like this discussion has gone off course. The idea here is to review this patch set[1] and provide working alternatives if there are issues with the current approach.
The bitmap based approach still has a number of outstanding issues including sparse memory and hotplug which have yet to be addressed. We can gloss over that, but there is a good chance that resolving those would have potential performance implications. With this most recent change there is now also the fact that it can only really support reporting at one page order so the solution is now much more prone to issues with memory fragmentation than it was before. I would consider the fact that my solution works with multiple page orders while the bitmap approach requires MAX_ORDER - 1 seems like another obvious win for my solution. Until we can get back to the point where we are comparing apples to apples I would prefer not to benchmark the bitmap solution as without the extra order limitation it was over 20% worse then my solution performance wise.
Ideally I would like to get code review for patches 3 and 4, and spend my time addressing issues reported there. The main things I need input on is if the solution of allowing the list iterators to be reset is good enough to address the compaction issues that were pointed out several releases ago or if I have to look for another solution. Also I have changed things so that page_reporting.h was split over two files with the new one now living in the mm/ folder. By doing that I was hoping to reduce the exposure of the internal state of the free-lists so that essentially all we end up providing is an interface for the notifier to be used by virtio- balloon.
Thanks.
- Alex
Quoted 39 lines · Alexander Duyck
Quoted 38 lines · Nitesh Narayan Lal
On 10/7/19 1:06 PM, Nitesh Narayan Lal wrote:
[...]Quoted 12 lines
Quoted 2 lines
So what was the size of your guest? One thing that just occurred to me is that you might be running a much smaller guest than I was.
I am running a 30 GB guest.
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
If so I would have expected a much higher difference versus
baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.Right now I have a different host-kernel. I can install the same kernel to the host as well and see if that changes anything.
Quoted 7 lines
Quoted 5 lines
The host kernel will have a fairly significant impact as I recall. For example running a stock CentOS kernel lowered the performance compared to running a linux-next kernel. As a result the numbers looked better since the overall baseline was lower to begin with as the host OS was introducing additional overhead.
I see in that case I will try by installing the same guest kernel to the host as well.
As per your suggestion, I tried replacing the host kernel with an upstream kernel without my patches i.e., my host has a kernel built on top of the upstream kernel's master branch which has Sept 23rd commit and the guest has the same kernel for the no-hinting case and same kernel + my patches for the page reporting case.
With the changes reported earlier on top of v12, I am not seeing any further degradation (other than what I have previously reported).
To be sure that THP is actively used, I did an experiment where I changed the MEMSIZE in the
page_fault. On doing so THP usage checked via/proc/meminfoalso increased as I expected.In any case, if you find something else please let me know and I will look into it again.
Quoted 8 lines
Quoted 5 lines
I am still looking into your suggestion about cache line bouncing and will reply to it, if I have more questions.
[...]
I really feel like this discussion has gone off course. The idea here is to review this patch set[1] and provide working alternatives if there are issues with the current approach.
Agreed.
Quoted 3 lines
The bitmap based approach still has a number of outstanding issues including sparse memory and hotplug which have yet to be addressed.
True, but I don't think those two are a blocker.
For sparse zone as we are maintaining the bitmap on a granularity of (MAX_ORDER - 2) / (MAX_ORDER - 1) etc. the memory wastage should be negligible in most of the cases.
For memory hotplug/hotremove, I did make sure that I don't break anything. Even if a user starts using this feature with page-reporting enabled. However, it is true that I don't report or capture any memory added/removed thought it.
Fixing these issues will be an optimization which I will do as I get my basic framework ready and in shape.
Quoted 8 lines
We can
gloss over that, but there is a good chance that resolving those would have potential performance implications. With this most recent change there is now also the fact that it can only really support reporting at one page order so the solution is now much more prone to issues with memory fragmentation than it was before. I would consider the fact that my solution works with multiple page orders while the bitmap approach requiresMAX_ORDER- 1 seems like another obvious win for my solution.
This is just a configuration change and only requires to update the macro 'PAGE_REPORTING_MIN_ORDER' to what you are using.
What order do we want to report could vary based on the use case where we are deploying the solution.
Ideally, this should be configurable maybe at the compile time or we can stick with pageblock_order which is originally suggested and used by you.
Quoted 3 lines
Until we can get back to the point where we are comparing apples to apples I would prefer not to benchmark the bitmap solution as without the extra order limitation it was over 20% worse then my solution performance wise..
Understood.
However, as I reported previously after making the configuration changes on top of v12 posting, I don't see the degradation.
I will be happy to try out more suggestions to see if the issue is really fixed.
I have started looking into your concern of cacheline bouncing after which I will look into Michal's suggestion of using page-isolation APIs to isolate and release pages back. After that, I can decide on posting my next series (if it is required).
Quoted 11 lines
Ideally I would like to get code review for patches 3 and 4, and spend my time addressing issues reported there. The main things I need input on is if the solution of allowing the list iterators to be reset is good enough to address the compaction issues that were pointed out several releases ago or if I have to look for another solution. Also I have changed things so that
page_reporting.hwas split over two files with the new one now living in themm/folder. By doing that I was hoping to reduce the exposure of the internal state of the free-lists so that essentially all we end up providing is an interface for the notifier to be used by virtio- balloon.
If everyone agrees that what you are proposing is the best way to move forward then, by all means, lets go ahead with it. :)
Quoted 7 lines
Thanks.
- Alex
Signature · 2 lines
Thanks Nitesh
Quoted 117 lines · Nitesh Narayan Lal
Quoted 39 lines · Alexander Duyck
Quoted 38 lines · Nitesh Narayan Lal
On 10/7/19 1:06 PM, Nitesh Narayan Lal wrote:
[...]Quoted 12 lines
Quoted 2 lines
So what was the size of your guest? One thing that just occurred to me is that you might be running a much smaller guest than I was.
I am running a 30 GB guest.
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
If so I would have expected a much higher difference versus
baseline as zeroing/faulting the pages in the host gets expensive fairly quick. What is the host kernel you are running your test on? I'm just wondering if there is some additional overhead currently limiting your setup. My host kernel was just the same kernel I was running in the guest, just built without the patches applied.Right now I have a different host-kernel. I can install the same kernel to the host as well and see if that changes anything.
Quoted 7 lines
Quoted 5 lines
The host kernel will have a fairly significant impact as I recall. For example running a stock CentOS kernel lowered the performance compared to running a linux-next kernel. As a result the numbers looked better since the overall baseline was lower to begin with as the host OS was introducing additional overhead.
I see in that case I will try by installing the same guest kernel to the host as well.
As per your suggestion, I tried replacing the host kernel with an upstream kernel without my patches i.e., my host has a kernel built on top of the upstream kernel's master branch which has Sept 23rd commit and the guest has the same kernel for the no-hinting case and same kernel + my patches for the page reporting case.
With the changes reported earlier on top of v12, I am not seeing any further degradation (other than what I have previously reported).
To be sure that THP is actively used, I did an experiment where I changed the MEMSIZE in the
page_fault. On doing so THP usage checked via/proc/meminfoalso increased as I expected.In any case, if you find something else please let me know and I will look into it again.
Quoted 8 lines
Quoted 5 lines
I am still looking into your suggestion about cache line bouncing and will reply to it, if I have more questions.
[...]
I really feel like this discussion has gone off course. The idea here is to review this patch set[1] and provide working alternatives if there are issues with the current approach.
Agreed.
Quoted 3 lines
The bitmap based approach still has a number of outstanding issues including sparse memory and hotplug which have yet to be addressed.
True, but I don't think those two are a blocker.
For sparse zone as we are maintaining the bitmap on a granularity of (
MAX_ORDER- 2) / (MAX_ORDER- 1) etc. the memory wastage should be negligible in most of the cases.For memory hotplug/hotremove, I did make sure that I don't break anything. Even if a user starts using this feature with page-reporting enabled. However, it is true that I don't report or capture any memory added/removed thought it.
Fixing these issues will be an optimization which I will do as I get my basic framework ready and in shape.
Quoted 8 lines
We can
gloss over that, but there is a good chance that resolving those would have potential performance implications. With this most recent change there is now also the fact that it can only really support reporting at one page order so the solution is now much more prone to issues with memory fragmentation than it was before. I would consider the fact that my solution works with multiple page orders while the bitmap approach requiresMAX_ORDER- 1 seems like another obvious win for my solution.This is just a configuration change and only requires to update the macro '
PAGE_REPORTING_MIN_ORDER' to what you are using.What order do we want to report could vary based on the use case where we are deploying the solution.
Ideally, this should be configurable maybe at the compile time or we can stick with
pageblock_orderwhich is originally suggested and used by you.Quoted 3 lines
Until we can get back to the point where we are comparing apples to apples I would prefer not to benchmark the bitmap solution as without the extra order limitation it was over 20% worse then my solution performance wise..
Understood.
However, as I reported previously after making the configuration changes on top of v12 posting, I don't see the degradation.I will be happy to try out more suggestions to see if the issue is really fixed.
I have started looking into your concern of cacheline bouncing after which I will look into Michal's suggestion of using page-isolation APIs to isolate and release pages back. After that, I can decide on posting my next series (if it is required).
Quoted 11 lines
Ideally I would like to get code review for patches 3 and 4, and spend my time addressing issues reported there. The main things I need input on is if the solution of allowing the list iterators to be reset is good enough to address the compaction issues that were pointed out several releases ago or if I have to look for another solution. Also I have changed things so that
page_reporting.hwas split over two files with the new one now living in themm/folder. By doing that I was hoping to reduce the exposure of the internal state of the free-lists so that essentially all we end up providing is an interface for the notifier to be used by virtio- balloon.
Quoted 3 lines
If everyone agrees that what you are proposing is the best way to move forward then, by all means, lets go ahead with it. :)
Sorry, i didn't get to follow the discussion, caught a cold and my body is still fighting with the last resistance.
Is there any rough summary on how much faster Alexanders approach is compared to some external tracking? For external tracking, there is a lot of optimization potential as far as I can read, however, I think a rough summary should be possible by now "how far we are off".
Also, are there benchmarks/setups where both perform the same?
Signature · 3 lines
Thanks, David / dhildenb
Quoted 4 lines · David Hildenbrand
Quoted 3 lines · Nitesh Narayan Lal
Quoted 2 lines · Alexander Duyck
Quoted 1 line · Nitesh Narayan Lal
On 10/7/19 1:06 PM, Nitesh Narayan Lal wrote:
[...]
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
Ideally I would like to get code review for patches 3 and 4, and spend my time addressing issues reported there. The main things I need input on is if the solution of allowing the list iterators to be reset is good enough to address the compaction issues that were pointed out several releases ago or if I have to look for another solution. Also I have changed things so that
page_reporting.hwas split over two files with the new one now living in themm/folder. By doing that I was hoping to reduce the exposure of the internal state of the free-lists so that essentially all we end up providing is an interface for the notifier to be used by virtio- balloon.
Quoted 5 lines
Quoted 3 lines
If everyone agrees that what you are proposing is the best way to move forward then, by all means, lets go ahead with it. :)
Sorry, i didn't get to follow the discussion, caught a cold and my body is still fighting with the last resistance.
I hope you feel better soon.
Quoted 7 lines
Is there any rough summary on how much faster Alexanders approach is compared to some external tracking? For external tracking, there is a lot of optimization potential as far as I can read, however, I think a rough summary should be possible by now "how far we are off".
Also, are there benchmarks/setups where both perform the same?
So I tried to follow up on the suggestion provided by Alexander to recreate his setup and with the posted v12, I did observe a drop in will-it-scale/page_fault. Specifically in the number of threads that were launched on the nth core.
However, I did not see that degradation after making the changes which I suggested previously on top of v12.
After those changes as per my observation, both series are introducing more or less the same amount of degradation over an unmodified kernel.
In any case, if there are more suggestions, I am open to performing more experiments to ensure that there is no further degradation with my series.
Signature · 2 lines
Thanks Nitesh