From: Andres Lagar-Cavilla <andres@lagarcavilla.org>
To: xen-devel@lists.xen.org
Cc: andres@gridcentric.ca, tim@xen.org, adin@gridcentric.ca
Subject: [PATCH 0 of 2] x86/mm: Unsharing ENOMEM handling
Date: Mon, 12 Mar 2012 11:29:36 -0400 [thread overview]
Message-ID: <patchbomb.1331566176@xdev.gridcentric.ca> (raw)
These two patches were originally posted on Feb 15th as part of a larger
series.
They were left to simmer as a discussion on wait queues took precedence.
Regardless of the ultimate fate of wait queues, these two patches are necessary
as they solve some bugs on the memory sharing side. When unsharing fails,
domains would spin forever, hosts would crash, etc.
The patches also clarify the semantics of unsharing, and comment how it's
handled.
Two comments against the Feb 15th series taken care of here:
- We assert that the unsharing code can only return success or ENOMEN.
- Acked-by Tim Deegan added to patch #1
Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Signed-off-by: Adin Scannell <adin@scannell.ca>
Acked-by: Tim Deegan <tim@xen.org>
xen/arch/x86/mm/mem_event.c | 5 ++-
xen/include/asm-x86/mem_event.h | 30 ++++++++++++++++++---
xen/arch/x86/hvm/hvm.c | 23 +++++++++++++++-
xen/arch/x86/mm.c | 8 +++--
xen/arch/x86/mm/mem_sharing.c | 54 +++++++++++++++++++++++---------------
xen/arch/x86/mm/p2m.c | 18 ++++++++++++-
xen/common/grant_table.c | 11 ++++---
xen/common/memory.c | 1 +
xen/include/asm-x86/mem_sharing.h | 27 ++++++++++++++++++-
9 files changed, 138 insertions(+), 39 deletions(-)
next reply other threads:[~2012-03-12 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 15:29 Andres Lagar-Cavilla [this message]
2012-03-12 15:29 ` [PATCH 1 of 2] x86/mm: Allow to not sleep on mem event ring Andres Lagar-Cavilla
2012-03-12 15:29 ` [PATCH 2 of 2] Memory sharing: better handling of ENOMEM while unsharing Andres Lagar-Cavilla
2012-03-15 11:34 ` [PATCH 0 of 2] x86/mm: Unsharing ENOMEM handling Tim Deegan
2012-03-15 14:35 ` Andres Lagar-Cavilla
2012-03-15 15:36 ` Tim Deegan
2012-03-15 16:44 ` 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.1331566176@xdev.gridcentric.ca \
--to=andres@lagarcavilla.org \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=tim@xen.org \
--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).