From: Thomas Gleixner <tglx@kernel.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>,
thomas.weissschuh@linutronix.de
Cc: luto@kernel.org, vincenzo.frascino@arm.com,
david.laight.linux@gmail.com, linux-kernel@vger.kernel.org,
zhanxusheng@xiaomi.com
Subject: Re: [PATCH v5 0/4] vdso: Keep the CLOCK_AUX base at full precision
Date: Wed, 30 Sep 2026 14:41:12 +0200 [thread overview]
Message-ID: <874if6j4if.ffs@fw13> (raw)
In-Reply-To: <20260916023252.418473-1-zhanxusheng@xiaomi.com>
On Wed, Sep 16 2026 at 10:32, Zhan Xusheng wrote:
> Testing on x86-64: checkpatch --strict, gcc W=1 and make LLVM=1 are all
> clean. Built and booted with kernel/configs/x86_debug.config plus
> panic_on_warn=1; no warning fired and the log holds no lockdep or
> debug-object complaint. A guest with an aux clock enabled saw no vDSO
> reading ahead of a later ktime_get_aux() in 100000 samples at each of
> offset 0, +5.123456789 and a negative offs_aux.
>
> The generated code in vsyscall.o, vdso64 and vdso32 is byte-identical to
> v4, so the reflowed lines changed nothing.
I've removed the series from tip timers/vdso due to the build fails
which were reported by 0-day.
Please address them and repost an updated series.
Thanks,
tgl
prev parent reply other threads:[~2026-09-30 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 2:32 Zhan Xusheng
2026-09-16 2:32 ` [PATCH v5 1/4] vdso/math64: Use OPTIMIZER_HIDE_VAR() in __iter_div_u64_rem() Zhan Xusheng
2026-09-25 7:44 ` Thomas Weißschuh
2026-09-29 19:27 ` [tip: timers/vdso] " tip-bot2 for Zhan Xusheng
2026-09-16 2:32 ` [PATCH v5 2/4] vdso/math64: Add and use __iter_div64_u64_rem() Zhan Xusheng
2026-09-29 19:27 ` [tip: timers/vdso] " tip-bot2 for Zhan Xusheng
2026-09-16 2:32 ` [PATCH v5 3/4] vdso/vsyscall: Keep the CLOCK_AUX base scaled Zhan Xusheng
2026-09-29 19:27 ` [tip: timers/vdso] " tip-bot2 for Zhan Xusheng
2026-09-16 2:32 ` [PATCH v5 4/4] vdso/gettimeofday: Assert that the clockid fits into the u32 bitmask Zhan Xusheng
2026-09-29 19:27 ` [tip: timers/vdso] " tip-bot2 for Zhan Xusheng
2026-09-30 12:41 ` 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=874if6j4if.ffs@fw13 \
--to=tglx@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®