All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	Dave McCracken <dcm@mccr.org>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH 1/2] PV hugepages - Xen patch
Date: Thu, 09 Oct 2008 17:05:38 -0700	[thread overview]
Message-ID: <48EE9C52.4020704@goop.org> (raw)
In-Reply-To: <20081009083848.GB26108@redhat.com>

Daniel P. Berrange wrote:
> Or you could just take the view this is a pre-migration capability check,
> and that admin (or mgmt app) must ensure sufficient free hugepages on the 
> destination before attempting migration. If this isn't satisfied then
> XenD can just fail / abort the migration op and leave it running on original
> host.
>   

And do something to prevent new hugepages from being allocated during 
the dirty logging phase?

    J

      reply	other threads:[~2008-10-10  0:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 23:26 [PATCH 1/2] PV hugepages - Xen patch Dave McCracken
2008-10-03  8:58 ` Keir Fraser
2008-10-08 17:05   ` Dave McCracken
2008-10-08 18:11     ` Keir Fraser
2008-10-08 18:28       ` Dave McCracken
2008-10-08 18:50         ` Keir Fraser
2008-10-08 22:07           ` Dave McCracken
2008-10-09  6:45             ` Keir Fraser
2008-10-09 10:21             ` Keir Fraser
2008-10-08 22:50       ` Jeremy Fitzhardinge
2008-10-09  8:38         ` Daniel P. Berrange
2008-10-10  0:05           ` Jeremy Fitzhardinge [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=48EE9C52.4020704@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=berrange@redhat.com \
    --cc=dcm@mccr.org \
    --cc=keir.fraser@eu.citrix.com \
    --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.