From: doug lkml <doug.lkml@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Query about might_sleep()
Date: Thu, 27 Feb 2014 09:48:45 +0530 [thread overview]
Message-ID: <CALY8T6raZsuChYC1OUV36OYw6fDASLO5rQWTLJy59oOu+9M+DA@mail.gmail.com> (raw)
In-Reply-To: <20140226225018.47eec511@gandalf.local.home>
>>
>> local_irq_save();
>> some_function();
>> rt_spin_lock() --> this calls __might_sleep
>> local_irq_restore(); --> In this case there's a bug right?
>
> Yes, that's a bug. And that's why you'll see a lot of updates in the
> -rt patch with things like: local_irq_save_nort(). And this is also the
> cause of some of the #ifdef CONFIG_PREEMPT_RT_FULL. And what makes this
> change so challenging ;-)
That clarifies my question. Thanks.
prev parent reply other threads:[~2014-02-27 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 6:55 Query about might_sleep() doug lkml
2014-02-27 2:55 ` Steven Rostedt
2014-02-27 3:37 ` doug lkml
2014-02-27 3:50 ` Steven Rostedt
2014-02-27 4:18 ` doug lkml [this message]
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=CALY8T6raZsuChYC1OUV36OYw6fDASLO5rQWTLJy59oOu+9M+DA@mail.gmail.com \
--to=doug.lkml@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).