| /linux/tools/memory-model/Documentation/ |
| H A D | README | 8 depending on what you know and what you would like to learn. Please note
17 like an overview of the types of low-level concurrency primitives
26 o You would like to access lock-protected shared variables without
30 like a detailed intuitive understanding of LKMM, including
33 o You would like a detailed understanding of what your compiler can
36 o You would like to mark concurrent normal accesses to shared
42 LKMM, and would like a quick reference: cheatsheet.txt
45 of LKMM, and would like to learn about LKMM's requirements,
|
| /linux/Documentation/core-api/ |
| H A 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 …]
|
| H A 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
|
| H A D | dma-api-howto.rst | 25 "resource_size_t". The kernel manages device resources like registers as
85 an interface like dma_map_single(), which sets up any required IOMMU
129 something like __va(). [ EDIT: Update this when we integrate
206 The 24-bit addressing device would do something like this::
213 The standard 64-bit addressing device would do something like this::
218 error code like::
225 So typical code like::
235 it would look like this::
248 address you might do something like::
332 something like::
[all …]
|
| /linux/drivers/misc/lkdtm/ |
| H A 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 …]
|
| /linux/scripts/mod/ |
| H A D | file2alias.c | 45 * @fmt: printf(3)-like format
181 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
249 /* Returns the previous value, so it works like i++ or i-- */
378 /* Looks like: hid:bNvNpN */
396 /* Looks like: ieee1394:venNmoNspNverN */
419 /* Looks like: pci:vNdNsvNsdNbcNscNiN or <prefix>_pci:vNdNsvNsdNbcNscNiN. */
474 /* looks like: "ccw:tNmNdtNdmN" */
497 /* looks like: "ap:tN" */
505 /* looks like: "css:tN" */
513 /* Looks like: "serio:tyNprNidNexN" */
[all …]
|
| /linux/Documentation/trace/coresight/ |
| H A 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::
|
| /linux/Documentation/kbuild/ |
| H A 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
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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.
|
| /linux/Documentation/sound/designs/ |
| H A 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 …]
|
| /linux/kernel/time/ |
| H A D | clocksource-wdtest.c | 114 * Verify that jiffies-like clocksources get the manually in wdtest_func()
117 pr_info("--- Verify jiffies-like uncertainty margin.\n"); in wdtest_func()
129 * Verify that tsc-like clocksources are assigned a reasonable in wdtest_func()
132 pr_info("--- Verify tsc-like uncertainty margin.\n"); in wdtest_func()
139 pr_info("--- tsc-like times: %lu - %lu = %lu.\n", j2, j1, j2 - j1); in wdtest_func()
143 /* Verify tsc-like stability with various numbers of errors injected. */ in wdtest_func()
161 /* Verify tsc-like stability with clock-value-fuzz error injection. */ in wdtest_func()
|
| /linux/drivers/clk/ |
| H A D | clk_kunit_helpers.c | 58 * Just like clk_get(), except the clk is managed by the test case and is
80 * Just like of_clk_get(), except the clk is managed by the test case and is
102 * Just like clk_hw_get_clk(), except the clk is managed by the test case and
124 * Just like
165 * Just like clk_hw_register(), except the clk registration is managed by the
188 * Just like of_clk_hw_register(), except the clk registration is managed by
216 * Just like of_clk_add_hw_provider(), except the clk_hw provider is managed by
|
| /linux/arch/loongarch/include/asm/ |
| H A 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.
|
| /linux/include/uapi/linux/ |
| H A 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) */
|
| H A 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 */
|
| /linux/Documentation/spi/ |
| H A D | spi-summary.rst | 28 Unlike serial busses like USB or SMBus, even low level protocols for
30 (except for commodities like SPI memory chips).
44 - Sometimes SPI is used to daisy-chain devices, like shift registers.
79 sensors and codecs, to memory, to peripherals like USB controllers
138 for those calls, including ones for common transaction types like writing
155 data to filesystems stored on SPI flash like DataFlash; and others might
216 like the physical address of the controller's first register and its IRQ.
225 So for example arch/.../mach-*/board-*.c files might have code like::
242 And SOC-specific utility code might look something like::
282 small handful.) That might look like::
[all …]
|
| /linux/Documentation/process/ |
| H A D | botching-up-ioctls.rst | 19 only cover technicalities and not the big-picture issues like what the command
20 submission ioctl exactly should look like. Learning these lessons is probably
31 the kernel has special types like __u32, __s64. Use them.
47 diminishes the checking tools like sparse can provide. The macro
117 killable. GPUs just die and your users won't like you more if you hang their
137 derived from different clock domains like your main system clock (provided
154 Especially if your reference clock is something really slow like the display
187 that the per-device modeset objects like connectors share a namespace with
215 per-device settings, or for child objects with fairly static lifetimes (like
|
| /linux/Documentation/networking/device_drivers/cable/ |
| H A D | sb1000.rst | 107 root to do this. It's better to use a utility like sudo to execute
108 frequently used commands like this with root permissions if possible. If you
110 driver message like this at the console::
123 11. If you can't get site names (like www.yahoo.com) to resolve into
124 IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file
126 If this doesn't help, try something like ``ping -c 5 204.71.200.67`` to
137 interface. It looks like I'm connected but I can't even ping any
203 and try setting the delay to something like 60 microseconds with:
205 it out. If it still doesn't work or you like playing with the driver, you may
|
| /linux/Documentation/ |
| H A D | atomic_t.txt | 64 (which implies -fwrapv) and defines signed overflow to behave like
73 With this we also conform to the C/C++ _Atomic behaviour and things like
174 Except of course when a successful operation has an explicit ordering like:
184 subsequent. Therefore a fully ordered primitive is like having an smp_mb()
193 ordering inherent to the op. These barriers act almost like a full smp_mb():
220 Further, while something like:
228 as well. Similarly, something like:
283 compact code. The functions relate like:
336 which on LL/SC becomes something like:
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-devices-system-cpu | 70 The format is like 0-3, 8-11, 14,17.
81 The format is like 0-3, 8-11, 14,17.
95 The format is like 0-3, 8-11, 14,17.
104 The format is like 0-3, 8-11, 14,17.
115 The format is like 0-3, 8-11, 14,17. it's only used on s390.
126 The format is like 0-3, 8-11, 14,17. it's only used on s390.
|
| /linux/scripts/ |
| H A D | rustdoc_test_builder.rs | 8 //! The `rustdoc`-generated test names look like `{file}_{line}_{number}`, e.g.
9 //! `...path_rust_kernel_sync_arc_rs_42_0`. `number` is the "test number", needed in cases like
13 //! at all. In the future, we would like `rustdoc` to give us the Rust item path associated with
27 // The line we are looking for looks like one of the following: in main()
56 // For tests that get generated with `Result`, like above, `rustdoc` generates an `unwrap()` on in main()
|
| /linux/Documentation/driver-api/usb/ |
| H A D | gadget.rst | 75 to hardware, through registers, fifos, dma, irqs, and the like. The
127 - networking subsystem (for network gadgets, like the CDC Ethernet
170 hardware-specific, any more than network protocols like X11, HTTP, or
223 Like the Linux-USB host side API, this API exposes the "chunky" nature
226 protocols, USB resembles synchronous protocols like HDLC (N bytes per
240 needs to handle some differences. Use the API like this:
288 enumeration until some higher level component (like a user mode daemon)
383 act like a net2280, a pxa25x, or an sa11x0 in terms of available
415 Pengutronix and Auerswald GmbH. This is like CDC Ethernet, but it runs
424 Familiar tools like GDB and pthreads can be used to develop and debug
[all …]
|
| /linux/drivers/mtd/ubi/ |
| H A D | Kconfig | 6 UBI is a software layer above MTD layer which admits use of LVM-like
8 flash chips like wear and bad blocks and provides some other useful
87 volume. This is handy to make MTD-oriented software (like JFFS2)
98 UBI driver will transparently handle things like bad eraseblocks and
101 practical for read-only file systems, like squashfs.
|
| /linux/samples/trace_events/ |
| H A D | trace_custom_sched.h | 4 * Like the headers that use TRACE_EVENT(), the TRACE_CUSTOM_EVENT()
17 * TRACE_CUSTOM_EVENT() is just like TRACE_EVENT(). The first parameter
39 * The rest is just like the TRACE_EVENT() macro except that
79 * Just like the headers that create TRACE_EVENTs, the below must
|
| /linux/fs/fat/ |
| H A D | Kconfig | 12 files on them, i.e. MSDOS files will look and behave just like all
50 transparent, i.e. the MSDOS files look and behave just like all
95 like FAT to use. It should probably match the character set
100 instead if you would like to use UTF-8 encoded file names by default.
111 Set this if you would like to have "utf8" mount option set
|