Home
last modified time | relevance | path

Searched +full:directory +full:- +full:based (Results 1 – 25 of 788) sorted by relevance

12345678910>>...32

/linux/Documentation/ABI/testing/
H A Dsysfs-kernel-mm-damon6 please refer to Documentation/admin-guide/mm/damon/index.rst.
19 named '0' to 'N-1' under the kdamonds/ directory.
26 based on the current status. Writing 'commit' to this file
33 'tried_regions' directory of every scheme directory of this
37 removes contents of the 'tried_regions' directory. Writing
59 'N-1' under the contexts/ directory.
85 the file returns the last-written 'address unit' value.
112 auto-tuning target DAMON-observed access events ratio within
113 the given time interval (aggrs in same directory), in bp
120 the monitoring intervals auto-tuning target DAMON-observed
[all …]
H A Dsysfs-devices-soc5 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 …]
H A Dsysfs-bus-optee-devices1 What: /sys/bus/tee/devices/optee-ta-<uuid>/
4 Contact: op-tee@lists.trustedfirmware.org
6 OP-TEE bus provides reference to registered drivers under this directory. The <uuid>
8 are free to create needed API under optee-ta-<uuid> directory.
10 What: /sys/bus/tee/devices/optee-ta-<uuid>/need_supplicant
13 Contact: op-tee@lists.trustedfirmware.org
15 Allows to distinguish whether an OP-TEE based TA/device requires user-space
16 tee-supplicant to function properly or not. This attribute will be present for
17 devices which depend on tee-supplicant to be running.
H A Dsysfs-kernel-mm-memory-tiers3 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.
H A Dsysfs-ptp5 This directory contains files and directories
13 This directory contains the attributes of the Nth PTP
24 name" and to help distinguish PHY based devices from
25 MAC based ones. The string does not necessarily have
41 Write integer to re-configure it.
88 This directory contains one file for each programmable
110 This write-only file enables or disables external
128 This write-only file enables or disables periodic
139 This write-only file enables or disables delivery of
H A Dsysfs-firmware-opal-sensor-groups3 Contact: Linux for PowerPC mailing list <linuxppc-dev@lists.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@lists.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/drivers/fsi/
H A DKconfig1 # 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"
77 This option enables an FSI based SCOM device driver.
83 This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
[all …]
/linux/Documentation/admin-guide/
H A DREADME.rst11 --------------
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/fs/adfs/
H A Ddir_f.c1 // 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/drivers/thermal/testing/
H A Dcommand.c1 // SPDX-License-Identifier: GPL-2.0
12 * It resides in the "thermal-testing" directory under the debugfs root and
21 * # echo addtz > /sys/kernel/debug/thermal-testing/command
23 * That template will be represented as a subdirectory in the "thermal-testing"
24 * directory, for example
26 * # ls /sys/kernel/debug/thermal-testing/
32 * # echo tzaddtrip:0 > /sys/kernel/debug/thermal-testing/command
35 * template 0 (represented by the tz0 subdirectory in "thermal-testing").
37 * # ls /sys/kernel/debug/thermal-testing/tz0
45 * The initial temperature of a thermal zone based on a template can be set by
[all …]
/linux/drivers/mtd/parsers/
H A Dredboot.c1 // 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/Documentation/litmus-tests/
H A DREADME8 a kernel test module based on a litmus test, please see
9 tools/memory-model/README.
12 atomic (/atomic directory)
13 --------------------------
15 Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus
20 Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus
24 cmpxchg-fail-ordered-1.litmus
28 cmpxchg-fail-ordered-2.litmus
32 cmpxchg-fail-unordered-1.litmus
36 cmpxchg-fail-unordered-2.litmus
[all …]
/linux/tools/testing/ktest/examples/
H A DREADME1 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/include/xen/
H A Dxen-front-pgdir-shbuf.h1 /* 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/include/uapi/linux/
H A Dinotify.h1 /* 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/Documentation/admin-guide/mm/
H A Dnumaperf.rst14 under different domains, or "nodes", based on locality and performance
21 +------------------+ +------------------+
22 | Compute Node 0 +-----+ Compute Node 1 |
24 +--------+---------+ +--------+---------+
26 +--------+---------+ +--------+---------+
28 +------------------+ +--------+---------+
36 performance when accessing a given memory target. Each initiator-target
48 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
49 relative: /sys/devices/system/node/nodeX/access0/targets/nodeY -> ../../nodeY
51 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
[all …]
/linux/drivers/xen/
H A Dxen-front-pgdir-shbuf.c1 // 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/Documentation/admin-guide/perf/
H A Ddwc_pcie_pmu.rst9 Port in a Vendor-Specific Extended Capability named RAS D.E.S (Debug, Error
17 - one 64-bit counter for Time Based Analysis (RX/TX data throughput and
18 time spent in each low-power LTSSM state) and
19 - one 32-bit counter per event for Event Counting (error and non-error
24 Time Based Analysis
25 -------------------
28 throughput and time spent in each low-power LTSSM state by the controller.
31 - Group#0: Percentage of time the controller stays in LTSSM states.
32 - Group#1: Amount of data processed (Units of 16 bytes).
35 -------------------
[all …]
/linux/drivers/edac/
H A Dedac_device.h9 * 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
57 * mc/ <existing memory device directory>
58 * cpu/cpu0/.. <L1 and L2 block directory>
59 * /L1-cache/ce_count
61 * /L2-cache/ce_count
63 * cpu/cpu1/.. <L1 and L2 block directory>
64 * /L1-cache/ce_count
[all …]
/linux/tools/perf/
H A DMakefile1 # 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 || grep -E -c '^processor|^CPU[0-9]' /proc/cpuinfo) 2>/…
35 # Only pass canonical directory names as the output directory:
[all …]
/linux/fs/ceph/
H A Dioctl.h1 /* 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/scripts/clang-tools/
H A Dgen_compile_commands.py2 # 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)')
73 cmdfiles_in_dir(directory) global() argument
[all...]
/linux/tools/perf/pmu-events/
H A DREADME2 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 …]
/linux/Documentation/networking/device_drivers/ethernet/dlink/
H A Ddl2k.rst1 .. SPDX-License-Identifier: GPL-2.0
4 D-Link DL2000-based Gigabit Ethernet Adapter Installation
11 - Compatibility List
12 - Quick Install
13 - Compiling the Driver
14 - Installing the Driver
15 - Option parameter
16 - Configuration Script Sample
17 - Troubleshooting
25 - D-Link DGE-550T Gigabit Ethernet Adapter.
[all …]
/linux/Documentation/filesystems/
H A Df2fs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Flash-Friendly File System (F2FS)
10 NAND flash memory-based storage devices, such as SSD, eMMC, and SD cards, have
16 F2FS is a file system exploiting NAND flash memory-based storage devices, which
17 is based on Log-structured File System (LFS). The design has been focused on
21 Since a NAND flash memory-based storage device shows different characteristic
23 F2FS and its tools support various parameters not only for configuring on-disk
29 - git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git
33 - linux-f2fs-devel@lists.sourceforge.net
37 - https://bugzilla.kernel.org/enter_bug.cgi?product=File%20System&component=f2fs
[all …]

12345678910>>...32