From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Voluntary Preempt additions
Date: Mon, 18 Oct 2004 20:13:31 +0200 [thread overview]
Message-ID: <20041018181331.GB2899@elte.hu> (raw)
In-Reply-To: <1098121769.26597.5.camel@dhcp153.mvista.com>
* Daniel Walker <dwalker@mvista.com> wrote:
> This is in addition to voluntary preempt U5 . So, first apply up to
> Voluntary Preempt U4 , then apply this patch. I'll release for U5 as
> soon as it's formally released.
i've released U5 an hour ago.
> We are releasing the following new features,
>
> - Architecture independent mutex with priority inheritance. Note, we
> have only tested this in x86.
there's new generic mutex code in -U5 which covers all the locking
primitives: semaphores, rw-semaphores, spinlock-mutexes and
rwlock-mutexes. PI should be done by improving the existing
rwsem-generic.c code.
> - Modified latency tracer to trace non-preemptable mutex locking , in
> /proc/lock_trace
hm, what is this good for? It is illegal to enter a schedulable section
with preemption disabled and there we currently dump a trace of all
critical sections held - this should be enough to pinpoint the bug.
> - Added two new locking functions _mutex_lock_cpu and
> _mutex_unlock_cpu.
hm, they are unused right now - what will they be used for?
Ingo
next prev parent reply other threads:[~2004-10-18 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 17:49 [patch] Voluntary Preempt additions Daniel Walker
2004-10-18 18:13 ` Ingo Molnar [this message]
2004-10-18 18:30 ` Robert Love
2004-10-18 18:38 ` Ingo Molnar
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=20041018181331.GB2899@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.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