From: Wei Ye <wei.ye@intel.com>
To: xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, tim@xen.org,
ian.jackson@eu.citrix.com, donald.d.dugger@intel.com,
Paul.Durrant@citrix.com, zhiyuan.lv@intel.com, JBeulich@suse.com,
yang.z.zhang@intel.com, Wei Ye <wei.ye@intel.com>
Subject: [PATCH v3 0/2] Extend ioreq-server to support page write protection
Date: Thu, 4 Sep 2014 05:53:17 +0800 [thread overview]
Message-ID: <1409781199-12052-1-git-send-email-wei.ye@intel.com> (raw)
Changes from v1:
- Changes the new p2m type name from p2m_ram_wp to p2m_mmio_write_dm. This
means that we treat the pages as a special mmio range instead of ram.
- Move macros to c file since only this file is using them.
- Address various comments from Jan.
Changes from v2:
- Remove excute attribute of the new p2m type p2m_mmio_write_dm
- Use existing rangeset for keeping the write protection page range instead of
introducing hash table.
- Some code style fix.
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_mmio_write_dm" 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_mmio_write_dm
ioreq-server: write protected range and forwarding
tools/libxc/xc_domain.c | 30 ++++++++++++++++++++++
tools/libxc/xenctrl.h | 18 ++++++++++++++
xen/arch/x86/hvm/hvm.c | 51 ++++++++++++++++++++++++++++++++++++--
xen/arch/x86/mm/p2m-ept.c | 1 +
xen/arch/x86/mm/p2m-pt.c | 1 +
xen/include/asm-x86/hvm/domain.h | 2 +-
xen/include/asm-x86/p2m.h | 1 +
xen/include/public/hvm/hvm_op.h | 1 +
8 files changed, 102 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-09-03 21:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 21:53 Wei Ye [this message]
2014-09-03 21:53 ` [PATCH v3 1/2] x86: add p2m_mmio_write_dm Wei Ye
2014-09-03 9:54 ` Paul Durrant
2014-09-03 10:03 ` Jan Beulich
2014-09-03 21:53 ` [PATCH v3 2/2] ioreq-server: write protected range and forwarding Wei Ye
2014-09-03 10:11 ` Paul Durrant
2014-09-04 23:10 ` Tian, Kevin
2014-09-05 0:44 ` Ye, Wei
2014-09-05 9:01 ` Paul Durrant
2014-09-10 6:10 ` Ye, Wei
2014-09-10 21:02 ` Tian, Kevin
2014-09-11 14:38 ` Paul Durrant
2014-09-16 21:25 ` Tian, Kevin
2014-09-11 14:45 ` Paul Durrant
2014-09-03 13:17 ` Jan Beulich
2014-09-04 0:31 ` Ye, Wei
2014-09-10 5:32 ` Ye, Wei
2014-09-10 9:19 ` Jan Beulich
2014-09-10 9:30 ` 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=1409781199-12052-1-git-send-email-wei.ye@intel.com \
--to=wei.ye@intel.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=donald.d.dugger@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
--cc=zhiyuan.lv@intel.com \
/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).