On Wed, Jan 25, 2017 at 01:38:40PM +0100, Christoffer Dall wrote:
> On Wed, Jan 25, 2017 at 10:07:15AM +0100, Auger Eric wrote:
> > Hi Christoffer,
> >
> > On 24/01/2017 14:25, Christoffer Dall wrote:
> > > Add a file to debugfs to read the in-kernel state of the vgic. We don't
> > > do any
On Wed, Jan 25, 2017 at 10:07:15AM +0100, Auger Eric wrote:
> Hi Christoffer,
>
> On 24/01/2017 14:25, Christoffer Dall wrote:
> > Add a file to debugfs to read the in-kernel state of the vgic. We don't
> > do any locking of the entire VGIC state while traversing all the IRQs,
> > so if the VM
Hi Christoffer,
On 24/01/17 13:25, Christoffer Dall wrote:
> Add a file to debugfs to read the in-kernel state of the vgic. We don't
> do any locking of the entire VGIC state while traversing all the IRQs,
> so if the VM is running the user/developer may not see a quiesced state,
> but should
Hi Christoffer,
On 24/01/2017 14:25, Christoffer Dall wrote:
> Add a file to debugfs to read the in-kernel state of the vgic. We don't
> do any locking of the entire VGIC state while traversing all the IRQs,
> so if the VM is running the user/developer may not see a quiesced state,
> but should
Hi Christoffer,
[auto build test ERROR on kvmarm/next]
[also build test ERROR on v4.10-rc5 next-20170124]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Add a file to debugfs to read the in-kernel state of the vgic. We don't
do any locking of the entire VGIC state while traversing all the IRQs,
so if the VM is running the user/developer may not see a quiesced state,
but should take care to pause the VM using facilities in user space for
that
