All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/libxc: Disable CONFIG_MIGRATE in stubdom environments
Date: Tue, 27 Jan 2015 17:25:28 +0000	[thread overview]
Message-ID: <1422379528.16180.28.camel@citrix.com> (raw)
In-Reply-To: <54C7C9B6.2000301@citrix.com>

On Tue, 2015-01-27 at 17:24 +0000, Andrew Cooper wrote:
> On 27/01/15 17:12, Ian Campbell wrote:
> > On Tue, 2015-01-27 at 17:10 +0000, Andrew Cooper wrote:
> >>> As opposed to e.g. an HVM domain using a qemu-stubdom, but being
> >>> migrated by a normal toolstack in domain 0 (or at least, not in a
> >>> mini-os based stubdom).
> >> A qemu-stubdom equally cant participate in migrate of its domain
> >> (because of the issues in passing the qemu save record), but that is a
> >> separate issue.
> > This works today AFAIK, I'm afraid I think it needs to keep working for
> > the new migration stuff to land.
> 
> Nothing along these lines is (should be) impacted by legacy vs
> migration-v2.  Migration v2 changes the point at which the existing qemu
> save record infrastructure is called, but does not change its functionality.
> 
> But as I say, this point is unrelated to the purpose of the patch.

Yes, I wasn't sure why you brought it up given that so I wanted to
clarify.

Ian.

      reply	other threads:[~2015-01-27 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 16:58 [PATCH] tools/libxc: Disable CONFIG_MIGRATE in stubdom environments Andrew Cooper
2015-01-27 17:01 ` Ian Campbell
2015-01-27 17:10   ` Andrew Cooper
2015-01-27 17:12     ` Ian Campbell
2015-01-27 17:24       ` Andrew Cooper
2015-01-27 17:25         ` 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=1422379528.16180.28.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@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.