From: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, a.p.zijlstra@chello.nl,
ego@in.ibm.com, mingo@elte.hu, andi@firstfloor.org,
venkatesh.pallipadi@intel.com, vatsa@linux.vnet.ibm.com,
arjan@infradead.org, svaidy@linux.vnet.ibm.com,
Arun Bharadwaj <arun@linux.vnet.ibm.com>
Subject: Re: [v4 RFC PATCH 4/4] timers: logic to move non pinned timers
Date: Mon, 6 Apr 2009 20:58:43 +0530 [thread overview]
Message-ID: <20090406152843.GA11645@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0904061248120.747@localhost.localdomain>
* Thomas Gleixner <tglx@linutronix.de> [2009-04-06 12:56:17]:
> Arun,
>
> On Mon, 6 Apr 2009, Arun R Bharadwaj wrote:
> >
> > +ktime_t clockevents_get_next_event(int cpu)
> > +{
> > + struct tick_device *td;
> > + struct clock_event_device *dev;
> > +
> > + td = &per_cpu(tick_cpu_device, cpu);
> > + dev = td->evtdev;
> > +
> > + return dev->next_event;
> > +}
> > +
>
> Preferrably this function should be in the clock events code and a
> stub inline function which returns KTIME_MAX for non clock events
> archs is probably necessary as well.
>
Sure.
> > /*
> > * Switch the timer base to the current CPU when possible.
> > */
> > @@ -198,8 +211,17 @@ switch_hrtimer_base(struct hrtimer *time
> > {
> > struct hrtimer_clock_base *new_base;
> > struct hrtimer_cpu_base *new_cpu_base;
> > + int cpu, preferred_cpu = -1;
> > +
> > + cpu = smp_processor_id();
> > + if (get_sysctl_timer_migration() && !pinned && idle_cpu(cpu)) {
> > + preferred_cpu = get_nohz_load_balancer();
> > + if (preferred_cpu >= 0)
> > + cpu = preferred_cpu;
> > + }
> >
> > - new_cpu_base = &__get_cpu_var(hrtimer_bases);
> > +again:
> > + new_cpu_base = &per_cpu(hrtimer_bases, cpu);
> > new_base = &new_cpu_base->clock_base[base->index];
> >
> > if (base != new_base) {
> > @@ -220,6 +242,32 @@ switch_hrtimer_base(struct hrtimer *time
> > spin_unlock(&base->cpu_base->lock);
> > spin_lock(&new_base->cpu_base->lock);
> > timer->base = new_base;
> > +
> > + if (cpu == preferred_cpu) {
> > + /* Calculate clock monotonic expiry time */
> > + ktime_t expires = ktime_sub(hrtimer_get_expires(timer),
> > + new_base->offset);
> > +
> > + /*
> > + * Get the next event on target cpu from the
> > + * clock events layer.
> > + * This covers the highres=off nohz=on case as well.
> > + */
> > + ktime_t next = clockevents_get_next_event(cpu);
> > +
> > + ktime_t delta = ktime_sub(expires, next);
> > +
> > + /*
> > + * We do not migrate the timer when it is expiring
> > + * before the next event on the target cpu because
> > + * we cannot reprogram the target cpu hardware and
> > + * we would cause it to fire late.
> > + */
> > + if (delta.tv64 < 0) {
> > + cpu = smp_processor_id();
>
> You are missing a small but fatal detail here: You hold
> new_base->cpu_base->lock. So you need to do:
>
I just moved the if block.. if (cpu==preferred_cpu) above the base
locking part to avoid the extra unlocking.
> spin_unlock(&new_base->cpu_base->lock);
> spin_lock(&base->cpu_base->lock);
>
> > + goto again;
> > + }
>
> Also you need to move
>
> > timer->base = new_base;
>
> here to avoid a stale timer->base setting.
>
The above takes care of this as well.
--arun
> > + }
> > }
> > return new_base;
> > }
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2009-04-06 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 11:31 [v4 RFC PATCH 0/4] timers: Framework for migration of timers Arun R Bharadwaj
2009-04-01 11:32 ` [v4 RFC PATCH 1/4] timers: Framework for identifying pinned timers Arun R Bharadwaj
2009-04-01 11:41 ` Andi Kleen
2009-04-02 5:09 ` Arun R Bharadwaj
2009-04-01 11:34 ` [v4 RFC PATCH 2/4] timers: Identifying the existing " Arun R Bharadwaj
2009-04-01 11:36 ` [v4 RFC PATCH 3/4] timers: /proc/sys sysctl hook to enable timer migration Arun R Bharadwaj
2009-04-01 11:37 ` [v4 RFC PATCH 4/4] timers: logic to move non pinned timers Arun R Bharadwaj
2009-04-01 11:46 ` Arun R Bharadwaj
2009-04-03 21:52 ` Thomas Gleixner
2009-04-06 5:16 ` Arun R Bharadwaj
2009-04-06 10:42 ` Arun R Bharadwaj
2009-04-06 10:56 ` Thomas Gleixner
2009-04-06 15:28 ` Arun R Bharadwaj [this message]
2009-04-06 15:31 ` Arun R Bharadwaj
2009-04-06 15:35 ` Thomas Gleixner
2009-04-06 16:00 ` Arun R Bharadwaj
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=20090406152843.GA11645@linux.vnet.ibm.com \
--to=arun@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vatsa@linux.vnet.ibm.com \
--cc=venkatesh.pallipadi@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