Re: [PATCH 00/10] arm/arm64: KVM: Active interrupt state switching for shared devices

2015-06-18 Thread Eric Auger
Hi Marc, I tested your series on Calxeda Midway (shared device path) Tested-by: Eric Auger eric.au...@linaro.org. No exotic migration use case though. I also exercised the non-shared device path. As already discussed some adaptations where needed in vgic state machine. If anyone is interested,

Re: [PATCH 00/10] arm/arm64: KVM: Active interrupt state switching for shared devices

2015-06-10 Thread Eric Auger
Hi Marc, On 06/10/2015 11:03 AM, Marc Zyngier wrote: Hi Eric, On 10/06/15 09:33, Eric Auger wrote: Hi Marc, On 06/08/2015 07:03 PM, Marc Zyngier wrote: From day 1, our timer code has been using a terrible hack: whenever the guest is scheduled with a timer interrupt pending (i.e. the HW

Re: [PATCH 00/10] arm/arm64: KVM: Active interrupt state switching for shared devices

2015-06-10 Thread Marc Zyngier
Hi Eric, On 10/06/15 09:33, Eric Auger wrote: Hi Marc, On 06/08/2015 07:03 PM, Marc Zyngier wrote: From day 1, our timer code has been using a terrible hack: whenever the guest is scheduled with a timer interrupt pending (i.e. the HW timer has expired), we restore the timer state with the

Re: [PATCH 00/10] arm/arm64: KVM: Active interrupt state switching for shared devices

2015-06-10 Thread Eric Auger
Hi Marc, On 06/08/2015 07:03 PM, Marc Zyngier wrote: From day 1, our timer code has been using a terrible hack: whenever the guest is scheduled with a timer interrupt pending (i.e. the HW timer has expired), we restore the timer state with the MASK bit set, in order to avoid the physical

[PATCH 00/10] arm/arm64: KVM: Active interrupt state switching for shared devices

2015-06-08 Thread Marc Zyngier
From day 1, our timer code has been using a terrible hack: whenever the guest is scheduled with a timer interrupt pending (i.e. the HW timer has expired), we restore the timer state with the MASK bit set, in order to avoid the physical interrupt to fire again. And again. And again... This is