public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Esben Nielsen <simlo@phys.au.dk>
Cc: Jens Axboe <axboe@suse.de>, Lee Revell <rlrevell@joe-job.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: CFQ + 2.6.13-rc4-RT-V0.7.52-02 = BUG: scheduling with irqs disabled
Date: Thu, 25 Aug 2005 09:40:54 +0200	[thread overview]
Message-ID: <20050825074054.GA30650@elte.hu> (raw)
In-Reply-To: <Pine.OSF.4.05.10508242321500.13279-100000@da410.phys.au.dk>


* Esben Nielsen <simlo@phys.au.dk> wrote:

> Yes, spin_lock(lock) is blocking since lock is mutex, not a spinlock 
> under preempt-rt. But isn't it easy to fix? Replace the two lines by 
> spin_lock_irqsave(flags). That would work for both preempt-rt and 
> !preempt-rt.

at this moment we do not pester upstream developers with PREEMPT_RT 
details. It is not at all clear at this moment whether and if how any 
API changes will look like. So there's nothing "to fix" at all!!

for the cases where there's a clear cleanup potential from merging flags 
and locks management we submit separate patches, which stand on their 
own. It happened already, and it will happen in the future. The rest 
Jens does not need to care about.

_often_, trouble on the PREEMPT_RT side highlights some potential 
trouble on the upstream side. Unclean locking rules, unecessary/unsafe 
disabling of interrupts, etc. But no way is there a 1:1 relationship.  
E.g. in this particular case i already fixed the warning in the current 
-RT tree.

	Ingo

  parent reply	other threads:[~2005-08-25  7:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 16:02 CFQ + 2.6.13-rc4-RT-V0.7.52-02 = BUG: scheduling with irqs disabled Lee Revell
2005-08-24 17:47 ` Jens Axboe
2005-08-24 21:35   ` Esben Nielsen
2005-08-25  6:10     ` Jens Axboe
2005-08-25  7:40     ` Ingo Molnar [this message]
2005-08-25  6:09   ` Ingo Molnar
2005-08-25  6:22     ` Jens Axboe
2005-08-25  7:52       ` Ingo Molnar
2005-08-25 11:17         ` Jens Axboe

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=20050825074054.GA30650@elte.hu \
    --to=mingo@elte.hu \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=simlo@phys.au.dk \
    /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