All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Lagar-Cavilla <andres@lagarcavilla.org>
To: xen-devel@lists.xensource.com
Cc: andres@gridcentric.ca, keir.xen@gmail.com, tim@xen.org,
	olaf@aepfle.de, adin@gridcentric.ca
Subject: [PATCH 0 of 2] Mem event ring management overhaul
Date: Mon, 05 Dec 2011 10:24:07 -0500	[thread overview]
Message-ID: <patchbomb.1323098647@xdev.gridcentric.ca> (raw)

Ensure no guest events are ever lost in the mem event ring.

This is one of two outstanding proposals to solve this issue. One
key difference between them being that ours does not necessitate wait 
queues.

Instead, we rely on foreign domain retry (already in place), preempting
hypercalls that may cause unbounded guest events (such as 
decrease_reservation), and ensuring there is always space left in the 
ring for each guest vcpu to place at least one event.
 
The patch has been refreshed to apply on top of 62ff6a318c5d, and untangled
from other mem event modifications that are essentially orthogonal and can 
go in independently. 

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          |   21 ++-
 xen/arch/x86/mm/mem_event.c     |  203 +++++++++++++++++++++++++++++----------
 xen/arch/x86/mm/mem_sharing.c   |   17 ++-
 xen/arch/x86/mm/p2m.c           |   47 +++++----
 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 +-
 10 files changed, 257 insertions(+), 96 deletions(-)

             reply	other threads:[~2011-12-05 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 15:24 Andres Lagar-Cavilla [this message]
2011-12-05 15:24 ` [PATCH 1 of 2] Allow decrease_reservation to be preempted if remove_page returns negative Andres Lagar-Cavilla
2011-12-06  9:48   ` Jan Beulich
2011-12-05 15:24 ` [PATCH 2 of 2] Improve ring management for memory events. Do not lose guest events Andres Lagar-Cavilla
2011-12-06 17:26 ` [PATCH 0 of 2] Mem event ring management overhaul Olaf Hering
2011-12-06 17:43   ` Andres Lagar-Cavilla
2011-12-07 13:17     ` Olaf Hering
2011-12-07 16:26       ` 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.1323098647@xdev.gridcentric.ca \
    --to=andres@lagarcavilla.org \
    --cc=adin@gridcentric.ca \
    --cc=andres@gridcentric.ca \
    --cc=keir.xen@gmail.com \
    --cc=olaf@aepfle.de \
    --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.