From: Luis Henriques <henrix@sapo.pt>
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.26.6-rt10
Date: Mon, 13 Oct 2008 01:15:12 +0100 [thread overview]
Message-ID: <48F29310.1030206@sapo.pt> (raw)
In-Reply-To: <1223839814.19319.5.camel@localhost.localdomain>
Hi Steven,
Steven Rostedt wrote:
> We are pleased to announce the 2.6.26.6-rt10 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.26.5-rt9
>
> - ported to 2.6.26.6
>
> - rwlock to handle unnested order unlocks (Steven Rostedt)
>
> - rwlock update torture test to test unnested unlocks (Steven Rostedt)
>
> - remove rt push comment (Gregory Haskins)
>
> - rt sched fix to handle dequeue (Gregory Haskins)
>
> - PPC: remove duplicate stack trace code (Robert Schwebel)
>
> - ARM: ftrace event IRQ call fix (Alexander Pazdnikov)
>
> - fair sched not to resched RT tasks (Peter Zijlstra)
>
> - ftrace quick stop (Steven Rostedt)
>
> - event trace of resched (Steven Rostedt)
>
>
> to build a 2.6.26.6-rt10 tree, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.tar.bz2
> http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.26.6.bz2
> http://rt.et.redhat.com/download/patch-2.6.26.6-rt10.bz2
>
>
>
> And like always, my RT version of Matt Mackall's ketchup will get this
> for you nicely:
>
> http://people.redhat.com/srostedt/rt/tools/ketchup-0.9.8-rt3
>
>
> The broken out patches are also available.
>
>
> -- Steve
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
I found a compilation error while compiling this new version of the rt
pach. I guess the following line is enough for you to trace the problem:
kernel/trace/trace_events.c:49: error: ‘function_trace_stop’ undeclared
(first use in this function)
It seems that an 'extern int function_trace_stop' is missing somewhere...
Regards,
--
Luis Henriques
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Luis Henriques <henrix@sapo.pt>
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.26.6-rt10
Date: Mon, 13 Oct 2008 01:15:12 +0100 [thread overview]
Message-ID: <48F29310.1030206@sapo.pt> (raw)
In-Reply-To: <1223839814.19319.5.camel@localhost.localdomain>
Hi Steven,
Steven Rostedt wrote:
> We are pleased to announce the 2.6.26.6-rt10 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.26.5-rt9
>
> - ported to 2.6.26.6
>
> - rwlock to handle unnested order unlocks (Steven Rostedt)
>
> - rwlock update torture test to test unnested unlocks (Steven Rostedt)
>
> - remove rt push comment (Gregory Haskins)
>
> - rt sched fix to handle dequeue (Gregory Haskins)
>
> - PPC: remove duplicate stack trace code (Robert Schwebel)
>
> - ARM: ftrace event IRQ call fix (Alexander Pazdnikov)
>
> - fair sched not to resched RT tasks (Peter Zijlstra)
>
> - ftrace quick stop (Steven Rostedt)
>
> - event trace of resched (Steven Rostedt)
>
>
> to build a 2.6.26.6-rt10 tree, the following patches should be applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.tar.bz2
> http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.26.6.bz2
> http://rt.et.redhat.com/download/patch-2.6.26.6-rt10.bz2
>
>
>
> And like always, my RT version of Matt Mackall's ketchup will get this
> for you nicely:
>
> http://people.redhat.com/srostedt/rt/tools/ketchup-0.9.8-rt3
>
>
> The broken out patches are also available.
>
>
> -- Steve
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
I found a compilation error while compiling this new version of the rt
pach. I guess the following line is enough for you to trace the problem:
kernel/trace/trace_events.c:49: error: ‘function_trace_stop’ undeclared
(first use in this function)
It seems that an 'extern int function_trace_stop' is missing somewhere...
Regards,
--
Luis Henriques
next prev parent reply other threads:[~2008-10-13 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 19:30 2.6.26.6-rt10 Steven Rostedt
2008-10-13 0:15 ` Luis Henriques [this message]
2008-10-13 0:15 ` 2.6.26.6-rt10 Luis Henriques
2008-10-13 4:46 ` 2.6.26.6-rt10 Steven Rostedt
2008-10-13 19:51 ` 2.6.26.6-rt10 Steven Rostedt
2008-10-13 21:15 ` 2.6.26.6-rt10 Luis Henriques
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=48F29310.1030206@sapo.pt \
--to=henrix@sapo.pt \
--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 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.