From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Claudio Fontana <cfontana@suse.de>,
Andrew Jones <drjones@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 3/3] target/arm: Restrict v7A TCG cpus to TCG accel
Date: Thu, 18 Mar 2021 14:14:37 +0100 [thread overview]
Message-ID: <cec1eb2b-197f-b3d5-4187-f06b59be1657@redhat.com> (raw)
In-Reply-To: <f41c34dc-2cad-5929-06d8-6ea098ab5b8a@suse.de>
On 3/18/21 1:50 PM, Claudio Fontana wrote:
> On 3/18/21 1:37 PM, Andrew Jones wrote:
>> On Thu, Mar 18, 2021 at 11:38:51AM +0000, Peter Maydell wrote:
>>> On Thu, 18 Mar 2021 at 11:31, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>>> I tend to agree. The problem is for the running VMs started before
>>>> 82bf7ae84ce (so up to any fork based on v5.2). I don't know what
>>>> the forks are supposed to do with the running VMs if they want to
>>>> migrate them to newer QEMU (or upgrade the host QEMU).
>>>
>>> Anybody with a Cortex-A15 KVM VM is just going to have to stay
>>> with their pre-existing ancient hardware, their pre-existing
>>> host kernel and their pre-existing QEMU binary. That's what
>>> "we deprecated and then dropped support for this" means:
>>> we no longer support running that kind of VM, so users who
>>> were doing it need to either do something else instead, or
>>> else just keep on going with the old versions they have.
>>>
>>
>> I strongly agree.
>>
>> And, downstream-wise, I can't speak for anything but RHEL, but RHEL
>> cannot have this problem. There are no 32-bit ARM builds for RHEL.
Great then. Sorry for the confusion.
> I don't see a strong issue with this either, there is no 32bit support for KVM ARM.
next prev parent reply other threads:[~2021-03-18 13:18 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
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é [this message]
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=cec1eb2b-197f-b3d5-4187-f06b59be1657@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--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).