[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PULL 18/18] qapi: move RTC_CHANGE to the target schema
From: |
Markus Armbruster |
Subject: |
Re: [Qemu-devel] [PULL 18/18] qapi: move RTC_CHANGE to the target schema |
Date: |
Sat, 25 Sep 2021 09:39:27 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Peter Maydell <peter.maydell@linaro.org> writes:
> On Fri, 24 Sept 2021 at 15:43, Daniel P. Berrangé <berrange@redhat.com> wrote:
>>
>> On Fri, Sep 24, 2021 at 03:35:52PM +0200, Markus Armbruster wrote:
>> > Peter Maydell <peter.maydell@linaro.org> writes:
>> > > Side side note: the JSON event doesn't seem to contemplate
>> > > the possibility that a machine might have more than one RTC...
>> >
>> > Right. It clearly needs an additional member @qom-path identifying the
>> > RTC device.
>>
>> Are there (mainstream) machines with more than one RTC ?
>
> Probably not many. The most likely case is probably "SoC has
> a crappy RTC and the board designer put a better one on the board".
> https://www.mail-archive.com/tech@openbsd.org/msg45128.html
> has a mention of some rockchip-based board like that.
Adding @qom-path is the right thing to do.
Simply ignore it when you know the VM has just one RTC, or that the
guest will use just one.