Searched full:sibling (Results 1 – 25 of 27) sorted by relevance
12
| /Documentation/devicetree/ |
| D | of_unittest.rst | 72 struct device_node *sibling;
77 considering only child and sibling pointers. There exists another pointer,
79 a particular level the child node and all the sibling nodes will have a parent
142 replaces the current child and turns it into its sibling. So, when the testcase
183 sibling compared to the earlier structure (Figure 2). After attaching first
185 (i.e. test-child0) to become a sibling and makes itself a child node,
204 node's parent to its sibling or attaches the previous sibling to the given
205 node's sibling, as appropriate. That is it :)
|
| /Documentation/x86/ |
| D | mds.rst | 163 sibling threads are offline CPU buffer clearing is not required.
178 sibling after the store buffer got repartitioned and all entries are
179 available to the non idle sibling.
182 sibling has half of it available. The back from idle CPU could be then
183 speculatively exposed to contents of the sibling. The buffers are
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-leds-gt683r | 7 of one LED will update the mode of its two sibling devices as
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | twl-charger.txt | 9 if there is a sibling of the BCI node which is compatible with
|
| /Documentation/devicetree/bindings/usb/ |
| D | twlxxxx-usb.txt | 33 If a sibling node is compatible "ti,twl4030-bci", then it will find
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,versatile.yaml | 30 PCI host controller. Like the sibling board, it is done specifically
|
| /Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 127 from the sibling thread, as level 1 cache and branch target buffer
129 program running on the sibling thread may influence its peer's BTB to
235 sibling hyperthread sharing a physical processor core on simultaneous
248 a sibling hardware thread sharing the same physical core.
259 sibling thread from controlling branch target buffer. In addition,
320 in the sibling hyperthread can be mitigated by the administrator,
522 sibling thread when the user program is running, and use IBPB to
561 To mitigate guest-to-guest attacks from sibling thread when SMT is
562 in use, an untrusted guest running in the sibling thread can have
729 sibling threads.
|
| D | special-register-buffer-data-sampling.rst | 58 executed on another core or sibling thread using MDS techniques.
89 take longer to execute and do not impact performance of sibling logical
|
| D | l1tf.rst | 100 the context which runs on the sibling Hyperthread of the same physical
206 sibling thread will also bring back its data into the L1D which makes it
223 If only a single guest or related guests run on sibling SMT threads on
227 Host memory is attackable, when one of the sibling SMT threads runs in
322 online a non-primary sibling is rejected
342 physical core two or more sibling threads are online.
|
| D | srso.rst | 90 - potentially create and pin an additional workload on the sibling
|
| /Documentation/driver-api/ |
| D | i2c.rst | 29 The System Management Bus (SMBus) is a sibling protocol. Most SMBus
|
| D | device_link.rst | 182 for HDMI/DP audio. In the device hierarchy the HDA controller is a sibling
|
| /Documentation/i2c/ |
| D | i2c-topology.rst | 101 non-sibling muxes.
326 Two mux-locked sibling muxes
350 Two parent-locked sibling muxes
374 Mux-locked and parent-locked sibling muxes
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 110 from lower-level subsystem trees and from others, either sibling trees or
135 Merging from sibling or upstream trees
|
| /Documentation/hwmon/ |
| D | amd_energy.rst | 52 reading those registers from the sibling threads would result
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 158 Consider two sibling groups A and B; both have 50% bandwidth, but A's
|
| /Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 51 understanding how things like cross linked block lists (e.g. sibling
161 sibling pointer lists). Hence we still need stateful checking in the main code
|
| /Documentation/core-api/ |
| D | xarray.rst | 364 * - Sibling
480 reveal sibling entries; these should be skipped over by the caller.
|
| D | dma-api.rst | 72 Note that unlike their sibling allocation calls, these routines
|
| /Documentation/dev-tools/ |
| D | kfence.rst | 283 directly influenced by GWP-ASan, and can be seen as its kernel sibling. Another
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cpusets.rst | 213 - If its cpu or memory is exclusive, they may not overlap any sibling.
548 on the same CPU X, and if CPU Y is X's sibling and performing idle,
|
| /Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 65 subsequently created by that thread. Any sibling threads existing
|
| /Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 522 core P-states support, when hyper-threading is enabled, if the sibling CPU
|
| D | intel-speed-select.rst | 482 Once a CPU is associated, its sibling CPUs are also associated to a CLOS group.
|
| /Documentation/driver-api/usb/ |
| D | usb.rst | 339 interface. *Bulk* transfers are easiest to use, but only their sibling
|
12