| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /kernel/linux/linux-5.10/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
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/arch/h8300/include/asm/ |
| D | pgtable.h | 6 #define PAGE_NONE __pgprot(0) /* these mean nothing to NO_MM */
7 #define PAGE_SHARED __pgprot(0) /* these mean nothing to NO_MM */
8 #define PAGE_COPY __pgprot(0) /* these mean nothing to NO_MM */
9 #define PAGE_READONLY __pgprot(0) /* these mean nothing to NO_MM */
10 #define PAGE_KERNEL __pgprot(0) /* these mean nothing to NO_MM */
29 * These would be in other places but having them here reduces the diffs.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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 */
|
| /kernel/linux/linux-5.10/Documentation/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
85 user_pac_address_keys and struct user_pac_generic_keys). These can be
94 requesting these two separate cpu features to be enabled. The current KVM
96 these userspace flags are checked before enabling pointer authentication.
98 if support is added in the future to allow these two features to be
105 Additionally, when these vcpu feature flags are not set then KVM will
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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)
|
| /kernel/linux/linux-5.10/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)
|
| /kernel/linux/linux-5.10/drivers/scsi/arm/ |
| D | Kconfig | 11 Acorn system with one of these, say Y. If unsure, say N.
51 Acorn system with one of these, say Y. If unsure, say N.
58 system with one of these, say Y, otherwise say N.
65 you have one of these, say Y. If unsure, say N.
76 Acorn system with one of these, say Y. If unsure, say N.
84 system with one of these, say Y. If unsure, say N.
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-5.10/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 */
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|