Home
last modified time | relevance | path

Searched full:gicv3 (Results 1 – 25 of 44) sorted by relevance

12

/linux/tools/testing/selftests/kvm/arm64/
H A Dno-vgic-v3.c
H A Dno-vgic.c3 // Check that, on a GICv3-capable system (GICv3 native, or GICv5 with
4 // FEAT_GCIE_LEGACY), not configuring GICv3 correctly results in all
93 "GICv3 wrongly advertised"); in guest_code_gicv3()
96 * Access all GICv3 registers, and fail if we don't get an UNDEF. in guest_code_gicv3()
280 "Neither GICv3 nor GICv5 supported."); in main()
286 pr_info("No GICv3 support: skipping no-vgic-v3 test\n"); in main()
H A Dvgic_init.c137 * ARM_VGIC (GICv2 or GICv3) device gets created with an overlapping
139 * used hence the overlap. In the case of GICv3, A RDIST region is set at @0x0
211 "attempt to mix GICv3 REDIST and REDIST_REGION"); in subtest_dist_rdist()
1017 print_skip("No GICv2 nor GICv3 support"); in main()
/linux/arch/arm64/boot/dts/arm/
H A Dfoundation-v8-gicv3-psci.dts4 * ARMv8 Foundation model DTS (GICv3+PSCI configuration)
8 #include "foundation-v8-gicv3.dtsi"
H A Dfoundation-v8-gicv3.dts5 * ARMv8 Foundation model DTS (GICv3 configuration)
9 #include "foundation-v8-gicv3.dtsi"
H A Dfoundation-v8-gicv3.dtsi4 * ARMv8 Foundation model DTS (GICv3 configuration)
/linux/Documentation/virt/kvm/devices/
H A Darm-vgic-v3.rst14 possible to create both a GICv3 and GICv2 on the same VM.
16 Creating a guest GICv3 device requires a host GICv3 host, or a GICv5 host with
25 Base address in the guest physical address space of the GICv3 distributor
30 Base address in the guest physical address space of the GICv3
106 in the GICv3/4 specs. Getting or setting such a register has the same
169 rules are documented in the GICv3 specification descriptions of the ICPENDR
H A Darm-vgic.rst16 GICv3 implementations with hardware compatibility support allow creating a
17 guest GICv2 through this interface. For information on creating a guest GICv3
19 create both a GICv3 and GICv2 device on the same VM.
/linux/arch/arm64/kvm/vgic/
H A Dvgic-v3.c415 * When emulating GICv3 on GICv3 with SRE=1 on the in vgic_v3_set_vmcr()
445 * When emulating GICv3 on GICv3 with SRE=1 on the in vgic_v3_get_vmcr()
478 * If we are emulating a GICv3, we do it in an non-GICv2-compatible in vgic_v3_reset()
505 /* Hide GICv3 sysreg if necessary */ in vcpu_set_ich_hcr()
884 kvm_info("GICv3 sysreg trapping enabled ([%s%s%s%s], reduced performance)\n", in vgic_v3_enable_cpuif_traps()
929 kvm_info("GICv3: no GICV resource entry\n"); in vgic_v3_probe()
947 kvm_err("Cannot register GICv3 KVM device.\n"); in vgic_v3_probe()
963 kvm_info("GICv3 with broken locally generated SEI\n"); in vgic_v3_probe()
H A Dvgic.c396 * A GICv3 (or GICv3-like) system exposing a GICv3 to the guest in vgic_model_needs_bcst_kick()
1043 * memory-mapped, and VHE systems can access GICv3 EL2 system in can_access_vgic_from_kernel()
1101 * required for GICv3-on-GICv3, GICv2-on-GICv3, GICv3-on-GICv5, and the in vgic_restore_state()
1102 * no-in-kernel-irqchip case on GICv3 hardware. Hence, adding a switch in vgic_restore_state()
H A Dvgic-init.c223 * require prior initialization in case of a virtual GICv3 or trigger in kvm_vgic_dist_init()
253 /* Default GICv3 Maintenance Interrupt INTID, as per SBSA */
406 * If we are creating a VCPU with a GICv3 we must also register the in kvm_vgic_vcpu_init()
591 * is a GICv2. A GICv3 must be explicitly initialized by userspace using the
704 pfr1 |= SYS_FIELD_PREP_ENUM(ID_PFR1_EL1, GIC, GICv3); in kvm_vgic_finalize_idregs()
H A Dvgic-mmio-v2.c392 /* GICv3 only uses ICH_AP1Rn for memory mapped (GICv2) guests */ in vgic_mmio_read_apr()
418 /* GICv3 only uses ICH_AP1Rn for memory mapped (GICv2) guests */ in vgic_mmio_write_apr()
H A Dvgic-mmio-v3.c376 /* report a GICv3 compliant implementation */ in vgic_mmio_read_v3_idregs()
601 * The GICv3 per-IRQ registers are split to control PPIs and SGIs in the
1091 * With GICv3 (and ARE=1) CPUs trigger SGIs by writing to a system register.
/linux/Documentation/translations/zh_CN/arch/arm64/
H A Dbooting.txt191 对于拥有 GICv3 中断控制器并以 v3 模式运行的系统：
198 - 设备树（DT）或 ACPI 表必须描述一个 GICv3 中断控制器。
200 对于拥有 GICv3 中断控制器并以兼容（v2）模式运行的系统：
H A Dsilicon-errata.txt74 | Cavium | ThunderX GICv3 | #23154 | CAVIUM_ERRATUM_23154 |
/linux/Documentation/translations/zh_TW/arch/arm64/
H A Dbooting.txt195 對於擁有 GICv3 中斷控制器並以 v3 模式運行的系統：
202 - 設備樹（DT）或 ACPI 表必須描述一個 GICv3 中斷控制器。
204 對於擁有 GICv3 中斷控制器並以兼容（v2）模式運行的系統：
H A Dsilicon-errata.txt78 | Cavium | ThunderX GICv3 | #23154 | CAVIUM_ERRATUM_23154 |
/linux/include/linux/irqchip/
H A Darm-vgic-info.h16 /* Full GICv3, optionally with v2 compat */
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Dsocionext,synquacer-exiu.yaml15 level-high type GICv3 SPIs.
/linux/drivers/irqchip/
H A Dirq-gic-v4.c18 * intricacies of GICv3, GICv4, and how a guest's view of a GICv3 gets
H A Dirq-gic-common.c111 * alone as they are in the redistributor registers on GICv3. in gic_dist_config()
H A Dirq-gic-v3-mbi.c7 #define pr_fmt(fmt) "GICv3: " fmt
/linux/tools/testing/selftests/arm64/fp/
H A DREADME76 --irqchip=gicv3. New kvmtool defaults to that if appropriate, but I
/linux/Documentation/devicetree/bindings/misc/
H A Dfsl,qoriq-mc.yaml48 For GICv3 and GIC ITS bindings, see:
/linux/arch/arm/kernel/
H A Dhyp-stub.S165 @ Check whether GICv3 system registers are available

12