From: Andres Lagar-Cavilla <andres@lagarcavilla.org>
To: xen-devel@lists.xen.org
Cc: andres@gridcentric.ca, tim@xen.org
Subject: [PATCH 0 of 2] Sharing bug fixes
Date: Tue, 24 Apr 2012 15:20:17 -0400 [thread overview]
Message-ID: <patchbomb.1335295217@xdev.gridcentric.ca> (raw)
Two small sharing bug fixes:
- Stats were going out of sync if unshare failed with ENOMEM.
- The test for a hole in the physmap in sharing_add_to_physmap was incomplete.
This latter patch adds feedback from Tim Deegan.
Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
xen/arch/x86/mm/mem_sharing.c | 2 ++
xen/arch/x86/mm/mem_sharing.c | 7 ++++---
xen/include/asm-x86/p2m.h | 8 ++++++++
3 files changed, 14 insertions(+), 3 deletions(-)
next reply other threads:[~2012-04-24 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 19:20 Andres Lagar-Cavilla [this message]
2012-04-24 19:20 ` [PATCH 1 of 2] x86/mem_sharing: Fix saved mfns stat for failed unsharing Andres Lagar-Cavilla
2012-04-26 9:13 ` Tim Deegan
2012-04-24 19:20 ` [PATCH 2 of 2] x86/mem_sharing: Rectify test for "empty" physmap entry in sharing_add_to_physmap Andres Lagar-Cavilla
2012-04-25 12:41 ` Tim Deegan
2012-04-25 15:20 ` 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.1335295217@xdev.gridcentric.ca \
--to=andres@lagarcavilla.org \
--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).