Re: [RFC 1/2] ARM64 / ACPI: VGIC probe support with ACPI

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 9/16/14 4:04 AM, Alexander Spyridakis wrote:
On 15 September 2014 23:26, Wei Huang <wei@xxxxxxxxxx> wrote:
diff --git a/include/kvm/arm_vgic.h b/include/kvm/arm_vgic.h
index 35b0c12..af652f2 100644
--- a/include/kvm/arm_vgic.h
+++ b/include/kvm/arm_vgic.h
@@ -35,6 +35,8 @@
   #define VGIC_V2_MAX_LRS               (1 << 6)
   #define VGIC_V3_MAX_LRS               16

+#define VGIC_CPU_INTERFACE_SIZE 0x2000
+


Given that GIC_CPU interface is well known, instead of defining
VGIC_CPU_INTERFACE_SIZE, SZ_8K can be used directly below.

Yes, I thought to be more explicit but skipping that define would be
better I guess.

+       vgic->maint_irq = acpi_register_gsi(NULL,
+               vgic_acpi->vgic_interrupt, trigger, ACPI_ACTIVE_HIGH);


Unless I missed something, according to GIC-400 all PPIs are active-LOW,
including maintenance interrupt.

Hmm I am confused. You are indeed right that GIC-400 at 2.3.2 states
that all PPIs are active-LOW, on the other hand though, the device
tree files for the gic node describe the virtual maintenance interrupt
as active high (0xf04 description from
Documentation/devicetree/bindings/arm/gic.txt). Am I missing
something?

It sounds to me that GIC-400 is wrong. It is better for Marc to answer it.

Marc: Because ACPI 5.1 only specifies trigger type for maintenance IRQ, instead of parsing ACPI entry we have to use hard-code value for polarity when calling acpi_register_gsi(). Could you take a look?

Regards.

_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm




[Index of Archives]     [Linux KVM]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux