Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-04-21 Thread Peter Maydell
On 21 April 2016 at 19:30, Christoffer Dall wrote: > So I agree about the latch state, that should be exported, if nothing > else so that a VM can't use this particular change to detect a > migration, for example. > > However, for the input level, I really do see this

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-04-21 Thread Christoffer Dall
On Wed, Apr 20, 2016 at 02:28:05PM +0100, Peter Maydell wrote: > On 20 April 2016 at 11:59, Christoffer Dall > wrote: > > On Friday, 15 April 2016, Peter Maydell wrote: > >> Nothing in here describes a mechanism for reading or writing the >

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-04-20 Thread Peter Maydell
On 20 April 2016 at 11:59, Christoffer Dall wrote: > On Friday, 15 April 2016, Peter Maydell wrote: >> Nothing in here describes a mechanism for reading or writing the >> current interrupt line_level state from the kernel (which doesn't >>

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-04-20 Thread Christoffer Dall
On Monday, 18 April 2016, Peter Maydell wrote: > On 15 April 2016 at 14:58, Peter Maydell > wrote: > > Nothing in here describes a mechanism for reading or writing the > > current interrupt line_level state from the kernel

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-04-20 Thread Christoffer Dall
On Friday, 15 April 2016, Peter Maydell wrote: > On 7 December 2015 at 12:29, Pavel Fedin > wrote: > > From: Christoffer Dall > > > > > Factor out the GICv3-specific documentation into a

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-04-18 Thread Peter Maydell
On 15 April 2016 at 14:58, Peter Maydell 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

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-04-15 Thread Peter Maydell
On 7 December 2015 at 12:29, Pavel Fedin wrote: > From: Christoffer Dall > > Factor out the GICv3-specific documentation into a separate > documentation file. Add description for how to access distributor, > redistributor, and CPU interface

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-03-02 Thread Christoffer Dall
On Fri, Feb 26, 2016 at 03:01:56PM +, Peter Maydell wrote: > On 7 December 2015 at 12:29, Pavel Fedin wrote: > > From: Christoffer Dall > > > > Factor out the GICv3-specific documentation into a separate > > documentation file. Add

Re: [PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2016-02-26 Thread Peter Maydell
On 7 December 2015 at 12:29, Pavel Fedin wrote: > From: Christoffer Dall > > Factor out the GICv3-specific documentation into a separate > documentation file. Add description for how to access distributor, > redistributor, and CPU interface

[PATCH v7 1/6] KVM: arm/arm64: Add VGICv3 save/restore API documentation

2015-12-07 Thread Pavel Fedin
From: Christoffer Dall 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