Searched full:other (Results 1 – 25 of 1853) sorted by relevance
12345678910>>...75
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-sec | 7 Only available for PF, and take no other effect on SEC.
47 Only available for PF, and take no other effect on SEC.
54 Available for both PF and VF, and take no other effect on SEC.
60 Available for both PF and VF, and take no other effect on SEC.
66 Available for both PF and VF, and take no other effect on SEC.
72 Available for both PF and VF, and take no other effect on SEC.
78 Available for both PF and VF, and take no other effect on SEC.
85 Available for both PF and VF, and take no other effect on SEC.
99 Only available for PF, and take no other effect on SEC.
105 and VF, and take no other effect on SEC.
[all …]
|
| D | debugfs-hisi-hpre | 74 Available for both PF and VF, and take no other effect on HPRE.
80 Available for both PF and VF, and take no other effect on HPRE.
86 Available for both PF and VF, and take no other effect on HPRE.
92 Available for both PF and VF, and take no other effect on HPRE.
98 Available for both PF and VF, and take no other effect on HPRE.
105 Available for both PF and VF, and take no other effect on HPRE.
119 Only available for PF, and take no other effect on HPRE.
125 and VF, and take no other effect on HPRE.
134 and take no other effect on HPRE.
147 Available for both PF and VF, and take no other effect on HPRE.
[all …]
|
| D | debugfs-hisi-zip | 67 Available for both PF and VF, and take no other effect on ZIP.
73 Available for both PF and VF, and take no other effect on ZIP.
79 Available for both PF and VF, and take no other effect on ZIP.
85 Available for both PF and VF, and take no other effect on ZIP.
91 Available for both PF and VF, and take no other effect on ZIP.
98 Available for both PF and VF, and take no other effect on ZIP.
112 Only available for PF, and take no other effect on ZIP.
118 and VF, and take no other effect on ZIP.
127 and take no other effect on ZIP.
140 Available for both PF and VF, and take no other effect on ZIP.
[all …]
|
| D | sysfs-class-scsi_tape | 18 reads, writes, and other SCSI commands issued to the tape
19 drive. An example of other SCSI commands would be tape
23 To determine the amount of time spent waiting for other I/O
33 The number of I/O requests issued to the tape drive other
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 50 2. Do all eHCA-Infiniband-related work on other CPUs, including
65 some other CPU.
78 occur on some other CPU and furthermore initiate all
79 Bluetooth activity on some other CPU.
103 do not offline any other CPUs, because doing so could force the
111 1. Force networking interrupts onto other CPUs.
112 2. Initiate any network I/O on other CPUs.
123 1. Force block-device interrupts onto some other CPU.
124 2. Initiate any block I/O on other CPUs.
135 1. Force block-device interrupts onto some other CPU.
[all …]
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 53 of sectors that are being re-synced by that node. No other
60 Each node has to communicate with other nodes when starting or ending
76 other nodes to acknowledge the message before proceeding. Only one
87 informs other nodes that the metadata has
94 informs other nodes that a resync is initiated or
104 informs other nodes that a device is being added to
165 received or other events that happened while waiting for the
231 other nodes from writing anywhere on the array.
234 environment when a resync is performed, it needs to tell other nodes
241 other nodes and other nodes remove the corresponding entry from the
[all …]
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 10 # of the recursive limitation is that drivers cannot negate features from other
14 # core requirement, and one uses "select" while the other uses "depends on" to
21 # negated by other drivers.
30 # other bells in the system cannot negate. The reason for this issue is
32 # with CORE, one uses "depends on" while the other uses "select". Another
|
| /Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 10 in different other namespaces (the rows):
28 other task living in a different namespace via a shared filesystem
31 other object in another namespace.
34 should not be equal from the VFS point of view. In other
|
| /Documentation/driver-api/ |
| D | wbrf.rst | 28 response to the radio frequencies of other components to mitigate the
32 of their particular frequencies so that other consumers can make relative
62 param to get other consumers properly notified.
64 `acpi_amd_wbrf_add_remove` with 'remove' param to get other consumers notified.
70 of frequency band change(add or remove) from other producers.
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 7 drivers can quite easily interconnect with other kernel subsystems using
55 appear as any other I2C bus to the system and makes it possible to connect
56 drivers for the I2C devices on the bus like any other I2C bus driver.
60 GPIO hammering (bitbang). It will appear as any other SPI bus on the system
62 any other SPI bus driver. For example any MMC/SD card can then be connected
67 the bus like any other W1 device.
86 any other NAND driving hardware.
90 any other serio bus to the system and makes it possible to connect drivers
91 for e.g. keyboards and other PS/2 protocol based devices.
|
| /Documentation/process/ |
| D | security-bugs.rst | 56 the fix or on any other disclosure channel without the permission of the
61 In other words our only interest is in getting bugs fixed. All other
66 Coordination with other groups
70 other groups focus on fixing issues in distros and coordinating
79 security team and other teams is difficult since for the kernel security
92 while an accepted fix has not yet been merged. In other words, until a
|
| D | code-of-conduct.rst | 26 * Showing empathy towards other community members
37 * Other conduct which could reasonably be considered inappropriate in a
49 comments, commits, code, wiki edits, issues, and other contributions that are
51 contributor for other behaviors that they deem inappropriate, threatening,
|
| D | stable-api-nonsense.rst | 31 get lots of other good benefits if your driver is in the main kernel
46 source, hidden source, binary blobs, source wrappers, or any other term
54 kernel source interfaces. They both depend on each other, but we will
185 - Other developers will add features to your driver.
186 - Other people will find and fix bugs in your driver.
187 - Other people will find tuning opportunities in your driver.
188 - Other people will update the driver for you when external interface
194 than any other operating system, and it supports these devices on more
195 different processor architectures than any other operating system, this
|
| /Documentation/filesystems/ |
| D | adfs.rst | 41 othmask=nnn The permission mask for ADFS 'other' permissions
55 - Other read
56 - Other write
70 Other read -> -r--r--r--
71 Other write -> --w--w--w-
72 Other read and filetype UnixExec -> ---x--x--x
74 Possible other mode permissions -> ----rwxrwx
|
| D | locks.rst | 35 for example. This gave rise to some other subtle problems if sendmail was
46 is to make flock() and fcntl() locks oblivious to each other. Both can
47 exists, and neither will have any effect on the other.
52 4.1.x and several other commercial Unices. The only OS's that support
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 22 to respond correctly. Other code may need to rely on YOUR code reporting
33 Note that the descriptions here are not exhaustive. There are other
34 codes that may be returned, and other cases where these codes should
35 be returned. However, drivers should not return other codes for these
48 transmit mode: some other master was transmitting different
53 to execute some other operation.
86 about probe faults other than ENXIO and ENODEV.)
|
| /Documentation/userspace-api/ |
| D | ELF.rst | 20 interpreter. Other PT_INTERP headers are ignored (since Linux 2.4.11).
26 (since Linux 2.6.6). Other PT_GNU_STACK headers are ignored.
33 program header of an executable is used. Other PT_GNU_PROPERTY headers
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 17 support and tools for Linux and many other operating systems).
29 signing, large files, Unicode support and other internationalization
32 the combination can provide a reasonable alternative to other network and
45 mount.cifs should be installed in the directory with the other mount helpers.
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 30 'arch_stack_walk_reliable', and other architectures must implement
42 but all other functions must be reported. These cases are described in
46 the stack or other unwind state is corrupt or otherwise unreliable. The
88 even if not caught by other checks, it is strongly recommended that
118 other code.
135 At function call boundaries the stack and other unwind state is expected to be
143 If an interrupt or other exception is taken while the stack or other unwind
151 exceptions (e.g. IRQ) but unreliable to unwind across other exceptions
222 are not required to unwind from other trampolines which modify the return
229 returns, but do transiently clobber the return address or other unwind state.
[all …]
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 71 by ``PR_SCHED_CORE_GET`` command. Should be 0 for all other commands.
87 Transferring a cookie between the current and other tasks is possible using
97 each other and share a core.
121 The scheduler tries its best to find tasks that trust each other such that all
154 each other. This is because the core scheduler does not have information about
156 communicate them. In other words, all tasks have a default cookie value of 0.
161 within such groups are considered to trust each other, but do not trust those
187 siblings run tasks which trust each other, when the kernel is executing
200 other (by tagging separately), then the guest to guest attacks would go away.
205 system to not trust every other untrusted task. While this could reduce
[all …]
|
| /Documentation/hwmon/ |
| D | lm83.rst | 32 Both are compatible with many other devices such as the LM84 and all
33 other ADM1021 clones. The main difference between the LM83 and the LM84
81 CPU. The two other sensors must be used to measure the temperature of
82 two other points of the motherboard. We suspect these points to be the
96 other second; reading them more often will do no harm, but will return
|
| /Documentation/trace/coresight/ |
| D | coresight-ect.rst | 15 devices and interconnects them via the Cross Trigger Matrix (CTM) to other
21 0 C 0----------->: : +======>(other CTI channel IO)
33 become active. The active channel is propagated to other CTIs via the CTM,
40 The CTIs are registered by the system to be associated with CPUs and/or other
56 a CTM to each other. On these systems a CTM index is declared to associate
62 The CTI devices appear on the existing CoreSight bus alongside the other
71 can be associated with other CoreSight devices, or other system hardware
167 the CTM to other connected devices.
171 (enable) the channel to other devices. This operation takes a channel
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 32 * OUR_CLAIM: output from us signaling to other hosts that we want the bus
36 sure that the other side doesn't want it also. A detailed explanation is
41 2. Waits a little bit for the other sides to notice (slew time, say 10
72 The GPIOs that the other sides use to claim the bus. Note that some
73 implementations may only support a single other master.
|
| /Documentation/devicetree/bindings/net/ |
| D | anarion-gmac.txt | 4 Please see stmmac.txt for the other unchanged properties.
8 - phy-mode: Should be "rgmii". Other modes are not currently supported.
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 10 hypervisor when running as a guest (under Xen, KVM or any other
16 booted at HYP. It can also be used by a hypervisor other than KVM
69 any other means (command line option, for example).
71 Any other value of r0/x0 triggers a hypervisor-specific handling,
|
12345678910>>...75