diff options
| author | Paul Durrant <paul.durrant@citrix.com> | 2017-02-13 17:03:23 +0000 |
|---|---|---|
| committer | Boris Ostrovsky <boris.ostrovsky@oracle.com> | 2017-02-14 15:13:43 -0500 |
| commit | ab520be8cd5d56867fc95cfbc34b90880faf1f9d (patch) | |
| tree | 4c432a918ffbd6308f752eaac36b322b811582b1 /arch/arm64/xen/hypercall.S | |
| parent | dc9eab6fd94dd26340749321bba2c58634761516 (diff) | |
| download | lwn-ab520be8cd5d56867fc95cfbc34b90880faf1f9d.tar.gz lwn-ab520be8cd5d56867fc95cfbc34b90880faf1f9d.zip | |
xen/privcmd: Add IOCTL_PRIVCMD_DM_OP
Recently a new dm_op[1] hypercall was added to Xen to provide a mechanism
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 __HYPERVISOR_dm_op.
NOTE: There is no requirement for user-space code to bounce data through
locked memory buffers (as with IOCTL_PRIVCMD_HYPERCALL) since
privcmd has enough information to lock the original buffers
directly.
[1] http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=524a98c2
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Diffstat (limited to 'arch/arm64/xen/hypercall.S')
| -rw-r--r-- | arch/arm64/xen/hypercall.S | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm64/xen/hypercall.S b/arch/arm64/xen/hypercall.S index 947830a459d2..401ceb71540c 100644 --- a/arch/arm64/xen/hypercall.S +++ b/arch/arm64/xen/hypercall.S @@ -84,6 +84,7 @@ HYPERCALL1(tmem_op); HYPERCALL1(platform_op_raw); HYPERCALL2(multicall); HYPERCALL2(vm_assist); +HYPERCALL3(dm_op); ENTRY(privcmd_call) mov x16, x0 |