[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 13/15] qapi: add HOTPLUG_STATE event
From: |
Vladimir Sementsov-Ogievskiy |
Subject: |
Re: [PATCH v3 13/15] qapi: add HOTPLUG_STATE event |
Date: |
Fri, 10 Feb 2023 16:38:57 +0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 |
On 10.02.23 15:01, Markus Armbruster wrote:
What do @hotplug-device and @device name? Are these qdev-id?
What kind of paths are @hotplug-path and @path? Are these paths to an
object device in the QOM tree? Which object?
device / path is same name and path as for DEVICE_DELETED
Got it. But there we have just one device, and here we have two. Which
two?
One is "bus" in which we insert the device. I'm not sure that's it correct to call pcie-root-port a
"bus", but on the other hand in device_add command it's a "bus" argument. In some arguments in code
it's called hotplug_dev or something like that. Probably "bus" is better.
Also, DEVICE_DELETED's doc comment is better:
# @device: the device's ID if it has one
#
# @path: the device's QOM path
Suggest to steal from there.
OK, agree.
--
Best regards,
Vladimir
- [PATCH v3 15/15] qapi: introduce query-hotplug command, (continued)
[PATCH v3 12/15] pci: introduce pci_find_the_only_child(), Vladimir Sementsov-Ogievskiy, 2023/02/09
[PATCH v3 14/15] qapi: introduce DEVICE_ON event, Vladimir Sementsov-Ogievskiy, 2023/02/09