All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: sedat.dilek@gmail.com, Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for April 14 (Call-traces: RCU/ACPI/WQ related?)
Date: Tue, 26 Apr 2011 04:31:13 -0700	[thread overview]
Message-ID: <20110426113113.GH4308@linux.vnet.ibm.com> (raw)
In-Reply-To: <1303812417.20212.239.camel@twins>

On Tue, Apr 26, 2011 at 12:06:57PM +0200, Peter Zijlstra wrote:
> On Sun, 2011-04-24 at 09:43 -0700, Paul E. McKenney wrote:
> > 
> > Peter, any thoughts on what I might have done wrong to get the scheduler
> > into a state where it was ignoring a runnable realtime task? 
> 
> Not really, the only thing I can think of is something like poking at
> task->state while its sleeping. One you set it to TASK_RUNNING wakeups
> will be ignored since its already running ;-)

Well, that does give my something to check for -- thank you!

							Thanx, Paul

  reply	other threads:[~2011-04-26 11:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  8:59 linux-next: Tree for April 14 (Call-traces: RCU/ACPI/WQ related?) Sedat Dilek
2011-04-14  9:16 ` Sedat Dilek
2011-04-14 10:19   ` Sedat Dilek
2011-04-14 22:19     ` Sedat Dilek
2011-04-14 22:44       ` Paul E. McKenney
2011-04-21  5:08         ` Paul E. McKenney
2011-04-21  9:07           ` Sedat Dilek
2011-04-21 10:24             ` Sedat Dilek
2011-04-21 12:49               ` Sedat Dilek
2011-04-21 14:28                 ` Paul E. McKenney
2011-04-21 14:47                   ` Sedat Dilek
2011-04-22  0:50                     ` Paul E. McKenney
2011-04-22  9:40                       ` Sedat Dilek
2011-04-22 15:02                         ` Paul E. McKenney
2011-04-22 17:36                           ` Sedat Dilek
2011-04-23 21:05                             ` Paul E. McKenney
2011-04-23 21:16                               ` Sedat Dilek
2011-04-23 23:04                                 ` Sedat Dilek
2011-04-23 23:08                                   ` Sedat Dilek
2011-04-24  6:27                                     ` Paul E. McKenney
2011-04-24  9:36                                       ` Sedat Dilek
2011-04-24 16:43                                         ` Paul E. McKenney
2011-04-26  5:06                                           ` Paul E. McKenney
2011-04-26 11:45                                             ` Sedat Dilek
2011-04-26 12:42                                               ` Paul E. McKenney
2011-04-26 12:50                                                 ` Sedat Dilek
2011-04-26 15:42                                                   ` Paul E. McKenney
2011-04-26 10:06                                           ` Peter Zijlstra
2011-04-26 11:31                                             ` Paul E. McKenney [this message]
2011-04-26 19:44                                               ` Paul E. McKenney

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=20110426113113.GH4308@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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.