Training courses

Kernel and Embedded Linux

Bootlin training courses

Embedded Linux, kernel,
Yocto Project, Buildroot, real-time,
graphics, boot time, debugging...

Bootlin logo

Elixir Cross Referencer

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
# SPDX-License-Identifier: GPL-2.0-only

menu "Memory Management options"

config CONFIG_SELECT_MEMORY_MODEL
	def_bool y
	depends on CONFIG_ARCH_SELECT_MEMORY_MODEL

choice
	prompt "Memory model"
	depends on CONFIG_SELECT_MEMORY_MODEL
	default CONFIG_DISCONTIGMEM_MANUAL if CONFIG_ARCH_DISCONTIGMEM_DEFAULT
	default CONFIG_SPARSEMEM_MANUAL if CONFIG_ARCH_SPARSEMEM_DEFAULT
	default CONFIG_FLATMEM_MANUAL
	help
	  This option allows you to change some of the ways that
	  Linux manages its memory internally. Most users will
	  only have one option here selected by the architecture
	  configuration. This is normal.

config CONFIG_FLATMEM_MANUAL
	bool "Flat Memory"
	depends on !(CONFIG_ARCH_DISCONTIGMEM_ENABLE || CONFIG_ARCH_SPARSEMEM_ENABLE) || CONFIG_ARCH_FLATMEM_ENABLE
	help
	  This option is best suited for non-CONFIG_NUMA systems with
	  flat address space. The CONFIG_FLATMEM is the most efficient
	  system in terms of performance and resource consumption
	  and it is the best option for smaller systems.

	  For systems that have holes in their physical address
	  spaces and for features like CONFIG_NUMA and memory hotplug,
	  choose "Sparse Memory"

	  If unsure, choose this option (Flat Memory) over any other.

config CONFIG_DISCONTIGMEM_MANUAL
	bool "Discontiguous Memory"
	depends on CONFIG_ARCH_DISCONTIGMEM_ENABLE
	help
	  This option provides enhanced support for discontiguous
	  memory systems, over CONFIG_FLATMEM.  These systems have holes
	  in their physical address spaces, and this option provides
	  more efficient handling of these holes.

	  Although "Discontiguous Memory" is still used by several
	  architectures, it is considered deprecated in favor of
	  "Sparse Memory".

	  If unsure, choose "Sparse Memory" over this option.

config CONFIG_SPARSEMEM_MANUAL
	bool "Sparse Memory"
	depends on CONFIG_ARCH_SPARSEMEM_ENABLE
	help
	  This will be the only option for some systems, including
	  memory hot-plug systems.  This is normal.

	  This option provides efficient support for systems with
	  holes is their physical address space and allows memory
	  hot-plug and hot-remove.

	  If unsure, choose "Flat Memory" over this option.

endchoice

config CONFIG_DISCONTIGMEM
	def_bool y
	depends on (!CONFIG_SELECT_MEMORY_MODEL && CONFIG_ARCH_DISCONTIGMEM_ENABLE) || CONFIG_DISCONTIGMEM_MANUAL

config CONFIG_SPARSEMEM
	def_bool y
	depends on (!CONFIG_SELECT_MEMORY_MODEL && CONFIG_ARCH_SPARSEMEM_ENABLE) || CONFIG_SPARSEMEM_MANUAL

config CONFIG_FLATMEM
	def_bool y
	depends on (!CONFIG_DISCONTIGMEM && !CONFIG_SPARSEMEM) || CONFIG_FLATMEM_MANUAL

config CONFIG_FLAT_NODE_MEM_MAP
	def_bool y
	depends on !CONFIG_SPARSEMEM

#
# Both the CONFIG_NUMA code and CONFIG_DISCONTIGMEM use arrays of pg_data_t's
# to represent different areas of memory.  This variable allows
# those dependencies to exist individually.
#
config CONFIG_NEED_MULTIPLE_NODES
	def_bool y
	depends on CONFIG_DISCONTIGMEM || CONFIG_NUMA

config CONFIG_HAVE_MEMORY_PRESENT
	def_bool y
	depends on CONFIG_ARCH_HAVE_MEMORY_PRESENT || CONFIG_SPARSEMEM

