From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PULL 03/18] target/arm: Store FPSR cumulative exception bits in env->vfp.fpsr
Date: Thu, 31 Oct 2024 17:01:08 +0000 [thread overview]
Message-ID: <CAFEAcA_xoSkhk-dGUXw3-0hQyb1NF+6qRP-+6TpoQkFPOBs8Jg@mail.gmail.com> (raw)
In-Reply-To: <95086c66-9e1c-4013-86d6-373d68d55441@tls.msk.ru>
On Thu, 31 Oct 2024 at 16:55, Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> 29.10.2024 18:10, Peter Maydell wrote:
> ...
> > (Note for stable backports: the bug goes back to 4a15527c9fee but
> > this code was refactored in commits ea8618382aba..a8ab8706d4cc461, so
> > fixing it in branches without those refactorings will mean either
> > backporting the refactor or else implementing a conceptually similar
> > fix for the old code.)
>
> What do you think is the better way here -- pick up the refactoring
> changes (to 9.0 and earlier), do a backport of this single fix, or
> do nothing? Note for 7.2 branch it probably requires quite a bit
> more work.
The bug being fixed here is a bit niche (I don't think many
people build with KVM support only) so I would not worry
about backporting it all the way to 7.2. I'm not sure about
the best approach for 9.0 (which is why I left that note rather
than actively suggestion one or the other) -- it depends whether
you value more "backport the change that's actually been tested
by being in mainline" or "make the minimal set of changes in the
stable branch"...
-- PMM
next prev parent reply other threads:[~2024-10-31 17:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 15:10 [PULL 00/18] target-arm queue Peter Maydell
2024-10-29 15:10 ` [PULL 01/18] arm/kvm: add support for MTE Peter Maydell
2024-10-29 15:10 ` [PULL 02/18] docs/system/cpu-hotplug: Update example's socket-id/core-id Peter Maydell
2024-10-29 15:10 ` [PULL 03/18] target/arm: Store FPSR cumulative exception bits in env->vfp.fpsr Peter Maydell
2024-10-31 16:55 ` Michael Tokarev
2024-10-31 17:01 ` Peter Maydell [this message]
2024-10-31 17:31 ` Michael Tokarev
2024-10-31 17:40 ` Peter Maydell
2024-10-31 17:44 ` Michael Tokarev
2024-10-29 15:10 ` [PULL 04/18] target/arm: Don't assert in regime_is_user() for E10 mmuidx values Peter Maydell
2024-10-29 15:10 ` [PULL 05/18] hw/sd/omap_mmc: Don't use sd_cmd_type_t Peter Maydell
2024-10-29 15:10 ` [PULL 06/18] tests/functional: Add a functional test for the collie board Peter Maydell
2024-10-29 15:10 ` [PULL 07/18] tests/functional: Add a functional test for the sx1 board Peter Maydell
2024-10-29 15:10 ` [PULL 08/18] scripts/symlink-install-tree.py: Fix MESONINTROSPECT parsing Peter Maydell
2024-10-29 15:10 ` [PULL 09/18] docs/system/arm/stm32: List olimex-stm32-h405 in document title Peter Maydell
2024-10-29 15:10 ` [PULL 10/18] docs/system/arm: Don't use wildcard '*-bmc' in doc titles Peter Maydell
2024-10-29 15:10 ` [PULL 11/18] docs/system/arm: Split fby35 out from aspeed.rst Peter Maydell
2024-10-29 15:10 ` [PULL 12/18] docs/system/arm: Add placeholder doc for exynos4 boards Peter Maydell
2024-10-29 15:10 ` [PULL 13/18] docs/system/arm: Add placeholder doc for xlnx-zcu102 board Peter Maydell
2024-10-29 15:10 ` [PULL 14/18] docs/system/arm: Add placeholder docs for mcimx6ul-evk and mcimx7d-sabre Peter Maydell
2024-10-29 15:10 ` [PULL 15/18] docs/system/target-arm.rst: Remove "many boards are undocumented" note Peter Maydell
2024-10-29 15:10 ` [PULL 16/18] target/arm: Fix arithmetic underflow in SETM instruction Peter Maydell
2024-10-29 15:10 ` [PULL 17/18] docs/devel/reset: Fix minor grammatical error Peter Maydell
2024-10-29 15:10 ` [PULL 18/18] target/arm: kvm: require KVM_CAP_DEVICE_CTRL Peter Maydell
2024-10-31 16:33 ` [PULL 00/18] target-arm queue Peter Maydell
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=CAFEAcA_xoSkhk-dGUXw3-0hQyb1NF+6qRP-+6TpoQkFPOBs8Jg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).