From: Wei Ye <wei.ye@intel.com>
To: xen-devel@lists.xen.org
Cc: keir@xen.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
Paul.Durrant@citrix.com, jbeulich@suse.com,
Wei Ye <wei.ye@intel.com>
Subject: [PATCH v1 0/2] Extend ioreq-server to support page write protection
Date: Tue, 29 Jul 2014 01:55:25 +0800 [thread overview]
Message-ID: <1406570127-3616-1-git-send-email-wei.ye@intel.com> (raw)
ioreq-server is proposed to forward PIO and MMIO request to multiple device
models according to the io range. XenGT (Intel Graphics Virtualization technology,
please refer to https://01.org/xen/blogs/srclarkx/2013/graphics-virtualization-
xengt) driver reside in Dom0 as a virtual graphics device model also need to trap
and emulate the guest's write operation to some specific memory pages, like the
memory pages used by guest graphics driver as PPGTT(per-process graphics
translation table). We add an new p2m type "p2m_ram_wp" to trap the page write
operation. Page of this new p2m type is read only and for write, the request will
go to device model via ioreq-server.
Wei Ye (2):
x86: add p2m_ram_wp
ioreq-server: Support scatter page forwarding
tools/libxc/xc_domain.c | 32 ++++++
tools/libxc/xenctrl.h | 18 ++++
xen/arch/x86/hvm/hvm.c | 214 +++++++++++++++++++++++++++++++++++++-
xen/arch/x86/mm/p2m-ept.c | 1 +
xen/include/asm-x86/hvm/domain.h | 14 +++
xen/include/asm-x86/p2m.h | 8 +-
xen/include/public/hvm/hvm_op.h | 12 +++
7 files changed, 296 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-07-28 17:55 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 17:55 Wei Ye [this message]
2014-07-28 8:24 ` [PATCH v1 0/2] Extend ioreq-server to support page write protection Jan Beulich
2014-08-04 5:05 ` Ye, Wei
2014-08-04 7:35 ` Jan Beulich
2014-08-04 21:34 ` Tian, Kevin
2014-08-05 6:35 ` Jan Beulich
2014-08-05 6:46 ` Ye, Wei
2014-08-05 7:51 ` Jan Beulich
2014-08-05 7:35 ` Zhang, Yang Z
2014-08-05 7:51 ` Jan Beulich
2014-08-05 8:20 ` Ye, Wei
2014-08-05 15:41 ` Tian, Kevin
2014-08-06 2:11 ` Zhang, Yang Z
2014-08-06 2:33 ` Tian, Kevin
2014-08-06 2:40 ` Zhang, Yang Z
2014-08-06 2:49 ` Tian, Kevin
2014-08-06 2:50 ` Tian, Kevin
2014-08-06 3:04 ` Zhang, Yang Z
2014-08-06 15:00 ` Konrad Rzeszutek Wilk
2014-08-06 16:08 ` Tian, Kevin
2014-08-07 6:45 ` Jan Beulich
2014-08-07 16:28 ` Tian, Kevin
2014-08-08 6:32 ` Jan Beulich
2014-08-08 16:02 ` Tian, Kevin
2014-08-08 16:04 ` Tian, Kevin
2014-08-12 23:15 ` Ye, Wei
2014-08-13 8:38 ` Tim Deegan
2014-08-13 16:14 ` Tian, Kevin
2014-08-14 8:08 ` Tim Deegan
2014-08-14 17:49 ` Tian, Kevin
2014-08-14 20:25 ` Tim Deegan
2014-08-14 22:53 ` Tian, Kevin
2014-08-14 23:12 ` Jan Beulich
2014-08-14 23:33 ` Tian, Kevin
2014-08-06 17:38 ` Tian, Kevin
2014-07-28 17:55 ` [PATCH v1 1/2] x86: add p2m_ram_wp Wei Ye
2014-07-28 8:31 ` Jan Beulich
2014-08-04 5:10 ` Ye, Wei
2014-08-04 7:37 ` Jan Beulich
2014-08-05 7:09 ` Ye, Wei
2014-07-28 17:55 ` [PATCH v1 2/2] ioreq-server: Support scatter page forwarding Wei Ye
2014-07-28 8:57 ` Jan Beulich
2014-08-04 5:41 ` Ye, Wei
2014-08-04 7:47 ` Jan Beulich
2014-08-04 21:39 ` Tian, Kevin
2014-08-05 6:38 ` 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=1406570127-3616-1-git-send-email-wei.ye@intel.com \
--to=wei.ye@intel.com \
--cc=Paul.Durrant@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.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).