#
# CONFIG_SPARSEMEM_EXTREME (which is the default) does some bootmem
# allocations when memory_present() is called.  If this cannot
# be done on your architecture, select this option.  However,
# statically allocating the mem_section[] array can potentially
# consume vast quantities of .bss, so be careful.
#
# This option will also potentially produce smaller runtime code
# with gcc 3.4 and later.
#
config CONFIG_SPARSEMEM_STATIC
	bool

#
# Architecture platforms which require a two level mem_section in CONFIG_SPARSEMEM
# must select this option. This is usually for architecture platforms with
# an extremely sparse physical address space.
#
config CONFIG_SPARSEMEM_EXTREME
	def_bool y
	depends on CONFIG_SPARSEMEM && !CONFIG_SPARSEMEM_STATIC

config CONFIG_SPARSEMEM_VMEMMAP_ENABLE
	bool

config CONFIG_SPARSEMEM_VMEMMAP
	bool "Sparse Memory virtual memmap"
	depends on CONFIG_SPARSEMEM && CONFIG_SPARSEMEM_VMEMMAP_ENABLE
	default y
	help
	 CONFIG_SPARSEMEM_VMEMMAP uses a virtually mapped memmap to optimise
	 pfn_to_page and page_to_pfn operations.  This is the most
	 efficient option when sufficient kernel resources are available.

config CONFIG_HAVE_MEMBLOCK_NODE_MAP
	bool

config CONFIG_HAVE_MEMBLOCK_PHYS_MAP
	bool

config CONFIG_HAVE_FAST_GUP
	depends on CONFIG_MMU
	bool

config CONFIG_ARCH_KEEP_MEMBLOCK
	bool

config CONFIG_MEMORY_ISOLATION
	bool

#
# Only be set on architectures that have completely implemented memory hotplug
# feature. If you are not sure, don't touch it.
#
config CONFIG_HAVE_BOOTMEM_INFO_NODE
	def_bool n

# eventually, we can have this option just 'select CONFIG_SPARSEMEM'
config CONFIG_MEMORY_HOTPLUG
	bool "Allow for memory hot-add"
	depends on CONFIG_SPARSEMEM || CONFIG_X86_64_ACPI_NUMA
	depends on CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG

config CONFIG_MEMORY_HOTPLUG_SPARSE
	def_bool y
	depends on CONFIG_SPARSEMEM && CONFIG_MEMORY_HOTPLUG

config CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE
        bool "Online the newly added memory blocks by default"
        depends on CONFIG_MEMORY_HOTPLUG
        help
	  This option sets the default policy setting for memory hotplug
	  onlining policy (/sys/devices/system/memory/auto_online_blocks) which
	  determines what happens to newly added memory regions. Policy setting
	  can always be changed at runtime.
	  See Documentation/admin-guide/mm/memory-hotplug.rst for more information.

	  Say Y here if you want all hot-plugged memory blocks to appear in
	  'online' state by default.
	  Say N here if you want the default policy to keep all hot-plugged
	  memory blocks in 'offline' state.

config CONFIG_MEMORY_HOTREMOVE
	bool "Allow for memory hot remove"
	select CONFIG_MEMORY_ISOLATION
	select CONFIG_HAVE_BOOTMEM_INFO_NODE if (CONFIG_X86_64 || CONFIG_PPC64)
	depends on CONFIG_MEMORY_HOTPLUG && CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE
	depends on CONFIG_MIGRATION

# Heavily threaded applications may benefit from splitting the mm-wide
# page_table_lock, so that faults on different parts of the user address
# space can be handled with less contention: split it at this CONFIG_NR_CPUS.
# Default to 4 for wider testing, though 8 might be more appropriate.
# CONFIG_ARM's adjust_pte (unused if VIPT) depends on mm-wide page_table_lock.
# PA-RISC 7xxx's spinlock_t would enlarge struct page from 32 to 44 bytes.
# CONFIG_DEBUG_SPINLOCK and CONFIG_DEBUG_LOCK_ALLOC spinlock_t also enlarge struct page.
#
config CONFIG_SPLIT_PTLOCK_CPUS
	int
	default "999999" if !CONFIG_MMU
	default "999999" if CONFIG_ARM && !CONFIG_CPU_CACHE_VIPT
	default "999999" if CONFIG_PARISC && !CONFIG_PA20
	default "4"

config CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK
	bool

#
# support for memory balloon
config CONFIG_MEMORY_BALLOON
	bool

#
# support for memory balloon compaction
config CONFIG_BALLOON_COMPACTION
	bool "Allow for balloon memory compaction/migration"
	def_bool y
	depends on CONFIG_COMPACTION && CONFIG_MEMORY_BALLOON
	help
	  Memory fragmentation introduced by ballooning might reduce
	  significantly the number of 2MB contiguous memory blocks that can be
	  used within a guest, thus imposing performance penalties associated
	  with the reduced number of transparent huge pages that could be used
	  by the guest workload. Allowing the compaction & migration for memory
	  pages enlisted as being part of memory balloon devices avoids the
	  scenario aforementioned and helps improving memory defragmentation.

#
# support for memory compaction
config CONFIG_COMPACTION
	bool "Allow for memory compaction"
	def_bool y
	select CONFIG_MIGRATION
	depends on CONFIG_MMU
	help
          Compaction is the only memory management component to form
          high order (larger physically contiguous) memory blocks
          reliably. The page allocator relies on compaction heavily and
          the lack of the feature can lead to unexpected OOM killer
          invocations for high order memory requests. You shouldn't
          disable this option unless there really is a strong reason for
          it and then we would be really interested to hear about that at
          linux-mm@kvack.org.

#
# support for page migration
#
config CONFIG_MIGRATION
	bool "Page migration"
	def_bool y
	depends on (CONFIG_NUMA || CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE || CONFIG_COMPACTION || CONFIG_CMA) && CONFIG_MMU
	help
	  Allows the migration of the physical location of pages of processes
	  while the virtual addresses are not changed. This is useful in
	  two situations. The first is on CONFIG_NUMA systems to put pages nearer
	  to the processors accessing. The second is when allocating huge
	  pages as migration can relocate pages to satisfy a huge page
	  allocation instead of reclaiming.

config CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION
	bool

config CONFIG_ARCH_ENABLE_THP_MIGRATION
	bool

config CONFIG_CONTIG_ALLOC
       def_bool (CONFIG_MEMORY_ISOLATION && CONFIG_COMPACTION) || CONFIG_CMA

config CONFIG_PHYS_ADDR_T_64BIT
	def_bool CONFIG_64BIT

config CONFIG_BOUNCE
	bool "Enable bounce buffers"
	default y
	depends on CONFIG_BLOCK && CONFIG_MMU && (CONFIG_ZONE_DMA || CONFIG_HIGHMEM)
	help
	  Enable bounce buffers for devices that cannot access
	  the full range of memory available to the CPU. Enabled
	  by default when CONFIG_ZONE_DMA or CONFIG_HIGHMEM is selected, but you
	  may say n to override this.

config CONFIG_VIRT_TO_BUS
	bool
	help
	  An architecture should select this if it implements the
	  deprecated interface virt_to_bus().  All new architectures
	  should probably not select this.


config CONFIG_MMU_NOTIFIER
	bool
	select CONFIG_SRCU

config CONFIG_KSM
	bool "Enable KSM for page merging"
	depends on CONFIG_MMU
	select CONFIG_XXHASH
	help
	  Enable Kernel Samepage Merging: CONFIG_KSM periodically scans those areas
	  of an application's address space that an app has advised may be
	  mergeable.  When it finds pages of identical content, it replaces
	  the many instances by a single page with that content, so
	  saving memory until one or another app needs to modify the content.
	  Recommended for use with CONFIG_KVM, or with other duplicative applications.
	  See Documentation/vm/ksm.rst for more information: CONFIG_KSM is inactive
	  until a program has madvised that an area is MADV_MERGEABLE, and
	  root has set /sys/kernel/mm/ksm/run to 1 (if CONFIG_SYSFS is set).

