| /linux-6.12.1/fs/nls/ |
| D | Kconfig | 44 native language character sets. These character sets are stored
46 codepage if you want to be able to read/write these filenames on
56 native language character sets. These character sets are stored
58 codepage if you want to be able to read/write these filenames on
68 native language character sets. These character sets are stored
70 codepage if you want to be able to read/write these filenames on
81 native language character sets. These character sets are stored in
83 codepage if you want to be able to read/write these filenames on
97 native language character sets. These character sets are stored in
99 codepage if you want to be able to read/write these filenames on
[all …]
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
104 These sysfs values expose the TIOCGSERIAL interface via
113 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /linux-6.12.1/Documentation/trace/coresight/ |
| D | coresight-perf.rst | 40 If you see these above, then your system is tracing CoreSight data
94 minimum level of functionality is met. The scripts that launch these
95 tests are in the same directory. These will all look like:
102 These perf record tests will not run if the tool binaries do not exist
105 CoreSight support or remove these binaries in order to not have these
108 These tests will log historical results in the current working
115 These statistic files log some aspects of the AUX data sections in
123 multiple times and all these csv files will have more and more data
127 This means sometimes these tests fail as they don't capture all the
132 Be aware that some of these tests take quite a while to run, specifically
[all …]
|
| /linux-6.12.1/Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /linux-6.12.1/include/linux/sunrpc/ |
| D | metrics.h | 11 * These statistics are not for detailed problem diagnosis, but simply
14 * These counters are not meant to be human-readable, but are meant to be
23 * arrays per-CPU because these counters are always modified behind locks.
39 * These counters give an idea about how many request
51 * These count how many bytes are sent and received for a
53 * particular procedure is putting on the network. These
71 * These statuses usually indicate error conditions.
|
| /linux-6.12.1/tools/memory-model/Documentation/ |
| D | ordering.txt | 15 2. Ordered memory accesses. These operations order themselves
23 some of these "unordered" operations provide limited ordering
46 Note well that many of these primitives generate absolutely no code
82 Second, some RMW atomic operations provide full ordering. These
113 Finally, RCU's grace-period primitives provide full ordering. These
115 synchronize_srcu() and so on. However, these primitives have orders
132 full ordering for these primitives. One way to obtain full ordering on
263 end in _release. These operations order their own store against all
321 and value-returning RMW operations whose names end in _acquire. These
441 Each of these two categories of unordered accesses has a section below:
[all …]
|
| /linux-6.12.1/drivers/scsi/arm/ |
| D | Kconfig | 11 Acorn system with one of these, say Y. If unsure, say N.
40 Acorn system with one of these, say Y. If unsure, say N.
47 system with one of these, say Y, otherwise say N.
54 you have one of these, say Y. If unsure, say N.
65 Acorn system with one of these, say Y. If unsure, say N.
73 system with one of these, say Y. If unsure, say N.
|
| /linux-6.12.1/arch/mips/include/uapi/asm/ |
| D | mman.h | 13 * Protections are chosen from these bits, OR'd together. The
40 /* These are linux-specific */
75 #define MADV_WILLNEED 3 /* will need these pages */
76 #define MADV_DONTNEED 4 /* don't need these pages */
78 /* common parameters: try to keep these consistent across architectures */
80 #define MADV_REMOVE 9 /* remove these pages & resources */
98 #define MADV_COLD 20 /* deactivate these pages */
99 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /linux-6.12.1/arch/xtensa/include/uapi/asm/ |
| D | mman.h | 19 * Protections are chosen from these bits, OR'd together. The
47 /* These are linux-specific */
84 #define MADV_WILLNEED 3 /* will need these pages */
85 #define MADV_DONTNEED 4 /* don't need these pages */
87 /* common parameters: try to keep these consistent across architectures */
89 #define MADV_REMOVE 9 /* remove these pages & resources */
106 #define MADV_COLD 20 /* deactivate these pages */
107 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /linux-6.12.1/fs/jffs2/ |
| D | LICENCE | 21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | device-io.rst | 54 historical accident, these are named byte, word, long and quad accesses.
63 8 bytes at a time. For these devices, the memcpy_toio(),
112 these cases, although only some platforms will honor the relaxed
126 addresses separate to the normal memory address space. Access to these
138 long. These functions are inb(), inw(),
142 Some variants are provided for these functions. Some devices require
171 These are the most generic accessors, providing serialization against other
174 should generally use these for any access to ``__iomem`` pointers.
183 DMA, these "relaxed" versions of the MMIO accessors only serialize against
185 might use these in a particularly performance sensitive fast path, with a
[all …]
|
| /linux-6.12.1/Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | 15 Description: These files show with which CPLD versions have been burned
34 Description: These files show with which CPLD versions have been burned
43 Description: These files enable and disable the access to the JTAG domain.
66 Description: These files allow asserting system power cycling, switching
93 Description: These files show the system reset cause, as following: power
110 Description: These files show the system reset cause, as following: ComEx
123 Description: These files show with which CPLD versions have been burned
137 Description: These files show the system reset cause, as following:
152 Description: These files show system static topology identification
165 Description: These files show the system reset causes, as following: reset
[all …]
|
| /linux-6.12.1/Documentation/virt/hyperv/ |
| D | coco.rst | 112 respectively, and not the guest Linux. Consequently, these exception handlers
118 support. While these CPUID flags are visible in fully-enlightened CoCo VMs,
119 the paravisor filters out these flags and the guest Linux does not see them.
120 Throughout the Linux kernel, explicitly testing these flags has mostly been
133 context), MMIO accesses to these devices must be encrypted references instead
143 TDX implementations of these callbacks are used. In paravisor mode, a Hyper-V
144 specific set of callbacks is used. These callbacks invoke the paravisor so
146 as necessary. See hv_vtom_init() where these callback are set up.
156 masking these complexities from the guest OS.
165 hypervisor. These hypercall sites test for a paravisor being present, and use
[all …]
|
| /linux-6.12.1/Documentation/security/ |
| D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
86 What remains are variables that are updated rarely (e.g. GDT). These
97 access userspace memory without explicit expectation to do so. These
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
26 match on these IP block-specific compatible strings.
|
| /linux-6.12.1/Documentation/arch/arm/nwfpe/ |
| D | netwinder-fpe.rst | 28 These instructions are fully implemented.
40 These instructions are fully implemented. They store/load three words
73 These are fully implemented.
87 These are fully implemented.
93 These are fully implemented as well. They use the same algorithm as the
96 to the ARM manual. The manual notes these are defined only for single
110 These are fully implemented.
116 These are fully implemented.
121 These are implemented. URD is implemented using the same code as the RND
141 These are not implemented. They are not currently issued by the compiler,
[all …]
|
| /linux-6.12.1/Documentation/rust/ |
| D | testing.rst | 18 These are the tests that come from the examples in the Rust documentation. They
24 These tests can be run via KUnit. For example via ``kunit_tool`` (``kunit.py``)
34 To use these KUnit doctests, the following must be enabled::
46 These documentation tests are typically examples of usage of any item (e.g.
68 For the kernel, however, these tests get transformed into KUnit test suites.
116 that forwards the call to KUnit instead. Importantly, these macros do not
129 Additionally, there are the ``#[test]`` tests. These can be run using the
135 (currently) and thus is fairly limited in what these tests can test.
|
| /linux-6.12.1/Documentation/arch/arm64/ |
| D | pointer-authentication.rst | 30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
84 user_pac_address_keys and struct user_pac_generic_keys). These can be
93 requesting these two separate cpu features to be enabled. The current KVM
95 these userspace flags are checked before enabling pointer authentication.
97 if support is added in the future to allow these two features to be
104 Additionally, when these vcpu feature flags are not set then KVM will
|
| /linux-6.12.1/tools/testing/selftests/net/forwarding/ |
| D | README | 7 Unfortunately, these namespaces can not be used with actual switching
41 These tests are written with switch ASICs in mind, but they can be run
65 various ways. A number of these variables can be overridden. The way these
72 Any of these variables can be overridden. Notably net/forwarding/lib.sh and
75 One way of overriding these variables is through the environment:
|
| /linux-6.12.1/include/linux/ |
| D | nfs_iostat.h | 10 * Generally these are not for detailed problem diagnosis, but
13 * These counters are not meant to be human-readable, but are meant
40 * These counters give a view of the data throughput into and out
46 * These counters can also help characterize which access methods
55 * These count the number of pages read or written via nfs_readpage(),
77 * These counters provide a low-overhead way of monitoring client
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | abi-testing.rst | 11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
|
| /linux-6.12.1/Documentation/bpf/ |
| D | fs_kfuncs.rst | 10 BPF kfuncs can be used to get these data.
16 To avoid recursions, these kfuncs follow the following rules:
18 1. These kfuncs are only permitted from BPF LSM function.
19 2. These kfuncs should not call into other LSM hooks, i.e. security_*(). For
|
| /linux-6.12.1/Documentation/arch/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
71 As the 'pdata' in the above examples indicates, these functions are
78 not support these functions should leave these function pointers set
84 The most common usage of these functions will probably be to specify
120 frequency. The OMAP PM interface contains functions for these
148 in these cases, the board file needs to do additional steps as follows:
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | vidioc-dbg-g-register.rst | 43 For driver debugging purposes these ioctls allow test applications to
50 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.
74 These ioctls are optional, not all drivers may support them. However
75 when a driver supports these ioctls it must also support
77 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.
83 We recommended the v4l2-dbg utility over calling these ioctls directly.
160 these ioctls.
|
| /linux-6.12.1/Documentation/i2c/ |
| D | fault-codes.rst | 21 In short, your I2C driver code may need to know these codes in order
28 These are returned as negative numbers from most calls, with zero or
30 numbers associated with these symbols differ between architectures,
34 codes that may be returned, and other cases where these codes should
35 be returned. However, drivers should not return other codes for these
62 on these as the only way to detect incorrect data transfers.
113 transaction it can't. (These limitations can't be seen in
|