From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
qemu-devel@nongnu.org, armbru@redhat.com, eblake@redhat.com,
eduardo@habkost.net, berrange@redhat.com, pbonzini@redhat.com,
marcel.apfelbaum@gmail.com, mst@redhat.com,
den-plotnikov@yandex-team.ru, antonkuchin@yandex-team.ru
Subject: Re: [PATCH v4 15/16] qapi: add HOTPLUG_STATE event
Date: Tue, 14 Feb 2023 09:56:50 +0100 [thread overview]
Message-ID: <877cwkoca5.fsf@pond.sub.org> (raw)
In-Reply-To: <7fc9712a-136a-d296-4a7b-194195f3b699@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Mon, 13 Feb 2023 15:10:29 +0100")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 13/2/23 15:01, Vladimir Sementsov-Ogievskiy wrote:
>> For PCIe and SHPC hotplug it's important to track led indicators,
>> especially the power led. Add an event that helps.
>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
>> ---
>> qapi/qdev.json | 175 ++++++++++++++++++++++++++++++++
>> include/hw/hotplug.h | 12 +++
>> include/hw/pci/pci.h | 3 +
>> include/hw/pci/pci_bridge.h | 2 +
>> include/hw/pci/pcie.h | 2 +
>> include/hw/pci/shpc.h | 2 +
>> include/monitor/qdev.h | 5 +
>> hw/core/hotplug.c | 13 +++
>> hw/pci-bridge/pci_bridge_dev.c | 14 +++
>> hw/pci-bridge/pcie_pci_bridge.c | 1 +
>> hw/pci/pcie.c | 79 ++++++++++++++
>> hw/pci/pcie_port.c | 1 +
>> hw/pci/shpc.c | 102 ++++++++++++++++++-
>> softmmu/qdev-monitor.c | 39 +++++++
>> 14 files changed, 445 insertions(+), 5 deletions(-)
>
> -ETOOBIG
Can't see how this could be split sensibly: it's a single query/event
pair. If you can, let us know.
next prev parent reply other threads:[~2023-02-14 8:57 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 14:00 [PATCH v4 00/16] pci hotplug tracking Vladimir Sementsov-Ogievskiy
2023-02-13 14:00 ` [PATCH v4 01/16] pci/shpc: set attention led to OFF on reset Vladimir Sementsov-Ogievskiy
2023-02-13 14:16 ` Philippe Mathieu-Daudé
2023-02-14 9:49 ` Vladimir Sementsov-Ogievskiy
2023-02-14 19:31 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 02/16] pci/shpc: change shpc_get_status() return type to uint8_t Vladimir Sementsov-Ogievskiy
2023-02-14 19:32 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 03/16] pci/shpc: shpc_slot_command(): handle PWRONLY -> ENABLED transition Vladimir Sementsov-Ogievskiy
2023-02-14 19:33 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 04/16] pci/shpc: more generic handle hot-unplug in shpc_slot_command() Vladimir Sementsov-Ogievskiy
2023-02-14 19:34 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 05/16] pci/shpc: pass PCIDevice pointer to shpc_slot_command() Vladimir Sementsov-Ogievskiy
2023-02-14 19:35 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 06/16] pci/shpc: refactor shpc_device_plug_common() Vladimir Sementsov-Ogievskiy
2023-02-14 19:36 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 07/16] pcie: pcie_cap_slot_write_config(): use correct macro Vladimir Sementsov-Ogievskiy
2023-02-14 19:37 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 08/16] pcie_regs: drop duplicated indicator value macros Vladimir Sementsov-Ogievskiy
2023-02-14 19:39 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 09/16] pcie: drop unused PCIExpressIndicator Vladimir Sementsov-Ogievskiy
2023-02-14 19:40 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 10/16] pcie: pcie_cap_slot_enable_power() use correct helper Vladimir Sementsov-Ogievskiy
2023-02-14 19:41 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 11/16] pcie: introduce pcie_sltctl_powered_off() helper Vladimir Sementsov-Ogievskiy
2023-02-14 19:41 ` Anton Kuchin
2023-02-13 14:00 ` [PATCH v4 12/16] pcie: set power indicator to off on reset by default Vladimir Sementsov-Ogievskiy
2023-02-14 19:42 ` Anton Kuchin
2023-02-13 14:01 ` [PATCH v4 13/16] pci: introduce pci_find_the_only_child() Vladimir Sementsov-Ogievskiy
2023-02-14 19:43 ` Anton Kuchin
2023-02-13 14:01 ` [PATCH v4 14/16] qapi: deprecate "device" field of DEVICE_* events Vladimir Sementsov-Ogievskiy
2023-02-13 14:13 ` Daniel P. Berrangé
2023-02-14 8:54 ` Markus Armbruster
2023-02-14 9:25 ` Peter Krempa
2023-02-14 11:14 ` Daniel P. Berrangé
2023-02-14 11:49 ` Markus Armbruster
2023-02-14 11:53 ` Philippe Mathieu-Daudé
2023-02-14 12:17 ` Markus Armbruster
2023-02-14 13:56 ` Philippe Mathieu-Daudé
2023-02-14 16:18 ` Markus Armbruster
2023-02-14 11:53 ` Markus Armbruster
2023-02-14 11:13 ` Daniel P. Berrangé
2023-02-14 11:57 ` Markus Armbruster
2023-02-14 13:51 ` Vladimir Sementsov-Ogievskiy
2023-02-14 13:59 ` Daniel P. Berrangé
2023-02-14 16:28 ` Markus Armbruster
2023-02-15 21:00 ` Vladimir Sementsov-Ogievskiy
2023-02-16 0:34 ` Markus Armbruster
2023-02-13 14:01 ` [PATCH v4 15/16] qapi: add HOTPLUG_STATE event Vladimir Sementsov-Ogievskiy
2023-02-13 14:10 ` Philippe Mathieu-Daudé
2023-02-14 8:56 ` Markus Armbruster [this message]
2023-02-14 9:52 ` Vladimir Sementsov-Ogievskiy
2023-02-13 14:01 ` [PATCH v4 16/16] qapi: introduce DEVICE_ON event Vladimir Sementsov-Ogievskiy
2023-02-13 14:12 ` Philippe Mathieu-Daudé
2023-02-14 8:58 ` Markus Armbruster
2023-02-14 9:56 ` 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=877cwkoca5.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=antonkuchin@yandex-team.ru \
--cc=berrange@redhat.com \
--cc=den-plotnikov@yandex-team.ru \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@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).