/linux/drivers/irqchip/ |
H A D | irq-gic-v3-its.c | 82 * value of BASER register configuration and ITS page size. 94 * The ITS structure - contains most of the infrastructure, with the 130 #define is_v4(its) (!!((its)->typer & GITS_TYPER_VLPIS)) argument 131 #define is_v4_1(its) (!!((its)->typer & GITS_TYPER_VMAPP)) argument 132 #define device_ids(its) (FIELD_GET(GITS_TYPER_DEVBITS, (its)->typer) + 1) argument 164 * The ITS view of a device - belongs to an ITS, owns an interrupt 165 * translation table, and a list of interrupts. If it some of its 171 struct its_node *its; member 297 static bool require_its_list_vmovp(struct its_vm *vm, struct its_node *its) in require_its_list_vmovp() argument 299 return (gic_rdists->has_rvpeid || vm->vlpi_count[its->list_nr]); in require_its_list_vmovp() [all …]
|
H A D | irq-gic-v3-its-fsl-mc-msi.c | 19 .name = "ITS-fMSI", 54 * Set the device Id to be passed to the GIC-ITS: in its_fsl_mc_msi_prepare() 79 { .compatible = "arm,gic-v3-its", }, 91 pr_err("%s: unable to locate ITS domain\n", name); in its_fsl_mc_msi_init_one() 117 node_name = kasprintf(GFP_KERNEL, "ITS@0x%lx", in its_fsl_mc_msi_parse_madt() 122 pr_err("%s: Unable to locate ITS domain handle\n", node_name); in its_fsl_mc_msi_parse_madt()
|
/linux/arch/mips/generic/ |
H A D | Platform | 18 its-y := vmlinux.its.S 19 its-$(CONFIG_FIT_IMAGE_FDT_BOSTON) += board-boston.its.S 20 its-$(CONFIG_FIT_IMAGE_FDT_NI169445) += board-ni169445.its.S 21 its-$(CONFIG_FIT_IMAGE_FDT_OCELOT) += board-ocelot.its.S 22 its-$(CONFIG_FIT_IMAGE_FDT_LUTON) += board-luton.its.S 23 its-$(CONFIG_FIT_IMAGE_FDT_JAGUAR2) += board-jaguar2.its.S 24 its-$(CONFIG_FIT_IMAGE_FDT_SERVAL) += board-serval.its.S 25 its-$(CONFIG_FIT_IMAGE_FDT_XILFPGA) += board-xilfpga.its.S 26 its-$(CONFIG_FIT_IMAGE_FDT_MARDUK) += board-marduk.its.S
|
/linux/tools/perf/pmu-events/arch/x86/knightslanding/ |
H A D | cache.json | 145 …t accounts for responses from a snoop request hit with data forwarded from its Far(not in the same… 155 …t accounts for responses from a snoop request hit with data forwarded from its Far(not in the same… 165 …hat accounts for responses from snoop request hit with data forwarded from its Near-other tile L2 … 175 …t accounts for responses from a snoop request hit with data forwarded from its Near-other tile's L… 185 …t accounts for responses from a snoop request hit with data forwarded from its Near-other tile's L… 195 …ads and prefetch code read requests that accounts for responses which hit its own tile's L2 with … 205 …ads and prefetch code read requests that accounts for responses which hit its own tile's L2 with … 215 …ads and prefetch code read requests that accounts for responses which hit its own tile's L2 with … 225 …ads and prefetch code read requests that accounts for responses which hit its own tile's L2 with … 265 …t accounts for responses from a snoop request hit with data forwarded from its Far(not in the same… [all …]
|
/linux/arch/um/os-Linux/ |
H A D | time.c | 49 struct itimerspec its; in os_timer_set_interval() local 51 its.it_value.tv_sec = nsecs / UM_NSEC_PER_SEC; in os_timer_set_interval() 52 its.it_value.tv_nsec = nsecs % UM_NSEC_PER_SEC; in os_timer_set_interval() 54 its.it_interval.tv_sec = nsecs / UM_NSEC_PER_SEC; in os_timer_set_interval() 55 its.it_interval.tv_nsec = nsecs % UM_NSEC_PER_SEC; in os_timer_set_interval() 57 if (timer_settime(event_high_res_timer, 0, &its, NULL) == -1) in os_timer_set_interval() 65 struct itimerspec its = { in os_timer_one_shot() local 73 timer_settime(event_high_res_timer, 0, &its, NULL); in os_timer_one_shot() 82 struct itimerspec its; in os_timer_disable() local 84 memset(&its, 0, sizeof(struct itimerspec)); in os_timer_disable() [all …]
|
/linux/arch/mips/boot/ |
H A D | Makefile | 115 targets += vmlinux.its.S 120 $(obj)/vmlinux.its.S: $(addprefix $(srctree)/arch/mips/$(PLATFORM)/,$(ITS_INPUTS)) FORCE 123 targets += vmlinux.its 124 targets += vmlinux.gz.its 125 targets += vmlinux.bz2.its 126 targets += vmlinux.lzma.its 127 targets += vmlinux.lzo.its 129 quiet_cmd_cpp_its_S = ITS $@ 139 $(obj)/vmlinux.its: $(obj)/vmlinux.its.S $(VMLINUX) FORCE 142 $(obj)/vmlinux.gz.its: $(obj)/vmlinux.its.S $(VMLINUX) FORCE [all …]
|
/linux/Documentation/admin-guide/hw-vuln/ |
H A D | indirect-target-selection.rst | 3 Indirect Target Selection (ITS) 6 ITS is a vulnerability in some Intel CPUs that support Enhanced IBRS and were 7 released before Alder Lake. ITS may allow an attacker to control the prediction 10 ITS is assigned CVE-2024-28956 with a CVSS score of 4.7 (Medium). 28 Below is the list of ITS affected CPUs [#f2]_ [#f3]_: 48 - IBPB isolation is affected on all ITS affected CPUs, and need a microcode 53 - Intel Atom CPUs are not affected by ITS. 58 in the lower half of the cacheline are vulnerable to ITS, the basic idea behind 62 compilers. ITS-vulnerable retpoline sites are runtime patched to point to newly 63 added ITS-safe thunks. These safe thunks consists of indirect branch in the [all …]
|
/linux/Documentation/power/ |
H A 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 323 then run pm_runtime_autosuspend(dev) and return its result 385 return its result 389 return its result; 392 if its return value is checked by the caller, as this is likely to 411 pm_request_idle(dev) and return its result [all …]
|
/linux/Documentation/admin-guide/device-mapper/ |
H A D | vdo-design.rst | 50 the next phase of its operation requires access to the structures in the 54 each zone has an implicit lock on the structures it manages for all its 76 when the index is full, it should cull its oldest records to make space for 113 only a subset of the block name as its key, so it cannot guarantee that an 127 mapping each block name to the chapter containing its newest record. This 131 not been deleted from its chapter. Like the chapter index, the volume index 132 uses only a subset of the block name as its key and can not definitively 140 request looks up its name in the chapter index. This will indicate either 142 new, the request will look for its name in the indicated record page. 160 splitting its key space into many sub-lists, each starting at a fixed key [all …]
|
/linux/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/ |
H A D | pipeline.json | 75 …"PublicDescription": "This event counts requests in L1D cache pipeline#0 that its sce bit of tagge… 78 …"BriefDescription": "This event counts requests in L1D cache pipeline#0 that its sce bit of tagged… 81 …"PublicDescription": "This event counts requests in L1D cache pipeline#0 that its pfe bit of tagge… 84 …"BriefDescription": "This event counts requests in L1D cache pipeline#0 that its pfe bit of tagged… 87 …"PublicDescription": "This event counts requests in L1D cache pipeline#1 that its sce bit of tagge… 90 …"BriefDescription": "This event counts requests in L1D cache pipeline#1 that its sce bit of tagged… 93 …"PublicDescription": "This event counts requests in L1D cache pipeline#1 that its pfe bit of tagge… 96 …"BriefDescription": "This event counts requests in L1D cache pipeline#1 that its pfe bit of tagged… 129 …"PublicDescription": "This event counts requests in L1D cache pipeline#0 that its sector cache ID … 132 …"BriefDescription": "This event counts requests in L1D cache pipeline#0 that its sector cache ID i… [all …]
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-usb | 142 connected to its receiver dongle, and, for example, consider 210 which wraps to 0 after its maximum is reached. This file supports 237 connection between a port and its connector. 329 See USB specs for its meaning. 335 See USB specs for its meaning. 344 Changing its value will change the device's configuration 351 See USB specs for its meaning. 357 See USB specs for its meaning. 363 See USB specs for its meaning. 369 See USB specs for its meaning. [all …]
|
/linux/drivers/acpi/arm64/ |
H A D | iort.c | 156 * ITS ID and base address to the list from where we can get it back later on. 157 * @trans_id: ITS ID. 158 * @base: ITS base address. 184 * iort_deregister_domain_token() - Deregister domain token based on ITS ID 185 * @trans_id: ITS ID. 205 * iort_find_domain_token() - Find domain token based on given ITS ID 206 * @trans_id: ITS ID. 487 * Get the special ID mapping index (if any) and skip its in iort_node_map_id() 534 * optional step 2: map the initial dev id if its parent is not in iort_node_map_platform_id() 536 * as NC (named component) -> SMMU -> ITS. If the type is matched, in iort_node_map_platform_id() [all …]
|
/linux/drivers/base/power/ |
H A D | common.c | 23 * its reference counter. Return 0 if new object has been created or refcount 48 /* kfree() verifies that its argument is nonzero. */ in dev_pm_get_subsys_data() 84 * dev_pm_domain_attach - Attach a device to its PM domain. 119 * dev_pm_domain_attach_by_id - Associate a device with one of its PM domains. 130 * in case its device requires power management through multiple PM domains. The 132 * towards its original device. Depending on the use-case and if needed, the 139 * Returns the virtual created device when successfully attached to its PM 155 * dev_pm_domain_attach_by_name - Associate a device with one of its PM domains. 172 * dev_pm_domain_attach_list - Associate a device with its PM domains. 177 * This function helps to attach a device to its multiple PM domains. The [all …]
|
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | arm,gic-v3.yaml | 189 "^gic-its@": false 192 "^(msi-controller|gic-its|interrupt-controller)@[0-9a-f]+$": 195 GICv3 has one or more Interrupt Translation Services (ITS) that are 199 const: arm,gic-v3-its 203 Present if the GIC ITS permits programming shareability and 217 Specifies the base physical address and size of the ITS registers. 220 socionext,synquacer-pre-its: 223 address and size of the pre-ITS window. 258 compatible = "arm,gic-v3-its"; 284 compatible = "arm,gic-v3-its"; [all …]
|
/linux/Documentation/admin-guide/cgroup-v1/ |
H A 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 …]
|
/linux/Documentation/security/ |
H A D | IMA-templates.rst | 90 - "ima": its format is ``d|n``; 91 - "ima-ng" (default): its format is ``d-ng|n-ng``; 92 - "ima-ngv2": its format is ``d-ngv2|n-ng``; 93 - "ima-sig": its format is ``d-ng|n-ng|sig``; 94 - "ima-sigv2": its format is ``d-ngv2|n-ng|sig``; 95 - "ima-buf": its format is ``d-ng|n-ng|buf``; 96 - "ima-modsig": its format is ``d-ng|n-ng|sig|d-modsig|modsig``; 97 …- "evm-sig": its format is ``d-ng|n-ng|evmsig|xattrnames|xattrlengths|xattrvalues|iuid|igid|imode`…
|
H A D | credentials.rst | 65 A subject has an additional interpretation of its credentials. A subset 66 of its credentials forms the 'subjective context'. The subjective context 96 Sometimes the object will include sets of rules as part of its 117 of its credentials. When an action is requested, they take the 160 itself to its effective or permitted sets through ``capset()``. This 252 Each task points to its credentials by a pointer called 'cred' in its 258 1. its reference count may be changed; 278 A task may only alter its _own_ credentials; it is no longer permitted for a 298 has _const_ pointers to its credential sets, as does struct file. Furthermore, 307 A task being able to alter only its own credentials permits the current process [all …]
|
/linux/rust/kernel/ |
H A D | opp.rs | 42 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in new() 182 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in new() 194 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in drop() 499 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in set() 574 /// The following example demonstrates how to get OPP [`Table`] for a [`Cpumask`] and set its 624 // SAFETY: By the safety requirements, ptr is valid and its refcount will be incremented. in from_raw_table() 640 // SAFETY: The requirements are satisfied by the existence of the [`Device`] and its safety in from_dev() 660 // SAFETY: The requirements are satisfied by the existence of the [`Device`] and its safety in from_of() 678 // SAFETY: The requirements are satisfied by the existence of the [`Device`] and its safety in remove_of() 713 // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety in opp_count() [all …]
|
/linux/arch/mips/mobileye/ |
H A D | Platform | 15 its-y := vmlinux.its.S 16 its-$(CONFIG_FIT_IMAGE_FDT_EPM5) += board-epm5.its.S
|
/linux/drivers/clk/sunxi-ng/ |
H A D | ccu_phase.c | 29 /* Get our parent clock, it's the one that can adjust its rate */ in ccu_phase_get_phase() 34 /* And its rate */ in ccu_phase_get_phase() 44 /* And its rate */ in ccu_phase_get_phase() 65 /* Get our parent clock, it's the one that can adjust its rate */ in ccu_phase_set_phase() 70 /* And its rate */ in ccu_phase_set_phase() 80 /* And its rate */ in ccu_phase_set_phase()
|
/linux/arch/sh/boards/mach-dreamcast/ |
H A D | irq.c | 24 * triggered, its corresponding bit in the Event Status Registers (ESRs) 62 /* Disable the hardware event by masking its bit in its EMR */ 74 /* Enable the hardware event by setting its bit in its EMR */ 86 /* Acknowledge a hardware event by writing its bit back to its ESR */
|
/linux/Documentation/filesystems/nfs/ |
H A D | client-identifier.rst | 14 There are risks if a client's NFSv4 identifier and its principal 29 The client is responsible for periodically renewing its leases. 33 If a client stops renewing its lease (for example, if it crashes), 37 associated with its previous leases is no longer valid and can be 51 they can associate the client with its lease. Each client's 116 client to reclaim its open and lock state, and may give those locks 126 By default, the Linux NFSv4 client implementation constructs its 147 Linux provides two mechanisms to add uniqueness to its "co_ownerid" 176 AUTH_SYS and UID 0 as the principal part of its client identity.
|
/linux/Documentation/userspace-api/media/mediactl/ |
H A D | media-types.rst | 108 its component parts, luminance and chrominance, and output it in 163 its sink pad(s) to a different encoding output on its source 171 the values of the pixels received on its sink pad to look up 172 entries in internal tables and output them on its source pad. 180 video frame(s) received on its sink pad(s) to a different 181 resolution output on its source pad(s). The range of 192 received on its sink pad and outputs the statistics data on 193 its source pad. 219 frames on its sink pad from an input video bus of one type (HDMI, eDP, 220 MIPI CSI-2, etc.), and outputs them on its source pad to an output [all …]
|
/linux/arch/sh/kernel/ |
H A D | ptrace.c | 5 * regs_query_register_offset() - query register offset from its name 9 * pt_regs from its name. If the name is invalid, this returns -EINVAL; 21 * regs_query_register_name() - query register name from its offset 24 * regs_query_register_name() returns the name of a register from its
|
/linux/Documentation/filesystems/ |
H A D | sharedsubtree.rst | 23 A process wants to clone its own namespace, but still wants to access the CD 131 This is the mount we are familiar with. Its the default type. 164 A) A process wants to clone its own namespace, but still wants to 182 B) A process wants its mounts invisible to any other process, but 193 of its namespace as slave:: 276 /mnt or /tmp reflect in all the other mounts of its peer 299 has its own peer group too. This vfsmount receives propagation 300 events from its master vfsmount, and also forwards propagation 301 events to its 'peer group' and to its slave vfsmounts. 303 Strictly speaking, the vfsmount is shared having its own [all …]
|