From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: xen-devel@lists.xen.org
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: [PATCH v3 0/6] Add dmops to allow use of VGA with restricted QEMU
Date: Fri, 12 Jan 2018 12:45:07 +0000 [thread overview]
Message-ID: <20180112124513.28082-1-ross.lagerwall@citrix.com> (raw)
The recently added support for restricting QEMU prevents use of the VGA
console. This series addresses that by adding a couple of new dmops.
A corresponding patch for QEMU is needed to make use of the new dmops.
Changes in v3:
* Address Jan's comments - primarily adding a new patch to remove the
existing pin_mem_cacheattr domctl.
Changes in v2:
* Address Paul's comments - mainly making add_to_physmap operate on a
range.
Ross Lagerwall (6):
xen/mm: Make xenmem_add_to_physmap global
x86/hvm: Provide XEN_DMOP_add_to_physmap
x86/hvm: Provide XEN_DMOP_pin_memory_cacheattr
tools: libxendevicemodel: Provide xendevicemodel_add_to_physmap
tools: libxendevicemodel: Provide xendevicemodel_pin_memory_cacheattr
x86/domctl: Remove XEN_DOMCTL_pin_mem_cacheattr
tools/flask/policy/modules/xen.if | 4 +-
tools/libs/devicemodel/Makefile | 2 +-
tools/libs/devicemodel/core.c | 39 ++++++++++++++++++
tools/libs/devicemodel/include/xendevicemodel.h | 29 +++++++++++++
tools/libs/devicemodel/libxendevicemodel.map | 6 +++
tools/libxc/include/xenctrl.h | 6 ---
tools/libxc/include/xenctrl_compat.h | 3 ++
tools/libxc/xc_devicemodel_compat.c | 8 ++++
tools/libxc/xc_domain.c | 15 -------
xen/arch/x86/domctl.c | 8 ----
xen/arch/x86/hvm/dm.c | 55 +++++++++++++++++++++++++
xen/common/memory.c | 5 +--
xen/include/public/domctl.h | 7 +---
xen/include/public/hvm/dm_op.h | 41 ++++++++++++++++++
xen/include/xen/mm.h | 3 ++
xen/include/xlat.lst | 2 +
xen/xsm/flask/hooks.c | 3 --
xen/xsm/flask/policy/access_vectors | 2 -
18 files changed, 192 insertions(+), 46 deletions(-)
--
2.9.5
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-01-12 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 12:45 Ross Lagerwall [this message]
2018-01-12 12:45 ` [PATCH v3 1/6] xen/mm: Make xenmem_add_to_physmap global Ross Lagerwall
2018-01-12 12:45 ` [PATCH v3 2/6] x86/hvm: Provide XEN_DMOP_add_to_physmap Ross Lagerwall
2018-01-15 13:33 ` Paul Durrant
2018-01-18 9:24 ` Jan Beulich
2018-01-18 9:32 ` Ross Lagerwall
2018-01-18 9:40 ` Jan Beulich
2018-01-12 12:45 ` [PATCH v3 3/6] x86/hvm: Provide XEN_DMOP_pin_memory_cacheattr Ross Lagerwall
2018-01-12 12:45 ` [PATCH v3 4/6] tools: libxendevicemodel: Provide xendevicemodel_add_to_physmap Ross Lagerwall
2018-01-12 12:45 ` [PATCH v3 5/6] tools: libxendevicemodel: Provide xendevicemodel_pin_memory_cacheattr Ross Lagerwall
2018-01-12 12:45 ` [PATCH v3 6/6] x86/domctl: Remove XEN_DOMCTL_pin_mem_cacheattr Ross Lagerwall
2018-01-15 13:38 ` Paul Durrant
2018-01-17 18:09 ` Daniel De Graaf
2018-01-18 9:29 ` Jan Beulich
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=20180112124513.28082-1-ross.lagerwall@citrix.com \
--to=ross.lagerwall@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).