From: "Michael S. Tsirkin" <mst@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-devel@nongnu.org, armbru@redhat.com, eblake@redhat.com,
eduardo@habkost.net, berrange@redhat.com, pbonzini@redhat.com,
marcel.apfelbaum@gmail.com, philmd@linaro.org,
den-plotnikov@yandex-team.ru, yc-core@yandex-team.ru
Subject: Re: [PATCH v8 0/4] pci hotplug tracking
Date: Thu, 2 Nov 2023 07:31:31 -0400 [thread overview]
Message-ID: <20231102072800-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20231005092926.56231-1-vsementsov@yandex-team.ru>
On Thu, Oct 05, 2023 at 12:29:22PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Main thing this series does is DEVICE_ON event - a counter-part to
> DEVICE_DELETED. A guest-driven event that device is powered-on.
> Details are in patch 2. The new event is paried with corresponding
> command query-hotplug.
Several things questionable here:
1. depending on guest activity you can get as many
DEVICE_ON events as you like
2. it's just for shpc and native pcie - things are
confusing enough for management, we should make sure
it can work for all devices
3. what about non hotpluggable devices? do we want the event for them?
I feel this needs actual motivation so we can judge what's the
right way to do it.
>
> v8:
> - improve naming, wording and style
> - make new QMP interface experimental
>
>
> Vladimir Sementsov-Ogievskiy (4):
> qapi/qdev.json: unite DEVICE_* event data into single structure
> qapi: add DEVICE_ON and query-hotplug infrastructure
> shpc: implement DEVICE_ON event and query-hotplug
> pcie: implement DEVICE_ON event and query-hotplug
>
> hw/core/hotplug.c | 12 +++
> hw/pci-bridge/pci_bridge_dev.c | 14 +++
> hw/pci-bridge/pcie_pci_bridge.c | 1 +
> hw/pci/pcie.c | 83 +++++++++++++++
> hw/pci/pcie_port.c | 1 +
> hw/pci/shpc.c | 86 +++++++++++++++
> include/hw/hotplug.h | 11 ++
> include/hw/pci/pci_bridge.h | 2 +
> include/hw/pci/pcie.h | 2 +
> include/hw/pci/shpc.h | 2 +
> include/hw/qdev-core.h | 7 ++
> include/monitor/qdev.h | 6 ++
> qapi/qdev.json | 178 +++++++++++++++++++++++++++++---
> softmmu/qdev-monitor.c | 58 +++++++++++
> 14 files changed, 451 insertions(+), 12 deletions(-)
>
> --
> 2.34.1
next prev parent reply other threads:[~2023-11-02 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 9:29 [PATCH v8 0/4] pci hotplug tracking Vladimir Sementsov-Ogievskiy
2023-10-05 9:29 ` [PATCH v8 1/4] qapi/qdev.json: unite DEVICE_* event data into single structure Vladimir Sementsov-Ogievskiy
2023-10-05 9:29 ` [PATCH v8 2/4] qapi: add DEVICE_ON and query-hotplug infrastructure Vladimir Sementsov-Ogievskiy
2023-11-02 11:35 ` Michael S. Tsirkin
2023-10-05 9:29 ` [PATCH v8 3/4] shpc: implement DEVICE_ON event and query-hotplug Vladimir Sementsov-Ogievskiy
2023-10-05 9:29 ` [PATCH v8 4/4] pcie: " Vladimir Sementsov-Ogievskiy
2023-11-02 8:06 ` [PATCH v8 0/4] pci hotplug tracking Vladimir Sementsov-Ogievskiy
2023-11-02 8:27 ` Vladimir Sementsov-Ogievskiy
2023-11-02 11:31 ` Michael S. Tsirkin [this message]
2023-11-02 12:00 ` Vladimir Sementsov-Ogievskiy
2023-11-02 12:12 ` Michael S. Tsirkin
2023-11-02 13:28 ` Vladimir Sementsov-Ogievskiy
2023-11-02 13:32 ` Michael S. Tsirkin
2023-11-02 13:38 ` Vladimir Sementsov-Ogievskiy
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=20231102072800-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=den-plotnikov@yandex-team.ru \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
--cc=yc-core@yandex-team.ru \
/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).