Searched full:these (Results 1 – 25 of 1737) sorted by relevance
12345678910>>...70
| /Documentation/ABI/testing/ |
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
104 These sysfs values expose the TIOCGSERIAL interface via
113 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| D | sysfs-class-fc_host | 5 These files contain the number of congestion notification
13 These files contain the number of link integrity error
21 These files contain the number of delivery related errors
|
| D | sysfs-class-fc_remote_ports | 5 These files contain the number of congestion notification
13 These files contain the number of link integrity error
21 These files contain the number of delivery related errors
|
| /Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
|
| /Documentation/bpf/ |
| D | fs_kfuncs.rst | 10 BPF kfuncs can be used to get these data.
16 To avoid recursions, these kfuncs follow the following rules:
18 1. These kfuncs are only permitted from BPF LSM function.
19 2. These kfuncs should not call into other LSM hooks, i.e. security_*(). For
|
| /Documentation/trace/coresight/ |
| D | coresight-perf.rst | 40 If you see these above, then your system is tracing CoreSight data
94 minimum level of functionality is met. The scripts that launch these
95 tests are in the same directory. These will all look like:
102 These perf record tests will not run if the tool binaries do not exist
105 CoreSight support or remove these binaries in order to not have these
108 These tests will log historical results in the current working
115 These statistic files log some aspects of the AUX data sections in
123 multiple times and all these csv files will have more and more data
127 This means sometimes these tests fail as they don't capture all the
132 Be aware that some of these tests take quite a while to run, specifically
[all …]
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
26 match on these IP block-specific compatible strings.
|
| /Documentation/RCU/ |
| D | rcu.rst | 24 barriers. The fact that these operations are quite expensive
34 Therefore, as soon as a CPU is seen passing through any of these
43 counters. These counters allow limited types of blocking within
46 critical sections. These variants of RCU detect grace periods
47 by sampling these counters.
78 Of these, one was allowed to lapse by the assignee, and the
|
| /Documentation/rust/ |
| D | testing.rst | 18 These are the tests that come from the examples in the Rust documentation. They
24 These tests can be run via KUnit. For example via ``kunit_tool`` (``kunit.py``)
34 To use these KUnit doctests, the following must be enabled::
46 These documentation tests are typically examples of usage of any item (e.g.
68 For the kernel, however, these tests get transformed into KUnit test suites.
116 that forwards the call to KUnit instead. Importantly, these macros do not
129 Additionally, there are the ``#[test]`` tests. These can be run using the
135 (currently) and thus is fairly limited in what these tests can test.
|
| /Documentation/arch/arm64/ |
| D | pointer-authentication.rst | 30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
84 user_pac_address_keys and struct user_pac_generic_keys). These can be
93 requesting these two separate cpu features to be enabled. The current KVM
95 these userspace flags are checked before enabling pointer authentication.
97 if support is added in the future to allow these two features to be
104 Additionally, when these vcpu feature flags are not set then KVM will
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-dbg-g-register.rst | 43 For driver debugging purposes these ioctls allow test applications to
50 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.
74 These ioctls are optional, not all drivers may support them. However
75 when a driver supports these ioctls it must also support
77 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.
83 We recommended the v4l2-dbg utility over calling these ioctls directly.
160 these ioctls.
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 21 In short, your I2C driver code may need to know these codes in order
28 These are returned as negative numbers from most calls, with zero or
30 numbers associated with these symbols differ between architectures,
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
62 on these as the only way to detect incorrect data transfers.
113 transaction it can't. (These limitations can't be seen in
|
| /Documentation/virt/kvm/x86/ |
| D | errata.rst | 27 Clearing these bits in CPUID has no effect on the operation of the guest;
28 if these bits are set on hardware, the features will not be present on
31 **Workaround:** It is recommended to always set these bits in guest CPUID.
32 Note however that any software (e.g ``WIN87EM.DLL``) expecting these features
33 to be present likely predates these CPUID feature bits, and therefore
|
| /Documentation/arch/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
71 As the 'pdata' in the above examples indicates, these functions are
78 not support these functions should leave these function pointers set
84 The most common usage of these functions will probably be to specify
120 frequency. The OMAP PM interface contains functions for these
148 in these cases, the board file needs to do additional steps as follows:
|
| /Documentation/arch/arm/nwfpe/ |
| D | netwinder-fpe.rst | 28 These instructions are fully implemented.
40 These instructions are fully implemented. They store/load three words
73 These are fully implemented.
87 These are fully implemented.
93 These are fully implemented as well. They use the same algorithm as the
96 to the ARM manual. The manual notes these are defined only for single
110 These are fully implemented.
116 These are fully implemented.
121 These are implemented. URD is implemented using the same code as the RND
141 These are not implemented. They are not currently issued by the compiler,
[all …]
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v1.yaml | 14 have the liberty of choosing these. These combinations are called Operating
15 Performance Points aka OPPs. This document defines bindings for these OPPs
|
| /Documentation/virt/hyperv/ |
| D | coco.rst | 112 respectively, and not the guest Linux. Consequently, these exception handlers
118 support. While these CPUID flags are visible in fully-enlightened CoCo VMs,
119 the paravisor filters out these flags and the guest Linux does not see them.
120 Throughout the Linux kernel, explicitly testing these flags has mostly been
133 context), MMIO accesses to these devices must be encrypted references instead
143 TDX implementations of these callbacks are used. In paravisor mode, a Hyper-V
144 specific set of callbacks is used. These callbacks invoke the paravisor so
146 as necessary. See hv_vtom_init() where these callback are set up.
156 masking these complexities from the guest OS.
165 hypervisor. These hypercall sites test for a paravisor being present, and use
[all …]
|
| /Documentation/hwmon/ |
| D | asb100.rst | 20 These are custom ASICs available only on Asus mainboards. Asus refuses to
21 supply a datasheet for these chips. Thanks go to many people who helped
30 these, the ASB100-A also implements a single PWM controller for fans 2 and
66 .. [2] The min and max registers for these values appear to
|
| /Documentation/security/ |
| D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
86 What remains are variables that are updated rarely (e.g. GDT). These
97 access userspace memory without explicit expectation to do so. These
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 51 these pins. One register is the output enable register
54 you can get/set the status if these pins. They can be used for input
57 Most grabber board vendors use these pins to control an external chip
59 These pins are also used by some companies to drive remote control
65 line for your board. The important fields are these two::
76 (``BT848_GPIO_OUT_EN``) will be set as these pins must be driven by the
87 card installed, you might to check out if you can read these registers
|
| /Documentation/arch/x86/ |
| D | iommu.rst | 32 PS2 emulation. The regions of memory used for these devices are marked
34 regions will fail. Hence BIOS uses RMRR to specify these regions along with
35 devices that need to access these regions. OS is expected to setup
36 unity mappings for these regions for these devices to access these regions.
52 - Memory regions used by SMI/SMM, platform firmware, and platform hardware. These are generally exc…
|
| /Documentation/driver-api/ |
| D | device-io.rst | 54 historical accident, these are named byte, word, long and quad accesses.
63 8 bytes at a time. For these devices, the memcpy_toio(),
112 these cases, although only some platforms will honor the relaxed
126 addresses separate to the normal memory address space. Access to these
138 long. These functions are inb(), inw(),
142 Some variants are provided for these functions. Some devices require
171 These are the most generic accessors, providing serialization against other
174 should generally use these for any access to ``__iomem`` pointers.
183 DMA, these "relaxed" versions of the MMIO accessors only serialize against
185 might use these in a particularly performance sensitive fast path, with a
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | 15 Description: These files show with which CPLD versions have been burned
34 Description: These files show with which CPLD versions have been burned
43 Description: These files enable and disable the access to the JTAG domain.
66 Description: These files allow asserting system power cycling, switching
93 Description: These files show the system reset cause, as following: power
110 Description: These files show the system reset cause, as following: ComEx
123 Description: These files show with which CPLD versions have been burned
137 Description: These files show the system reset cause, as following:
152 Description: These files show system static topology identification
165 Description: These files show the system reset causes, as following: reset
[all …]
|
| /Documentation/accel/ |
| D | introduction.rst | 11 These devices can be either stand-alone ASICs or IP blocks inside an SoC/GPU.
12 Although these devices are typically designed to accelerate
14 is not limited to handling these types of accelerators.
20 or an IP inside a SoC (e.g. laptop web camera). These devices
29 addition, these devices will usually have some tools, such as profiler and
37 All these devices typically have different runtime user-space software stacks,
|
12345678910>>...70