From: Peter Zijlstra <peterz@infradead.org> To: David Ahern <dsahern@gmail.com> Cc: Ingo Molnar <mingo@kernel.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: deadlock in scheduler enabling HRTICK feature Date: Thu, 27 Jun 2013 12:43:09 +0200 [thread overview] Message-ID: <20130627104309.GQ28407@twins.programming.kicks-ass.net> (raw) In-Reply-To: <51CB1AE9.5090709@gmail.com> On Wed, Jun 26, 2013 at 10:46:33AM -0600, David Ahern wrote: > On 6/26/13 1:05 AM, Peter Zijlstra wrote: > >>What is the expectation that the feature provides? not a whole lot of > >>documentation on it. I walked down the path wondering if it solved an odd > >>problem we are seeing with the CFS in 2.6.27 kernel. > > > >Its supposed to use hrtimers for slice expiry instead of the regular tick. > > So theoretically CPU bound tasks would get preempted sooner? That was my > guess/hope anyways. Doth the below worketh? --- kernel/sched/core.c | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 9b1f2e5..0d8eb45 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -370,13 +370,6 @@ static struct rq *this_rq_lock(void) #ifdef CONFIG_SCHED_HRTICK /* * Use HR-timers to deliver accurate preemption points. - * - * Its all a bit involved since we cannot program an hrt while holding the - * rq->lock. So what we do is store a state in in rq->hrtick_* and ask for a - * reschedule event. - * - * When we get rescheduled we reprogram the hrtick_timer outside of the - * rq->lock. */ static void hrtick_clear(struct rq *rq) @@ -404,6 +397,15 @@ static enum hrtimer_restart hrtick(struct hrtimer *timer) } #ifdef CONFIG_SMP + +static int __hrtick_restart(struct rq *rq) +{ + struct hrtimer *timer = &rq->hrtick_timer; + ktime_t time = hrtimer_get_softexpires(timer); + + return __hrtimer_start_range_ns(timer, time, 0, HRTIMER_MODE_ABS_PINNED, 0); +} + /* * called from hardirq (IPI) context */ @@ -412,7 +414,7 @@ static void __hrtick_start(void *arg) struct rq *rq = arg; raw_spin_lock(&rq->lock); - hrtimer_restart(&rq->hrtick_timer); + __hrtick_restart(rq); rq->hrtick_csd_pending = 0; raw_spin_unlock(&rq->lock); } @@ -430,7 +432,7 @@ void hrtick_start(struct rq *rq, u64 delay) hrtimer_set_expires(timer, time); if (rq == this_rq()) { - hrtimer_restart(timer); + __hrtick_restart(rq); } else if (!rq->hrtick_csd_pending) { __smp_call_function_single(cpu_of(rq), &rq->hrtick_csd, 0); rq->hrtick_csd_pending = 1;
next prev parent reply other threads:[~2013-06-27 10:43 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-25 21:05 David Ahern 2013-06-25 21:17 ` Peter Zijlstra 2013-06-25 21:20 ` David Ahern 2013-06-26 7:05 ` Peter Zijlstra 2013-06-26 16:46 ` David Ahern 2013-06-27 10:43 ` Peter Zijlstra [this message] 2013-06-27 10:53 ` Peter Zijlstra 2013-06-27 12:28 ` Mike Galbraith 2013-06-27 13:06 ` Ingo Molnar 2013-06-27 19:18 ` Andy Lutomirski 2013-06-27 20:37 ` Peter Zijlstra 2013-06-27 22:28 ` David Ahern 2013-06-28 9:00 ` Ingo Molnar 2013-06-28 9:18 ` Peter Zijlstra 2013-07-12 13:29 ` [tip:sched/core] sched: Fix HRTICK tip-bot for Peter Zijlstra 2013-06-28 9:09 ` deadlock in scheduler enabling HRTICK feature Peter Zijlstra 2013-06-28 17:28 ` David Ahern
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=20130627104309.GQ28407@twins.programming.kicks-ass.net \ --to=peterz@infradead.org \ --cc=dsahern@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --subject='Re: deadlock in scheduler enabling HRTICK feature' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.