qemu-stable
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Stable-8.0.5 00/66] v2 Patch Round-up for stable 8.0.5, freeze on 2


From: Kevin Wolf
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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]