From: Gregory Haskins <ghaskins@novell.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"linux >> LKML" <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RT] [git pull] updates for rt/sched
Date: Wed, 21 Jan 2009 12:54:41 -0500 [thread overview]
Message-ID: <49776161.1080801@novell.com> (raw)
In-Reply-To: <497760A1.9090806@novell.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Gregory Haskins wrote:
> Hi Steve,
> Here is a backport of the latest patches that went into tip/sched/rt
>
> -Greg
>
[Adding Peter to CC, since he contributed too]
>
> -------------
> The following changes since commit 0ea6fdc871f24f65e28cd9a92ead1c881783741a:
> Gregory Haskins (1):
> rt/sched: ensure interrupts are disabled during post-schedule()
> processing
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ghaskins/linux-2.6-hacks.git
> rt/sched
>
> Gregory Haskins (6):
> sched: cleanup inc/dec_rt_tasks
> sched: track the next-highest priority on each runqueue
> sched: use highest_prio.curr for pull threshold
> sched: use highest_prio.next to optimize pull operations
> sched: de CPP-ify the scheduler code
> sched: fix build error in kernel/sched_rt.c when RT_GROUP_SCHED &&
> !SMP
>
> Peter Zijlstra (1):
> sched: make plist a library facility
>
> init/Kconfig | 1 -
> kernel/sched.c | 12 ++-
> kernel/sched_rt.c | 372
> ++++++++++++++++++++++++++++++++++------------------
> lib/Kconfig | 6 -
> lib/Makefile | 4 +-
> 5 files changed, 255 insertions(+), 140 deletions(-)
>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-01-21 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 17:51 [RT] [git pull] updates for rt/sched Gregory Haskins
2009-01-21 17:54 ` Gregory Haskins [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=49776161.1080801@novell.com \
--to=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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