From: Thomas Gleixner <tglx@linutronix.de>
To: Benjamin Segall <bsegall@google.com>,
linux-kernel@vger.kernel.org,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v2] posix-cpu-timers: clear TICK_DEP_BIT_POSIX_TIMER on clone
Date: Sat, 19 Oct 2024 22:59:04 +0200 [thread overview]
Message-ID: <8734kr95d3.ffs@tglx> (raw)
In-Reply-To: <xm26ttd9ay34.fsf@google.com>
On Fri, Oct 18 2024 at 14:41, Benjamin Segall wrote:
> When we clone a new thread, we do not inherit its posix_cputimers, and
We? We neither clone something nor can we inherit anything from the
kernel. Please do not impersonate code and use passive voice.
> clear them with posix_cputimers_init. However, this does not clear the
Please denote functions with brackets, i.e. fun() so its obvious.
> tick dependency it creates in tsk->tick_dep_mask, and the handler does
> not reach the code to clear the dependency if there were no timers to
> begin with.
>
> Thus if a thread has a cputimer running before cloneing/forking, that
> hierarchy will prevent nohz_full unless they create a cputimer of their
> own.
>
> Process-wide timers do not have this problem because fork does not copy
> signal_struct as a baseline, it creates one from scratch.
And the solution to this is described where in the change log?
Thanks,
tglx
prev parent reply other threads:[~2024-10-19 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 21:41 [PATCH v2] posix-cpu-timers: clear TICK_DEP_BIT_POSIX_TIMER on clone Benjamin Segall
2024-10-19 20:59 ` 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=8734kr95d3.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=bsegall@google.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.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