From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Wangyang Guo <wangyang.guo@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
<linux-kernel@vger.kernel.org>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
Benjamin Lei <benjamin.lei@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Tianyou Li <tianyou.li@intel.com>
Subject: Re: [PATCH v3] sched/clock: Avoid false sharing for sched_clock_irqtime
Date: Mon, 19 Jan 2026 09:43:49 +0530 [thread overview]
Message-ID: <653ac450-2f00-4eb0-bb97-e40576435462@amd.com> (raw)
In-Reply-To: <CAKfTPtA-UoLj-b6guqFk9MrHFJXaNwvYJw2tZ0Sey9hCRTkh3w@mail.gmail.com>
Hello Vincent,
On 1/16/2026 10:11 PM, Vincent Guittot wrote:
>>> I think that disabling irq time accounting if it was enabled in
>>> __sched_clock_work() should be good
>>
>> I though about this and you can have this particular case as a result
>> of when TSC vs sched_clock is marked unstable:
>>
>> tsc_init()
>> enable_sched_clock_irqtime() # irqtime accounting is enabled here
>> ...
>> if (unsynchronized_tsc()) # true
>> mark_tsc_unstable()
>> clear_sched_clock_stable()
>> __sched_clock_stable_early = 0;
>> ...
>> if (static_key_count(&sched_clock_running.key) == 2) # Only happens at sched_clock_init_late()
>> __clear_sched_clock_stable(); # Never executed
>> ...
>>
>> # late_initcall() phase
>> sched_clock_init_late()
>> if (__sched_clock_stable_early) # Already false
>> __set_sched_clock_stable(); # sched_clock is never marked stable
>>
>> # TSC unstable; irqtime_enabled() is true
>>
>>
>> The current approach from Wangyang covers this case so the v3 should be
>> good as is.
>
> The need of a workqueue is only for CONFIG_HAVE_UNSTABLE_SCHED_CLOCK
> and I'd like to keep it there instead of making the use of a workqueue
> the default behavior for disabling irq time accounting whereas it's
> not needed
>
> So either we can use a single workqueue in unstable clock to handle
> the disabling of one or both __sched_clock_stable and
> sched_clock_irqtime
>
> or unstable clock need another workqueue for disabling sched_clock_irqtime
Ack! We'll likely need a second workqueue and call it early in
__clear_sched_clock_stable().
AFAICT, PA-RISC already suffers from this since it marks
sched_clock_unstable() on SMP but since it uses the generic sched_clock,
on a >= 1MHz processor, it enabled irqtime anyways and nothing disables
it later (unlike TSC, the clocksource doesn't have a "mark_unstable"
callback).
If we can delay enabling the irqtime accounting until we do
__set_sched_clock_stable() for CONFIG_HAVE_UNSTABLE_SCHED_CLOCK (I have
no clue if this is acceptable of not), then we can move the enabling /
disabling of irqtime to the same spots as when we flip
__sched_clock_stable.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-01-19 4:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 2:39 Wangyang Guo
2026-01-16 9:43 ` K Prateek Nayak
2026-01-16 10:22 ` Vincent Guittot
2026-01-16 14:22 ` K Prateek Nayak
2026-01-16 16:41 ` Vincent Guittot
2026-01-19 4:13 ` K Prateek Nayak [this message]
2026-01-22 10:36 ` Vincent Guittot
2026-01-23 4:51 ` K Prateek Nayak
2026-01-23 15:58 ` Vincent Guittot
2026-01-23 16:48 ` K Prateek Nayak
2026-01-26 2:25 ` Guo, Wangyang
2026-01-16 16:58 ` Shrikanth Hegde
2026-01-26 2:28 ` Guo, Wangyang
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=653ac450-2f00-4eb0-bb97-e40576435462@amd.com \
--to=kprateek.nayak@amd.com \
--cc=benjamin.lei@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--cc=tianyou.li@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangyang.guo@intel.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®