/linux/tools/testing/selftests/kvm/aarch64/ |
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() 169 "GICv3 not supported."); in main()
|
H A D | vgic_init.c | 136 * ARM_VGIC (GICv2 or GICv3) device gets created with an overlapping 138 * used hence the overlap. In the case of GICv3, A RDIST region is set at @0x0 210 "attempt to mix GICv3 REDIST and REDIST_REGION"); in subtest_dist_rdist() 760 print_skip("No GICv2 nor GICv3 support"); in main()
|
/linux/include/kvm/ |
H A D | arm_vgic.h | 41 VGIC_V3, /* New fancy GICv3 */ 78 /* Pseudo GICv3 from outer space */ 147 u32 mpidr; /* GICv3 target VCPU */ 236 /* vGIC model the kernel emulates for the guest (GICv2 or GICv3) */ 242 #define KVM_VGIC_IMP_REV_3 3 /* GICv3 GICR_CTLR.{IW,CES,RWP} */ 258 /* or a number of GICv3 redistributor regions */ 279 * GICv3 spec: IHI 0069E 6.1.1 "LPI Configuration tables" 347 * 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/arch/arm64/kvm/vgic/ |
H A D | vgic-v3.c | 207 * When emulating GICv3 on GICv3 with SRE=1 on the in vgic_v3_set_vmcr() 239 * When emulating GICv3 on GICv3 with SRE=1 on the in vgic_v3_get_vmcr() 272 * If we are emulating a GICv3, we do it in an non-GICv2-compatible in vgic_v3_enable() 301 /* Hide GICv3 sysreg if necessary */ in vcpu_set_ich_hcr() 674 kvm_info("GICv3: no GICV resource entry\n"); in vgic_v3_probe() 692 kvm_err("Cannot register GICv3 KVM device.\n"); in vgic_v3_probe() 706 kvm_info("GICv3 with broken locally generated SEI\n"); in vgic_v3_probe() 718 kvm_info("GICv3 sysreg trapping enabled ([%s%s%s%s], reduced performance)\n", in vgic_v3_probe()
|
/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 as well. 24 Base address in the guest physical address space of the GICv3 distributor 29 Base address in the guest physical address space of the GICv3 103 in the GICv3/4 specs. Getting or setting such a register has the same 154 rules are documented in the GICv3 specification descriptions of the ICPENDR
|
H A D | arm-vgic-its.rst | 11 optional. Creating a virtual ITS controller also requires a host GICv3 (see 26 Base address in the guest physical address space of the GICv3 ITS 66 The GICV3 must be restored before the ITS and all ITS registers but 73 The expected ordering when restoring the GICv3/ITS is described in section 147 Revision 0 of the ABI only supports the features of a virtual GICv3, and does
|
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/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/drivers/irqchip/ |
H A D | irq-gic-v3.c | 7 #define pr_fmt(fmt) "GICv3: " fmt 108 * see GICv3/GICv4 Architecture Specification (IHI0069D): 968 /* Extended SPI range, not handled by the GICv2/GICv3 common code */ in gic_dist_init() 1152 pr_info("GICv3 features: %d PPIs%s%s\n", in gic_update_rdist_properties() 1438 "irqchip/arm/gicv3:checkrdist", in gic_smp_init() 1442 "irqchip/arm/gicv3:starting", in gic_smp_init() 1536 .name = "GICv3", 1554 .name = "GICv3", 1920 .desc = "GICv3: Qualcomm MSM8996 broken firmware", 1925 .desc = "GICv3: ASR erratum 8601001", [all …]
|
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/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.
|
H A D | arm,gic-v3.yaml | 13 AArch64 SMP cores are often associated with a GICv3, providing Private 196 GICv3 has one or more Interrupt Translation Services (ITS) that are
|
/linux/Documentation/arch/arm64/ |
H A D | booting.rst | 223 For systems with a GICv3 interrupt controller to be used in v3 mode: 237 - The DT or ACPI tables must describe a GICv3 interrupt controller. 239 For systems with a GICv3 interrupt controller to be used in
|
/linux/tools/testing/selftests/arm64/fp/ |
H A D | README | 76 --irqchip=gicv3. New kvmtool defaults to that if appropriate, but I
|
/linux/drivers/pci/controller/ |
H A D | pcie-iproc.c | 237 * GICv3 ITS) 251 * programmed. When ARM GICv3 ITS is used, this should be programmed 1225 * Check if 'msi-map' points to ARM GICv3 ITS, which is the only in iproce_pcie_get_msi() 1233 /* derive GITS_TRANSLATER address from GICv3 */ in iproce_pcie_get_msi() 1288 /* steering MSI to GICv3 ITS */ in iproc_pcie_paxc_v2_msi_steer()
|
/linux/arch/arm64/include/asm/ |
H A D | arch_gicv3.h | 47 * The gicv3 of ThunderX requires a modified version for reading the
|