Searched full:into (Results 1 – 25 of 1558) sorted by relevance
12345678910>>...63
| /Documentation/filesystems/ |
| D | idmappings.rst | 14 An idmapping is essentially a translation of a range of ids into another or the
37 idmapping is an order isomorphism from ``U`` into ``K``. So ``U`` and ``K`` are
50 dealing with subsets we can embed idmappings into each other, i.e. we can
126 of userspace ids into a range of kernel ids::
174 immediately translated into a kernel id according to the idmapping associated
212 then translate ``k11000`` into a userspace id in the second idmapping using the
215 /* Map the kernel id up into a userspace id in the second idmapping. */
221 /* Map the userspace id down into a kernel id in the second idmapping. */
224 /* Map the kernel id up into a userspace id in the first idmapping. */
233 into a kernel id according to the idmapping associated with the filesystem.
[all …]
|
| D | ramfs-rootfs-initramfs.rst | 27 With ramfs, there is no backing store. Files written into ramfs allocate
45 fake block device into the page cache (and copying changes back out), as well
65 One downside of ramfs is you can keep writing data into it until you fill
95 extracted into rootfs when the kernel boots up. After extracting, the kernel
100 archive is extracted into it, the kernel will fall through to the older code
107 linked into the linux kernel image. (The directory ``linux-*/usr`` is
111 such as ext2, that needed a driver built into the kernel), while the new
139 archive and links it into the resulting kernel binary. By default, this
144 initramfs archive, which will automatically be incorporated into the
183 or by the kernel build) back into its component files::
[all …]
|
| D | relay.rst | 14 clients write into the channel buffers using efficient write
15 functions; these automatically log into the current cpu's channel
21 The format of the data logged into the channel buffers is completely
44 message couldn't fit into a sub-buffer. Userspace can use this
86 regardless of whether a channel to write into exists or not, or even
87 whether the relay interface is compiled into the kernel or not. These
117 mmap() results in channel buffer being mapped into the caller's
267 number of sub-buffers by the sub-buffer size passed into relay_open().
299 The private_data passed into relay_open() allows clients to associate
337 subdivided into one or more sub-buffers. Messages are written into
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 34 I/O devices into low-power states (possibly lower-power than available in the
58 I/O devices into low-power states, which is done for :ref:`suspend-to-idle
60 are suspended during transitions into this state. For this reason, it should
79 energy savings as everything in the system is put into a low-power state, except
80 for memory, which should be placed into the self-refresh mode to retain its
89 suspended and put into low-power states. In many cases, all peripheral buses
118 It takes three system state changes to put it into hibernation and two system
122 creates a snapshot image of memory to be written into persistent storage. Next,
123 the system goes into a state in which the snapshot image can be saved, the image
124 is written out and finally the system goes into the target low-power state in
[all …]
|
| D | suspend-flows.rst | 13 system to get from the working state into one of the supported
19 For those sleep states, the transition from the working state of the system into
22 be clear from the context) and the transition back from the sleep state into the
65 put into uninterruptible sleep until the end of the subsequent system resume
71 to be frozen and to put themselves into uninterruptible sleep if so. [Note,
102 into the deepest available idle state. While doing that, each of them
124 :ref:`suspend-to-idle <s2idle>` sleep state into the working state:
154 uninterruptible sleep that they went into at that time and user space tasks
186 There are platforms that can go into a very deep low-power state internally
188 devices have been put into low-power states. On those platforms,
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-turris-mox-rwtm | 5 Description: (Read) Board version burned into eFuses of this Turris Mox board.
12 Description: (Read) MAC addresses burned into eFuses of this Turris Mox board.
20 as pair to the ECDSA private key burned into eFuses of this
29 during manufacturing and burned into eFuses. Can be 512 or 1024.
36 Description: (Read) Serial number burned into eFuses of this Turris Mox device.
|
| D | sysfs-ptp | 14 hardware clock registered into the PTP class driver
94 assignment may be changed by two writing numbers into
112 channel index followed by a "1" into the file.
114 index followed by a "0" into the file.
130 integers into the file: channel index, start time
141 events, write a "1" into the file. To disable events,
142 write a "0" into the file.
|
| D | sysfs-bus-iio-trigger-sysfs | 8 into an in kernel buffer. This approach can be valuable during
29 into the associated file, which will serve as the id of the
39 achieve this, one should write a positive integer into the
|
| /Documentation/power/ |
| D | pci.rst | 31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
46 specific value into one of its standard configuration registers. The second
53 to put the device that sent it into the full-power state. However, the PCI Bus
92 programmed to go into it. The second one, D3cold, is the state that PCI devices
94 to program a PCI device to go into D3cold, although there may be a programmable
95 interface for putting the bus the device is on into a state in which Vcc is
111 programmatically put into D0. Thus the kernel can switch the device back and
[all …]
|
| /Documentation/gpu/amdgpu/ |
| D | amdgpu-glossary.rst | 36 (memory or MMIO space) into the GPU's address space so the GPU can access
51 allow the GPU to remap VRAM and system resources into GPU virtual address
58 use by the GPU. These addresses can be mapped into the "GART" GPUVM page
59 table for use by the kernel driver or into per process GPUVM page tables
|
| /Documentation/process/ |
| D | 2.Process.rst | 39 community) is merged into the mainline kernel. The bulk of changes for a
67 As fixes make their way into the mainline, the patch rate will slow over
110 bug, and (2) already be merged into the mainline for the next development
143 Patches do not go directly from the developer's keyboard into the mainline
153 a patch gets into the kernel. What follows below is an introduction which
174 subsystem tree and into the -next trees (described below). When the
188 - Merging into the mainline. Eventually, a successful patch will be
189 merged into the mainline repository managed by Linus Torvalds. More
205 is to try to cut the process down to a single "merging into the mainline"
209 How patches get into the Kernel
[all …]
|
| D | 6.Followthrough.rst | 10 posting patches indicates a transition into the next stage of the process,
19 prevent the inclusion of your patches into the mainline.
116 entry into a subsystem maintainer's tree. How that works varies from one
127 Inclusion into a subsystem tree can bring a higher level of visibility to a
137 burner so that the remaining patches can be worked into shape and merged.
146 merged into the mainline kernel. Congratulations! Once the celebration is
149 Merging into the mainline brings its own challenges.
158 More importantly, though: inclusion into the mainline puts your code into
161 how many people will build your code into their kernels. And, of course,
169 negating all of the work you have done to get your patch into the mainline,
[all …]
|
| D | 1.Intro.rst | 12 merged into the official ("mainline") kernel, including automatic
42 assuming that the job is done when a patch is merged into the mainline.
56 kernel has evolved into a best-of-breed operating system component which
117 The importance of getting code into the mainline
121 learning how to work with the kernel community and get their code into the
132 - Code which has been merged into the mainline kernel is available to all
136 works, for the developer and for the user. Incorporation into the
151 which has been merged into the mainline has significantly lower
158 - Kernel code is subjected to review, both before and after merging into
189 There are, however, additional factors which should be taken into account
[all …]
|
| /Documentation/networking/ |
| D | xdp-rx-metadata.rst | 31 An XDP program can use these kfuncs to read the metadata into stack
33 consumers, an XDP program can store it into the metadata area carried
52 An XDP program can store individual metadata items into this ``data_meta``
61 program that redirects XDP frames into the ``AF_XDP`` socket (``XSK``) and
83 into the kernel. The kernel creates the ``skb`` out of the ``xdp_buff``
101 into devmaps and cpumaps.
107 in its ``skb``. If such a packet is later redirected into an ``XSK``,
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv-boot.rst | 27 switch into PV mode itself, the user can load encrypted guest
44 Subcode 10: Move into Protected Virtualization mode
47 that is necessary to move into PV mode.
76 Re-IPL into a protected mode is only possible via a detour into non
|
| /Documentation/core-api/ |
| D | symbol-namespaces.rst | 24 their exported symbols into separate namespaces. That is useful for
27 kernel. As of today, modules that make use of symbols exported into namespaces,
31 Additionally, it is possible to put symbols into a module namespace, strictly
37 Symbols can be exported into namespace using different methods. All of them are
46 available to export symbols into a certain namespace: EXPORT_SYMBOL_NS() and
49 preprocessor symbol. E.g. to export the symbol ``usb_stor_suspend`` into the
71 export all symbols defined in usb-common into the namespace USB_COMMON, add a
78 still be exported into the namespace that is passed as the namespace argument
93 Symbols exported using this macro are put into a module namespace. This
109 In order to use symbols that are exported into namespaces, kernel modules need
|
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 6 into vmlinux directly, to enable avoiding having to look for firmware from
15 into the kernel with CONFIG_EXTRA_FIRMWARE:
19 want to stuff the firmware into the boot initramfs.
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 16 transaction reservations are structured and accounted, and then move into how we
161 available to write the modification into the journal before we start making
163 enough to take into account the amount of metadata that the change might need to
167 take into account all the hidden changes that might occur.
171 the extent into the inode's extent map might require a split of the extent map
180 so that when we come to write the dirty metadata into the log we don't run out
220 offset into the log. A LSN carries the cycle in the upper 32 bits and the
235 into the log rather than basic blocks. Hence it technically isn't using LSNs to
241 and need to write into the log. The reserve head is used to prevent new
350 metadata into the log.
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | st,stm32-dma2d.yaml | 16 - Copying a part or the whole of a source image into a part or the whole of
18 - Copying a part or the whole of a source image into a part or the whole of
21 format and copy the result into a part or the whole of a destination image
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 31 Drivers will use one or both of these models to put devices into low-power
55 Devices may also be put into low-power states while the system is
61 operations on the device for this purpose. Devices put into low power
74 have been put into low-power states (at runtime), the effect may be very similar
77 into a state where even deeper power saving options are available.
188 they should be put into the full-power state. Those interrupts may or may not
215 majority of cases should and will) be put into a low-power state during a
226 When the system goes into a sleep state, each device's driver is asked to
227 suspend the device by putting it into a state compatible with the target
315 When the system goes into the freeze, standby or memory sleep state,
[all …]
|
| /Documentation/admin-guide/media/ |
| D | opera-firmware.rst | 14 from the windriver disk into this directory.
29 Copy them into /lib/firmware/ .
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-mmio.yaml | 57 will turn that line into an output line. Conversely, clearing a bit
58 will turn that line into an input.
61 will turn that line into an input line. Conversely, clearing a bit
62 will turn that line into an output.
|
| /Documentation/rust/ |
| D | general-information.rst | 15 kernel must opt into this behavior using the ``#![no_std]`` attribute.
106 into carefully reviewed and documented abstractions. Then users of these
117 By including a C header from ``include/`` into
132 access to the bindings into an as-safe-as-possible API that they expose to their
137 the sense that they turn the C interfaces into "idiomatic" Rust code. Basic
138 examples are to turn the C resource acquisition and release into Rust
139 constructors and destructors or C integer error codes into Rust's ``Result``\ s.
|
| /Documentation/trace/coresight/ |
| D | coresight-config.rst | 37 a matching device, either when the feature is loaded into the system, or when the
40 The load process involves interpreting the descriptor into a set of register
42 translated into appropriate register accesses. This interpretation makes it easy
47 will be programmed into the device hardware.
69 The current value of the parameter is loaded into the device when the feature
125 In this case 'strobing' is enabled & programmed into the ETMv4.
136 The set of configurations and features that are currently loaded into the
212 The configurations loaded into the CoreSight configuration management are
280 Custom configurations and / or features can be dynamically loaded into the
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | rockchip,rk3399-dmc.yaml | 61 memories are placed into power-down mode if bus is idle for PD_IDLE DFI
70 which memories are placed into self-refresh mode if bus is idle for
80 Memories are placed into self-refresh mode and memory controller clock
90 placed into self-refresh power down mode if bus is idle for
99 Defines the standby idle period in which memories are placed into
288 period in which memories are placed into power-down mode if bus is idle
294 period in which memories are placed into self-refresh mode if bus is idle
301 Memories are placed into self-refresh mode and memory controller clock
307 placed into self-refresh power down mode if bus is idle for
312 Defines the standby idle period in which memories are placed into
[all …]
|
12345678910>>...63