On 7 December 2015 at 12:29, Pavel Fedin <p.fedin@xxxxxxxxxxx> wrote: > From: Christoffer Dall <christoffer.dall@xxxxxxxxxx> > > Factor out the GICv3-specific documentation into a separate > documentation file. Add description for how to access distributor, > redistributor, and CPU interface registers for GICv3 in this new file. > > Acked-by: Peter Maydell <peter.maydell@xxxxxxxxxx> > Acked-by: Marc Zyngier <marc.zyngier@xxxxxxx> > Signed-off-by: Christoffer Dall <christoffer.dall@xxxxxxxxxx> > Signed-off-by: Pavel Fedin <p.fedin@xxxxxxxxxxx> Nothing in here describes a mechanism for reading or writing the current interrupt line_level state from the kernel (which doesn't matter for edge triggered interrupts but does for level triggered interrupts). Do we need accessors for these or does somebody have a good rationale for why we don't need to migrate that data? (Christoffer?) (GICv2 doesn't do this either and I suspect it's wrong too.) thanks -- PMM -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
