Searched full:its (Results 1 – 25 of 1366) sorted by relevance
12345678910>>...55
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic-its.rst | 4 ARM Virtual Interrupt Translation Service (ITS)
10 The ITS allows MSI(-X) interrupts to be injected into guests. This extension is
11 optional. Creating a virtual ITS controller also requires a host GICv3 (see
12 arm-vgic-v3.txt), but does not depend on having physical ITS controllers.
14 There can be multiple ITS controllers per guest, each of them has to have
26 Base address in the guest physical address space of the GICv3 ITS
37 -ENODEV Incorrect attribute or the ITS is not supported.
46 request the initialization of the ITS, no additional parameter in
50 reset the ITS, no additional parameter in kvm_device_attr.addr.
51 See "ITS Reset State" section.
[all …]
|
| /Documentation/ABI/removed/ |
| D | raw1394 | 6 access to FireWire buses. Its major drawbacks were its inability
7 to implement sensible device security policies, and its low level
|
| /Documentation/power/ |
| D | runtime_pm.rst | 108 the helper functions described in Section 4 for the device until its status
113 mechanism allowing the device to request a change of its power state, such as
136 4 for the device, until its status is directly set to either 'active', or
148 idle callback with the device as its argument.
266 PM core as 'suspended', regardless of its real hardware status
319 then run pm_runtime_autosuspend(dev) and return its result
373 return its result
377 return its result
396 pm_request_idle(dev) and return its result
400 pm_request_autosuspend(dev) and return its result
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 32 The msi-map property is used to associate the devices with both the ITS
38 For GICv3 and GIC ITS bindings, see:
127 - msi-map: Maps an ICID to a GIC ITS and associated msi-specifier
131 (icid-base,gic-its,msi-base,length).
134 associated with the listed GIC ITS, with the msi-specifier
162 its: gic-its@6020000 {
163 compatible = "arm,gic-v3-its";
175 msi-map = <23 &its 23 41>;
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-online | 11 successful) its 'offline' field is updated accordingly. In
14 for the device and (if successful) its 'offline' field is
19 it is removed (i.e. device_del() is called for it), or its bus
|
| D | sysfs-bus-fsi | 7 on its links.
24 Sends an FSI terminate command from the master to its
27 addition the slave freezes its internal error register for
|
| /Documentation/hwmon/ |
| D | ibmpowernv.rst | 19 sensor type and its attribute data.
46 disable/enable all of its temperature sensors.
59 disable/enable all of its voltage sensors.
70 disable/enable all of its power sensors.
81 disable/enable all of its current sensors.
|
| D | lm95245.rst | 29 the temperature of a remote diode as well as its own temperature.
38 Each sensor has its own critical limit. Additionally, there is a relative
45 The lm95245 driver can change its update interval to a fixed set of values.
|
| D | lm95234.rst | 30 or four (LM95234) remote diodes as well as its own temperature.
40 Each sensor has its own maximum limit, but the hysteresis is common to all
45 The lm95234 driver can change its update interval to a fixed set of values.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,gic-v3.yaml | 158 "^gic-its@": false
161 "^(msi-controller|gic-its|interrupt-controller)@[0-9a-f]+$":
164 GICv3 has one or more Interrupt Translation Services (ITS) that are
168 const: arm,gic-v3-its
180 Specifies the base physical address and size of the ITS registers.
183 socionext,synquacer-pre-its:
186 address and size of the pre-ITS window.
222 compatible = "arm,gic-v3-its";
247 compatible = "arm,gic-v3-its";
254 compatible = "arm,gic-v3-its";
|
| /Documentation/devicetree/bindings/iommu/ |
| D | rockchip,iommu.txt | 5 its master device. Each slave device is bound to a single master device, and
6 shares its clocks, power domain and irq.
15 to associate with its master device. See:
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 57 tasks belonging to the cgroup and all its descendant cgroups. Each
58 cgroup has its own state (self-state) and the state inherited from the
71 belonging to the cgroup and its descendants become frozen. Note that
73 to the cgroup or one of its descendant cgroups until the new task is
78 if not already freezing, enters FREEZING state along with all its
84 becomes THAWED, all its descendants which are freezing because of
|
| D | cpusets.rst | 57 include CPUs in its CPU affinity mask, and using the mbind(2) and
58 set_mempolicy(2) system calls to include Memory Nodes in its memory
61 schedule a task on a CPU that is not allowed in its cpus_allowed
145 - in fork and exit, to attach and detach a task from its cpuset.
191 command. The properties of a cpuset, such as its flags, allowed
211 - Its CPUs and Memory Nodes must be a subset of its parents.
212 - It can't be marked exclusive unless its parent is.
213 - If its cpu or memory is exclusive, they may not overlap any sibling.
253 isolating each job's user allocation in its own cpuset. To do this,
398 The algorithmic cost of load balancing and its impact on key shared
[all …]
|
| D | cpuacct.rst | 9 group accumulates the CPU usage of all of its child groups and the tasks
10 directly present in its group.
30 process (bash) into it. CPU time consumed by this bash and its children
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 43 To reduce its OS jitter, do any of the following:
52 3. Rework the eHCA driver so that its per-CPU kthreads are
62 To reduce its OS jitter, do the following:
73 To reduce its OS jitter, do one of the following:
87 To reduce its OS jitter, each softirq vector must be handled
166 interrupts that the de-jittered CPU receives, minimizing its
208 2. Enable RCU to do its processing remotely via dyntick-idle by
228 To reduce its OS jitter, do any of the following:
242 to remove it, even if its addition was a mistake.
248 use of each CPU's workqueues to run its cache_reap()
[all …]
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | par_io.txt | 11 - reg : offset to the register set and its length.
27 via its own gpio-controller node:
33 - reg : offset to the register set and its length.
|
| /Documentation/networking/ |
| D | sysfs-tagging.rst | 24 ``void *ns member`` of its ``kernfs_node``. If a directory entry is tagged,
32 will be differentiated from other sysfs mounts by having its
42 - call kobj_ns_type_register() with its ``kobj_ns_type_operations`` which has
|
| /Documentation/powerpc/ |
| D | vcpudispatch_stats.rst | 12 from its home node).
42 6. number of times this vcpu was dispatched in its home node (chip)
71 its last dispatch.
75 outside its home node, on a neighbouring chip.
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-detect.rst | 37 - The image is divided into a grid, each cell with its own motion
41 - The image is divided into a grid, each cell with its own region
43 should be used. Each region has its own thresholds. How these
|
| /Documentation/translations/ |
| D | index.rst | 22 than English. Its aim is to help people who do not understand English or have
23 doubts about its interpretation. Additionally, some people prefer to read
45 one language directly to all other languages. Each language has its own
|
| /Documentation/scheduler/ |
| D | sched-domains.rst | 26 flag is set on the corresponding scheduling domain and its groups may not be
31 load of each of its member CPUs, and only when the load of a group becomes
42 our CPU is on, starting from its base domain and going up the ->parent chain.
43 While doing that, it checks to see if the current domain has exhausted its
66 might have just one domain covering its one NUMA level.
|
| /Documentation/RCU/ |
| D | UP.rst | 7 may immediately invoke its function. The basis of this misconception
25 Now, if call_rcu() were to directly invoke its arguments, then upon return
37 by having call_rcu() directly invoke its arguments only if it was called
47 its arguments would cause it to fail to make the fundamental guarantee
48 underlying RCU, namely that call_rcu() defers invoking its arguments until
91 Permitting call_rcu() to immediately invoke its arguments breaks RCU,
|
| /Documentation/driver-api/ |
| D | lightnvm-pblk.rst | 5 block I/O interface. Its primary responsibilities are:
9 - Maintain the integrity and consistency of the L2P table as well as its
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 58 example, a parent device cannot be suspended unless all of its child
147 The :c:member:`power.can_wakeup` flag just records whether the device (and its
152 its system wakeup mechanism and for notifying the PM core of system wakeup
207 runtime power-managed by its driver. Writing "on" calls
216 system-wide transition to a sleep state even though its :c:member:`runtime_auto`
237 and then turn its hardware as "off" as possible during suspend_noirq. The
239 before reactivating its class I/O queues.
255 its parent; and can't be removed or suspended after that parent.
331 method must not update its state in case it is necessary to resume it
351 PM, then its prepare callback must never return a positive value. This
[all …]
|
| /Documentation/filesystems/caching/ |
| D | object.rst | 96 Within FS-Cache, each active object is managed by its own individual state
106 be created or accessed with respect to its parent object.
158 preparation states in which the object sets itself up and waits for its parent
159 object to transit to a state that allows access to its children:
204 There are some normal running states in which the object spends its time
242 The object comes here if it is dying due to an error, because its parent
247 can destroy themselves. This object waits for all its children to go away
252 The object comes to this state if it was waiting on its parent in
253 FSCACHE_OBJECT_INIT, but its parent died. The object will destroy itself
260 all its children, if it is dying because the netfs relinquished its
[all …]
|
12345678910>>...55