From: Thomas Gleixner <tglx@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Andy Lutomirski" <luto@kernel.org>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
"Shuah Khan" <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: Re: [PATCH 0/3] vdso/gettimeofday: Add support for ALARM clocks
Date: Tue, 29 Sep 2026 21:12:22 +0200 [thread overview]
Message-ID: <87ld8jj2i1.ffs@fw13> (raw)
In-Reply-To: <20260921-vdso-alarm-clocks-v1-0-617abb5271c7@weissschuh.net>
On Mon, Sep 21 2026 at 11:53, Thomas Weißschuh wrote:
> Extend the generic vDSO library to also handle CLOCK_BOOTTIME_ALARM
> and CLOCK_REALTIME_ALARM. This does not introduce any runtime overhead
> in the userspace fast path and only memory copies in the tick update
> path.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Thomas Weißschuh (3):
> selftests: vDSO: vdso_test_abi: Also test ALARM clocks
> vdso/gettimeofday: Add support for CLOCK_BOOTTIME_ALARM
> vdso/gettimeofday: Add support for CLOCK_REALTIME_ALARM
Patch "selftests: vDSO: vdso_test_abi: Also test ALARM clocks" has no SOB
Patch "vdso/gettimeofday: Add support for CLOCK_BOOTTIME_ALARM" has no SOB
Patch "vdso/gettimeofday: Add support for CLOCK_REALTIME_ALARM" has no SOB
Please try again.
prev parent reply other threads:[~2026-09-29 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 9:53 [PATCH 0/3] vdso/gettimeofday: Add support for ALARM clocks Thomas Weißschuh
2026-09-21 9:54 ` [PATCH 1/3] selftests: vDSO: vdso_test_abi: Also test " Thomas Weißschuh
2026-09-21 9:54 ` [PATCH 2/3] vdso/gettimeofday: Add support for CLOCK_BOOTTIME_ALARM Thomas Weißschuh
2026-09-21 9:54 ` [PATCH 3/3] vdso/gettimeofday: Add support for CLOCK_REALTIME_ALARM Thomas Weißschuh
2026-09-29 19:12 ` Thomas Gleixner [this message]
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=87ld8jj2i1.ffs@fw13 \
--to=tglx@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=luto@kernel.org \
--cc=shuah@kernel.org \
--cc=vincenzo.frascino@arm.com \
/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.