linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/kvm: Add generic v8 KVM target
Date: Fri, 26 Jun 2015 11:53:18 +0200	[thread overview]
Message-ID: <20150626095318.GG28244@cbox> (raw)
In-Reply-To: <CAFEAcA_ULz=ugQW=NmthzqYRtvcfwteQTh0DonHRN6U5NykEtQ@mail.gmail.com>

On Thu, Jun 25, 2015 at 02:49:08PM +0100, Peter Maydell wrote:
> On 25 June 2015 at 14:44, Marc Zyngier <marc.zyngier@arm.com> wrote:
> > It should always be possible to emulate a "known" CPU on a generic host,
> > and it should be able to migrate. The case we can't migrate is when we
> > let the guest be generic (which I guess should really be unknown, and
> > not generic).
> >
> > So if the user specify "-cpu cortex-a57" on the command line, the guest
> > should be able to migrate from an A72 to an A53. if the user specified
> > "-cpu host", the resulting guest won't be able to migrate.
> >
> > Does it make sense?
> 
> Yes. We've always said "-cpu host" won't be cross-host migratable
> from a QEMU point of view.
> 
ok, this makes sense.  It's basically up to userspace to mandate that
trying to migrate something that used unknown cpu (via -cpu host or
whatever) cannot be migrated.

-Christoffer

  reply	other threads:[~2015-06-26  9:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  9:00 [PATCH] arm64/kvm: Add generic v8 KVM target Suzuki K. Poulose
2015-06-19 20:31 ` Timur Tabi
2015-06-22  6:47   ` Marc Zyngier
2015-06-22  8:44 ` Peter Maydell
2015-06-23 12:39   ` Christoffer Dall
2015-06-23 14:03     ` Suzuki K. Poulose
2015-06-23 14:16       ` Peter Maydell
2015-06-24  8:29   ` Marc Zyngier
2015-06-24  8:51     ` Christoffer Dall
2015-06-24  9:32       ` Marc Zyngier
2015-06-25 12:30         ` Christoffer Dall
2015-06-25 12:40           ` Marc Zyngier
2015-06-25 13:44             ` Marc Zyngier
2015-06-25 13:49               ` Peter Maydell
2015-06-26  9:53                 ` Christoffer Dall [this message]
2015-06-29 17:13                   ` Chalamarla, Tirumalesh
2015-06-29 17:30                     ` Marc Zyngier
2015-06-29 17:38                       ` Peter Maydell
2015-06-29 17:52                         ` Marc Zyngier
2015-06-29 18:39                           ` Chalamarla, Tirumalesh
     [not found]                             ` <D805D093-CCFE-4835-853A-B2654DAA10A1@caviumnetworks.com>
2015-07-03  8:08                               ` Marc Zyngier
2015-07-03  8:12                                 ` Peter Maydell
2015-07-03  8:28                                   ` Marc Zyngier
2015-07-03  9:34                                     ` Peter Maydell
2015-07-03 10:10                                       ` Marc Zyngier
2015-07-17  9:33                                         ` Christoffer Dall
2015-07-17  9:56                                           ` Marc Zyngier
2015-07-17 10:15                                             ` Christoffer Dall
2015-07-17 10:19                                               ` Marc Zyngier
2015-07-17 17:56                                                 ` Chalamarla, Tirumalesh

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=20150626095318.GG28244@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).