config CONFIG_DEFAULT_MMAP_MIN_ADDR
        int "Low address space to protect from user allocation"
	depends on CONFIG_MMU
        default 4096
        help
	  This is the portion of low virtual memory which should be protected
	  from userspace allocation.  Keeping a user from writing to low pages
	  can help reduce the impact of kernel NULL pointer bugs.

	  For most ia64, ppc64 and x86 users with lots of address space
	  a value of 65536 is reasonable and should cause no problems.
	  On arm and other archs it should not be higher than 32768.
	  Programs which use vm86 functionality or have some need to map
	  this low address space will need CAP_SYS_RAWIO or disable this
	  protection by setting the value to 0.

	  This value can be changed after boot using the
	  /proc/sys/vm/mmap_min_addr tunable.

config CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE
	bool

config CONFIG_MEMORY_FAILURE
	depends on CONFIG_MMU
	depends on CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE
	bool "Enable recovery from hardware memory errors"
	select CONFIG_MEMORY_ISOLATION
	select CONFIG_RAS
	help
	  Enables code to recover from some memory failures on systems
	  with CONFIG_MCA recovery. This allows a system to continue running
	  even when some of its memory has uncorrected errors. This requires
	  special hardware support and typically ECC memory.

config CONFIG_HWPOISON_INJECT
	tristate "HWPoison pages injector"
	depends on CONFIG_MEMORY_FAILURE && CONFIG_DEBUG_KERNEL && CONFIG_PROC_FS
	select CONFIG_PROC_PAGE_MONITOR

config CONFIG_NOMMU_INITIAL_TRIM_EXCESS
	int "Turn on mmap() excess space trimming before booting"
	depends on !CONFIG_MMU
	default 1
	help
	  The NOMMU mmap() frequently needs to allocate large contiguous chunks
	  of memory on which to store mappings, but it can only ask the system
	  allocator for chunks in 2^N*PAGE_SIZE amounts - which is frequently
	  more than it requires.  To deal with this, mmap() is able to trim off
	  the excess and return it to the allocator.

	  If trimming is enabled, the excess is trimmed off and returned to the
	  system allocator, which can cause extra fragmentation, particularly
	  if there are a lot of transient processes.

	  If trimming is disabled, the excess is kept, but not used, which for
	  long-term mappings means that the space is wasted.

	  Trimming can be dynamically controlled through a sysctl option
	  (/proc/sys/vm/nr_trim_pages) which specifies the minimum number of
	  excess pages there must be before trimming should occur, or zero if
	  no trimming is to occur.

	  This option specifies the initial value of this option.  The default
	  of 1 says that all excess pages should be trimmed.

	  See Documentation/nommu-mmap.txt for more information.

config CONFIG_TRANSPARENT_HUGEPAGE
	bool "Transparent Hugepage Support"
	depends on CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE
	select CONFIG_COMPACTION
	select CONFIG_XARRAY_MULTI
	help
	  Transparent Hugepages allows the kernel to use huge pages and
	  huge tlb transparently to the applications whenever possible.
	  This feature can improve computing performance to certain
	  applications by speeding up page faults during memory
	  allocation, by reducing the number of tlb misses and by speeding
	  up the pagetable walking.

	  If memory constrained on embedded, you may want to say N.

choice
	prompt "Transparent Hugepage Support sysfs defaults"
	depends on CONFIG_TRANSPARENT_HUGEPAGE
	default CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
	help
	  Selects the sysfs defaults for Transparent Hugepage Support.

	config CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
		bool "always"
	help
	  Enabling Transparent Hugepage always, can increase the
	  memory footprint of applications without a guaranteed
	  benefit but it will work automatically for all applications.

	config CONFIG_TRANSPARENT_HUGEPAGE_MADVISE
		bool "madvise"
	help
	  Enabling Transparent Hugepage madvise, will only provide a
	  performance improvement benefit to the applications using
	  madvise(MADV_HUGEPAGE) but it won't risk to increase the
	  memory footprint of applications without a guaranteed
	  benefit.
endchoice

config CONFIG_ARCH_WANTS_THP_SWAP
       def_bool n

config CONFIG_THP_SWAP
	def_bool y
	depends on CONFIG_TRANSPARENT_HUGEPAGE && CONFIG_ARCH_WANTS_THP_SWAP && CONFIG_SWAP
	help
	  Swap transparent huge pages in one piece, without splitting.
	  XXX: For now, swap cluster backing transparent huge page
	  will be split after swapout.

	  For selection by architectures with reasonable THP sizes.

