diff options
| author | Markus Armbruster <armbru@redhat.com> | 2022-02-22 13:02:07 +0100 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2022-02-28 11:39:35 +0100 |
| commit | 2beb1e5f9acb443d90fe4d366463f89d32d83bc8 (patch) | |
| tree | 3039414c1a58c8778309dd16014befeb882489a7 /qapi | |
| parent | 03397528d96ff5d631fd2fa40b753548e53b5149 (diff) | |
rtc: Have event RTC_CHANGE identify the RTC by QOM path
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?
Which one changed? New @qom-path identifies it.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <87a6ejnm80.fsf@pond.sub.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Diffstat (limited to 'qapi')
| -rw-r--r-- | qapi/misc.json | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/qapi/misc.json b/qapi/misc.json index 0ab235e41f..b83cc39029 100644 --- a/qapi/misc.json +++ b/qapi/misc.json @@ -536,6 +536,8 @@ # @offset: offset in seconds between base RTC clock (as specified # by -rtc base), and new RTC clock value # +# @qom-path: path to the RTC object in the QOM tree +# # Note: This event is rate-limited. # It is not guaranteed that the RTC in the system implements # this event, or even that the system has an RTC at all. @@ -550,4 +552,4 @@ # ## { 'event': 'RTC_CHANGE', - 'data': { 'offset': 'int' } } + 'data': { 'offset': 'int', 'qom-path': 'str' } } |