From: Claudio Fontana <cfontana@suse.de>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "Andrew Jones" <drjones@redhat.com>,
qemu-arm@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 3/3] target/arm: Restrict v7A TCG cpus to TCG accel
Date: Thu, 18 Mar 2021 10:56:48 +0100 [thread overview]
Message-ID: <e0d11b2c-7b1c-c968-feb2-675a8c98c7a4@suse.de> (raw)
In-Reply-To: <8a302c84-b69c-b0c2-de45-607dd1f686a6@redhat.com>
On 3/18/21 10:47 AM, Philippe Mathieu-Daudé wrote:
> Hi Peter,
>
> On 3/11/21 11:43 AM, Claudio Fontana wrote:
>> On 2/21/21 11:26 PM, Philippe Mathieu-Daudé wrote:
>>> KVM requires the target cpu to be at least ARMv8 architecture
>>> (support on ARMv7 has been dropped in commit 82bf7ae84ce:
>>> "target/arm: Remove KVM support for 32-bit Arm hosts").
>>>
>>> A KVM-only build won't be able to run TCG cpus, move the
>>> v7A CPU definitions to cpu_tcg.c.
>>>
>>> Reported-by: Peter Maydell <peter.maydell@linaro.org>
>>> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>
>>
>> Here I think it's better to keep the "a15" cpu around,
>> until we fix the board configuration situation.
>>
>> I added a patch that does that into my KVM-only build series, to avoid the resulting breakages.
>
> Actually I got a downstream report that this break migration from QEMU
> 5.2 to QEMU 6.0.
>
> I first thought it was on an old kernel (with 32-bit KVM enabled),
> but not, it is for Aarch64 VMs on recent KVM (without 32-bit support)
> but the 'virt' machines were started with default Cortex-A15 CPU...
>
> mc->default_cpu_type = ARM_CPU_TYPE_NAME("cortex-a15");
>
> I'm not sure upstream should care about this case, but I though
> maybe you could give me hints about the best way to keep old VMs
> working, as this likely affects any distribution. Obviously not
> upgrading QEMU is not a solution :)
>
> The simplest seems to revert 82bf7ae84ce and this patch, but I
> doubt this will be enough.
>
> Maybe there is some clever thing to do before reverting 82bf7ae84ce,
> that could also benefit upstream, by doing something with versioned
> machines? I have no idea (yet) how that work and if it could work.
Does just applying my series fix it?
https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg06463.html
Ie, I have resurrected specifically the a15 to keep things working for "virt".
Patch 22/50. Maybe I am missing something though?
https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg06494.html
Ciao,
Claudio
next prev parent reply other threads:[~2021-03-18 9:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 22:26 [PATCH v2 0/3] target/arm: Restrict v7A TCG cpus to TCG accel Philippe Mathieu-Daudé
2021-02-21 22:26 ` [PATCH v2 1/3] target/arm: Restrict v8M IDAU to TCG Philippe Mathieu-Daudé
2021-03-09 13:41 ` Claudio Fontana
2021-03-09 14:18 ` Philippe Mathieu-Daudé
2021-03-09 14:55 ` Claudio Fontana
2021-03-10 11:46 ` Claudio Fontana
2021-03-10 13:42 ` Philippe Mathieu-Daudé
2021-03-10 13:45 ` Claudio Fontana
2021-03-10 14:00 ` Claudio Fontana
2021-03-10 14:19 ` Philippe Mathieu-Daudé
2021-02-21 22:26 ` [PATCH v2 2/3] target/arm/cpu: Update coding style to make checkpatch.pl happy Philippe Mathieu-Daudé
2021-02-21 22:26 ` [PATCH v2 3/3] target/arm: Restrict v7A TCG cpus to TCG accel Philippe Mathieu-Daudé
2021-03-11 10:43 ` Claudio Fontana
2021-03-18 9:47 ` Philippe Mathieu-Daudé
2021-03-18 9:56 ` Claudio Fontana [this message]
2021-03-18 10:47 ` Philippe Mathieu-Daudé
2021-03-18 11:09 ` Philippe Mathieu-Daudé
2021-03-18 11:21 ` Peter Maydell
2021-03-18 11:31 ` Philippe Mathieu-Daudé
2021-03-18 11:38 ` Peter Maydell
2021-03-18 12:37 ` Andrew Jones
2021-03-18 12:50 ` Claudio Fontana
2021-03-18 13:14 ` Philippe Mathieu-Daudé
2021-03-05 14:38 ` [PATCH v2 0/3] " Peter Maydell
2021-03-06 15:13 ` Philippe Mathieu-Daudé
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=e0d11b2c-7b1c-c968-feb2-675a8c98c7a4@suse.de \
--to=cfontana@suse.de \
--cc=alex.bennee@linaro.org \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@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).