| /linux/tools/testing/selftests/kvm/arm64/ |
| H A D | no-vgic-v3.c | 3 // Check that, on a GICv3 system, not configuring GICv3 correctly
59 "GICv3 wrongly advertised"); in guest_code()
62 * Access all GICv3 registers, and fail if we don't get an UNDEF. in guest_code()
146 /* Create a VM without a GICv3 */ in test_guest_no_gicv3()
171 "GICv3 not supported."); in main()
|
| H A D | vgic_init.c | 137 * 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/include/kvm/ |
| H A D | arm_vgic.h | 40 VGIC_V3, /* New fancy GICv3 */
81 /* Pseudo GICv3 from outer space */
84 /* GICv3 system register CPU interface */
87 /* GICv3 compat mode on a GICv5 host */
158 u32 mpidr; /* GICv3 target VCPU */
246 /* vGIC model the kernel emulates for the guest (GICv2 or GICv3) */
252 #define KVM_VGIC_IMP_REV_3 3 /* GICv3 GICR_CTLR.{IW,CES,RWP} */
274 /* or a number of GICv3 redistributor regions */
299 * GICv3 spec: IHI 0069E 6.1.1 "LPI Configuration tables"
367 * Members below are used with GICv3 emulation only and represent
|
| /linux/arch/arm64/boot/dts/arm/ |
| H A D | foundation-v8-gicv3-psci.dts | 4 * ARMv8 Foundation model DTS (GICv3+PSCI configuration)
8 #include "foundation-v8-gicv3.dtsi"
|
| H A D | foundation-v8-gicv3.dts | 5 * ARMv8 Foundation model DTS (GICv3 configuration)
9 #include "foundation-v8-gicv3.dtsi"
|
| H A D | Makefile | 4 foundation-v8-gicv3.dtb foundation-v8-gicv3-psci.dtb
|
| H A D | foundation-v8-gicv3.dtsi | 4 * ARMv8 Foundation model DTS (GICv3 configuration)
|
| /linux/Documentation/virt/kvm/devices/ |
| H A D | arm-vgic-v3.rst | 14 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 D | arm-vgic.rst | 16 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 D | vgic-v3.c | 417 * When emulating GICv3 on GICv3 with SRE=1 on the in vgic_v3_set_vmcr()
449 * When emulating GICv3 on GICv3 with SRE=1 on the in vgic_v3_get_vmcr()
482 * If we are emulating a GICv3, we do it in an non-GICv2-compatible in vgic_v3_reset()
509 /* Hide GICv3 sysreg if necessary */ in vcpu_set_ich_hcr()
920 kvm_info("GICv3: no GICV resource entry\n"); in vgic_v3_probe()
938 kvm_err("Cannot register GICv3 KVM device.\n"); in vgic_v3_probe()
954 kvm_info("GICv3 with broken locally generated SEI\n"); in vgic_v3_probe()
960 kvm_info("GICv3 sysreg trapping enabled ([%s%s%s%s], reduced performance)\n", in vgic_v3_probe()
|
| H A D | vgic-init.c | 173 pfr1 |= SYS_FIELD_PREP_ENUM(ID_PFR1_EL1, GIC, GICv3); in kvm_vgic_create()
211 * require prior initialization in case of a virtual GICv3 or trigger in kvm_vgic_dist_init()
241 /* Default GICv3 Maintenance Interrupt INTID, as per SBSA */
356 * If we are creating a VCPU with a GICv3 we must also register the in kvm_vgic_vcpu_init()
531 * is a GICv2. A GICv3 must be explicitly initialized by userspace using the
|
| H A D | vgic-v3-nested.c | 45 * Nesting GICv3 support
358 * GICv3 emulation code. Yes, this is a pretty sorry hack. in vgic_v3_load_nested()
|
| H A D | vgic-mmio-v2.c | 392 /* 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 D | vgic.c | 380 * A GICv3 (or GICv3-like) system exposing a GICv3 to the guest in vgic_model_needs_bcst_kick()
991 * memory-mapped, and VHE systems can access GICv3 EL2 system in can_access_vgic_from_kernel()
|
| /linux/Documentation/translations/zh_CN/arch/arm64/ |
| H A D | booting.txt | 191 对于拥有 GICv3 中断控制器并以 v3 模式运行的系统：
198 - 设备树（DT）或 ACPI 表必须描述一个 GICv3 中断控制器。
200 对于拥有 GICv3 中断控制器并以兼容（v2）模式运行的系统：
|
| H A D | silicon-errata.txt | 74 | Cavium | ThunderX GICv3 | #23154 | CAVIUM_ERRATUM_23154 |
|
| /linux/Documentation/translations/zh_TW/arch/arm64/ |
| H A D | booting.txt | 195 對於擁有 GICv3 中斷控制器並以 v3 模式運行的系統：
202 - 設備樹（DT）或 ACPI 表必須描述一個 GICv3 中斷控制器。
204 對於擁有 GICv3 中斷控制器並以兼容（v2）模式運行的系統：
|
| H A D | silicon-errata.txt | 78 | Cavium | ThunderX GICv3 | #23154 | CAVIUM_ERRATUM_23154 |
|
| /linux/include/linux/irqchip/ |
| H A D | arm-vgic-info.h | 16 /* Full GICv3, optionally with v2 compat */
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | socionext,synquacer-exiu.yaml | 15 level-high type GICv3 SPIs.
|
| /linux/drivers/irqchip/ |
| H A D | irq-gic-v4.c | 18 * intricacies of GICv3, GICv4, and how a guest's view of a GICv3 gets
|
| H A D | irq-gic-common.c | 111 * alone as they are in the redistributor registers on GICv3. in gic_dist_config()
|
| /linux/tools/testing/selftests/arm64/fp/ |
| H A D | README | 76 --irqchip=gicv3. New kvmtool defaults to that if appropriate, but I
|
| /linux/arch/arm64/kernel/ |
| H A D | image-vars.h | 109 /* Static key indicating whether GICv3 has GICv2 compatibility */
|
| /linux/Documentation/devicetree/bindings/misc/ |
| H A D | fsl,qoriq-mc.yaml | 48 For GICv3 and GIC ITS bindings, see:
|