On Wed, Sep 28, 2016 at 6:10 PM, Stefano Stabellini
wrote:
> On Wed, 28 Sep 2016, Tamas K Lengyel wrote:
>> On Wed, Sep 28, 2016 at 5:58 PM, Stefano Stabellini
>> wrote:
>> > On Fri, 16 Sep 2016, Tamas K Lengyel wrote:
>> >> The ARM SMC instructions are already configured to trap to Xen by
>> >>
On Wed, 28 Sep 2016, Tamas K Lengyel wrote:
> On Wed, Sep 28, 2016 at 5:58 PM, Stefano Stabellini
> wrote:
> > On Fri, 16 Sep 2016, Tamas K Lengyel wrote:
> >> The ARM SMC instructions are already configured to trap to Xen by default.
> >> In
> >> this patch we allow a user-space process in a pri
On Wed, Sep 28, 2016 at 5:58 PM, Stefano Stabellini
wrote:
> On Fri, 16 Sep 2016, Tamas K Lengyel wrote:
>> The ARM SMC instructions are already configured to trap to Xen by default. In
>> this patch we allow a user-space process in a privileged domain to receive
>> notification of when such event
On Fri, 16 Sep 2016, Tamas K Lengyel wrote:
> The ARM SMC instructions are already configured to trap to Xen by default. In
> this patch we allow a user-space process in a privileged domain to receive
> notification of when such event happens through the vm_event subsystem by
> introducing the PRIV
Hi Tamas,
On 16/09/2016 10:43, Tamas K Lengyel wrote:
The ARM SMC instructions are already configured to trap to Xen by default. In
this patch we allow a user-space process in a privileged domain to receive
notification of when such event happens through the vm_event subsystem by
introducing the
The ARM SMC instructions are already configured to trap to Xen by default. In
this patch we allow a user-space process in a privileged domain to receive
notification of when such event happens through the vm_event subsystem by
introducing the PRIVILEGED_CALL type.
The intended use-case for this fe
