On Wed, Nov 28, 2012 at 7:47 AM, Will Deacon will.dea...@arm.com wrote:
Just a bunch of typos in this one :)
On Sat, Nov 10, 2012 at 03:44:30PM +, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
When an interrupt occurs for the guest, it is sometimes necessary
to find
Just a bunch of typos in this one :)
On Sat, Nov 10, 2012 at 03:44:30PM +, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
When an interrupt occurs for the guest, it is sometimes necessary
to find out which vcpu was running at that point.
Keep track of which vcpu is
On 28/11/12 12:47, Will Deacon wrote:
Just a bunch of typos in this one :)
Typos? me? ;-)
On Sat, Nov 10, 2012 at 03:44:30PM +, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
When an interrupt occurs for the guest, it is sometimes necessary
to find out which vcpu was
From: Marc Zyngier marc.zyng...@arm.com
When an interrupt occurs for the guest, it is sometimes necessary
to find out which vcpu was running at that point.
Keep track of which vcpu is being tun in kvm_arch_vcpu_ioctl_run(),
and allow the data to be retrived using either:
-
