RE: [PATCH v3 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP
From: Paul Durrant
Date: Wed Feb 15 2017 - 04:14:41 EST
> -----Original Message-----
> From: Stefano Stabellini [mailto:sstabellini@xxxxxxxxxx]
> Sent: 14 February 2017 18:39
> To: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
> Cc: Paul Durrant <Paul.Durrant@xxxxxxxxxx>; xen-devel@xxxxxxxxxxxxxxxxxxxx;
> linux-kernel@xxxxxxxxxxxxxxx; Stefano Stabellini <sstabellini@xxxxxxxxxx>;
> Juergen Gross <jgross@xxxxxxxx>
> Subject: Re: [PATCH v3 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP
> On Tue, 14 Feb 2017, Boris Ostrovsky wrote:
> > On 02/13/2017 12:03 PM, Paul Durrant wrote:
> > > Recently a new dm_op hypercall was added to Xen to provide a
> > > for restricting device emulators (such as QEMU) to a limited set of
> > > hypervisor operations, and being able to audit those operations in the
> > > kernel of the domain in which they run.
> > >
> > > This patch adds IOCTL_PRIVCMD_DM_OP as gateway for
> > >
> > > NOTE: There is no requirement for user-space code to bounce data
> > > locked memory buffers (as with IOCTL_PRIVCMD_HYPERCALL) since
> > > privcmd has enough information to lock the original buffers
> > > directly.
> > >
> > >  http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=524a98c2
> > >
> > > Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
> > Stefano,
> > Are you OK with ARM changes?
> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
> Thanks for CC'ing me, I missed the patch.
Sorry. My fault for nor re-running get-maintaner.pl after fixing up the ARM build.