From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: "Nikunj A Dadhania" <nikunj@linux.vnet.ibm.com>,
"Alexander Graf" <agraf@suse.de>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Paul Mackerras" <paulus@samba.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [RFC PATCH] spapr: add initial ibm, client-architecture-support rtas call support
Date: Wed, 04 Sep 2013 21:54:12 +1000 [thread overview]
Message-ID: <1378295652.4321.18.camel@pasglop> (raw)
In-Reply-To: <52271C41.7070005@ozlabs.ru>
On Wed, 2013-09-04 at 21:40 +1000, Alexey Kardashevskiy wrote:
> One of the examples (came from Paul) is:
> the host runs on POWER8, the guest boots a kernel which is capable of
> POWER7 only + POWER7-compat. We do this reboot tweak and boot in
> POWER7-compat mode. Then the guest does "yum update" and gets POWER8
> kernel
> installed so when it reboots, it will boot in normal POWER8 mode.
> Everybody
> is happy.
>
> Having POWER7-compat mode set from the very beginning will break this
> behaviour.
But it will allow migrating that partition to a P7 machine. It's
important to be able to specify the compat mode for that reason, to
create guests that can be migrated to older machines.
Cheers,
Ben.
next prev parent reply other threads:[~2013-09-04 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 10:19 [Qemu-devel] [RFC PATCH] spapr: add initial ibm, client-architecture-support rtas call support Alexey Kardashevskiy
2013-09-04 10:42 ` Alexander Graf
2013-09-04 11:40 ` Alexey Kardashevskiy
2013-09-04 11:54 ` Benjamin Herrenschmidt [this message]
2013-09-04 12:59 ` Alexey Kardashevskiy
2013-09-04 12:13 ` Alexander Graf
2013-09-04 13:08 ` Alexey Kardashevskiy
2013-09-04 13:37 ` Alexander Graf
2013-09-04 21:32 ` Anthony Liguori
2013-09-05 10:16 ` Paul Mackerras
2013-09-05 10:19 ` Alexander Graf
2013-09-05 11:55 ` Paul Mackerras
2013-09-05 13:04 ` Alexander Graf
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=1378295652.4321.18.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=nikunj@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--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).