From: Kevin Wolf <kwolf@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Stable-8.0.5 00/66] v2 Patch Round-up for stable 8.0.5, freeze on 2023-09-19
Date: Wed, 13 Sep 2023 17:38:03 +0200 [thread overview]
Message-ID: <ZQHXW74CpyTIVYET@redhat.com> (raw)
In-Reply-To: <qemu-stable-8.0.5-20230913160844@cover.tls.msk.ru>
Am 13.09.2023 um 15:17 hat Michael Tokarev geschrieben:
> The following patches are queued for QEMU stable v8.0.5:
>
> https://gitlab.com/qemu-project/qemu/-/commits/staging-8.0
>
> Patch freeze is 2023-09-19, and the release is planned for 2023-09-21:
>
> https://wiki.qemu.org/Planning/8.0
>
> Please respond here or CC qemu-stable@nongnu.org on any additional patches
> you think should (or shouldn't) be included in the release.
>
> The changes which are staging for inclusion, with the original commit hash
> from master branch, are given below the bottom line.
>
> The v2 version includes reentrancy fixes the same way as staging-7.2, -
> thought I'd not make the two different from each other in this context.
> It also includes a few more changes accumulated to date.
>
> I'm not sure about this change for now:
> 56 92e2e6a86733 Kevin Wolf:
> virtio: Drop out of coroutine context in virtio_load()
>
> since it introduces regression on mips ( https://gitlab.com/qemu-project/qemu/-/issues/1866 ) -
> should it be in 8.0 (or 7.2) to begin with? I think I should wait for
> a while and include it in earlier versions only after the fix for the
> regression will be found, and include this change in 8.1 only for now.
> (Cc'ing Kevin for this).
What is the change in commit 92e2e6a86733 that could affect this bug? I
only changed the migration code path, but the Gitlab issue doesn't
mention migration at all. In the issue itself, I can only see it linked
to a different commit (0d58c660 softmmu: Use async_run_on_cpu in
tcg_commit).
Did you mean a different commit or a different issue?
Kevin
next prev parent reply other threads:[~2023-09-13 15:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 13:17 [Stable-8.0.5 00/66] v2 Patch Round-up for stable 8.0.5, freeze on 2023-09-19 Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 01/66] memory: prevent dma-reentracy issues Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 02/66] async: Add an optional reentrancy guard to the BH API Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 03/66] async: avoid use-after-free on re-entrancy guard Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 04/66] checkpatch: add qemu_bh_new/aio_bh_new checks Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 05/66] hw: replace most qemu_bh_new calls with qemu_bh_new_guarded Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 06/66] lsi53c895a: disable reentrancy detection for script RAM Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 07/66] lsi53c895a: disable reentrancy detection for MMIO region, too Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 08/66] bcm2835_property: disable reentrancy detection for iomem Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 09/66] raven: " Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 10/66] apic: disable reentrancy detection for apic-msi Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 11/66] loongarch: mark loongarch_ipi_iocsr re-entrnacy safe Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 12/66] pnv_lpc: disable reentrancy detection for lpc-hc Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 56/66] virtio: Drop out of coroutine context in virtio_load() Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 57/66] arm64: Restore trapless ptimer access Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 58/66] hw/char/riscv_htif: Fix printing of console characters on big endian hosts Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 59/66] hw/char/riscv_htif: Fix the console syscall " Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 60/66] hw/intc: Fix upper/lower mtime write calculation Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 61/66] hw/intc: Make rtc variable names consistent Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 62/66] linux-user/riscv: Use abi type for target_ucontext Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 63/66] hw/riscv: virt: Fix riscv,pmu DT node path Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 64/66] target/riscv: fix satp_mode_finalize() when satp_mode.supported = 0 Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 65/66] target/riscv/pmp.c: respect mseccfg.RLB for pmpaddrX changes Michael Tokarev
2023-09-13 13:17 ` [Stable-8.0.5 66/66] hw/tpm: TIS on sysbus: Remove unsupport ppi command line option Michael Tokarev
2023-09-13 15:38 ` Kevin Wolf [this message]
2023-09-13 16:11 ` [Stable-8.0.5 00/66] v2 Patch Round-up for stable 8.0.5, freeze on 2023-09-19 Michael Tokarev
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=ZQHXW74CpyTIVYET@redhat.com \
--to=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--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).