qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: "Alexey Kardashevskiy" <aik@ozlabs.ru>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Paul Mackerras" <paulus@samba.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH] spapr: support time base offset migration
Date: Mon, 09 Sep 2013 19:29:36 +1000	[thread overview]
Message-ID: <1378718976.11525.1.camel@pasglop> (raw)
In-Reply-To: <7B3E1C54-B3E4-4E86-ACC0-2824199BA154@suse.de>

On Mon, 2013-09-09 at 08:06 +0200, Alexander Graf wrote:
> I think it's ok to restrict live migration to machines with the same
> tb frequency when kvm is enabled. Whether you implement it through a
> hardcoded 512Mhz or through a timebase value that gets live migrated
> and then compared is up to you - both ways work for me :).

The latter might be handy if we want to support migration on 970, though
we don't have the TBU40 stuff there so adjusting the TB in the host
kernel would be ... problematic.

Cheers,
Ben.

  reply	other threads:[~2013-09-09  9:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  7:31 [Qemu-devel] [RFC PATCH] spapr: support time base offset migration Alexey Kardashevskiy
2013-09-03  8:42 ` Andreas Färber
2013-09-03  9:07   ` Alexey Kardashevskiy
2013-09-03  9:22     ` Andreas Färber
2013-09-04  1:13       ` Alexey Kardashevskiy
2013-09-04  1:27         ` Alexander Graf
2013-09-05  4:30 ` David Gibson
2013-09-05  4:54   ` Alexey Kardashevskiy
2013-09-05  9:16     ` Alexander Graf
2013-09-05  9:48       ` Alexey Kardashevskiy
2013-09-05  9:58         ` Alexander Graf
2013-09-05 11:44           ` Benjamin Herrenschmidt
2013-09-05 12:37             ` Alexander Graf
2013-09-05 13:36               ` Benjamin Herrenschmidt
2013-09-05 13:39                 ` Alexander Graf
2013-09-05 14:14                   ` Andreas Färber
2013-09-05 14:26                     ` Benjamin Herrenschmidt
2013-09-05 15:11                       ` Alexander Graf
2013-09-09  2:40                         ` Alexey Kardashevskiy
2013-09-09  5:50                           ` Alexander Graf
2013-09-09  5:58                             ` Alexey Kardashevskiy
2013-09-09  6:06                               ` Alexander Graf
2013-09-09  9:29                                 ` Benjamin Herrenschmidt [this message]
2013-09-09  9:32                                   ` Alexander Graf
2013-09-09  9:38                                     ` Benjamin Herrenschmidt
2013-09-09  9:41                                       ` Alexander Graf
2013-09-13  5:20                                 ` David Gibson
2013-09-13 18:06                                   ` Alexander Graf
2013-09-05 11:42         ` Benjamin Herrenschmidt
2013-09-05 12:09           ` Alexey Kardashevskiy
2013-09-06  3:00     ` David Gibson

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=1378718976.11525.1.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=paulus@samba.org \
    --cc=pbonzini@redhat.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 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).