From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/kvm: Add generic v8 KVM target
Date: Fri, 03 Jul 2015 09:28:23 +0100 [thread overview]
Message-ID: <559647A7.7010309@arm.com> (raw)
In-Reply-To: <CAFEAcA8nt7yr0K4QesJjWqEwBgziWOt2DViY70E=z2wjt=X7XA@mail.gmail.com>
On 03/07/15 09:12, Peter Maydell wrote:
> On 3 July 2015 at 09:08, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> On 02/07/15 21:29, Chalamarla, Tirumalesh wrote:
>>> is there a chance that this get merged in to 4.2? if not is it possible
>>> to accept the other patches like adding implementations explicitly(like
>>> Thunder).
>>
>> We first need to reach a conclusion on this. Until then, I don't plan to
>> get anything in. As for 4.2, it feels way too late (the merge window is
>> almost closed now).
>
> I would still like to see the proponents of this patch say
> what their model is for userspace support of cross-host migration,
> if we're abandoning the model the current API envisages.
I thought we had discussed this above, and don't really see this as a
departure from the current model:
- "-cpu host" results in "GENERIC" being used: VM can only be migrated
to the exact same HW (no cross-host migration). MIDR should probably
become RO.
- "-cpu host" results in "A57" (for example): VM can be migrated to a
variety of A57 platforms, and allow for some fuzzing on the revision (or
accept any revision).
- "-cpu a57" forces an A57 model to be emulated, always. It is always
possible to migrate such a VM on any host.
I think only the first point is new, but the last two are what we have
(or what we should have).
Does it answer your concerns, or did you have something else in mind?
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-07-03 8:28 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
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 [this message]
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=559647A7.7010309@arm.com \
--to=marc.zyngier@arm.com \
--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).