| /linux-4.1.27/arch/s390/kernel/ |
| D | debug.c | 196 debug_entry_t*** areas; in debug_areas_alloc() local
199 areas = kmalloc(nr_areas * in debug_areas_alloc()
202 if (!areas) in debug_areas_alloc()
205 areas[i] = kmalloc(pages_per_area * in debug_areas_alloc()
207 if (!areas[i]) { in debug_areas_alloc()
211 areas[i][j] = kzalloc(PAGE_SIZE, GFP_KERNEL); in debug_areas_alloc()
212 if(!areas[i][j]) { in debug_areas_alloc()
214 kfree(areas[i][j]); in debug_areas_alloc()
216 kfree(areas[i]); in debug_areas_alloc()
221 return areas; in debug_areas_alloc()
[all …]
|
| D | crash_dump.c | 58 save_areas = krealloc(dump_save_areas.areas, in dump_save_area_create()
65 dump_save_areas.areas = save_areas; in dump_save_area_create()
67 dump_save_areas.areas[cpu] = save_area; in dump_save_area_create()
527 if (dump_save_areas.areas[i]->sa.pref_reg == 0) in get_cpu_cnt()
580 sa_ext = dump_save_areas.areas[i]; in notes_init()
|
| /linux-4.1.27/Documentation/vm/ |
| D | ksm.txt | 8 The KSM daemon ksmd periodically scans those areas of user memory which
23 KSM only operates on those areas of address space which an application
41 Like other madvise calls, they are intended for use on mapped areas of
43 includes unmapped gaps (though working on the intervening mapped areas),
47 restricting its use to areas likely to benefit. KSM's scans may use a lot
79 but leave mergeable areas registered for next run
89 full_scans - how many times all mergeable areas have been scanned
|
| D | pagemap.txt | 31 determine which areas of memory are actually mapped and llseek to
|
| /linux-4.1.27/Documentation/cma/ |
| D | debugfs.txt | 2 different CMA areas and to test allocation/release in each of the areas.
|
| /linux-4.1.27/Documentation/s390/ |
| D | s390dbf.txt | 23 debug log for the caller. For each debug log exists a number of debug areas
25 pages in memory. In the debug areas there are stored debug entries (log records)
39 The debug areas themselves are also ordered in form of a ring buffer.
109 nr_areas: number of debug areas
125 nr_areas: Number of debug areas
343 /* register 4 debug areas with one page each and 4 byte data field */
377 /* register 4 debug areas with one page each and data field for */
434 Flushing debug areas
436 Debug areas can be flushed with piping the number of the desired
437 area (0...n) to the debugfs file "flush". When using "-" all debug areas
[all …]
|
| D | 3270.txt | 183 The driver defines three areas on the 3270 screen: the log area, the
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-docg3 | 7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
22 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
|
| D | sysfs-kernel-mm-ksm | 19 full_scans: how many times all mergeable areas have been
|
| D | sysfs-block | 225 areas on disk or to initialize drives in a RAID
|
| /linux-4.1.27/mm/ |
| D | percpu.c | 1950 void **areas = NULL; in pcpu_embed_first_chunk() local
1963 areas = memblock_virt_alloc_nopanic(areas_size, 0); in pcpu_embed_first_chunk()
1964 if (!areas) { in pcpu_embed_first_chunk()
1987 areas[group] = ptr; in pcpu_embed_first_chunk()
1999 void *ptr = areas[group]; in pcpu_embed_first_chunk()
2016 ai->groups[group].base_offset = areas[group] - base; in pcpu_embed_first_chunk()
2043 if (areas[group]) in pcpu_embed_first_chunk()
2044 free_fn(areas[group], in pcpu_embed_first_chunk()
2048 if (areas) in pcpu_embed_first_chunk()
2049 memblock_free_early(__pa(areas), areas_size); in pcpu_embed_first_chunk()
|
| D | Kconfig | 82 # to represent different areas of memory. This variable allows
334 Enable Kernel Samepage Merging: KSM periodically scans those areas
527 int "Maximum count of the CMA areas"
531 CMA allows to create CMA areas for particular purpose, mainly,
|
| /linux-4.1.27/drivers/s390/net/ |
| D | ctcm_dbug.c | 48 ctcm_dbf[x].areas, in ctcm_register_dbf_views()
|
| D | ctcm_dbug.h | 57 int areas; member
|
| D | qeth_core.h | 47 int areas; member
|
| D | qeth_core_main.c | 5351 qeth_dbf[x].areas, in qeth_register_dbf_views()
|
| /linux-4.1.27/Documentation/fmc/ |
| D | fmc-chardev.txt | 20 and write semantics, users can simply fread or fwrite bigger areas in
21 order to dump or store bigger memory areas.
|
| /linux-4.1.27/Documentation/arm/ |
| D | memory.txt | 81 Please note that mappings which collide with the above areas may result
87 to TASK_SIZE address range. If they wish to access these areas, they
|
| D | Porting | 130 Machine specific function to map IO areas (including the debug
|
| D | IXP4xx | 12 in industrial control and other areas due to low cost and power
|
| /linux-4.1.27/Documentation/mmc/ |
| D | mmc-dev-attrs.txt | 55 areas.
60 size for erasing large areas.
|
| /linux-4.1.27/arch/s390/ |
| D | Kconfig.debug | 27 who are working in architecture specific areas of the kernel.
|
| /linux-4.1.27/Documentation/devicetree/bindings/misc/ |
| D | sram.txt | 11 Reserving sram areas:
|
| /linux-4.1.27/arch/s390/include/asm/ |
| D | ipl.h | 92 struct save_area_ext **areas; member
|
| D | debug.h | 41 debug_entry_t*** areas; member
|
| /linux-4.1.27/Documentation/virtual/ |
| D | paravirt_ops.txt | 14 functionalities in various areas. pv-ops allows for optimizations at run
|
| /linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
| D | sdhci-pxa.txt | 13 * for "marvell,armada-380-sdhci", three register areas. The first
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | zero.txt | 14 device. Reads to previously unwritten areas will return a zero'd buffer. When
|
| D | statistics.txt | 46 "<area_size>" - the range is subdivided into areas each containing
49 number of areas.
|
| D | thin-provisioning.txt | 374 read-only snapshot origin: reads to unprovisioned areas of the
|
| /linux-4.1.27/Documentation/input/ |
| D | appletouch.txt | 9 been improved in some areas:
|
| D | event-codes.txt | 289 visual/haptic areas for left, middle, right buttons intended to be used
|
| /linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,orion-pinctrl.txt | 10 - reg: two register areas, the first one describing the first two
|
| /linux-4.1.27/drivers/s390/char/ |
| D | zcore.c | 261 struct save_area *save_area = &dump_save_areas.areas[i]->sa; in zcore_add_lc()
596 prefix = dump_save_areas.areas[i]->sa.pref_reg; in zcore_header_init()
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | hfs.txt | 10 HFS but is extended in various areas. Use the hfsplus filesystem driver
|
| D | sysv-fs.txt | 43 separate areas for inodes and for directories/data.
|
| D | f2fs.txt | 38 areas on disk for fast writing, we divide the log into segments and use a
325 F2FS splits the entire volume into six areas, and all the areas except superblock
|
| D | proc.txt | 597 vmallocinfo Show vmalloced areas
869 Highmem areas are for use by userspace programs, or
929 Provides information about vmalloced/vmaped areas. One line per area,
1607 - (bit 4) ELF header pages in file-backed private memory areas (it is
1833 comparing their inode numbers to figure out which anonymous memory areas
|
| /linux-4.1.27/Documentation/power/ |
| D | swsusp-and-swap-files.txt | 6 areas:
|
| /linux-4.1.27/arch/arm64/ |
| D | Kconfig.debug | 16 who are working in architecture specific areas of the kernel.
|
| /linux-4.1.27/Documentation/x86/ |
| D | tlb.txt | 5 from areas other than the one we are trying to flush will be
|
| /linux-4.1.27/arch/mn10300/mm/ |
| D | Kconfig.cache | 66 bool "Flush areas by way of automatic purge registers (AM34 only)"
|
| /linux-4.1.27/Documentation/devicetree/bindings/dma/ |
| D | ste-dma40.txt | 6 - reg-names: Names of the above areas to use during resource look-up
|
| /linux-4.1.27/fs/jffs2/ |
| D | Kconfig | 25 areas which at one point needed debugging, but when the bugs were
|
| /linux-4.1.27/Documentation/locking/ |
| D | mutex-design.txt | 97 - Memory areas where held locks reside must not be freed.
|
| D | spinlocks.txt | 32 using spinlocks they tend to expand to areas you might not have noticed
|
| /linux-4.1.27/Documentation/ |
| D | md-cluster.txt | 138 of the areas which are suspended. Before a resync starts, the node
|
| D | debugging-via-ohci1394.txt | 36 buffer on to debug early boot problems in areas like ACPI where the system
|
| D | HOWTO | 244 is self-contained and does not affect areas outside of the code that
301 happening in the different areas of the kernel. In areas where
|
| D | kmemleak.txt | 152 kmemleak_scan_area - add scan areas inside a memory block
|
| D | rbtree.txt | 28 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
|
| D | ManagementStyle | 198 not necessarily translate to other areas. So you might prod people in
|
| D | cachetlb.txt | 386 the kernel trying to do I/O to vmap areas must manually manage
|
| D | kernel-docs.txt | 179 virtual memory areas (VMAs), vremap, PCI.
|
| D | devices.txt | 88 See block major 144, 145, 146 for expansion areas.
|
| /linux-4.1.27/Documentation/fb/ |
| D | udlfb.txt | 104 module to track changed areas of the framebuffer by page faults.
|
| /linux-4.1.27/Documentation/trace/ |
| D | mmiotrace.txt | 61 accesses to areas that are ioremapped while mmiotrace is active.
|
| D | ftrace.txt | 502 Traces the areas that disable interrupts and saves
1878 need to see what happens in detail on any areas (or specific
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | devres.txt | 48 devres is basically linked list of arbitrarily sized memory areas
|
| /linux-4.1.27/Documentation/ia64/ |
| D | aliasing.txt | 182 never generate an uncacheable reference to the WB-only areas unless
|
| D | err_inject.txt | 864 /* Allocate two memory areas va1 and va2 in shm */
|
| /linux-4.1.27/Documentation/timers/ |
| D | hrtimers.txt | 94 used in various performance-critical areas of e.g. memory management and
|
| D | highres.txt | 46 code out of the architecture-specific areas into a generic management
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig.debug | 75 who are working in architecture specific areas of the kernel.
|
| /linux-4.1.27/Documentation/thermal/ |
| D | intel_powerclamp.txt | 45 Test/Analysis has been made in the areas of power, performance,
|
| /linux-4.1.27/Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec4.txt | 239 perform run-time integrity check of memory areas that should not modified.
|
| /linux-4.1.27/arch/xtensa/ |
| D | Kconfig | 220 lowermost 128 MB of memory linearly to the areas starting
|
| /linux-4.1.27/Documentation/target/ |
| D | tcmu-design.txt | 248 memory areas.
|
| /linux-4.1.27/drivers/mtd/maps/ |
| D | Kconfig | 360 Map driver for RAM areas described via the platform device
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 373 This file contains the maximum number of memory map areas a process
374 may have. Memory map areas are used as a side-effect of calling
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 6.Followthrough | 110 For patches applying to areas for which there is no obvious subsystem tree
|
| D | 4.Coding | 344 them, as appropriate, for externally-available functions. Even in areas
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | provider.txt | 163 - The device is able to perform XOR operations on memory areas
|
| /linux-4.1.27/drivers/misc/ |
| D | Kconfig | 507 areas found on many SoCs.
|
| /linux-4.1.27/Documentation/crypto/ |
| D | descore-readme.txt | 194 the input and output work areas do not need to be word-aligned.
|
| /linux-4.1.27/drivers/char/ |
| D | Kconfig | 14 The /dev/mem device is used to access areas of physical
|
| /linux-4.1.27/drivers/ata/ |
| D | Kconfig | 58 power management, or other areas.
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig.debug | 12 who are working in architecture specific areas of the kernel.
|
| /linux-4.1.27/Documentation/security/ |
| D | keys.txt | 832 be broken down into two areas: keys and key types.
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 412 kernel with a list of physical memory areas that are "reserved"
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 3303 text or data areas. Let's see what's in the vma:
|
| /linux-4.1.27/ |
| D | MAINTAINERS | 123 Maintainers List (try to look for most precise areas first)
|