| /linux/drivers/char/hw_random/ |
| H A D | Kconfig | 28 This driver provides kernel-side support for a generic Random
43 This driver provides kernel-side support for the Random Number
57 This driver provides kernel-side support for the Random Number
70 This driver provides kernel-side support for the True Random Number
83 This driver provides kernel-side support for the Random Number
95 This driver provides kernel-side support for the Random Number
107 This driver provides kernel-side support for the Random Number
120 This driver provides kernel-side support for the Random Number
133 This driver provides kernel-side support for the RNG200
147 This driver provides kernel-side support for the Random Number
[all …]
|
| /linux/Documentation/usb/ |
| H A D | gadget_serial.rst | 57 side driver. It runs on a Linux system that has USB device side
84 On the device-side Linux system, the gadget serial driver looks
87 On the host-side system, the gadget serial device looks like a
92 The host side driver can potentially be any ACM compliant driver
98 With the gadget serial driver and the host side ACM or generic
100 the host and the gadget side systems as if they were connected by a
111 side kernel for "Support for USB Gadgets", for a "USB Peripheral
128 side Linux system. You can add this to the start up scripts, if
149 either the Windows or Linux ACM driver on the host side. If gadget
151 Linux generic serial driver on the host side. Follow the appropriate
[all …]
|
| /linux/Documentation/RCU/ |
| H A D | lockdep.rst | 8 aware of when each task enters and leaves any flavor of RCU read-side
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
83 1. An RCU read-side critical section (implicit), or
88 RCU read-side critical sections, in case (2) the ->file_lock prevents
99 complain even if this was used in an RCU read-side critical section unless
107 traversal primitives check for being called from within an RCU read-side
111 false and they are called from outside any RCU read-side critical section.
[all …]
|
| H A D | checklist.rst | 18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
28 read-side primitives is critically important.
59 2. Do the RCU read-side critical sections make proper use of
63 under your read-side code, which can greatly increase the
68 rcu_read_lock_sched(), or by the appropriate update-side lock.
72 spinlock also enters an RCU read-side critical section.
78 Letting RCU-protected pointers "leak" out of an RCU read-side
82 *before* letting them out of the RCU read-side critical section.
159 perfectly legal (if redundant) for update-side code to
[all …]
|
| H A D | whatisRCU.rst | 103 b. Wait for all previous readers to complete their RCU read-side
166 reclaimer that the reader is entering an RCU read-side critical
167 section. It is illegal to block while in an RCU read-side
169 can preempt RCU read-side critical sections. Any RCU-protected
170 data structure accessed during an RCU read-side critical section
176 or interrupts also enters an RCU read-side critical section.
177 Acquiring a spinlock also enters an RCU read-side critical
180 Sleeplocks do *not* enter RCU read-side critical sections.
187 reclaimer that the reader is exiting an RCU read-side critical
189 or interrupts also exits an RCU read-side critical section.
[all …]
|
| H A D | lockdep-splat.rst | 15 RCU read-side critical section or (2) holding the right update-side lock.
72 This form says that it must be in a plain vanilla RCU read-side critical
84 code was invoked either from within an RCU read-side critical section
89 On the other hand, perhaps we really do need an RCU read-side critical
104 read-side critical section, which again would have suppressed the
|
| /linux/drivers/block/rnbd/ |
| H A D | README | 12 on the client side as local block devices.
26 Server side:
29 Client side:
39 mapped from the server side. After the session to the server machine is
40 established, the mapped device will appear on the client side under
51 to the block device on the server side by concatenating dev_search_path
73 information: side, max_hw_sectors, etc.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-frequency-admv1013 | 18 side.
24 Read/write value for the Local Oscillatior Feedthrough Offset Calibration Q Positive side.
31 side.
38 side.
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 20 updaters do not block readers, which means that RCU's read-side
74 of all pre-existing RCU read-side critical sections. An RCU read-side
77 RCU treats a nested set as one big RCU read-side critical section.
131 | Second, even when using synchronize_rcu(), the other update-side |
173 The RCU read-side critical section in do_something_dlm() works with
190 In order to avoid fatal problems such as deadlocks, an RCU read-side
192 Similarly, an RCU read-side critical section must not contain anything
198 be good to be able to use RCU to coordinate read-side access to linked
370 outermost RCU read-side critical section containing that
387 #. Wait for all pre-existing RCU read-side critical sections to complete
[all …]
|
| /linux/Documentation/litmus-tests/rcu/ |
| H A D | RCU+sync+read.litmus | 7 * sees all stores done in prior RCU read-side critical sections. Such
8 * read-side critical sections would have ended before the grace period ended.
11 * other things) that an RCU read-side critical section cannot span a grace period.
|
| /linux/tools/include/uapi/ |
| H A D | README | 47 was pushed back on from the kernel side, when tooling modified the
52 notification mechanism to look at new kernel side changes.
57 tooling, driven by non-fatal warnings on the tooling side build when
66 The tooling policy is to always pick up the kernel side headers as-is,
69 side.
|
| /linux/sound/pci/hda/ |
| H A D | Kconfig | 98 tristate "KUnit test for Cirrus side-codec library" if !KUNIT_ALL_TESTS
104 This builds KUnit tests for the cirrus side-codec library.
123 tristate "Build CS35L41 HD-audio side codec support for I2C Bus"
133 Say Y or M here to include CS35L41 I2C HD-audio side codec support
136 comment "Set to Y if you want auto-loading the side codec driver"
150 Say Y or M here to include CS35L41 SPI HD-audio side codec support
153 comment "Set to Y if you want auto-loading the side codec driver"
160 tristate "Build CS35L56 HD-audio side codec support for I2C Bus"
177 tristate "Build CS35L56 HD-audio side codec support for SPI Bus"
194 tristate "Build TAS2781 HD-audio side codec support for I2C Bus"
[all …]
|
| /linux/drivers/char/ipmi/ |
| H A D | Kconfig | 118 The driver implements the BMC side of the KCS contorller, it
119 provides the access of KCS IO space for BMC side.
130 The driver implements the BMC side of the KCS contorller, it
131 provides the access of KCS IO space for BMC side.
140 Provides a BMC-side character device implementing IPMI
171 implements the BMC side of the BT interface.
178 management (BMC) side.
180 The driver implements the BMC side of the SMBus system
|
| /linux/Documentation/driver-api/ |
| H A D | io-mapping.rst | 49 io_mapping_map_local_wc() has a side effect on X86 32bit as it disables
50 migration to make the mapping code work. No caller can rely on this side
53 io_mapping_map_atomic_wc() has the side effect of disabling preemption and
72 undoes the side effects of the mapping functions.
80 This works like io_mapping_map_atomic/local_wc() except it has no side
|
| /linux/include/uapi/linux/netfilter/ |
| H A D | xt_recent.h | 34 __u8 side; member
43 __u8 side; member
|
| /linux/Documentation/staging/ |
| H A D | speculation.rst | 17 absence of data in caches. Such state may form side-channels which can be
67 Mitigating speculation side-channels
72 speculation-based side-channels are expected to implement these
76 prevent information from being leaked via side-channels.
|
| /linux/Documentation/networking/ |
| H A D | tc-queue-filters.rst | 8 to a single queue on both the transmit and receive side.
10 On the transmit side:
22 Likewise, on the receive side, the two filters for selecting set of
|
| /linux/drivers/infiniband/ulp/rtrs/ |
| H A D | README | 11 possibility to either write data from an sg list to the remote side
12 or to request ("read") data transfer from the remote side into a given
29 server side for a given client for rdma transfer. A session
36 chunks reserved for him on the server side. Their number, size and addresses
49 discussed in LPC RDMA MC 2019. When always_invalidate=Y, on the server side we
97 side or network outage in an absence of IO.
123 on the server side and rdma writes there the user data, user header and the
140 on the server side and rdma writes there the user data, user header and the
163 on the server side and rdma writes there the user header and the
182 on the server side and rdma writes there the user header and the
|
| /linux/Documentation/hwmon/ |
| H A D | ina2xx.rst | 82 The INA219 is a high-side current shunt and power monitor with an I2C
86 The INA220 is a high or low side current shunt and power monitor with an I2C
92 INA230 and INA231 are high or low side current shunt and power monitors
96 INA260 is a high or low side current and power monitor with integrated shunt
99 The SY24655 is a high- and low-side current shunt and power monitor with an I2C
|
| /linux/drivers/usb/usbip/ |
| H A D | usbip_common.c | 687 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
709 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_iso()
771 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) { in usbip_recv_xbuff()
828 if (ud->side == USBIP_STUB || ud->side == USBIP_VUDC) in usbip_recv_xbuff()
|
| /linux/Documentation/PCI/endpoint/ |
| H A D | pci-vntb-howto.rst | 11 be followed in the host side and EP side is given below. For the hardware
133 lspci Output at Host side
158 The host side software follows the standard NTB software architecture in Linux.
159 All the existing client side NTB utilities like NTB Transport Client and NTB
|
| /linux/drivers/block/ |
| H A D | swim.c | 31 unsigned char side; member
458 int side, int track, in swim_read_sector() argument
470 swim_head(base, side); in swim_read_sector()
471 swim_write(base, mode0, side); in swim_read_sector()
487 if ((header.side != side) || (header.track != track) || in swim_read_sector()
500 int side, track, sector; in floppy_read_sectors() local
509 side = x / fs->secpertrack; in floppy_read_sectors()
514 ret = swim_read_sector(fs, side, track, sector, in floppy_read_sectors()
|
| /linux/Documentation/rust/ |
| H A D | general-information.rst | 70 Abstractions are Rust code wrapping kernel functionality from the C side.
72 In order to use functions and types from the C side, bindings are created.
74 the C side.
77 a ``struct mutex`` from the C side and calls its functions through the bindings.
124 wrapper function to ``rust/helpers/`` to make it available for the Rust side as
|
| /linux/drivers/crypto/allwinner/ |
| H A D | Kconfig | 32 Select this option if you want to provide kernel-side support for
86 Select this option if you want to provide kernel-side support for
94 Select this option if you want to provide kernel-side support for
129 Select this option if you want to provide kernel-side support for
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-aspeed-vuart | 4 Description: Configures which IO port the host side of the UART
12 Description: Configures which interrupt number the host side of
|