Searched full:like (Results 1 – 25 of 1310) sorted by relevance
12345678910>>...53
| /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 | 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:
|
| 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
|
| /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::
|
| /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
|
| /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.
|
| /Documentation/devicetree/bindings/arc/ |
| D | pct.txt | 4 CPU and cache events like cache misses and hits. Like conventional PCT there
|
| D | snps,archs-pct.yaml | 14 CPU and cache events like cache misses and hits. Like conventional PCT there
|
| /Documentation/ABI/stable/ |
| 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.
|
| /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 …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | google,cros-ec-i2c-tunnel.yaml | 17 other side of the EC (like a battery and PMIC). To get access to
20 The node for this device should be under a cros-ec node like
31 description: The EC bus we'd like to talk to.
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | sensor-groups.txt | 17 operations like clearing the min/max history of all
26 sensor groups like clearing min/max, enabling/disabling sensor
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-opal-sensor-groups | 8 like power, temperature, frequency, current, etc. They
10 different owners like CSM, Profiler, Job-Scheduler
|
| D | configfs-tsm | 51 (RO) A name for the format-specification of @outblob like
83 different privilege levels, like SEV-SNP "VMPL", specify the
103 provider for TVMs, like SEV-SNP running under an SVSM.
120 provider for TVMs, like SEV-SNP running under an SVSM.
138 provider for TVMs, like SEV-SNP running under an SVSM.
|
| /Documentation/networking/device_drivers/cable/ |
| 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
|
| /Documentation/ |
| 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:
|
| /Documentation/process/ |
| 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
|
| /Documentation/i2c/ |
| D | i2c-stub.rst | 22 operations. This allows for continuous byte reads like those supported by
33 The typical use-case is like this:
66 something like relayfs.
|
| /Documentation/mm/ |
| D | z3fold.rst | 17 To keep the determinism and simplicity, z3fold, just like zbud, always
22 Unlike zbud (but like zsmalloc for that matter) z3fold_alloc() does not
|
| /Documentation/i2c/busses/ |
| D | i2c-sis630.rst | 38 If you see something like this::
43 or like this::
48 or like this::
|
| /Documentation/fb/ |
| D | cmap_xfbdev.rst | 24 - X11 apps do something like the following when trying to use grayscale::
36 There's also named equivalents like gray1..x provided you have an rgb.txt.
54 that the app wants to match to. The above code is doing what looks like a least
|
| /Documentation/doc-guide/ |
| D | kernel-doc.rst | 44 the comment is formatted like a normal multi-line comment with a column
67 The general format of a function and function-like macro kernel-doc comment is::
234 It is possible to document nested structs and unions, like::
288 on a line of their own, like all other kernel-doc comments::
344 Object-like macro documentation
347 Object-like macros are distinct from function-like macros. They are
349 left parenthesis ('(') for function-like macros or not followed by one
350 for object-like macros.
352 Function-like macros are handled like functions by ``scripts/kernel-doc``.
353 They may have a parameter list. Object-like macros have do not have a
[all …]
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 24 the key(s) from an external device like a pcmcia flash disk
34 it will always look like the following::
44 modify. For lilo the simplest setup looks like the following
58 like the following::
123 for init like "single" or "emergency" as boot parameters.
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 6 Good development is like gardening, and codebases are our gardens. Tend to them
56 invariants with runtime checks - much like the way people working in
84 like in procfs. Part of the job of the debugging tools is to educate users and
114 like to help - otherwise they wouldn't be reporting the bug in the first place.
125 and perhaps even your documentation, too. Like anything else in life, the more
143 perhaps more robust. Just don't hesitate to abandon the idea if it looks like
160 often go astray - doing something because it seems like it'll be useful often
|
| /Documentation/spi/ |
| 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 …]
|
12345678910>>...53