From: Thomas Gleixner <tglx@linutronix.de>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
vatikaharlalka@gmail.com,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
stable@vger.kernel.org
Subject: Re: get_nohz_timer_target?
Date: Fri, 8 Jul 2016 18:48:49 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1607081848060.4083@nanos> (raw)
In-Reply-To: <20160708114937.GB30200@lerouge>
On Fri, 8 Jul 2016, Frederic Weisbecker wrote:
> On Fri, Jul 08, 2016 at 11:05:58AM +0200, Thomas Gleixner wrote:
> > On Mon, 18 Apr 2016, Richard Cochran wrote:
> > > Looking at kernel/sched/core.c:get_nohz_timer_target(), I don't
> > > understand the change made in:
> > >
> > > commit 9642d18eee2cd169b60c6ac0f20bda745b5a3d1e
> > > Author: Vatika Harlalka <vatikaharlalka@gmail.com>
> > > Date: Tue Sep 1 16:50:59 2015 +0200
> > > nohz: Affine unpinned timers to housekeepers
> > >
> > > After that change, the code now reads like this:
> > >
> > > int i, cpu = smp_processor_id();
> > > struct sched_domain *sd;
> > >
> > > if (!idle_cpu(cpu) && is_housekeeping_cpu(cpu))
> > > return cpu;
> > >
> > > rcu_read_lock();
> > > for_each_domain(cpu, sd) {
> > > for_each_cpu(i, sched_domain_span(sd)) {
> > > if (!idle_cpu(i) && is_housekeeping_cpu(cpu)) {
> > > --------------------------------------------------------------- ^^^
> > > Was this supposed to be 'i' instead?
> >
> > Yes. Care to send a patch?
>
> Ah this got fixed already: 444969223c81c7d0a95136b7b4cfdcfbc96ac5bd
> ("sched/nohz: Fix affine unpinned timers mess")
Good. Though that patch misses a stable tag.
Thanks,
tglx
prev parent reply other threads:[~2016-07-08 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 13:37 get_nohz_timer_target? Richard Cochran
2016-07-08 9:05 ` get_nohz_timer_target? Thomas Gleixner
2016-07-08 11:49 ` get_nohz_timer_target? Frederic Weisbecker
2016-07-08 16:48 ` 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=alpine.DEB.2.11.1607081848060.4083@nanos \
--to=tglx@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=richardcochran@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vatikaharlalka@gmail.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