xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: andres@gridcentric.ca, adin@gridcentric.ca, olaf@aepfle.de,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] Mem event: don't leave zombie domains if there are wait-queued vcpus
Date: Thu, 15 Mar 2012 11:32:22 +0000	[thread overview]
Message-ID: <20120315113222.GD4798@ocelot.phlegethon.org> (raw)
In-Reply-To: <06a927b592df2899be2b.1331565426@xdev.gridcentric.ca>

At 11:17 -0400 on 12 Mar (1331551026), Andres Lagar-Cavilla wrote:
>  xen/arch/x86/mm/mem_event.c |  19 ++++++++++++++++---
>  1 files changed, 16 insertions(+), 3 deletions(-)
> 
> 
> Vcpus in wait queues retain a domain reference. Upon domain destruction, we
> were not taking care of draining the wait queues.

Applied, thanks.

Tim.

      reply	other threads:[~2012-03-15 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 15:17 [PATCH] Mem event: don't leave zombie domains if there are wait-queued vcpus Andres Lagar-Cavilla
2012-03-15 11:32 ` Tim Deegan [this message]

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=20120315113222.GD4798@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=adin@gridcentric.ca \
    --cc=andres@gridcentric.ca \
    --cc=andres@lagarcavilla.org \
    --cc=olaf@aepfle.de \
    --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).