From: Ingo Molnar <mingo@elte.hu>
To: Gregory Haskins <ghaskins@novell.com>
Cc: rostedt@goodmis.org, peterz@infradead.org, npiggin@suse.de,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 0/3] sched: newidle and RT wake-buddy fixes
Date: Thu, 3 Jul 2008 16:41:24 +0200 [thread overview]
Message-ID: <20080703144124.GA653@elte.hu> (raw)
In-Reply-To: <4868DCC7.BA47.005A.0@novell.com>
* Gregory Haskins <ghaskins@novell.com> wrote:
> I may have found the issue: It looks like the hunk that initially
> disables interrupts in load_balance_newidle() was inadvertently
> applied to load_balance() instead during the merge to linux-tip. If
> you fold the following patch into my original patch, it should set
> things right again.
ah, sorry - indeed! I've reactivated your patch and i'm testing it now.
Ingo
next prev parent reply other threads:[~2008-07-03 14:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 20:29 [PATCH 0/3] sched: newidle and RT wake-buddy fixes Gregory Haskins
2008-06-27 20:29 ` [PATCH 1/3] sched: enable interrupts and drop rq-lock during newidle balancing Gregory Haskins
2008-06-27 20:29 ` [PATCH 2/3] sched: terminate newidle balancing once at least one task has moved over Gregory Haskins
2008-07-08 5:00 ` Nick Piggin
2008-07-08 12:37 ` Gregory Haskins
2008-07-09 8:09 ` Nick Piggin
2008-07-09 10:53 ` Gregory Haskins
2008-07-09 11:17 ` Nick Piggin
2008-07-09 11:53 ` Gregory Haskins
2008-06-27 20:30 ` [PATCH 3/3] sched: add avg-overlap support to RT tasks Gregory Haskins
2008-06-27 20:51 ` [PATCH 0/3] sched: newidle and RT wake-buddy fixes Peter Zijlstra
2008-06-30 12:56 ` Ingo Molnar
2008-06-30 13:15 ` Ingo Molnar
2008-06-30 11:20 ` Gregory Haskins
2008-06-30 14:41 ` Gregory Haskins
2008-06-30 15:01 ` Steven Rostedt
2008-06-30 17:16 ` Gregory Haskins
2008-06-30 18:10 ` Ingo Molnar
2008-07-03 14:41 ` Ingo Molnar [this message]
2008-07-03 15:12 ` Ingo Molnar
2008-07-08 12:38 ` Gregory Haskins
2008-07-08 16:45 ` Gregory Haskins
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=20080703144124.GA653@elte.hu \
--to=mingo@elte.hu \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox