From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
david singleton <dsingleton@mvista.com>
Subject: Re: 2.6.14-rt15: cannot build with !PREEMPT_RT
Date: Thu, 08 Dec 2005 20:05:15 -0500 [thread overview]
Message-ID: <1134090316.11053.3.camel@mindpipe> (raw)
In-Reply-To: <20051129093231.GA5028@elte.hu>
On Tue, 2005-11-29 at 10:32 +0100, Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > * Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > > On Mon, 2005-11-28 at 17:40 -0500, Lee Revell wrote:
> > > > 2.6.11-RT-V0.7.40-04 works
> > >
> > > and 2.6.12-RT-V0.7.51-28 does not.
> >
> > thanks. I have further narrowed it down from this point: your .config
> > breaks from the 51-01 to the 51-02 kernel (on my testbox).
>
> ok, fixed this one, it was the CURRENT_PTR optimization on UP that broke
> if 4K stacks were enabled. (i disabled the optimization for now)
>
> But interestingly, your .config unearthed 2 other serious bugs (!) as
> well: the spin_unlock_irq() upon printk was incorrect for !PREEMPT_RT,
> and there was an assert introduced by the get-rid-of-bitlocks ext3
> patches which was invalid on UP && !PREEMPT_RT. We had these bugs for
> quite some time.
>
> I've released -rt21 with these fixes, does it work better for you?
Ingo,
We are unable to build a similar .config (PREEMPT_DESKTOP with soft and
hardirq preemption disabled) on x86-64:
In file included from include/linux/mm.h:15,
from kernel/printk.c:20:
include/linux/fs.h: In function `lock_super':
include/linux/fs.h:849: warning: implicit declaration of function `down'
include/linux/fs.h: In function `unlock_super':
include/linux/fs.h:855: warning: implicit declaration of function `up'
Let me know if you need the exact .config
Lee
next prev parent reply other threads:[~2005-12-09 1:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 6:52 2.6.14-rt15: cannot build with !PREEMPT_RT Lee Revell
2005-11-26 12:23 ` Ingo Molnar
2005-11-26 19:05 ` Lee Revell
2005-11-26 19:46 ` Thomas Gleixner
2005-11-27 12:30 ` Ingo Molnar
2005-11-27 19:57 ` Lee Revell
2005-11-28 11:44 ` Ingo Molnar
2005-11-28 1:27 ` Lee Revell
2005-11-28 11:48 ` Ingo Molnar
2005-11-28 14:56 ` Lee Revell
2005-11-28 16:00 ` Ingo Molnar
2005-11-28 17:50 ` Lee Revell
2005-11-28 20:34 ` Lee Revell
2005-11-28 22:40 ` Lee Revell
2005-11-29 2:08 ` Lee Revell
2005-11-29 7:29 ` Ingo Molnar
2005-11-29 9:32 ` Ingo Molnar
2005-11-29 23:19 ` Lee Revell
2005-12-09 1:05 ` Lee Revell [this message]
2005-12-10 0:25 ` Lee Revell
2005-12-12 17:44 ` 2.6.15-rc5-rt1 will not compile (was Re: 2.6.14-rt15: cannot build with !PREEMPT_RT) Lee Revell
2005-12-12 21:49 ` Steven Rostedt
2005-12-12 22:14 ` Lee Revell
2005-12-12 22:22 ` Steven Rostedt
2005-12-12 22:31 ` Lee Revell
2005-12-12 22:34 ` Steven Rostedt
2005-12-13 3:28 ` Steven Rostedt
2005-12-13 8:08 ` Ingo Molnar
2005-12-16 20:53 ` Lee Revell
2005-12-12 22:39 ` K.R. Foley
2005-12-13 8:15 ` Ingo Molnar
2005-12-13 14:32 ` [PATCH -RT] fix i386 RWSEM_GENERIC_SPINLOCK (was: Re: 2.6.15-rc5-rt1 will not compile) Steven Rostedt
2005-12-13 15:03 ` 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=1134090316.11053.3.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dsingleton@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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