linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Jaap-Jan Boor <jjboor@aimsys.nl>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [BUG][PPC32] Preemption patch for 2.4 Kernels
Date: Thu, 7 Oct 2004 11:35:51 -0700	[thread overview]
Message-ID: <20041007183551.GA22982@gate.ebshome.net> (raw)
In-Reply-To: <C3EF3884-188D-11D9-841F-000A95B15278@aimsys.nl>

On Thu, Oct 07, 2004 at 08:21:54PM +0200, Jaap-Jan Boor wrote:
> 
> On 7-okt-04, at 19:34, Eugene Surovegin wrote:
> 
> >On Thu, Oct 07, 2004 at 03:29:12PM +0200, Gerhard Jaeger wrote:
> >>maybe the 2.4 series is somewhat outdatet, but nevertheless used in
> >>several embedded systems and also with your preemption patches.
> >>During some investigations, we found out that the patches found on
> >>http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/
> >>contain a severe bug, when using the patches on PPC systems.
> >
> >Yes, it's a known problem with rml preempt patches - DON'T USE THEM
> >on PPC. I sent him similar patch _two_ years ago - nothing happened.
> >MVL tree is IMHO better place to get preempt stuff for 2.4 - it's
> >actually tested and works.
> 
> yes, because there are more changes then only the forgotten '{'
> 

You're right, there were other (not so obvious) problems which rml 
patch (like preempt_enable_no_resched() in 
irq.c::preempt_intercept()), maybe others I don't remember now)...

--
Eugene

      reply	other threads:[~2004-10-07 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 13:29 [BUG][PPC32] Preemption patch for 2.4 Kernels Gerhard Jaeger
2004-10-07 17:34 ` Eugene Surovegin
2004-10-07 18:21   ` Jaap-Jan Boor
2004-10-07 18:35     ` Eugene Surovegin [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=20041007183551.GA22982@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=jjboor@aimsys.nl \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).