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
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
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
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