config	CONFIG_TRANSPARENT_HUGE_PAGECACHE
	def_bool y
	depends on CONFIG_TRANSPARENT_HUGEPAGE

#
# UP and nommu archs use km based percpu allocator
#
config CONFIG_NEED_PER_CPU_KM
	depends on !CONFIG_SMP
	bool
	default y

config CONFIG_CLEANCACHE
	bool "Enable cleancache driver to cache clean pages if tmem is present"
	help
	  Cleancache can be thought of as a page-granularity victim cache
	  for clean pages that the kernel's pageframe replacement algorithm
	  (PFRA) would like to keep around, but can't since there isn't enough
	  memory.  So when the PFRA "evicts" a page, it first attempts to use
	  cleancache code to put the data contained in that page into
	  "transcendent memory", memory that is not directly accessible or
	  addressable by the kernel and is of unknown and possibly
	  time-varying size.  And when a cleancache-enabled
	  filesystem wishes to access a page in a file on disk, it first
	  checks cleancache to see if it already contains it; if it does,
	  the page is copied into the kernel and a disk access is avoided.
	  When a transcendent memory driver is available (such as zcache or
	  Xen transcendent memory), a significant I/O reduction
	  may be achieved.  When none is available, all cleancache calls
	  are reduced to a single pointer-compare-against-NULL resulting
	  in a negligible performance hit.

	  If unsure, say Y to enable cleancache

config CONFIG_FRONTSWAP
	bool "Enable frontswap to cache swap pages if tmem is present"
	depends on CONFIG_SWAP
	help
	  Frontswap is so named because it can be thought of as the opposite
	  of a "backing" store for a swap device.  The data is stored into
	  "transcendent memory", memory that is not directly accessible or
	  addressable by the kernel and is of unknown and possibly
	  time-varying size.  When space in transcendent memory is available,
	  a significant swap I/O reduction may be achieved.  When none is
	  available, all frontswap calls are reduced to a single pointer-
	  compare-against-NULL resulting in a negligible performance hit
	  and swap data is stored as normal on the matching swap device.

	  If unsure, say Y to enable frontswap.

config CONFIG_CMA
	bool "Contiguous Memory Allocator"
	depends on CONFIG_MMU
	select CONFIG_MIGRATION
	select CONFIG_MEMORY_ISOLATION
	help
	  This enables the Contiguous Memory Allocator which allows other
	  subsystems to allocate big physically-contiguous blocks of memory.
	  CONFIG_CMA reserves a region of memory and allows only movable pages to
	  be allocated from it. This way, the kernel can use the memory for
	  pagecache and when a subsystem requests for contiguous area, the
	  allocated pages are migrated away to serve the contiguous request.

	  If unsure, say "n".

config CONFIG_CMA_DEBUG
	bool "CMA debug messages (DEVELOPMENT)"
	depends on CONFIG_DEBUG_KERNEL && CONFIG_CMA
	help
	  Turns on debug messages in CONFIG_CMA.  This produces KERN_DEBUG
	  messages for every CONFIG_CMA call as well as various messages while
	  processing calls such as dma_alloc_from_contiguous().
	  This option does not affect warning and error messages.

config CONFIG_CMA_DEBUGFS
	bool "CMA debugfs interface"
	depends on CONFIG_CMA && CONFIG_DEBUG_FS
	help
	  Turns on the DebugFS interface for CONFIG_CMA.

config CONFIG_CMA_AREAS
	int "Maximum count of the CMA areas"
	depends on CONFIG_CMA
	default 7
	help
	  CONFIG_CMA allows to create CONFIG_CMA areas for particular purpose, mainly,
	  used as device private area. This parameter sets the maximum
	  number of CONFIG_CMA area in the system.

	  If unsure, leave the default value "7".

config CONFIG_MEM_SOFT_DIRTY
	bool "Track memory changes"
	depends on CONFIG_CHECKPOINT_RESTORE && CONFIG_HAVE_ARCH_SOFT_DIRTY && CONFIG_PROC_FS
	select CONFIG_PROC_PAGE_MONITOR
	help
	  This option enables memory changes tracking by introducing a
	  soft-dirty bit on pte-s. This bit it set when someone writes
	  into a page just as regular dirty bit, but unlike the latter
	  it can be cleared by hands.

	  See Documentation/admin-guide/mm/soft-dirty.rst for more details.

