From: Paul Durrant <paul.durrant@citrix.com>
To: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH v3 0/3] xen/privcmd: support for dm_op and restriction
Date: Mon, 13 Feb 2017 17:03:21 +0000 [thread overview]
Message-ID: <1487005404-3183-1-git-send-email-paul.durrant@citrix.com> (raw)
This patch series follows on from my recent Xen series [1], to provide
support in privcmd for de-privileging of device emulators.
[1] https://lists.xen.org/archives/html/xen-devel/2017-01/msg02558.html
Paul Durrant (3):
xen/privcmd: return -ENOTTY for unimplemented IOCTLs
xen/privcmd: Add IOCTL_PRIVCMD_DM_OP
xen/privcmd: add IOCTL_PRIVCMD_RESTRICT
arch/arm/xen/enlighten.c | 1 +
arch/arm/xen/hypercall.S | 1 +
arch/arm64/xen/hypercall.S | 1 +
arch/x86/include/asm/xen/hypercall.h | 7 ++
drivers/xen/privcmd.c | 226 +++++++++++++++++++++++++++++++++--
include/uapi/xen/privcmd.h | 15 +++
include/xen/arm/hypercall.h | 1 +
include/xen/interface/hvm/dm_op.h | 32 +++++
include/xen/interface/xen.h | 1 +
9 files changed, 276 insertions(+), 9 deletions(-)
create mode 100644 include/xen/interface/hvm/dm_op.h
--
2.1.4
next reply other threads:[~2017-02-13 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 17:03 Paul Durrant [this message]
2017-02-13 17:03 ` [PATCH v3 1/3] xen/privcmd: return -ENOTTY for unimplemented IOCTLs Paul Durrant
2017-02-13 18:52 ` Boris Ostrovsky
2017-02-13 17:03 ` [PATCH v3 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP Paul Durrant
2017-02-13 19:11 ` Boris Ostrovsky
2017-02-14 9:20 ` Paul Durrant
2017-02-14 14:11 ` Boris Ostrovsky
2017-02-14 17:25 ` Boris Ostrovsky
2017-02-14 18:38 ` Stefano Stabellini
2017-02-15 9:14 ` Paul Durrant
2017-02-15 14:47 ` Boris Ostrovsky
2017-02-13 17:03 ` [PATCH v3 3/3] xen/privcmd: add IOCTL_PRIVCMD_RESTRICT Paul Durrant
2017-02-13 19:20 ` Boris Ostrovsky
2017-02-15 14:49 ` Boris Ostrovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1487005404-3183-1-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome