All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v4] spapr: add uuid/host details to device tree
Date: Tue, 08 Jul 2014 20:55:52 +1000	[thread overview]
Message-ID: <1404816952.16156.79.camel@pasglop> (raw)
In-Reply-To: <53BBCC9D.5070000@suse.de>

On Tue, 2014-07-08 at 12:49 +0200, Alexander Graf wrote:
> Please be aware that all of the above is bogus when you start
> thinking 
> about live migration.

What's probably where we need to start thinking about implementing
migration according to PAPR :-)

IE. With pre and post-migration notifications to the guest including
device-tree updates.

Cheers,
Ben.

  reply	other threads:[~2014-07-08 10:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  5:00 [Qemu-devel] [PATCH v4] spapr: add uuid/host details to device tree Nikunj A Dadhania
2014-07-08 10:49 ` Alexander Graf
2014-07-08 10:55   ` Benjamin Herrenschmidt [this message]
2014-07-08 11:04   ` Nikunj A Dadhania
2014-07-08 11:11     ` Alexander Graf
2014-07-08 11:26       ` Nikunj A Dadhania

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=1404816952.16156.79.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=agraf@suse.de \
    --cc=nikunj@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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.