| /linux/arch/arm64/kvm/vgic/ |
| H A D | vgic-its.c | 28 static int vgic_its_save_tables_v0(struct vgic_its *its); 29 static int vgic_its_restore_tables_v0(struct vgic_its *its); 30 static int vgic_its_commit_v0(struct vgic_its *its); 169 int (*save_tables)(struct vgic_its *its); 170 int (*restore_tables)(struct vgic_its *its); 171 int (*commit)(struct vgic_its *its); 190 inline const struct vgic_its_abi *vgic_its_get_abi(struct vgic_its *its) in vgic_its_get_abi() argument 192 return &its_table_abi_versions[its->abi_rev]; in vgic_its_get_abi() 195 static int vgic_its_set_abi(struct vgic_its *its, u32 rev) in vgic_its_set_abi() argument 199 its->abi_rev = rev; in vgic_its_set_abi() [all …]
|
| H A D | vgic-debug.c | 372 static void vgic_its_iter_next(struct vgic_its *its, struct vgic_its_iter *iter) in vgic_its_iter_next() argument 378 if (list_is_last(&dev->dev_list, &its->device_list)) { in vgic_its_iter_next() 410 struct vgic_its *its = s->private; in vgic_its_debug_start() local 415 mutex_lock(&its->its_lock); in vgic_its_debug_start() 417 dev = list_first_entry_or_null(&its->device_list, in vgic_its_debug_start() 431 vgic_its_iter_next(its, iter); in vgic_its_debug_start() 455 struct vgic_its *its = s->private; in vgic_its_debug_next() local 459 vgic_its_iter_next(its, iter); in vgic_its_debug_next() 477 struct vgic_its *its = s->private; in vgic_its_debug_stop() local 482 mutex_unlock(&its->its_lock); in vgic_its_debug_stop() [all …]
|
| /linux/drivers/irqchip/ |
| H A D | irq-gic-v3-its.c | 131 #define is_v4(its) (!!((its)->typer & GITS_TYPER_VLPIS)) argument 132 #define is_v4_1(its) (!!((its)->typer & GITS_TYPER_VMAPP)) argument 133 #define device_ids(its) (FIELD_GET(GITS_TYPER_DEVBITS, (its)->typer) + 1) argument 172 struct its_node *its; member 298 static bool require_its_list_vmovp(struct its_vm *vm, struct its_node *its) in require_its_list_vmovp() argument 300 return (gic_rdists->has_rvpeid || vm->vlpi_count[its->list_nr]); in require_its_list_vmovp() 310 struct its_node *its; in get_its_list() local 313 list_for_each_entry(its, &its_nodes, entry) { in get_its_list() 314 if (!is_v4(its)) in get_its_list() 317 if (require_its_list_vmovp(vm, its)) in get_its_list() [all …]
|
| H A D | irq-gic-v5-its.c | 62 static void gicv5_its_dcache_clean(struct gicv5_its_chip_data *its, void *start, in gicv5_its_dcache_clean() argument 67 if (its->flags & ITS_FLAGS_NON_COHERENT) in gicv5_its_dcache_clean() 73 static void its_write_table_entry(struct gicv5_its_chip_data *its, __le64 *entry, in its_write_table_entry() argument 77 gicv5_its_dcache_clean(its, entry, sizeof(*entry)); in its_write_table_entry() 80 #define devtab_cfgr_field(its, f) \ argument 81 FIELD_GET(GICV5_ITS_DT_CFGR_##f, (its)->devtab_cfgr.cfgr) 83 static int gicv5_its_cache_sync(struct gicv5_its_chip_data *its) in gicv5_its_cache_sync() argument 85 return gicv5_wait_for_op_atomic(its->its_base, GICV5_ITS_STATUSR, in gicv5_its_cache_sync() 89 static void gicv5_its_syncr(struct gicv5_its_chip_data *its, in gicv5_its_syncr() argument 97 its_writeq_relaxed(its, syncr, GICV5_ITS_SYNCR); in gicv5_its_syncr() [all …]
|
| /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/testing/selftests/timers/ |
| H A D | posix_timers.c | 261 struct itimerspec its; in check_sig_ign() local 300 its.it_value.tv_sec = 0; in check_sig_ign() 301 its.it_value.tv_nsec = 100000000; in check_sig_ign() 302 its.it_interval.tv_sec = 0; in check_sig_ign() 303 its.it_interval.tv_nsec = 100000000; in check_sig_ign() 304 timer_settime(timerid, 0, &its, NULL); in check_sig_ign() 347 struct itimerspec its; in check_rearm() local 373 its.it_value.tv_sec = 0; in check_rearm() 374 its.it_value.tv_nsec = 100000000; in check_rearm() 375 its.it_interval.tv_sec = 0; in check_rearm() [all …]
|
| /linux/arch/um/os-Linux/ |
| H A D | time.c | 63 struct itimerspec its; in os_timer_set_interval() local 65 its.it_value.tv_sec = nsecs / UM_NSEC_PER_SEC; in os_timer_set_interval() 66 its.it_value.tv_nsec = nsecs % UM_NSEC_PER_SEC; in os_timer_set_interval() 68 its.it_interval.tv_sec = nsecs / UM_NSEC_PER_SEC; in os_timer_set_interval() 69 its.it_interval.tv_nsec = nsecs % UM_NSEC_PER_SEC; in os_timer_set_interval() 71 if (timer_settime(event_high_res_timer[cpu], 0, &its, NULL) == -1) in os_timer_set_interval() 79 struct itimerspec its = { in os_timer_one_shot() local 87 timer_settime(event_high_res_timer[cpu], 0, &its, NULL); in os_timer_one_shot() 97 struct itimerspec its; in os_timer_disable() local 99 memset(&its, 0, sizeof(struct itimerspec)); in os_timer_disable() [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/arch/mips/boot/compressed/ |
| H A D | Makefile | 178 targets += ../vmlinuz.its.S 183 $(objboot)/vmlinuz.its.S: $(addprefix $(srctree)/arch/mips/$(PLATFORM)/,$(ITS_INPUTS)) FORCE 186 targets += ../vmlinuz.its 198 $(objboot)/vmlinuz.its: $(objboot)/vmlinuz.its.S FORCE 212 $(objboot)/vmlinuz.itb: $(objboot)/vmlinuz.its $(objboot)/vmlinuz.bin FORCE
|
| /linux/include/linux/ |
| H A D | time.h | 62 static inline bool itimerspec64_valid(const struct itimerspec64 *its) in itimerspec64_valid() argument 64 if (!timespec64_valid(&(its->it_interval)) || in itimerspec64_valid() 65 !timespec64_valid(&(its->it_value))) in itimerspec64_valid()
|
| /linux/Documentation/hwmon/ |
| H A 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.
|
| /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 | snp-tdx-threat-model.rst | 27 of data in use (vs. data at rest or data in transit). At its core, CoCo 39 inside a CoCo VM. Namely, confidential computing allows its users to 40 confirm the trustworthiness of all SW pieces to include in its reduced 41 Trusted Computing Base (TCB) given its ability to attest the state of these 59 VM, manage its access to system resources, etc. However, since it 60 typically stays out of CoCo VM TCB, its access is limited to preserve the 110 its TCB. The primary attacker resides in the userspace, and all of the data 125 Confidential Computing threat model and its security objectives 131 CoCo VM TCB due to its large SW attack surface. It is important to note 201 data should also be considered untrusted until its integrity and [all …]
|
| /linux/Documentation/core-api/kho/ |
| H A D | fdt.rst | 35 Generally, a KHO user serialize its state into its own FDT and instructs 37 can recover its state from the preserved FDT. 40 of its own FDT in that node's property ``fdt`` .
|
| /linux/Documentation/ABI/testing/ |
| H A 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
|
| 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 …]
|
| H A 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
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse-passthrough.rst | 20 When a FUSE file is subsequently opened, the FUSE daemon can, in its response to 36 ``FUSE_PASSTHROUGH`` capability and specify its desired 39 on its connection file descriptor (e.g., ``/dev/fuse``) to register a 67 A significant concern arises because the FUSE daemon can close its own file 76 daemon closes its file descriptor, the open backing file held by the kernel 86 and then close its own FDs, it could potentially cause the kernel to hold 94 **NOTE**: ``io_uring`` solves this similar issue by exposing its "fixed files", 129 the kernel to perform direct operations on its behalf based on user-provided
|
| /linux/Documentation/i2c/ |
| H A D | i2c-topology.rst | 29 an I2C transfer on one of its child adapters. The mux driver can 72 2. M1 locks muxes on its parent (the root adapter in this case). 74 4. M1 (presumably) does some I2C transfers as part of its select. 77 5. M1 feeds the I2C transfer from step 1 to its parent adapter as a 81 8. M1 unlocks muxes on its parent. 151 2. M1 locks muxes on its parent (the root adapter in this case). 152 3. M1 locks its parent adapter. 155 its select, those transfers must be unlocked I2C transfers so 162 9. M1 unlocks its parent adapter. 163 10. M1 unlocks muxes on its parent. [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. 264 PM core as 'suspended', regardless of its real hardware status 321 then run pm_runtime_autosuspend(dev) and return its result 382 return its result 386 return its result; 389 if its return value is checked by the caller, as this is likely to 408 pm_request_idle(dev) and return its result [all …]
|
| /linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| H A 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.
|
| /linux/Documentation/arch/powerpc/ |
| H A 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.
|
| /linux/arch/arm64/boot/dts/arm/ |
| H A D | foundation-v8-gicv3.dtsi | 22 its: msi-controller@2f020000 { label 23 compatible = "arm,gic-v3-its";
|
| /linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 42 ``original capacity`` is its maximum attainable capacity, i.e. its maximum 44 the function arch_scale_cpu_capacity(). A CPU's ``capacity`` is its ``original 104 Executing the same workload as described in 1.3.1, which each CPU running at its 208 - duty_cycle(p) == 25% if p runs on CPU0 at its maximum frequency 209 - duty_cycle(p) == 75% if p runs on CPU1 at its maximum frequency 233 if it were running on the highest-capacity CPU in the system, running at its 236 Any mention of task utilization in the following sections will imply its 258 Linux cannot currently figure out CPU capacity on its own, this information thus 345 task "fits" on its CPU. If it is violated, the task will need to achieve more 346 work than what its CPU can provide: it will be CPU-bound. [all …]
|
| /linux/Documentation/usb/ |
| H A D | gadget_configfs.rst | 18 A gadget is seen by its host as a set of configurations, each of which contains 62 For each gadget to be created its corresponding directory must be created:: 76 Each gadget needs to have its vendor id <VID> and product id <PID> specified:: 81 A gadget also needs its serial number, manufacturer and product strings. 120 Each configuration also needs its strings, so a subdirectory must be created 136 The gadget will provide some functions, for each function its corresponding 150 Each function provides its specific set of attributes, with either read-only 364 a number of its default sub-groups created automatically. 371 1. A gadget has its config group, which has some attributes (idVendor, 391 4. Each USB function naturally has its own view of what it wants configured, so
|