config CONFIG_ZSWAP
	bool "Compressed cache for swap pages (EXPERIMENTAL)"
	depends on CONFIG_FRONTSWAP && CONFIG_CRYPTO=y
	select CONFIG_CRYPTO_LZO
	select CONFIG_ZPOOL
	help
	  CONFIG_A lightweight compressed cache for swap pages.  It takes
	  pages that are in the process of being swapped out and attempts to
	  compress them into a dynamically allocated RAM-based memory pool.
	  This can result in a significant I/O reduction on swap device and,
	  in the case where decompressing from RAM is faster that swap device
	  reads, can also improve workload performance.

	  This is marked experimental because it is a new feature (as of
	  v3.11) that interacts heavily with memory reclaim.  While these
	  interactions don't cause any known issues on simple memory setups,
	  they have not be fully explored on the large set of potential
	  configurations and workloads that exist.

config CONFIG_ZPOOL
	tristate "Common API for compressed memory storage"
	help
	  Compressed memory storage API.  This allows using either zbud or
	  zsmalloc.

config CONFIG_ZBUD
	tristate "Low (Up to 2x) density storage for compressed pages"
	help
	  CONFIG_A special purpose allocator for storing compressed pages.
	  It is designed to store up to two compressed pages per physical
	  page.  While this design limits storage density, it has simple and
	  deterministic reclaim properties that make it preferable to a higher
	  density approach when reclaim will be used.

config CONFIG_Z3FOLD
	tristate "Up to 3x density storage for compressed pages"
	depends on CONFIG_ZPOOL
	help
	  CONFIG_A special purpose allocator for storing compressed pages.
	  It is designed to store up to three compressed pages per physical
	  page. It is a CONFIG_ZBUD derivative so the simplicity and determinism are
	  still there.

config CONFIG_ZSMALLOC
	tristate "Memory allocator for compressed pages"
	depends on CONFIG_MMU
	help
	  zsmalloc is a slab-based memory allocator designed to store
	  compressed RAM pages.  zsmalloc uses virtual memory mapping
	  in order to reduce fragmentation.  However, this results in a
	  non-standard allocator interface where a handle, not a pointer, is
	  returned by an alloc().  This handle must be mapped in order to
	  access the allocated space.

config CONFIG_PGTABLE_MAPPING
	bool "Use page table mapping to access object in zsmalloc"
	depends on CONFIG_ZSMALLOC
	help
	  By default, zsmalloc uses a copy-based object mapping method to
	  access allocations that span two pages. However, if a particular
	  architecture (ex, CONFIG_ARM) performs VM mapping faster than copying,
	  then you should select this. This causes zsmalloc to use page table
	  mapping rather than copying for object mapping.

	  You can check speed with zsmalloc benchmark:
	  https://github.com/spartacus06/zsmapbench

config CONFIG_ZSMALLOC_STAT
	bool "Export zsmalloc statistics"
	depends on CONFIG_ZSMALLOC
	select CONFIG_DEBUG_FS
	help
	  This option enables code in the zsmalloc to collect various
	  statistics about whats happening in zsmalloc and exports that
	  information to userspace via debugfs.
	  If unsure, say N.

config CONFIG_GENERIC_EARLY_IOREMAP
	bool

config CONFIG_MAX_STACK_SIZE_MB
	int "Maximum user stack size for 32-bit processes (MB)"
	default 80
	range 8 2048
	depends on CONFIG_STACK_GROWSUP && (!CONFIG_64BIT || CONFIG_COMPAT)
	help
	  This is the maximum stack size in Megabytes in the VM layout of 32-bit
	  user processes when the stack grows upwards (currently only on parisc
	  arch). The stack will be located at the highest memory address minus
	  the given value, unless the RLIMIT_STACK hard limit is changed to a
	  smaller value in which case that is used.

	  CONFIG_A sane initial value is 80 MB.

