[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC 4/4] rtc: Have event RTC_CHANGE identify the RTC by QOM p
|
From: |
Markus Armbruster |
|
Subject: |
Re: [PATCH RFC 4/4] rtc: Have event RTC_CHANGE identify the RTC by QOM path |
|
Date: |
Tue, 22 Feb 2022 16:04:03 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Philippe Mathieu-Daudé <philippe.mathieu.daude@gmail.com> writes:
> Hi Markus,
>
> On 22/2/22 13:02, Markus Armbruster wrote:
>> Event RTC_CHANGE is "emitted when the guest changes the RTC time" (and
>> the RTC supports the event). What if there's more than one RTC?
>
> w.r.t. RTC, a machine having multiple RTC devices is silly...
>
> Assuming one wants to emulate that; shouldn't all QMP events have a
> qom-path by default? Or have a generic "event-from-multiple-sources"
> flag which automatically add this field?
Not all events originate from a device, or even a QOM object.
The ones that do could all use a qom-path member, I guess.
[...]
Re: [PATCH v2 0/3] qapi: Move RTC_CHANGE back out of target schema, Markus Armbruster, 2022/02/25