Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-04 Thread Auger Eric
Hi Andre, On 04/08/2016 12:17, Andre Przywara wrote: > Hi Eric, > > On 04/08/16 11:11, Auger Eric wrote: >> Hi Andre, >> >> On 03/08/2016 16:57, Andre Przywara wrote: >>> Currently we register ITS devices upon userland issuing the CTRL_INIT >>> ioctl to mark initialization of the ITS as done.

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-04 Thread Andre Przywara
Hi Eric, On 04/08/16 11:11, Auger Eric wrote: > Hi Andre, > > On 03/08/2016 16:57, Andre Przywara wrote: >> Currently we register ITS devices upon userland issuing the CTRL_INIT >> ioctl to mark initialization of the ITS as done. >> This deviates from the initialization sequence of the existing

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-04 Thread Auger Eric
Hi Andre, On 03/08/2016 16:57, Andre Przywara wrote: > Currently we register ITS devices upon userland issuing the CTRL_INIT > ioctl to mark initialization of the ITS as done. > This deviates from the initialization sequence of the existing GIC > devices and does not play well with the way QEMU

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Auger Eric
On 03/08/2016 19:56, Auger Eric wrote: > Hi > > On 03/08/2016 19:48, Auger Eric wrote: >> Hi Andre, Christoffer, >> >> On 03/08/2016 19:18, Andre Przywara wrote: >>> Hi, >>> >>> On 03/08/16 18:11, Christoffer Dall wrote: On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: >

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread kbuild test robot
Hi Andre, [auto build test ERROR on kvmarm/next] [also build test ERROR on next-20160803] [cannot apply to v4.7] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Auger Eric
Hi On 03/08/2016 19:48, Auger Eric wrote: > Hi Andre, Christoffer, > > On 03/08/2016 19:18, Andre Przywara wrote: >> Hi, >> >> On 03/08/16 18:11, Christoffer Dall wrote: >>> On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: Currently we register ITS devices upon userland

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Christoffer Dall
On Wed, Aug 03, 2016 at 07:48:15PM +0200, Auger Eric wrote: > Hi Andre, Christoffer, > > On 03/08/2016 19:18, Andre Przywara wrote: > > Hi, > > > > On 03/08/16 18:11, Christoffer Dall wrote: > >> On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: > >>> Currently we register ITS

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Auger Eric
Hi Andre, Christoffer, On 03/08/2016 19:18, Andre Przywara wrote: > Hi, > > On 03/08/16 18:11, Christoffer Dall wrote: >> On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: >>> Currently we register ITS devices upon userland issuing the CTRL_INIT >>> ioctl to mark initialization of

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Christoffer Dall
On Wed, Aug 03, 2016 at 06:18:48PM +0100, Andre Przywara wrote: > Hi, > > On 03/08/16 18:11, Christoffer Dall wrote: > > On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: > >> Currently we register ITS devices upon userland issuing the CTRL_INIT > >> ioctl to mark initialization of

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Andre Przywara
Hi, On 03/08/16 18:11, Christoffer Dall wrote: > On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: >> Currently we register ITS devices upon userland issuing the CTRL_INIT >> ioctl to mark initialization of the ITS as done. >> This deviates from the initialization sequence of the

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Christoffer Dall
On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: > Currently we register ITS devices upon userland issuing the CTRL_INIT > ioctl to mark initialization of the ITS as done. > This deviates from the initialization sequence of the existing GIC > devices and does not play well with the

Re: [PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Christoffer Dall
On Wed, Aug 03, 2016 at 03:57:45PM +0100, Andre Przywara wrote: > Currently we register ITS devices upon userland issuing the CTRL_INIT > ioctl to mark initialization of the ITS as done. > This deviates from the initialization sequence of the existing GIC > devices and does not play well with the

[PATCH] KVM: arm64: ITS: move ITS registration into first VCPU run

2016-08-03 Thread Andre Przywara
Currently we register ITS devices upon userland issuing the CTRL_INIT ioctl to mark initialization of the ITS as done. This deviates from the initialization sequence of the existing GIC devices and does not play well with the way QEMU handles things. To be more in line with what we are used to,