From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0 of 2] v2: memshare/xenpaging/xen-access fixes for xen-unstable
Date: Thu, 08 Sep 2011 11:57:08 +0200 [thread overview]
Message-ID: <patchbomb.1315475828@probook.site> (raw)
The following two patches allow the parallel use of memsharing, xenpaging and
xen-access by using an independent ring buffer for each feature.
Please review.
v2:
- update mem_event_check_ring arguments, check domain rather than domain_id
- check ring_full first because its value was just evaluated
- check if ring buffer is initialized before calling
mem_access_domctl/mem_paging_domctl
Olaf
tools/libxc/Makefile | 2
tools/libxc/xc_mem_access.c | 21 ++-
tools/libxc/xc_mem_event.c | 15 --
tools/libxc/xc_mem_paging.c | 33 +++-
tools/libxc/xc_memshr.c | 16 +-
tools/libxc/xenctrl.h | 9 -
tools/tests/xen-access/xen-access.c | 4
tools/xenpaging/xenpaging.c | 4
xen/arch/ia64/xen/dom0_ops.c | 2
xen/arch/x86/hvm/hvm.c | 4
xen/arch/x86/mm/mem_event.c | 242 +++++++++++++++++++-----------------
xen/arch/x86/mm/mem_paging.c | 4
xen/arch/x86/mm/mem_sharing.c | 22 +--
xen/arch/x86/mm/p2m.c | 18 +-
xen/include/asm-x86/mem_event.h | 8 -
xen/include/public/domctl.h | 43 +++---
xen/include/xen/sched.h | 6
17 files changed, 250 insertions(+), 203 deletions(-)
next reply other threads:[~2011-09-08 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 9:57 Olaf Hering [this message]
2011-09-08 9:57 ` [PATCH 1 of 2] mem_event: pass mem_event_domain pointer to mem_event functions Olaf Hering
2011-09-08 9:57 ` [PATCH 2 of 2] mem_event: use different ringbuffers for share, paging and access Olaf Hering
2011-09-12 13:57 ` [PATCH 0 of 2] v2: memshare/xenpaging/xen-access fixes for xen-unstable Tim Deegan
2011-09-15 10:21 ` Ian Jackson
2011-09-16 11:20 ` Tim Deegan
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=patchbomb.1315475828@probook.site \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.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).