public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <bitbucket@online.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	ethan.kernel@gmail.com, rjw@sisk.pl, daniel.lezcano@linaro.org,
	linux-pm@vger.kernel.org, lenb@kernel.org
Subject: Re: [PATCH V3]hrtimer: Fix a performance regression by disable reprogramming in remove_hrtimer
Date: Wed, 11 Sep 2013 12:25:23 +0200	[thread overview]
Message-ID: <1378895123.5476.83.camel@marge.simpson.net> (raw)
In-Reply-To: <20130911085643.GS26785@twins.programming.kicks-ass.net>

On Wed, 2013-09-11 at 10:56 +0200, Peter Zijlstra wrote: 
> On Mon, Sep 09, 2013 at 03:46:35PM +0200, Peter Zijlstra wrote:
> > On Mon, Sep 09, 2013 at 03:30:44PM +0200, Peter Zijlstra wrote:
> > > diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
> > > index fa6964d..486c0ba 100644
> > > --- a/drivers/idle/intel_idle.c
> > > +++ b/drivers/idle/intel_idle.c
> > > @@ -359,6 +359,14 @@ static int intel_idle(struct cpuidle_device *dev,
> > >  	if (!(lapic_timer_reliable_states & (1 << (cstate))))
> > >  		clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_ENTER, &cpu);
> > >  
> > > +	current_thread_into()->status |= TS_POLLING;
> > > +
> > > +	/*
> > > +	 * Order against setting of TS_POLLING against the reading of
> > > +	 * NEED_RESCHED, matched by resched_task().
> > > +	 */
> > > +	smp_mb();
> > > +
> > >  	if (!need_resched()) {
> > >  
> > >  		__monitor((void *)&current_thread_info()->flags, 0, 0);
> > > @@ -367,6 +375,8 @@ static int intel_idle(struct cpuidle_device *dev,
> > >  			__mwait(eax, ecx);
> > >  	}
> > >  
> > > +	current_thread_into()->status &= ~TS_POLLING;
> > > +
> > >  	if (!(lapic_timer_reliable_states & (1 << (cstate))))
> > >  		clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_EXIT, &cpu);
> > 
> > Hmm, arguably it would be better to set this from
> > intel_idle_cpuidle_driver_init() and clear it whenever this goes away.
> > Not sure how all that works, the cpuidle driver framework seems 'weird'.
> 
> OK, so I went over the idle stuff again, and we do set TS_POLLING like
> stuff, it got hidden in current_{clr,set}_polling().
> 
> Still if that patch causes extra IPIs its bound to be broken in some
> creative way.. I'll prod.

(thanks, when I get a break from testing/poking this'n'that, I'll take a
peek too...  well, good_intentions++ anyway;)

  reply	other threads:[~2013-09-11 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130729115701.GD3008@twins.programming.kicks-ass.net>
     [not found] ` <24EECBCC-F655-404F-8946-73CC36095A5F@gmail.com>
     [not found]   ` <1378362989.18435.2.camel@marge.simpson.net>
     [not found]     ` <20130905111428.GB23362@gmail.com>
     [not found]       ` <1378386697.6567.9.camel@marge.simpson.net>
     [not found]         ` <20130905133750.GA26637@gmail.com>
     [not found]           ` <1378445942.5434.31.camel@marge.simpson.net>
     [not found]             ` <20130909122325.GX31370@twins.programming.kicks-ass.net>
     [not found]               ` <1378730538.5586.30.camel@marge.simpson.net>
     [not found]                 ` <20130909133044.GB31370@twins.programming.kicks-ass.net>
2013-09-09 13:46                   ` [PATCH V3]hrtimer: Fix a performance regression by disable reprogramming in remove_hrtimer Peter Zijlstra
2013-09-11  8:56                     ` Peter Zijlstra
2013-09-11 10:25                       ` Mike Galbraith [this message]
2013-10-04 12:06                         ` Ethan Zhao
2013-10-07  4:41                           ` Mike Galbraith
2013-10-07  4:57                             ` Ethan Zhao
2013-12-12 14:14                               ` Ethan Zhao
2013-12-12 14:42                                 ` Mike Galbraith

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=1378895123.5476.83.camel@marge.simpson.net \
    --to=bitbucket@online.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=ethan.kernel@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    /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