Re: [virtio-comment] [RFC PATCH v3 3/4] virtio-rtc: Add alarm feature

[Jason Wang <jasowang@redhat.com>]

On Sat, Dec 23, 2023 at 2:57âAM Cornelia Huck <cohuck@redhat.com> wrote:
>
> On Mon, Dec 18 2023, Peter Hilber <peter.hilber@opensynergy.com> wrote:
>
> > Add the VIRTIO_RTC_F_ALARM feature (without normative statements).
> >
> > The intended use case is: A driver needs to react when an alarm time has
> > been reached, but the driver may be in a sleep state or powered off at
> > alarm time. The alarm feature can resume and notify the driver in this
> > case. Alarms may be retained across device resets (including reset on
> > boot).
>
> Does the driver have some kind of control or information about whether
> alarms are retained? I.e. to start with a clean slate, if wanted.

It might be otherwise we may have security implications?

Userspace driver set the alarm, and the device was shifted to kernel
driver which may get this alarm accidentally?

Thanks

>
> I'm not familiar with RTC, so I'm not sure if that even makes sense, or
> if I have missed something in the spec.
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
>