From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Peter Hilber <quic_philber@quicinc.com>
Cc: virtio-comment@lists.linux.dev, Cornelia Huck <cohuck@redhat.com>,
Parav Pandit <parav@nvidia.com>, Jason Wang <jasowang@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
"Ridoux, Julien" <ridouxj@amazon.com>,
Trilok Soni <quic_tsoni@quicinc.com>
Subject: Re: [PATCH v8 0/4] virtio-rtc: Add device specification
Date: Wed, 16 Apr 2025 15:02:51 +0200 [thread overview]
Message-ID: <Z/+qe+tyH5EGaIXq@fedora> (raw)
In-Reply-To: <20250306095112.1293-1-quic_philber@quicinc.com>
Hello Peter,
I only now had time to share my comments. I could not cover all the
patches though. These are minor changes. Apologies for the delay.
Matias
On Thu, Mar 06, 2025 at 10:51:08AM +0100, Peter Hilber wrote:
> This iteration of the spec should address multiple review findings from
> Matias Ezequiel Vara Larsen.
>
> Summary
> -------
>
> The RTC (Real Time Clock) device provides information about current
> time. The device can provide different clocks, for the UTC or TAI time
> standards, or for physical time elapsed since some past epoch. For UTC
> clocks, the device can also indicate how leap seconds are handled. The
> driver can read the clocks with simple or more accurate methods.
> Optionally, the driver can set an alarm.
>
> Changelog
> ---------
>
> v8:
>
> - Explicitly describe alarm enabled status, where relevant (Matias Ezequiel
> Vara Larsen).
>
> - Reword multiple sentences and requirements (Matias Ezequiel Vara Larsen).
>
> - Drop unnecessary or redundant requirements (Matias Ezequiel Vara Larsen).
>
> - Change word order from "field X" to "the X field" (Matias Ezequiel Vara
> Larsen).
>
> - Change word order from "flag X" to "the X flag" or "X".
>
> - Move requirements to serve alarm expiration events before requirements
> about stopping to serve (Matias Ezequiel Vara Larsen).
>
> v7:
>
> - Remove leap second and performance indications from struct
> virtio_rtc_resp_read_cross. Remove backing definitions.
>
> - Move wording change which was mistakenly placed in last patch to first
> patch.
>
> v6:
>
> - Make leap second status information optional if the clock smears (or
> might smear) leap seconds.
>
> - Do not use union for leap second indication.
>
> - Improve wording.
>
> - Refer to the new POSIX.1-2024 for UTC epoch definition.
>
> v5:
>
> - Change structure and wording to support adding shared memory like
> vmclock [2].
>
> - Add dedicated clock types for UTC leap second smearing (David
> Woodhouse).
>
> - Extend leap second indications.
>
> - Replace VIRTIO_RTC_SUBTYPE_ by VIRTIO_RTC_SMEAR_.
>
> - For Arm Generic Timer, only support Virtual Count Register (David
> Woodhouse).
>
> - Rename MONO clock to MONOTONIC clock.
>
> - Harmonize bit widths with vmclock [2].
>
> - Change formatting.
>
> v4:
>
> - Distinguish UTC clocks with and without leap smearing (David
> Woodhouse).
>
> - Add UTC leap second and TAI offset indication (David Woodhouse).
>
> - Add clock performance information (David Woodhouse).
>
> - Drop distinction of Arm Generic Timer virtual and physical counter.
>
> - Change requirements so that driver can reset alarm to clean slate, and
> document how driver can achieve this (Cornelia Hell, Jason Wang).
>
> - Device should assume that driver reads clock from first vCPU (David
> Woodhouse).
>
> - Driver should read clock to confirm that alarm has expired.
>
> - Require driver to set unused flags to zero.
>
> - Require device to support all expressible alarm times.
>
> - Formatting and wording improvements.
>
> v3:
>
> - Address comments from Parav Pandit.
>
> - Add an optional alarm feature.
>
> - Various other changes.
>
> v2:
>
> - Address comments from Cornelia Huck.
>
> [1] https://lore.kernel.org/lkml/61364452-bdf5-4bd8-adb1-a9e6236c9d26@opensynergy.com/
> [2] https://lore.kernel.org/lkml/20240708092924.1473461-1-dwmw2@infradead.org/
> [3] https://lore.kernel.org/all/78969a39b51ec00e85551b752767be65f6794b46.camel@infradead.org/
> [4] https://lore.kernel.org/lkml/20241219204208.3160-1-quic_philber@quicinc.com/
>
>
> Peter Hilber (4):
> virtio-rtc: Add initial device specification
> virtio-rtc: Add initial normative statements
> virtio-rtc: Add alarm feature
> virtio-rtc: Add normative statements for alarm feature
>
> conformance.tex | 2 +
> content.tex | 3 +-
> device-types/rtc/description.tex | 1100 +++++++++++++++++++++++
> device-types/rtc/device-conformance.tex | 13 +
> device-types/rtc/driver-conformance.tex | 11 +
> introduction.tex | 6 +
> 6 files changed, 1134 insertions(+), 1 deletion(-)
> create mode 100644 device-types/rtc/description.tex
> create mode 100644 device-types/rtc/device-conformance.tex
> create mode 100644 device-types/rtc/driver-conformance.tex
>
>
> base-commit: 124fcd0e97f209aab19639e7369116d99ede22a2
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-04-16 13:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 9:51 [PATCH v8 0/4] virtio-rtc: Add device specification Peter Hilber
2025-03-06 9:51 ` [PATCH v8 1/4] virtio-rtc: Add initial " Peter Hilber
2025-04-15 13:43 ` Cornelia Huck
2025-04-15 14:17 ` Peter Hilber
2025-04-15 14:38 ` Cornelia Huck
2025-04-15 15:04 ` Matias Ezequiel Vara Larsen
2025-04-17 14:42 ` Peter Hilber
2025-04-16 15:33 ` Michael S. Tsirkin
2025-04-17 15:14 ` Peter Hilber
2025-04-17 16:14 ` Michael S. Tsirkin
2025-04-22 10:47 ` Peter Hilber
2025-04-22 10:52 ` Michael S. Tsirkin
2025-03-06 9:51 ` [PATCH v8 2/4] virtio-rtc: Add initial normative statements Peter Hilber
2025-04-15 13:46 ` Cornelia Huck
2025-04-15 14:28 ` Peter Hilber
2025-04-15 16:03 ` Matias Ezequiel Vara Larsen
2025-04-17 14:58 ` Peter Hilber
2025-04-16 15:42 ` Michael S. Tsirkin
2025-04-17 15:15 ` Peter Hilber
2025-03-06 9:51 ` [PATCH v8 3/4] virtio-rtc: Add alarm feature Peter Hilber
2025-04-16 8:17 ` Matias Ezequiel Vara Larsen
2025-04-17 15:04 ` Peter Hilber
2025-05-06 15:19 ` Peter Hilber
2025-03-06 9:51 ` [PATCH v8 4/4] virtio-rtc: Add normative statements for " Peter Hilber
2025-04-16 12:14 ` Matias Ezequiel Vara Larsen
2025-04-17 15:07 ` Peter Hilber
2025-04-15 12:46 ` [PATCH v8 0/4] virtio-rtc: Add device specification Peter Hilber
2025-04-16 13:02 ` Matias Ezequiel Vara Larsen [this message]
2025-04-16 14:44 ` Peter Hilber
2025-04-16 14:59 ` Matias Ezequiel Vara Larsen
2025-04-16 15:43 ` Michael S. Tsirkin
2025-04-17 15:08 ` Peter Hilber
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=Z/+qe+tyH5EGaIXq@fedora \
--to=mvaralar@redhat.com \
--cc=cohuck@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=quic_philber@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=ridouxj@amazon.com \
--cc=virtio-comment@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.