| /Linux-v6.1/Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - *DAMON user space tool.*
11 system administrators who want a just-working human-friendly interface.
12 Using this, users can use the DAMON’s major features in a human-friendly way.
17 - *sysfs interface.*
28 - *debugfs interface.*
32 - *Kernel Space Programming Interface.*
45 creates multiple directories and files under its sysfs directory,
47 from the files under the directory.
60 ---------------
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | README.rst | 11 --------------
14 Linus Torvalds with assistance from a loosely-knit team of hackers across
17 It has all the features you would expect in a modern fully-fledged Unix,
19 loading, shared copy-on-write executables, proper memory management,
22 It is distributed under the GNU General Public License v2 - see the
26 -----------------------------
28 Although originally developed first for 32-bit x86-based PCs (386 or higher),
31 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
34 Linux is easily portable to most general-purpose 32- or 64-bit architectures
40 userspace application - this is called UserMode Linux (UML).
[all …]
|
| /Linux-v6.1/drivers/fsi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 FSI - the FRU Support Interface - is a simple bus for low-level
12 access to POWER-based hardware.
17 bool "Create '/dev/fsi' directory for char devices"
21 located under a common /dev/fsi/ directory. Set to N unless your
29 symlinks in /dev/fsi/by-path when this option is enabled.
32 tristate "GPIO-based FSI master"
47 tristate "FSI master based on Aspeed ColdFire coprocessor"
68 This option enables an FSI based SCOM device driver.
74 This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
[all …]
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-devices-soc | 5 The /sys/devices/ directory contains a sub-directory for each
6 System-on-Chip (SoC) device on a running platform. Information
10 The directory created for each SoC will also house information
19 Read-only attribute common to all SoCs. Contains the SoC machine
26 Read-only attribute common to all SoCs. Contains SoC family name
29 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
57 Read-only attribute supported by most SoCs. Contains the SoC's
64 Read-only attribute supported by most SoCs. In the case of
65 ST-Ericsson's chips this contains the SoC serial number.
67 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
[all …]
|
| D | sysfs-kernel-mm-memory-tiers | 3 Contact: Linux memory management mailing list <linux-mm@kvack.org>
15 Contact: Linux memory management mailing list <linux-mm@kvack.org>
16 Description: Directory with details of a specific memory tier
18 This is the directory containing information about a particular
19 memory tier, memtierN, where N is derived based on abstract distance.
|
| D | sysfs-firmware-opal-sensor-groups | 3 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
4 Description: Sensor groups directory for POWER9 powernv servers
6 Each folder in this directory contains a sensor group
7 which are classified based on type of the sensor
10 different owners like CSM, Profiler, Job-Scheduler
14 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
15 Description: Sysfs file to clear the min-max of all the sensors
20 In POWER9, the min-max of a sensor is the historical minimum
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | autofs.rst | 2 autofs - how it works
8 The goal of autofs is to provide on-demand mounting and race free
17 media with a media-changing robot.
23 filesystem can even be programmatic rather than database-backed,
24 allowing wildcards for example, and can vary based on the user who
31 There also needs to be a user-space program which looks up names
35 required with any user-space program. Subsequent text refers to this
52 directory should be a mount trap is based on a master map. This master
58 mount is considered to be *indirect*), then the root directory is
59 always a regular directory, otherwise it is a mount trap when it is
[all …]
|
| D | directory-locking.rst | 2 Directory Locking
6 Locking scheme used for directory operations is based on two
7 kinds of locks - per-inode (->i_rwsem) and per-filesystem
8 (->s_vfs_rename_mutex).
10 When taking the i_rwsem on multiple non-directory objects, we
16 1) read access. Locking rules: caller locks directory we are accessing.
25 4) rename() that is _not_ cross-directory. Locking rules: caller locks
28 if the target already exists, lock it. If the source is a non-directory,
37 * check that source is not a directory
43 6) cross-directory rename. The trickiest in the whole bunch. Locking
[all …]
|
| D | erofs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 EROFS - Enhanced Read-Only File System
10 EROFS filesystem stands for Enhanced Read-Only File System. It aims to form a
11 generic read-only filesystem solution for various read-only use cases instead
17 random-access friendly high-performance filesystem to get rid of unneeded I/O
18 amplification and memory-resident overhead compared to similar approaches.
22 - read-only storage media or
24 - part of a fully trusted read-only solution, which means it needs to be
25 immutable and bit-for-bit identical to the official golden image for
28 - hope to minimize extra storage space with guaranteed end-to-end performance
[all …]
|
| D | sysfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 sysfs - _The_ filesystem for exporting kernel objects
18 sysfs is a ram-based filesystem initially based on ramfs. It provides
23 Documentation/core-api/kobject.rst for more information concerning the kobject
33 mount -t sysfs sysfs /sys
36 Directory Creation
39 For every kobject that is registered with the system, a directory is
40 created for it in sysfs. That directory is created as a subdirectory
42 userspace. Top-level directories in sysfs represent the common
47 directory in the kernfs_node object associated with the directory. In
[all …]
|
| /Linux-v6.1/fs/adfs/ |
| D | dir_f.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright (C) 1997-1999 Russell King
7 * E and F format directory handling
48 int _off = idx - (_buf << blocksize_bits);\
49 *(u8 *)(bh[_buf]->b_data + _off); \
54 int _off = idx - (_buf << blocksize_bits);\
55 *(__le32 *)(bh[_buf]->b_data + _off); \
60 int _off = _idx - (_buf << blocksize_bits);\
61 (void *)(_bh[_buf]->b_data + _off); \
72 struct buffer_head * const *bh = dir->bh; in adfs_dir_checkbyte()
[all …]
|
| /Linux-v6.1/tools/testing/ktest/examples/ |
| D | README | 1 This directory contains example configs to use ktest for various tasks.
6 The configs are based off of real working configs but have been modified
10 crosstests.conf - this config shows an example of testing a git repo against
16 test.conf - A generic example of a config. This is based on an actual config
19 kvm.conf - A example of a config that is used to test a virtual guest running
22 snowball.conf - An example config that was used to demo ktest.pl against
25 include/ - The include directory holds default configs that can be
|
| /Linux-v6.1/include/xen/ |
| D | xen-front-pgdir-shbuf.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR MIT */
4 * Xen frontend/backend page directory based shared buffer
25 * - for frontend allocated/imported buffers this holds the number
26 * of grant references for the page directory and the pages
29 * - for the buffer provided by the backend this only holds the number
30 * of grant references for the page directory itself as grant
35 /* Page directory backing storage. */
36 u8 *directory; member
40 * directory).
67 * This is allocated outside because there are use-cases when
|
| /Linux-v6.1/drivers/mtd/parsers/ |
| D | redboot.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Parse RedBoot-style Flash Image System (FIS) tables and
7 * Copyright © 2001-2010 David Woodhouse <dwmw2@infradead.org>
26 unsigned char _pad[256 - (16 + 7 * sizeof(u32))];
36 static int directory = CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK; variable
37 module_param(directory, int, 0);
60 ret = of_property_read_u32(npart, "fis-index-block", &dirblock); in parse_redboot_of()
67 * directory block pointer. in parse_redboot_of()
69 directory = dirblock; in parse_redboot_of()
94 if (directory < 0) { in parse_redboot_partitions()
[all …]
|
| /Linux-v6.1/include/uapi/linux/ |
| D | inotify.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
3 * Inode based directory notification for Linux
16 * struct inotify_event - structure read from the inotify device for each event
18 * When you are watching a directory, you will receive the filename for events
29 /* the following are legal, implemented events that user-space can watch for */
53 #define IN_ONLYDIR 0x01000000 /* only watch the path if it is a directory */
62 * All of the events - we build the list by hand so that we can add flags in
77 * except historical FIONREAD, which is based on 'T'.
|
| /Linux-v6.1/Documentation/arm/samsung-s3c24xx/ |
| D | overview.rst | 8 ------------
10 The Samsung S3C24XX range of ARM9 System-on-Chip CPUs are supported
21 included under the arch/arm/mach-s3c directory. Note, while core
27 -------------
38 ------
41 platform code contained in arch/arm/mach-s3c with headers in
42 arch/arm/mach-s3c/include
44 arch/arm/mach-s3c:
54 this directory, the name becomes invalid. We stick to s3c2440-<x>
62 --------
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/mm/ |
| D | numaperf.rst | 13 under different domains, or "nodes", based on locality and performance
20 +------------------+ +------------------+
21 | Compute Node 0 +-----+ Compute Node 1 |
23 +--------+---------+ +--------+---------+
25 +--------+---------+ +--------+---------+
27 +------------------+ +--------+---------+
35 performance when accessing a given memory target. Each initiator-target
47 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
48 relative: /sys/devices/system/node/nodeX/access0/targets/nodeY -> ../../nodeY
50 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/sysctl/ |
| D | fs.rst | 13 ------------------------------------------------------------------------------
18 The files in this directory can be used to tune and monitor
29 - aio-max-nr
30 - aio-nr
31 - dentry-state
32 - dquot-max
33 - dquot-nr
34 - file-max
35 - file-nr
36 - inode-max
[all …]
|
| /Linux-v6.1/drivers/xen/ |
| D | xen-front-pgdir-shbuf.c | 1 // SPDX-License-Identifier: GPL-2.0 OR MIT
4 * Xen frontend/backend page directory based shared buffer
22 #include <xen/xen-front-pgdir-shbuf.h>
27 * buffer. This structure is common to many Xen para-virtualized
45 * e.g. if grefs are required for page directory only or the buffer
50 /* Fill page directory according to para-virtual display protocol. */
66 * page directory. Usually this is passed to the backend,
70 * \param buf shared buffer which page directory is of interest.
72 * page directory.
77 if (!buf->grefs) in xen_front_pgdir_shbuf_get_dir_start()
[all …]
|
| /Linux-v6.1/drivers/edac/ |
| D | edac_device.h | 9 * Based on work by Dan Hollis <goemon at anime dot net> and others.
10 * http://www.anime.net/~goemon/linux-ecc/
15 * Refactored for multi-source files:
18 * Please look at Documentation/driver-api/edac.rst for more info about
58 * mc/ <existing memory device directory>
59 * cpu/cpu0/.. <L1 and L2 block directory>
60 * /L1-cache/ce_count
62 * /L2-cache/ce_count
64 * cpu/cpu1/.. <L1 and L2 block directory>
65 * /L1-cache/ce_count
[all …]
|
| /Linux-v6.1/tools/perf/ |
| D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0
4 # with a -j option to do parallel builds
6 # If you want to invoke the perf build in some non-standard way then
7 # you can use the 'make -f Makefile.perf' method to invoke it.
11 # Clear out the built-in rules GNU make defines by default (such as .o targets),
17 # We don't want to pass along options like -j:
22 # Do a parallel build with multiple jobs, based on the number of CPUs online
23 # in this system: 'make -j8' on a 8-CPU system, etc.
28 …JOBS := $(shell (getconf _NPROCESSORS_ONLN || egrep -c '^processor|^CPU[0-9]' /proc/cpuinfo) 2>/de…
35 # Only pass canonical directory names as the output directory:
[all …]
|
| /Linux-v6.1/fs/ceph/ |
| D | ioctl.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
11 * CEPH_IOC_GET_LAYOUT - get file layout or dir layout policy
12 * CEPH_IOC_SET_LAYOUT - set file layout
13 * CEPH_IOC_SET_LAYOUT_POLICY - set dir layout policy
20 * Files get a new layout based on the policy set on the containing
21 * directory or one of its ancestors. The GET_LAYOUT ioctl will let
22 * you examine the layout for a file or the policy on a directory.
29 * on a directory that will apply to any new files created in that
30 * directory (or any child directory that doesn't specify a layout of
39 /* obsolete. new values ignored, always return -1 */
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/net/ |
| D | ftgmac100.txt | 4 - compatible: "faraday,ftgmac100"
10 - "aspeed,ast2400-mac"
11 - "aspeed,ast2500-mac"
12 - "aspeed,ast2600-mac"
14 - reg: Address and length of the register set for the device
15 - interrupts: Should contain ethernet controller interrupt
18 - phy-handle: See ethernet.txt file in the same directory.
19 - phy-mode: See ethernet.txt file in the same directory. If the property is
22 - use-ncsi: Use the NC-SI stack instead of an MDIO PHY. Currently assumes
23 rmii (100bT) but kept as a separate property in case NC-SI grows support
[all …]
|
| /Linux-v6.1/scripts/clang-tools/ |
| D | gen_compile_commands.py | 2 # SPDX-License-Identifier: GPL-2.0
24 # The tools/ directory adopts a different build system, and produces .cmd
29 """Sets up and parses command-line arguments.
33 directory: The work directory where the objects were built.
35 output: Where to write the compile-commands JSON file.
41 directory_help = ('specify the output directory used for the kernel build '
42 '(defaults to the working directory)')
43 parser.add_argument('-d', '--directory', type=str, default='.',
48 parser.add_argument('-o', '--output', type=str, default=_DEFAULT_OUTPUT,
53 parser.add_argument('--log_level', choices=_VALID_LOG_LEVELS,
[all …]
|
| /Linux-v6.1/tools/perf/pmu-events/ |
| D | README | 2 The contents of this directory allow users to specify PMU events in their
5 The main program in this directory, is the 'jevents', which is built and
8 The 'jevents' program tries to locate and process JSON files in the directory
9 tree tools/perf/pmu-events/arch/foo.
11 - Regular files with '.json' extension in the name are assumed to be
14 - The CSV file that maps a specific CPU to its set of PMU events is to
17 - Directories are traversed, but all other files are ignored.
19 - To reduce JSON event duplication per architecture, platform JSONs may
23 folder. Matching is based on the "EventName" field.
26 such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
[all …]
|
