mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Esben Nielsen <nielsen.esben@googlemail.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: rtmutex's wait_lock in 2.6.18-rt7
Date: Tue, 24 Oct 2006 11:46:03 +0200	[thread overview]
Message-ID: <1161683163.22373.68.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0610231150500.12557@frodo.shire>

On Mon, 2006-10-23 at 11:55 +0200, Esben Nielsen wrote:
> Hi,
>   I see that in 2.6.18-rt7 the rtmutex's wait_lock is sudden interrupt 
> disabling. I don't see the need as no (hard) interrupt-handlers should be 
> touching any mutex.

It does not touch mutexes, but the dynamic priority adjustment of the
hrtimer softirq needs it. 

The correct solution will be moving the timer callback into the process
context, as it will be woken up anyway, but that's more complex to do
than it looks in the first place.

	tglx



  reply	other threads:[~2006-10-24  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23  9:55 Esben Nielsen
2006-10-24  9:46 ` Thomas Gleixner [this message]
2006-10-24 12:19   ` Esben Nielsen

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=1161683163.22373.68.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nielsen.esben@googlemail.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

all inboxes | Powered by JetHome®