From: Andres Lagar-Cavilla <andres@lagarcavilla.org>
To: xen-devel@lists.xensource.com
Cc: ian.campbell@citrix.com, andres@gridcentric.ca, tim@xen.org,
keir.xen@gmail.com, JBeulich@suse.com, ian.jackson@citrix.com,
adin@gridcentric.ca
Subject: [PATCH 0 of 5] Memory event interface improvements
Date: Tue, 29 Nov 2011 16:55:09 -0500 [thread overview]
Message-ID: <patchbomb.1322603709@xdev.gridcentric.ca> (raw)
In this patch series we improve the management of congestion in the memory
events ring. We ensure no guest events are lost, even in the face of unbounded
flooding from foreign maps, or balloon.
Also, we enable resumption of mem events via an event channel kick from
user-space to Xen. This is more light-weight and scalable than the current
domctl interface, and allows for batching as well.
Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Signed-off-by: Adin Scannell <adin@scannell.ca>
xen/common/memory.c | 29 +++++-
xen/arch/x86/hvm/hvm.c | 20 ++-
xen/arch/x86/mm/mem_event.c | 205 ++++++++++++++++++++++++++++++---------
xen/arch/x86/mm/mem_sharing.c | 27 +++-
xen/arch/x86/mm/p2m.c | 104 ++++++++++---------
xen/common/memory.c | 7 +-
xen/include/asm-x86/mem_event.h | 16 ++-
xen/include/asm-x86/p2m.h | 6 +-
xen/include/xen/mm.h | 2 +
xen/include/xen/sched.h | 5 +-
xen/arch/ia64/vmx/vmx_init.c | 2 +-
xen/arch/x86/hvm/hvm.c | 7 +-
xen/arch/x86/mm/mem_event.c | 3 +-
xen/common/event_channel.c | 75 +++++++++++---
xen/include/xen/event.h | 5 +-
xen/include/xen/sched.h | 2 +-
xen/arch/x86/mm/mem_access.c | 3 +-
xen/arch/x86/mm/p2m.c | 3 +-
xen/include/asm-x86/p2m.h | 2 +-
xen/arch/x86/mm/mem_event.c | 26 +++-
20 files changed, 389 insertions(+), 160 deletions(-)
next reply other threads:[~2011-11-29 21:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 21:55 Andres Lagar-Cavilla [this message]
2011-11-29 21:55 ` [PATCH 1 of 5] Allow decrease_reservation to be preempted if remove_page returns negative Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 2 of 5] Improve ring management for memory events. Do not lose guest events Andres Lagar-Cavilla
2011-11-30 12:58 ` Olaf Hering
2011-11-30 15:11 ` Andres Lagar-Cavilla
2011-12-01 15:36 ` Olaf Hering
2011-12-01 14:51 ` Olaf Hering
2011-12-01 15:25 ` Andres Lagar-Cavilla
2011-12-05 11:23 ` Olaf Hering
2011-12-05 15:27 ` Andres Lagar-Cavilla
2011-12-01 18:10 ` Tim Deegan
2011-12-01 10:19 ` Keir Fraser
2011-12-01 18:27 ` Andres Lagar-Cavilla
2011-12-01 18:23 ` Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 3 of 5] Create a generic callback mechanism for Xen-bound event channels Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 4 of 5] Make the prototype of p2m_mem_access_resume consistent Andres Lagar-Cavilla
2011-12-01 18:01 ` Tim Deegan
2011-12-01 18:05 ` Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 5 of 5] Allow memevent responses to be signaled via the event channel Andres Lagar-Cavilla
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.1322603709@xdev.gridcentric.ca \
--to=andres@lagarcavilla.org \
--cc=JBeulich@suse.com \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=keir.xen@gmail.com \
--cc=tim@xen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.