All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Anshul Makkar <anshul.makkar@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.6 v2] x86/mm: Make {hap, shadow}_teardown() preemptible
Date: Thu, 6 Aug 2015 10:28:26 +0100	[thread overview]
Message-ID: <1438853306.9747.125.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZas8ph7bE4w5RBSvpXWJ_vu137G2XbTwdxizqsrwhLS-g@mail.gmail.com>

On Wed, 2015-08-05 at 18:00 +0100, George Dunlap wrote:
> On Wed, Aug 5, 2015 at 4:47 PM, Andrew Cooper <andrew.cooper3@citrix.com> 
> wrote:
> > From: Anshul Makkar <anshul.makkar@citrix.com>
> > 
> > A domain with sufficient shadow allocation can cause a watchdog timeout
> > during domain destruction.  Expand the existing -ERESTART logic in
> > paging_teardown() to allow {hap/sh}_set_allocation() to become
> > restartable during the DOMCTL_destroydomain hypercall.
> > 
> > Signed-off-by: Anshul Makkar <anshul.makkar@citrix.com>
> > Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > Reviewed-by: Tim Deegan <tim@xen.org>
> 
> Looks good, thanks:
> 
> Reviewed-by: George Dunlap <george.dunlap@eu.citrix.com>

Applied, thanks.

      reply	other threads:[~2015-08-06  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 15:47 [PATCH for-4.6 v2] x86/mm: Make {hap, shadow}_teardown() preemptible Andrew Cooper
2015-08-05 16:17 ` Wei Liu
2015-08-05 17:00 ` George Dunlap
2015-08-06  9:28   ` Ian Campbell [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=1438853306.9747.125.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anshul.makkar@citrix.com \
    --cc=wei.liu2@citrix.com \
    --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 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.