From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Keenan Pepper <keenanpepper@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Lee Revell <rlrevell@joe-job.com>
Subject: Re: realtime-preempt + reiser4?
Date: Wed, 13 Jul 2005 20:23:18 +0400 [thread overview]
Message-ID: <42D53FF6.2020200@namesys.com> (raw)
In-Reply-To: <1121213099.3548.39.camel@localhost.localdomain>
Hello
Steven Rostedt wrote:
> On Tue, 2005-07-12 at 19:37 -0400, Keenan Pepper wrote:
>
>
>>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!
>
>
> No, since it probably wont be "uped" by the same process. So what you
> want to do is change the definition of name from semaphore to
> compat_semaphore, and keep it as init_MUTEX_LOCKED. And please send
> patches to Ingo (I've included him on CC). Also include Ingo on all RT
> related issues, since he is the one maintaining the patch.
>
ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12/reiser4-for-2.6.12-realtime-preempt-2.6.12-final-V0.7.51-29.patch.gz
It applies to 2.6.12 + http://people.redhat.com/mingo/realtime-preempt/older/realtime-preempt-2.6.12-final-V0.7.51-29
next prev parent reply other threads:[~2005-07-13 16:25 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
2005-07-12 23:51 ` Lee Revell
2005-07-13 0:04 ` Steven Rostedt
2005-07-13 16:23 ` Vladimir V. Saveliev [this message]
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=42D53FF6.2020200@namesys.com \
--to=vs@namesys.com \
--cc=keenanpepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.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 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.