Searched full:under (Results 1 – 25 of 701) sorted by relevance
12345678910>>...29
| /Documentation/ABI/stable/ |
| D | sysfs-hypervisor-xen | 5 Description: If running under Xen:
14 Description: If running under Xen:
23 Description: If running under Xen:
32 Description: If running under Xen:
54 Description: If running under Xen:
63 Description: If running under Xen:
71 Description: If running under Xen:
80 Description: If running under Xen:
87 Description: If running under Xen:
95 Description: If running under Xen:
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-hypervisor-xen | 5 Description: If running under Xen:
16 Description: If running under Xen:
34 Description: If running under Xen:
43 Description: If running under Xen:
|
| D | sysfs-bus-optee-devices | 6 OP-TEE bus provides reference to registered drivers under this directory. The <uuid>
8 are free to create needed API under optee-ta-<uuid> directory.
|
| D | sysfs-class-led-flash | 78 * led-under-voltage
82 * controller-under-voltage
84 controller is below the limit under which strobing the
|
| D | sysfs-class-bdi | 26 Files under /sys/class/bdi/<bdi>/
34 Under normal circumstances each device is given a part of the
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 65 Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y.
136 Each memcg has its own private LRU. Now, its handling is under global
137 VM's control (means that it's handled under global pgdat->lru_lock).
139 list management functions under pgdat->lru_lock.
158 to be very small rather than GB. Many races found in the test under
161 (Memory behavior under GB and Memory behavior under MB shows very
190 under cpuset.::
234 run jobs under child_a and child_b
254 and do task move, mkdir, rmdir etc...under this.
272 Run malloc(100M) program under this. You'll see 60M of swaps.
[all …]
|
| /Documentation/iio/ |
| D | iio_configfs.rst | 21 Then, mount the configfs filesystem (usually under /config directory)::
27 under /config/iio. Next chapters will describe available IIO configuration
35 under /config/iio/triggers.
76 Each trigger type has its own directory under /config/iio/triggers. Loading
88 users to create hrtimer triggers under /config/iio/triggers/hrtimer.
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 7 which is driven by the I2C bus master driver under test. The GPIO fault
26 because the bus master under test will not be able to clock. It should detect
36 master under test should detect this condition and trigger a bus recovery (see
63 above, the bus master under test should detect this condition and try a bus
89 Here, we want to simulate the condition where the master under test loses the
99 Arbitration lost is achieved by waiting for SCL going down by the master under
115 This fault injector will create a Kernel panic once the master under test
130 under test. A good starting point for using this fault injector is::
|
| /Documentation/admin-guide/ |
| D | bootconfig.rst | 92 Moreover, sub-keys and a value can coexist under a parent key.
99 Note, since there is no syntax to put a raw value directly under a
110 Also, the order of the value node under a key is fixed. If there
181 To do this operation, Linux kernel provides "bootconfig" command under
203 key-value entries) must be under 1024 nodes.
208 will be under 100 entries and smaller than 8KB, so it would be enough.
220 a root (prefix) key node and find key-values under that node.
237 keys under the prefix node with xbc_node_for_each_key_value().
239 But the most typical usage is to get the named value under prefix
240 or get the named array under prefix as below::
|
| /Documentation/s390/ |
| D | driver-model.rst | 12 structures under devices/::
35 be found under bus/ccw/devices/.
52 notify function under 1.2), piping 0 to online will forcibly delete
57 There is also some data exported on a per-subchannel basis (see under
84 under include/asm/ccwdev.h::
271 Channel paths show up, like subchannels, under the channel subsystem root (css0)
301 xpram shows up under devices/system/ as 'xpram'.
306 For each cpu, a directory is created under devices/system/cpu/. Each cpu has an
316 The netiucv driver creates an attribute 'connection' under
320 Netiucv connections show up under devices/iucv/ as "netiucv<ifnum>". The interface
|
| /Documentation/userspace-api/media/ |
| D | fdl-appendix.rst | 46 placed by the copyright holder saying it can be distributed under the
78 :ref:`Document <fdl-document>` is released under this License.
85 :ref:`Document <fdl-document>` is released under this License.
138 You may also lend copies, under the same conditions stated above, and
192 of the :ref:`Document <fdl-document>` under the conditions of sections
194 that you release the Modified Version under precisely this License, with
232 :ref:`Modified Version <fdl-modified>` under the terms of this
324 documents released under this License, under the terms defined in
353 :ref:`Document <fdl-document>` and other documents released under this
360 it individually under this License, provided you insert a copy of this
[all …]
|
| /Documentation/arm/sa1100/ |
| D | lart.rst | 11 is under development, with plenty of others in different stages of
14 The hardware designs for this board have been released under an open license;
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 15 paths to be tested in the code under test; this is only possible if the code
16 under test is very small and does not have any external dependencies outside of
21 tests to be written in userspace and run on the kernel under test; this is true
49 should allow all possible code paths to be tested in the code under test; this
50 is only possible if the code under test is very small and does not have any
60 code under test. For example, someone might write an end-to-end test for the
|
| /Documentation/admin-guide/mm/ |
| D | cma_debugfs.rst | 8 Each CMA zone represents a directory under <debugfs>/cma/, indexed by the
13 The structure of the files created under that directory is as follows:
|
| D | memory-hotplug.rst | 11 Because Memory Hotplug is still under development, contents of this text will
109 - Memory hotplug (under ACPI Support menu) (``CONFIG_ACPI_HOTPLUG_MEMORY``)
115 - ACPI0004,PNP0A05 and PNP0A06 Container Driver (under ACPI Support menu)
127 is described under ``/sys/devices/system/memory`` as::
146 Under each memory block, you can see 5 files:
282 be hotplugged. Currently offline blocks keep their state. It is possible, under
335 migratable. Under current Linux, migratable pages are anonymous pages and
375 A memory block under ZONE_MOVABLE is considered to be able to be offlined
376 easily. But under some busy state, it may return -EBUSY. Even if a memory
383 offlining higher and to guarantee unplugging memory under any situation. But
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | cirrus,clps711x-intc.txt | 20 8: TC1OI TC1 under flow
21 9: TC2OI TC2 under flow
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | prcm.txt | 3 Power Reset and Clock Manager lists the device clocks and clockdomains under
5 each describing one module and the clock hierarchy under it. see [1] for
|
| /Documentation/process/ |
| D | license-rules.rst | 8 The Linux Kernel is provided under the terms of the GNU General Public
28 Aside from that, individual files can be provided under a dual license,
29 e.g. one of the compatible GPL variants and alternatively under a
48 under which the content of the file is contributed. SPDX license
125 to be selected. For example, some dtsi files are available under dual
431 determining the exact license under which the source code of the module
441 "GPL" Module is licensed under GPL version 2. This
452 module source is dual licensed under a
457 module is dual licensed under a GPL v2
460 "Dual BSD/GPL" The module is dual licensed under a GPL v2
[all …]
|
| /Documentation/staging/ |
| D | speculation.rst | 61 Under speculation, the first call to load_array() may return the value
71 respected even under speculation. Architectures which are affected by
79 value that is bounded to [0, size) even under cpu speculation
|
| /Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 8 nfsd is controlled mainly by pseudofiles under the "nfsd" filesystem,
32 For more detail about files under nfsd/ and what they control, see
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 8 Nice levels were always pretty weak under Linux and people continuously
11 Unfortunately that was not that easy to implement under the old
84 run audio (and other multimedia) apps under RT priorities such as
109 and forcing audio apps to run under the more dangerous SCHED_FIFO
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imx-pinctrl.txt | 28 imx*-pinfunc.h under device tree source folder. The last integer CONFIG is
46 1. We have pin function node defined under iomux controller node to represent
49 to be defined under that specific function node.
|
| /Documentation/leds/ |
| D | leds-class-multicolor.rst | 4 Multicolor LED handling under Linux
17 array. These files are children under the LED parent node created by the
21 Each colored LED will be indexed under the multi_* files. The order of the
|
| /Documentation/devicetree/bindings/gpio/ |
| D | spear_spics.txt | 4 Cell spi controller through its system registers, which otherwise remains under
5 PL022 control. If chipselect remain under PL022 control then they would be
|
| /Documentation/scsi/ |
| D | qlogicfas.rst | 59 Make sure it works properly under DOS. You should also do an initial FDISK
86 Remember, if it doesn't work under DOS, it probably won't work under
|
12345678910>>...29