From: Peter Zijlstra <peterz@infradead.org>
To: Qais Yousef <qyousef@layalina.io>
Cc: Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Stultz <jstultz@google.com>,
Thomas Gleixner <tglx@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] sched/tick: Decouple sched_tick() from HZ
Date: Tue, 19 May 2026 11:13:12 +0200 [thread overview]
Message-ID: <20260519091312.GB3102624@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260519004256.tixhmh6hmfnbu7cx@airbuntu>
On Tue, May 19, 2026 at 01:42:56AM +0100, Qais Yousef wrote:
> On 05/18/26 09:40, Peter Zijlstra wrote:
> > On Sun, May 17, 2026 at 05:07:37AM +0100, Qais Yousef wrote:
> > > With HRTICK now is default on,
> >
> > .. for archs that use GENERIC_ENTRY. So for example, ARM64 doesn't (yet)
> > have this.
>
> I remembering trying to trace down the deps on HRTIMER_REARM_DEFERRED and then
> got distracted.
>
> HRTIMER on arm are cheap. Do we need this deps on generic entry?
>
> Anyways. More reason to decouple I take :)
ARM64 Generic Entry patches are en-route somewhere. I'll get sorted.
prev parent reply other threads:[~2026-05-19 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 4:07 Qais Yousef
2026-05-17 4:07 ` [PATCH 1/3] " Qais Yousef
2026-05-17 4:07 ` [PATCH 2/3] sched/tick: Move TICK_NSEC users to PTICK_NSEC Qais Yousef
2026-05-17 4:07 ` [PATCH 3/3] sched/tick: Turn on PTICK by default Qais Yousef
2026-05-17 4:19 ` [PATCH 0/3] sched/tick: Decouple sched_tick() from HZ Qais Yousef
2026-05-17 14:10 ` David Laight
2026-05-17 15:44 ` Qais Yousef
2026-05-17 16:09 ` David Laight
2026-05-17 17:26 ` Qais Yousef
2026-05-18 7:40 ` Peter Zijlstra
2026-05-19 0:42 ` Qais Yousef
2026-05-19 9:13 ` Peter Zijlstra [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=20260519091312.GB3102624@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=frederic@kernel.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=tglx@kernel.org \
--cc=vincent.guittot@linaro.org \
/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®