From: "Gregory Haskins" <ghaskins@novell.com>
To: <mingo@elte.hu>
Cc: <jim.houston@ccur.com>, <joe.korty@ccur.com>,
<rostedt@goodmis.org>, <tglx@linutronix.de>, <dwalker@mvista.com>,
"David Bahi" <DBahi@novell.com>,
"Moiz Kohari" <MKohari@novell.com>,
"Sven Dietrich" <SDietrich@novell.com>, <dsaxena@plexity.net>,
<williams@redhat.com>, <abogani@texware.it>,
<linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: Forward port of latest RT patch (2.6.21.5-rt20) to 2.6.22 available
Date: Thu, 12 Jul 2007 12:26:48 -0400 [thread overview]
Message-ID: <46961E080200005A000276AE@mcclure.wal.novell.com> (raw)
On Thu, 2007-07-12 at 14:07 +0200, Ingo Molnar wrote:
> great! We had the upstream -rt port to .22 in the works too, it was just
> held up by the hpet breakage - which Thomas managed to fix earlier
> today. I've released the 2.6.22.1-rt1 patch to the usual place:
>
> http://redhat.com/~mingo/realtime-preempt/
Hi Ingo,
For the most part, it seems you guys have resolved most of the issues
that we ran into as well (e.g. early-flush-tlb, relocated die-notifier,
etc, come to mind). I found one patch that was missing that allows
debug configurations to build properly. Heres that patch:
--- linux-2.6.21.orig/kernel/latency_trace.c
+++ linux-2.6.21/kernel/latency_trace.c
@@ -24,6 +24,7 @@
#include <linux/utsrelease.h>
#include <asm/uaccess.h>
#include <asm/unistd.h>
+#include <asm/asm-offsets.h>
#include <asm/rtc.h>
#include <linux/stacktrace.h>
With this patch in place, I am able to build/boot both a 21.1-rt1 kernel
with a standard x86_64 PREEMPT_RT+SMP both with and without the usual
debug options, so that is great!
We did find a regression. I was mistaken earlier when I mentioned our
T60p laptops couldn't boot. It turns out that issue was resolved
somewhere along the way and our published patches based on 21.5-rt19 do
allow the laptop to boot event with acpi=on. With 22.1-rt1 the laptop
crashes unless acpi=off. Now that we have your queue we will bisect
this and post that fix as well.
Thanks!
-Greg
next reply other threads:[~2007-07-12 16:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 16:26 Gregory Haskins [this message]
2007-07-12 16:33 ` Ingo Molnar
2007-07-12 20:21 ` Sven-Thorsten Dietrich
2007-07-13 12:52 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2007-07-12 12:26 Gregory Haskins
2007-07-12 13:09 ` Ingo Molnar
2007-07-13 6:25 ` Peter Williams
2007-07-13 6:52 ` Thomas Gleixner
2007-07-13 8:43 ` Gene Heskett
2007-07-13 9:42 ` Thomas Gleixner
2007-07-14 0:27 ` Peter Williams
2007-07-14 0:52 ` Gene Heskett
2007-07-12 11:10 Gregory Haskins
2007-07-12 10:17 Gregory Haskins
2007-07-12 0:58 Gregory Haskins
2007-07-12 1:05 ` Daniel Walker
2007-07-12 5:14 ` Thomas Gleixner
2007-07-12 7:27 ` Alessio Igor Bogani
2007-07-12 12:07 ` Ingo Molnar
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=46961E080200005A000276AE@mcclure.wal.novell.com \
--to=ghaskins@novell.com \
--cc=DBahi@novell.com \
--cc=MKohari@novell.com \
--cc=SDietrich@novell.com \
--cc=abogani@texware.it \
--cc=dsaxena@plexity.net \
--cc=dwalker@mvista.com \
--cc=jim.houston@ccur.com \
--cc=joe.korty@ccur.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 \
--cc=williams@redhat.com \
/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
all inboxes | Powered by JetHome®