public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keenan Pepper <keenanpepper@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: realtime-preempt + reiser4?
Date: Tue, 12 Jul 2005 19:37:28 -0400	[thread overview]
Message-ID: <42D45438.6040409@gmail.com> (raw)
In-Reply-To: <1121198723.10580.10.camel@mindpipe>

Lee Revell wrote:
> Maybe you could apply the broken out reiser4 patches from -mm and the
> realtime preempt patches.  Testing with PREEMPT_DESKTOP and latency
> tracing enabled will tell you whether reiser4 has any latency hot spots.

I'm trying this now and it's not exactly trivial; the patches conflict 
in some places so I had to fix by hand. Now I've got it almost compiled 
but it says:

fs/built-in.o: In function `kcond_wait':
: undefined reference to `there_is_no_init_MUTEX_LOCKED_for_RT_semaphores'
fs/built-in.o: In function `kcond_timedwait':
: undefined reference to `there_is_no_init_MUTEX_LOCKED_for_RT_semaphores'

I naively changed these two calls from

init_MUTEX_LOCKED(&name);

to

init_MUTEX(&name);
down(&name);

but I'm not sure if that's right. I guess I'll see when I try to boot it!

Keenan

  parent reply	other threads:[~2005-07-12 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 19:55 realtime-preempt + reiser4? Keenan Pepper
2005-07-12 20:05 ` Lee Revell
2005-07-12 22:01   ` Hans Reiser
2005-07-12 23:37   ` Keenan Pepper [this message]
2005-07-12 23:51     ` Lee Revell
2005-07-13  0:04     ` Steven Rostedt
2005-07-13 16:23       ` Vladimir V. Saveliev
2005-07-14  6:20         ` Keenan Pepper

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=42D45438.6040409@gmail.com \
    --to=keenanpepper@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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