Message ID | 20210413002648.8281-1-david@gibson.dropbear.id.au (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Tue, 13 Apr 2021 at 01:26, David Gibson <david@gibson.dropbear.id.au> wrote: > > The following changes since commit 555249a59e9cdd6b58da103aba5cf3a2d45c899f: > > Merge remote-tracking branch 'remotes/ehabkost-gl/tags/x86-next-pull-request' into staging (2021-04-10 16:58:56 +0100) > > are available in the Git repository at: > > https://gitlab.com/dgibson/qemu.git tags/ppc-for-6.0-20210412 > > for you to fetch changes up to 2b18fc794f312a91482998bae5ea6c8724200e06: > > spapr.c: always pulse guest IRQ in spapr_core_unplug_request() (2021-04-12 12:27:14 +1000) > > > Ugh, sorry Peter. I meant to sent this yesterday, but apparently > forgot to execute the last step to actuall send it out. > > ---------------------------------------------------------------- > ppc patch queue for 2021-04-21 > > Here's what I hope is the last ppc related pull request for qemu-6.0. > > The 2 patches here revert a behavioural change that after further > discussion we concluded was a bad idea (adding a timeout for > possibly-failed hot unplug requests). Instead it implements a > different approach to the original problem: we again let unplug > requests the guest doesn't respond to remain pending indefinitely, but > no longer allow those to block attempts to retry the same unplug > again. > > The change is a bit more complex than I'd like for this late in the > freeze. Nonetheless, I think it's important to merge this for 6.0, so > we don't allow a release which has the probably-a-bad-idea timeout > behaviour. Applied, thanks. Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0 for any user-visible changes. -- PMM