From: Ankita Garg <ankita@in.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24.7-rt18
Date: Wed, 10 Sep 2008 11:36:24 +0530 [thread overview]
Message-ID: <20080910060624.GA7484@in.ibm.com> (raw)
In-Reply-To: <1221018283.22713.20.camel@localhost.localdomain>
Hi Steven,
On Tue, Sep 09, 2008 at 11:44:42PM -0400, Steven Rostedt wrote:
> We are pleased to announce the 2.6.24.7-rt18 tree, which can be
> downloaded from the location:
>
> http://rt.et.redhat.com/download/
>
> Information on the RT patch can be found at:
>
> http://rt.wiki.kernel.org/index.php/Main_Page
>
> Changes since 2.6.24.7-rt17
>
> - seqlock serialize writes (Gregory Haskins)
>
> - Fix above patch that broke non PREEMPT_RT (Steven Rostedt)
>
> - Add sysctl to warn on RT task using non PI futex (Steven Rostedt)
>
A trivial patch to remove the hard coded value of MAX_RT_PRIO in the
above patch.
Signed-off-by: Ankita Garg <ankita@in.ibm.com>
Index: linux-2.6.26.5/kernel/futex.c
===================================================================
--- linux-2.6.26.5.orig/kernel/futex.c 2008-09-09 22:58:19.000000000 -0700
+++ linux-2.6.26.5/kernel/futex.c 2008-09-09 22:58:38.000000000 -0700
@@ -1241,7 +1241,7 @@
"RT task %s:%d with priority %d"
" using non PI futex\n",
current->comm, current->pid,
- 100 - current->prio);
+ MAX_RT_PRIO - current->prio);
}
}
--
Regards,
Ankita Garg (ankita@in.ibm.com)
Linux Technology Center
IBM India Systems & Technology Labs,
Bangalore, India
next prev parent reply other threads:[~2008-09-10 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 3:44 2.6.24.7-rt18 Steven Rostedt
2008-09-10 6:06 ` Ankita Garg [this message]
2008-09-10 11:32 ` 2.6.24.7-rt18 Steven Rostedt
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=20080910060624.GA7484@in.ibm.com \
--to=ankita@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--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