Home
last modified time | relevance | path

Searched full:ppis (Results 1 – 21 of 21) sorted by relevance

/linux/tools/testing/selftests/kvm/arm64/
H A Dvgic_v5.c124 /* Read out the PPIs that user space is allowed to drive. */ in test_vgic_v5_ppis()
168 TEST_ASSERT(ret == 0, "Failed to test GICv5 PPIs"); in test_vgic_v5_ppis()
204 pr_info("Test VGICv5 PPIs\n"); in run_tests()
H A Dvgic_irq.c98 /* can inject PPIs, PPIs, and/or SPIs. */
463 /* Timer PPIs cannot be injected from userspace */ in test_preemption()
/linux/Documentation/devicetree/bindings/timer/
H A Darm,arch_timer.yaml18 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
/linux/arch/arm64/kvm/vgic/
H A Dvgic-init.c107 * as the per-vCPU arrays of private IRQs (SGIs, PPIs). in kvm_vgic_create()
290 /* PPIs */ in vgic_allocate_private_irq()
354 * configure all PPIs as level-triggered. in vgic_allocate_private_irqs_locked()
H A Dvgic.c124 /* SGIs and PPIs */ in vgic_get_vcpu_irq()
518 * @vcpu: The CPU for PPIs or NULL for global interrupts
712 * @vcpu: Pointer to the VCPU (used for PPIs)
H A Dvgic-mmio-v3.c601 * The GICv3 per-IRQ registers are split to control PPIs and SGIs in the
/linux/drivers/clocksource/
H A Dtimer-mediatek-cpux.c87 * on the CPU timer PPIs as well, so we don't declare TIMER_OF_IRQ.
/linux/drivers/irqchip/
H A Dirq-hip04.c135 /* Misconfigured PPIs are usually not fatal */ in hip04_irq_set_type()
H A Dirq-gic-v5.c507 * GICv5's PPIs do not have a configurable trigger or handling in gicv5_ppi_irq_set_type()
625 * Handling mode is hardcoded for PPIs, set the type using in gicv5_irq_domain_translate()
H A Dirq-gic.c308 /* Misconfigured PPIs are usually not fatal */ in gic_set_type()
/linux/include/linux/irqchip/
H A Darm-gic-v5.h28 * Architected PPIs
/linux/tools/testing/selftests/kvm/lib/arm64/
H A Dgic_v3.c336 /* Set a default priority for all the SGIs and PPIs */ in gicv3_cpu_init()
/linux/Documentation/virt/kvm/devices/
H A Darm-vgic-v3.rst352 PPIs are reported per VCPU as specified in the mpidr field, and SPIs are
/linux/drivers/net/hyperv/
H A Dhyperv_net.h950 u8 ppi_flags; /* valid/present bits for the above PPIs */
H A Drndis_filter.c396 /* Copy the PPIs into nvchan->recv_buf */ in rndis_get_ppi()
/linux/drivers/perf/
H A Darm_spe_pmu.c1304 /* Request our PPIs (note that the IRQ is still disabled) */ in arm_spe_pmu_dev_init()
/linux/arch/arm64/kvm/
H A Dconfig.c1716 * We present a different subset of PPIs the guest from what in __compute_ich_hfgwtr()
H A Dsys_regs.c734 * If we're only handling architected PPIs and the guest writes to the in access_gicv5_ppi_enabler()
735 * enable for the non-architected PPIs, we just return as there's in access_gicv5_ppi_enabler()
752 * PPIs as we don't expose many to the guest. in access_gicv5_ppi_enabler()
H A Darm.c1511 * Only allow PPIs that are explicitly exposed to in kvm_vm_ioctl_irq_line()
/linux/arch/arm64/include/asm/
H A Dkvm_host.h358 /* Timer PPIs made immutable */
/linux/Documentation/virt/kvm/
H A Dapi.rst899 use PPIs designated for specific cpus. The irq field is interpreted