All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: deadlock in scheduler enabling HRTICK feature
Date: Fri, 28 Jun 2013 11:28:54 -0600	[thread overview]
Message-ID: <51CDC7D6.9070804@gmail.com> (raw)
In-Reply-To: <20130628090939.GD29209@dyad.programming.kicks-ass.net>

On 6/28/13 3:09 AM, Peter Zijlstra wrote:

> Yah! :-) Obviously doing a wakeup while holding scheduler locks isn't going to
> work out well. And the only reason we really need that pesky softirq nonsense
> is when we accidentally schedule a timer that's already expired; in that case
> we'll run it from sirq context.
>
> We don't care about missing events like that; there's always the actual tick
> for backup.
>
> I suppose I'd better go write a Changelog and properly submit the patch :-)
>

Thanks for the quick turnaround on the patch - and the explanation.

David

      reply	other threads:[~2013-06-28 17:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 21:05 deadlock in scheduler enabling HRTICK feature 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
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 [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=51CDC7D6.9070804@gmail.com \
    --to=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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 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.