| /kernel/linux/linux-5.10/block/partitions/ |
| D | Kconfig | 8 Say Y here if you would like to use hard disks under Linux which
29 Say Y here if you would like to use hard disks under Linux which
42 Say Y here if you would like to use hard disks under Linux which
75 Say Y here if you would like to be able to read the hard disk
87 Say Y here if you would like to use hard disks under Linux which
94 Say Y here if you would like to use hard disks under Linux which
101 Say Y here if you would like to use hard disks under Linux which
108 Say Y here if you would like to be able to read the hard disk
116 Say Y here if you would like to use hard disks under Linux which
150 Like most systems, Solaris x86 uses its own hard disk partition
[all …]
|
| /kernel/linux/linux-6.6/block/partitions/ |
| D | Kconfig | 10 Say Y here if you would like to use hard disks under Linux which
31 Say Y here if you would like to use hard disks under Linux which
44 Say Y here if you would like to use hard disks under Linux which
77 Say Y here if you would like to be able to read the hard disk
89 Say Y here if you would like to use hard disks under Linux which
96 Say Y here if you would like to use hard disks under Linux which
103 Say Y here if you would like to use hard disks under Linux which
110 Say Y here if you would like to be able to read the hard disk
118 Say Y here if you would like to use hard disks under Linux which
152 Like most systems, Solaris x86 uses its own hard disk partition
[all …]
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | entry.rst | 16 exceptions`_, `NMI and NMI-like exceptions`_.
64 invoked from low-level assembly code looks like this:
88 and then invokes the various entry work functions like ptrace, seccomp, audit,
94 returning to user space like tracing, audit, signals, task work etc. After
197 NMI and NMI-like exceptions
200 NMIs and NMI-like exceptions (machine checks, double faults, debug
206 in kernel mode (code patching). From user-space, they are treated like
207 interrupts, while from kernel mode they are treated like NMIs.
209 NMIs and other NMI-like exceptions handle state transitions without
229 Architecture-specific code looks like this:
[all …]
|
| D | asm-annotations.rst | 12 Some code like entries, trampolines, or boot code needs to be written in
21 Over time, the Linux kernel has adopted macros from various projects (like
42 annotated objects like this, tools can be run on them to generate more useful
76 1. ``SYM_FUNC_*`` -- to annotate C-like functions. This means functions with
83 Checking tools like ``objtool`` should ensure such marked functions conform
85 debugging information (like *ORC data*) automatically.
93 this code needs hints like ``UNWIND_HINT_REGS`` provided by developers.
111 conventions -- global and local. Like in C, they both align the functions to
124 So in most cases, developers should write something like in the following
|
| D | packing.rst | 51 1. Normally (no quirks), we would do it like this:
67 2. If QUIRK_MSB_ON_THE_RIGHT is set, we do it like this:
80 3. If QUIRK_LITTLE_ENDIAN is set, we do it like this:
94 like this:
104 5. If just QUIRK_LSW32_IS_FIRST is set, we do it like this:
118 6. If QUIRK_LSW32_IS_FIRST and QUIRK_MSB_ON_THE_RIGHT are set, we do it like
129 7. If QUIRK_LSW32_IS_FIRST and QUIRK_LITTLE_ENDIAN are set, it looks like
141 are set, it looks like this:
|
| /kernel/linux/linux-5.10/drivers/misc/lkdtm/ |
| D | refcount.c | 42 /* refcount_add() should behave just like refcount_inc() above. */
60 /* refcount_inc_not_zero() should behave just like refcount_inc() above. */
72 /* refcount_add_not_zero() should behave just like refcount_inc() above. */
156 * A refcount_dec_and_test() should act like refcount_dec() above when
171 * A refcount_sub_and_test() should act like refcount_dec_and_test()
186 * A refcount_sub_and_test() by zero when the counter is at zero should act like
243 * A refcount_add() should act like refcount_inc() above when starting
295 /* Should act like refcount_inc() above from saturated. */
306 /* Should act like refcount_inc() above from saturated. */
317 /* Should act like refcount_inc() above from saturated. */
[all …]
|
| /kernel/linux/linux-6.6/tools/memory-model/Documentation/ |
| D | README | 8 depending on what you know and what you would like to learn. Please note
15 like an overview of the types of low-level concurrency primitives
25 like a detailed intuitive understanding of LKMM, including
28 o You would like a detailed understanding of what your compiler can
32 LKMM, and would like a quick reference: cheatsheet.txt
35 of LKMM, and would like to learn about LKMM's requirements,
|
| /kernel/linux/linux-6.6/Documentation/trace/coresight/ |
| D | coresight-perf.rst | 13 can log such data with a perf record command like::
20 readable text with a command like::
24 You should find some sections of this file have AUX data blocks like::
68 enabled like::
87 kernel tree. Some tests will check some internal perf support like:
95 tests are in the same directory. These will all look like:
109 directory (e.g. tools/perf) and will be named stats-\*.csv like:
138 test like::
144 directory for later inspection like::
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 14 can write a makefile like follows::
24 and handles as if the source file were input like follows::
33 file like this::
53 Like in Make, a variable in Kconfig works as a macro variable. A macro
96 Like Make, Kconfig provides several built-in functions. Every function takes a
145 Kconfig adopts Make-like macro language, but the function call syntax is
148 A function call in Make looks like this::
156 to make "info" function print " hello", you can write like follows::
173 'call', like this::
241 Instead, you can do like follows so that any function call is statically
|
| /kernel/linux/linux-6.6/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 14 can write a makefile like follows::
24 and handles as if the source file were input like follows::
33 file like this::
53 Like in Make, a variable in Kconfig works as a macro variable. A macro
96 Like Make, Kconfig provides several built-in functions. Every function takes a
145 Kconfig adopts Make-like macro language, but the function call syntax is
148 A function call in Make looks like this::
156 to make "info" function print " hello", you can write like follows::
173 'call', like this::
241 Instead, you can do like follows so that any function call is statically
|
| /kernel/linux/linux-6.6/drivers/misc/lkdtm/ |
| D | refcount.c | 42 /* refcount_add() should behave just like refcount_inc() above. */
60 /* refcount_inc_not_zero() should behave just like refcount_inc() above. */
72 /* refcount_add_not_zero() should behave just like refcount_inc() above. */
156 * A refcount_dec_and_test() should act like refcount_dec() above when
171 * A refcount_sub_and_test() should act like refcount_dec_and_test()
228 * A refcount_add() should act like refcount_inc() above when starting
280 /* Should act like refcount_inc() above from saturated. */
291 /* Should act like refcount_inc() above from saturated. */
302 /* Should act like refcount_inc() above from saturated. */
314 /* Should act like refcount_inc() above from saturated. */
[all …]
|
| /kernel/linux/linux-6.6/scripts/mod/ |
| D | file2alias.c | 168 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
238 /* Returns the previous value, so it works like i++ or i-- */
399 /* Looks like: hid:bNvNpN */
417 /* Looks like: ieee1394:venNmoNspNverN */
441 /* Looks like: pci:vNdNsvNsdNbcNscNiN or <prefix>_pci:vNdNsvNsdNbcNscNiN. */
497 /* looks like: "ccw:tNmNdtNdmN" */
520 /* looks like: "ap:tN" */
530 /* looks like: "css:tN" */
540 /* Looks like: "serio:tyNprNidNexN" */
559 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | libv4l-introduction.rst | 72 applications work with v4l2 devices. These functions work exactly like
113 Those functions operate just like the gcc function ``dup()`` and
121 operates like the :c:func:`open()` function.
125 operates like the :c:func:`close()` function.
129 operates like the libc ``dup()`` function, duplicating a file handler.
133 operates like the :c:func:`ioctl()` function.
137 operates like the :c:func:`read()` function.
141 operates like the :c:func:`munmap()` function.
145 operates like the :c:func:`munmap()` function.
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | libv4l-introduction.rst | 72 applications work with v4l2 devices. These functions work exactly like
113 Those functions operate just like the gcc function ``dup()`` and
121 operates like the :c:func:`open()` function.
125 operates like the :c:func:`close()` function.
129 operates like the libc ``dup()`` function, duplicating a file handler.
133 operates like the :c:func:`ioctl()` function.
137 operates like the :c:func:`read()` function.
141 operates like the :c:func:`mmap()` function.
145 operates like the :c:func:`munmap()` function.
|
| /kernel/linux/linux-5.10/scripts/mod/ |
| D | file2alias.c | 156 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
226 /* Returns the previous value, so it works like i++ or i-- */
387 /* Looks like: hid:bNvNpN */
405 /* Looks like: ieee1394:venNmoNspNverN */
429 /* Looks like: pci:vNdNsvNsdNbcNscNiN. */
472 /* looks like: "ccw:tNmNdtNdmN" */
495 /* looks like: "ap:tN" */
505 /* looks like: "css:tN" */
515 /* Looks like: "serio:tyNprNidNexN" */
534 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | asm-annotations.rst | 12 Some code like entries, trampolines, or boot code needs to be written in
21 Over time, the Linux kernel has adopted macros from various projects (like
42 annotated objects like this, tools can be run on them to generate more useful
75 1. ``SYM_FUNC_*`` -- to annotate C-like functions. This means functions with
82 Checking tools like ``objtool`` should ensure such marked functions conform
84 debugging information (like *ORC data*) automatically.
92 this code needs hints like ``UNWIND_HINT_REGS`` provided by developers.
110 conventions -- global and local. Like in C, they both align the functions to
123 So in most cases, developers should write something like in the following
|
| /kernel/linux/linux-6.6/Documentation/sound/designs/ |
| D | oss-emulation.rst | 29 ``alias sound-slot-0 snd-card-0`` doesn't work any more like the old
65 (NOTE: Some distributions have the device files like /dev/midi0 and
90 define like this:
97 device on the second card to /dev/adsp1, define like below:
125 This will lead to some problems for some applications like quake or
168 quake, send a command via echo like the following:
191 for OSS devices, define like the following:
209 and restore it like
271 file, /proc/asound/cardX/oss_mixer, which will be like the following
288 send the command like the following:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/sound/designs/ |
| D | oss-emulation.rst | 29 ``alias sound-slot-0 snd-card-0`` doesn't work any more like the old
65 (NOTE: Some distributions have the device files like /dev/midi0 and
90 define like this:
97 device on the second card to /dev/adsp1, define like below:
125 This will lead to some problems for some applications like quake or
168 quake, send a command via echo like the following:
191 for OSS devices, define like the following:
209 and restore it like
271 file, /proc/asound/cardX/oss_mixer, which will be like the following
288 send the command like the following:
[all …]
|
| /kernel/linux/linux-6.6/kernel/time/ |
| D | clocksource-wdtest.c | 113 * Verify that jiffies-like clocksources get the manually in wdtest_func()
116 pr_info("--- Verify jiffies-like uncertainty margin.\n"); in wdtest_func()
128 * Verify that tsc-like clocksources are assigned a reasonable in wdtest_func()
131 pr_info("--- Verify tsc-like uncertainty margin.\n"); in wdtest_func()
138 pr_info("--- tsc-like times: %lu - %lu = %lu.\n", j2, j1, j2 - j1); in wdtest_func()
141 /* Verify tsc-like stability with various numbers of errors injected. */ in wdtest_func()
159 /* Verify tsc-like stability with clock-value-fuzz error injection. */ in wdtest_func()
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | sound.h | 17 #define SND_DEV_DSP16 5 /* Like /dev/dsp but 16 bits/sample */
27 #define SND_DEV_ADSP 12 /* Like /dev/dsp (obsolete) */
28 #define SND_DEV_AMIDI 13 /* Like /dev/midi (obsolete) */
29 #define SND_DEV_ADMMIDI 14 /* Like /dev/dmmidi (onsolete) */
|
| D | if_vlan.h | 43 VLAN_NAME_TYPE_PLUS_VID, /* Name will look like: vlan0005 */
44 VLAN_NAME_TYPE_RAW_PLUS_VID, /* name will look like: eth1.0005 */
45 VLAN_NAME_TYPE_PLUS_VID_NO_PAD, /* Name will look like: vlan5 */
46 VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD, /* Name will look like: eth0.5 */
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | sound.h | 17 #define SND_DEV_DSP16 5 /* Like /dev/dsp but 16 bits/sample */
27 #define SND_DEV_ADSP 12 /* Like /dev/dsp (obsolete) */
28 #define SND_DEV_AMIDI 13 /* Like /dev/midi (obsolete) */
29 #define SND_DEV_ADMMIDI 14 /* Like /dev/dmmidi (onsolete) */
|
| D | if_vlan.h | 43 VLAN_NAME_TYPE_PLUS_VID, /* Name will look like: vlan0005 */
44 VLAN_NAME_TYPE_RAW_PLUS_VID, /* name will look like: eth1.0005 */
45 VLAN_NAME_TYPE_PLUS_VID_NO_PAD, /* Name will look like: vlan5 */
46 VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD, /* Name will look like: eth0.5 */
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | packing.rst | 51 1. Normally (no quirks), we would do it like this:
67 2. If QUIRK_MSB_ON_THE_RIGHT is set, we do it like this:
80 3. If QUIRK_LITTLE_ENDIAN is set, we do it like this:
94 like this:
104 5. If just QUIRK_LSW32_IS_FIRST is set, we do it like this:
118 6. If QUIRK_LSW32_IS_FIRST and QUIRK_MSB_ON_THE_RIGHT are set, we do it like
129 7. If QUIRK_LSW32_IS_FIRST and QUIRK_LITTLE_ENDIAN are set, it looks like
141 are set, it looks like this:
|
| /kernel/linux/linux-6.6/arch/loongarch/include/asm/ |
| D | uaccess.h | 36 * space. It supports simple types like char and int, but not larger
37 * data types like structures or arrays.
63 * space. It supports simple types like char and int, but not larger
64 * data types like structures or arrays.
88 * space. It supports simple types like char and int, but not larger
89 * data types like structures or arrays.
118 * space. It supports simple types like char and int, but not larger
119 * data types like structures or arrays.
|