On Wed, Apr 15, 2015 at 10:26:52, Ian Campbell wrote:
We would like to use memaccess to perform (1) - but rather than
pausing the VCPU in (2), instead simply directly inject the
exception into the VCPU.
That is, into the VCPUs whose permissions have been modified behind
its back and not
On Fri, Apr 10, 2015 at 17:03:26, Andrew Cooper wrote:
Are you perhaps looking for something similar to Intel #VE support?
Yes, in that we want a way to notify a guest that it has made an access that
violated a stage-2 / EPT permission. However, for our purposes a trap into the
hypervisor
On Fri, 2015-04-17 at 10:35 +0100, Gareth Stockwell wrote:
On Wed, Apr 15, 2015 at 10:26:52, Ian Campbell wrote:
We would like to use memaccess to perform (1) - but rather than
Is the guest expected to be aware of this, i.e. to be somewhat
paravirtualised? I suppose it must have to be in
On Fri, 2015-04-10 at 16:04 +0100, Gareth Stockwell wrote:
We would like to use memaccess to perform (1) - but rather than
pausing the VCPU in (2), instead simply directly inject the exception
into the VCPU.
That is, into the VCPUs whose permissions have been modified behind its
back and not
On Fri, 2015-04-10 at 16:23 +0100, Julien Grall wrote:
Hi Razvan,
On 10/04/15 16:11, Razvan Cojocaru wrote:
It's not entirely clear to me what you're trying to do, but if I
understand it correctly, there's always the third option of simply using
the vm_event system as it is now, and when
