From: Marc Zyngier <marc.zyngier@arm.com>
To: "Chalamarla, Tirumalesh" <Tirumalesh.Chalamarla@caviumnetworks.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
kvm-devel <kvm@vger.kernel.org>,
"timur@codeaurora.org" <timur@codeaurora.org>,
"vgandhi@codeaurora.org" <vgandhi@codeaurora.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64/kvm: Add generic v8 KVM target
Date: Fri, 03 Jul 2015 09:08:14 +0100 [thread overview]
Message-ID: <559642EE.1050605@arm.com> (raw)
In-Reply-To: <D805D093-CCFE-4835-853A-B2654DAA10A1@caviumnetworks.com>
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).
Thanks,
M.
>
> Thanks,
> Tirumalesh.
>> On Jun 29, 2015, at 11:39 AM, Chalamarla, Tirumalesh
>> <Tirumalesh.Chalamarla@caviumnetworks.com
>> <mailto:Tirumalesh.Chalamarla@caviumnetworks.com>> wrote:
>>
>>>
>>> On Jun 29, 2015, at 10:52 AM, Marc Zyngier <marc.zyngier@arm.com
>>> <mailto:marc.zyngier@arm.com>> wrote:
>>>
>>> On 29/06/15 18:38, Peter Maydell wrote:
>>>> On 29 June 2015 at 18:30, Marc Zyngier <marc.zyngier@arm.com
>>>> <mailto:marc.zyngier@arm.com>> wrote:
>>>>> On 29/06/15 18:13, Chalamarla, Tirumalesh wrote:
>>>>>> Will this also prevents migrating between same implementations,
>>>>>> if no how is this identified.
>>>>>
>>>>> This shouldn't. It is pretty easy to look at the incoming guest's MIDR,
>>>>> and verify that it matches the default MIDR on the receiving
>>>>> system. Any
>>>>> difference, and the migration should abort.
>>>>
>>>> Do you really want to forbid migration between (say)
>>>> Cortex-A57 r3p0 and Cortex-A57 r3p1 ?
>>>>
>>>> That seems pretty harsh.
>>>
>>> I think we may need to allow for some flexibility (same major version
>>> only, or +/- 1 minor version...). The idea I'm trying to convey is that
>>> with "generic CPI", migration is not guaranteed unless we're on
>>> extremely similar hardware.
>>>
>> yes, this is the point i am trying to make, we need some flexibility.
>> so that it works with same chips with different passes may be.
>> if we are allowing this, then we are not putting emulation as a
>> requirement.
>>
>> Thanks,
>> Tirumalesh.
>>
>>> M.
>>> --
>>> Jazz is not dead. It just smells funny...
>
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
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:08:14 +0100 [thread overview]
Message-ID: <559642EE.1050605@arm.com> (raw)
In-Reply-To: <D805D093-CCFE-4835-853A-B2654DAA10A1@caviumnetworks.com>
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).
Thanks,
M.
>
> Thanks,
> Tirumalesh.
>> On Jun 29, 2015, at 11:39 AM, Chalamarla, Tirumalesh
>> <Tirumalesh.Chalamarla@caviumnetworks.com
>> <mailto:Tirumalesh.Chalamarla@caviumnetworks.com>> wrote:
>>
>>>
>>> On Jun 29, 2015, at 10:52 AM, Marc Zyngier <marc.zyngier@arm.com
>>> <mailto:marc.zyngier@arm.com>> wrote:
>>>
>>> On 29/06/15 18:38, Peter Maydell wrote:
>>>> On 29 June 2015 at 18:30, Marc Zyngier <marc.zyngier@arm.com
>>>> <mailto:marc.zyngier@arm.com>> wrote:
>>>>> On 29/06/15 18:13, Chalamarla, Tirumalesh wrote:
>>>>>> Will this also prevents migrating between same implementations,
>>>>>> if no how is this identified.
>>>>>
>>>>> This shouldn't. It is pretty easy to look at the incoming guest's MIDR,
>>>>> and verify that it matches the default MIDR on the receiving
>>>>> system. Any
>>>>> difference, and the migration should abort.
>>>>
>>>> Do you really want to forbid migration between (say)
>>>> Cortex-A57 r3p0 and Cortex-A57 r3p1 ?
>>>>
>>>> That seems pretty harsh.
>>>
>>> I think we may need to allow for some flexibility (same major version
>>> only, or +/- 1 minor version...). The idea I'm trying to convey is that
>>> with "generic CPI", migration is not guaranteed unless we're on
>>> extremely similar hardware.
>>>
>> yes, this is the point i am trying to make, we need some flexibility.
>> so that it works with same chips with different passes may be.
>> if we are allowing this, then we are not putting emulation as a
>> requirement.
>>
>> Thanks,
>> Tirumalesh.
>>
>>> M.
>>> --
>>> Jazz is not dead. It just smells funny...
>
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-07-03 8:08 UTC|newest]
Thread overview: 61+ 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-17 9:00 ` Suzuki K. Poulose
2015-06-19 20:31 ` Timur Tabi
2015-06-19 20:31 ` Timur Tabi
2015-06-22 6:47 ` Marc Zyngier
2015-06-22 6:47 ` Marc Zyngier
2015-06-22 8:44 ` Peter Maydell
2015-06-22 8:44 ` Peter Maydell
2015-06-23 12:39 ` Christoffer Dall
2015-06-23 12:39 ` Christoffer Dall
2015-06-23 14:03 ` Suzuki K. Poulose
2015-06-23 14:03 ` Suzuki K. Poulose
2015-06-23 14:16 ` Peter Maydell
2015-06-23 14:16 ` Peter Maydell
2015-06-24 8:29 ` Marc Zyngier
2015-06-24 8:29 ` Marc Zyngier
2015-06-24 8:51 ` Christoffer Dall
2015-06-24 8:51 ` Christoffer Dall
2015-06-24 9:32 ` Marc Zyngier
2015-06-24 9:32 ` Marc Zyngier
2015-06-25 12:30 ` Christoffer Dall
2015-06-25 12:30 ` Christoffer Dall
2015-06-25 12:40 ` Marc Zyngier
2015-06-25 12:40 ` Marc Zyngier
2015-06-25 13:44 ` Marc Zyngier
2015-06-25 13:44 ` Marc Zyngier
2015-06-25 13:49 ` Peter Maydell
2015-06-25 13:49 ` Peter Maydell
2015-06-26 9:53 ` Christoffer Dall
2015-06-26 9:53 ` Christoffer Dall
2015-06-29 17:13 ` Chalamarla, Tirumalesh
2015-06-29 17:13 ` Chalamarla, Tirumalesh
2015-06-29 17:30 ` Marc Zyngier
2015-06-29 17:30 ` Marc Zyngier
2015-06-29 17:38 ` Peter Maydell
2015-06-29 17:38 ` Peter Maydell
2015-06-29 17:52 ` Marc Zyngier
2015-06-29 17:52 ` Marc Zyngier
2015-06-29 18:39 ` Chalamarla, Tirumalesh
2015-06-29 18:39 ` Chalamarla, Tirumalesh
2015-07-02 20:29 ` Chalamarla, Tirumalesh
2015-07-03 8:08 ` Marc Zyngier [this message]
2015-07-03 8:08 ` Marc Zyngier
2015-07-03 8:12 ` Peter Maydell
2015-07-03 8:12 ` Peter Maydell
2015-07-03 8:28 ` Marc Zyngier
2015-07-03 8:28 ` Marc Zyngier
2015-07-03 9:34 ` Peter Maydell
2015-07-03 9:34 ` Peter Maydell
2015-07-03 10:10 ` Marc Zyngier
2015-07-03 10:10 ` Marc Zyngier
2015-07-17 9:33 ` Christoffer Dall
2015-07-17 9:33 ` Christoffer Dall
2015-07-17 9:56 ` Marc Zyngier
2015-07-17 9:56 ` Marc Zyngier
2015-07-17 10:15 ` Christoffer Dall
2015-07-17 10:15 ` Christoffer Dall
2015-07-17 10:19 ` Marc Zyngier
2015-07-17 10:19 ` Marc Zyngier
2015-07-17 17:56 ` Chalamarla, Tirumalesh
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=559642EE.1050605@arm.com \
--to=marc.zyngier@arm.com \
--cc=Tirumalesh.Chalamarla@caviumnetworks.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peter.maydell@linaro.org \
--cc=timur@codeaurora.org \
--cc=vgandhi@codeaurora.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.