From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, qemu-ppc@nongnu.org, groug@kaod.org,
david@gibson.dropbear.id.au
Subject: Re: [PATCH 0/4] DEVICE_NOT_DELETED/DEVICE_UNPLUG_ERROR QAPI events
Date: Tue, 20 Apr 2021 14:11:38 -0300 [thread overview]
Message-ID: <c350efdf-cc61-243d-6d8f-7eade48618e4@gmail.com> (raw)
In-Reply-To: <20210312200740.815014-1-danielhb413@gmail.com>
Hello,
Quick update about this work:
- the hotunplug timeout was reverted in the pSeries machine for 6.0.0.
This means that we have no use for a DEVICE_NOT_DELETED event or similar.
I'll drop it for the next version of the series.
- there is a good chance that the pSeries kernel will introduce a way to
report hotunplug errors in v5.13 ([1] for more info). This would make
the DEVICE_UNPLUG_ERROR event relevant again (otherwise it would just be
a rebranding of the existing mem_unplug_error) since we'll be able to
properly report guest side unplug errors for all devices in the pSeries
machine, starting with CPUs.
Thanks,
DHB
[1] https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20210416210216.380291-3-danielhb413@gmail.com/
On 3/12/21 5:07 PM, Daniel Henrique Barboza wrote:
> Hi,
>
> This series adds 2 new QAPI events, DEVICE_NOT_DELETED and
> DEVICE_UNPLUG_ERROR. They were (and are still being) discussed in [1].
>
> Patches 1 and 3 are independent of the ppc patches and can be applied
> separately. Patches 2 and 4 are based on David's ppc-for-6.0 branch and
> are dependent on the QAPI patches.
>
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg01900.html
>
> Daniel Henrique Barboza (4):
> qapi/qdev.json: add DEVICE_NOT_DELETED event
> spapr_drc.c: send DEVICE_NOT_DELETED event on unplug timeout
> qapi/machine.json: add DEVICE_UNPLUG_ERROR QAPI event
> spapr.c: use DEVICE_UNPLUG_ERROR event in
> spapr_memory_unplug_rollback()
>
> hw/ppc/spapr.c | 2 +-
> hw/ppc/spapr_drc.c | 8 ++++++++
> qapi/machine.json | 23 +++++++++++++++++++++++
> qapi/qdev.json | 28 ++++++++++++++++++++++++++++
> 4 files changed, 60 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2021-04-20 17:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 20:07 [PATCH 0/4] DEVICE_NOT_DELETED/DEVICE_UNPLUG_ERROR QAPI events Daniel Henrique Barboza
2021-03-12 20:07 ` [PATCH 1/4] qapi/qdev.json: add DEVICE_NOT_DELETED event Daniel Henrique Barboza
2021-03-23 18:00 ` Eric Blake
2021-03-23 18:12 ` Daniel Henrique Barboza
2021-03-12 20:07 ` [PATCH 2/4] spapr_drc.c: send DEVICE_NOT_DELETED event on unplug timeout Daniel Henrique Barboza
2021-03-12 20:07 ` [PATCH 3/4] qapi/machine.json: add DEVICE_UNPLUG_ERROR QAPI event Daniel Henrique Barboza
2021-03-12 20:07 ` [PATCH 4/4] spapr.c: use DEVICE_UNPLUG_ERROR event in spapr_memory_unplug_rollback() Daniel Henrique Barboza
2021-03-23 1:12 ` [PATCH 0/4] DEVICE_NOT_DELETED/DEVICE_UNPLUG_ERROR QAPI events David Gibson
2021-03-23 17:10 ` Daniel Henrique Barboza
2021-03-24 1:40 ` David Gibson
2021-03-24 19:09 ` Daniel Henrique Barboza
2021-03-25 1:32 ` David Gibson
2021-03-29 23:28 ` Igor Mammedov
2021-03-30 23:46 ` David Gibson
2021-03-31 9:49 ` Igor Mammedov
2021-04-01 1:31 ` David Gibson
2021-03-31 19:47 ` Daniel Henrique Barboza
2021-04-01 1:36 ` David Gibson
2021-03-31 19:40 ` Daniel Henrique Barboza
2021-04-20 17:11 ` Daniel Henrique Barboza [this message]
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=c350efdf-cc61-243d-6d8f-7eade48618e4@gmail.com \
--to=danielhb413@gmail.com \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).