On Monday, 18 April 2016, Peter Maydell <peter.mayd...@linaro.org> wrote:
> On 15 April 2016 at 14:58, Peter Maydell <peter.mayd...@linaro.org > <javascript:;>> wrote: > > 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?) > > Relatedly, we should have a mechanism for directly reading and > writing the pending-latch state in the KVM GIC, which for > a level triggered interrupt is not the same as the behaviour > of reading and writing the PENDING register. > > Strictly speaking, yes. But can we think of a use case that would really need this? (I saw this as a thing that was implemented for software to capture the state of the gic and restore it, but since that's what we're doing here, it seems redundant) Thanks, -Christoffer
_______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