config CONFIG_DEFERRED_STRUCT_PAGE_INIT
	bool "Defer initialisation of struct pages to kthreads"
	depends on CONFIG_SPARSEMEM
	depends on !CONFIG_NEED_PER_CPU_KM
	depends on CONFIG_64BIT
	help
	  Ordinarily all struct pages are initialised during early boot in a
	  single thread. On very large machines this can take a considerable
	  amount of time. If this option is set, large machines will bring up
	  a subset of memmap at boot and then initialise the rest in parallel
	  by starting one-off "pgdatinitX" kernel thread for each node X. This
	  has a potential performance impact on processes running early in the
	  lifetime of the system until these kthreads finish the
	  initialisation.

config CONFIG_IDLE_PAGE_TRACKING
	bool "Enable idle page tracking"
	depends on CONFIG_SYSFS && CONFIG_MMU
	select CONFIG_PAGE_EXTENSION if !CONFIG_64BIT
	help
	  This feature allows to estimate the amount of user pages that have
	  not been touched during a given period of time. This information can
	  be useful to tune memory cgroup limits and/or for job placement
	  within a compute cluster.

	  See Documentation/admin-guide/mm/idle_page_tracking.rst for
	  more details.

config CONFIG_ARCH_HAS_PTE_DEVMAP
	bool

config CONFIG_ZONE_DEVICE
	bool "Device memory (pmem, HMM, etc...) hotplug support"
	depends on CONFIG_MEMORY_HOTPLUG
	depends on CONFIG_MEMORY_HOTREMOVE
	depends on CONFIG_SPARSEMEM_VMEMMAP
	depends on CONFIG_ARCH_HAS_PTE_DEVMAP
	select CONFIG_XARRAY_MULTI

	help
	  Device memory hotplug support allows for establishing pmem,
	  or other device driver discovered memory regions, in the
	  memmap. This allows pfn_to_page() lookups of otherwise
	  "device-physical" addresses which is needed for using a CONFIG_DAX
	  mapping in an O_DIRECT operation, among other things.

	  If CONFIG_FS_DAX is enabled, then say Y.

config CONFIG_DEV_PAGEMAP_OPS
	bool

#
# Helpers to mirror range of the CPU page tables of a process into device page
# tables.
#
config CONFIG_HMM_MIRROR
	bool
	depends on CONFIG_MMU
	depends on CONFIG_MMU_NOTIFIER

config CONFIG_DEVICE_PRIVATE
	bool "Unaddressable device memory (GPU memory, ...)"
	depends on CONFIG_ZONE_DEVICE
	select CONFIG_DEV_PAGEMAP_OPS

	help
	  Allows creation of struct pages to represent unaddressable device
	  memory; i.e., memory that is only accessible from the device (or
	  group of devices). You likely also want to select CONFIG_HMM_MIRROR.

config CONFIG_FRAME_VECTOR
	bool

config CONFIG_ARCH_USES_HIGH_VMA_FLAGS
	bool
config CONFIG_ARCH_HAS_PKEYS
	bool

config CONFIG_PERCPU_STATS
	bool "Collect percpu memory statistics"
	help
	  This feature collects and exposes statistics via debugfs. The
	  information includes global and per chunk statistics, which can
	  be used to help understand percpu memory usage.

config CONFIG_GUP_BENCHMARK
	bool "Enable infrastructure for get_user_pages_fast() benchmarking"
	help
	  Provides /sys/kernel/debug/gup_benchmark that helps with testing
	  performance of get_user_pages_fast().

	  See tools/testing/selftests/vm/gup_benchmark.c

config CONFIG_GUP_GET_PTE_LOW_HIGH
	bool

config CONFIG_READ_ONLY_THP_FOR_FS
	bool "Read-only THP for filesystems (EXPERIMENTAL)"
	depends on CONFIG_TRANSPARENT_HUGE_PAGECACHE && CONFIG_SHMEM

	help
	  Allow khugepaged to put read-only file-backed pages in THP.

	  This is marked experimental because it is a new feature. Write
	  support of file THPs will be developed in the next few release
	  cycles.

config CONFIG_ARCH_HAS_PTE_SPECIAL
	bool

#
# Some architectures require a special hugepage directory format that is
# required to support multiple hugepage sizes. For example a4fe3ce76
# "powerpc/mm: Allow more flexible layouts for hugepage pagetables"
# introduced it on powerpc.  This allows for a more flexible hugepage
# pagetable layouts.
#
config CONFIG_ARCH_HAS_HUGEPD
	bool

endmenu