From: "Mike Frysinger" <vapier.adi@gmail.com>
To: fundu_1999@yahoo.com
Cc: linux embedded <linux-embedded@vger.kernel.org>
Subject: Re: local_save_flags(flags)
Date: Tue, 23 Sep 2008 19:11:03 -0400 [thread overview]
Message-ID: <8bd0f97a0809231611y48102c29u66e6f8b9f483a726@mail.gmail.com> (raw)
In-Reply-To: <903542.11891.qm@web63401.mail.re1.yahoo.com>
On Tue, Sep 23, 2008 at 16:01, Fundu wrote:
>> > 2) so is disable interrupts twice is a problem, or just
>> enabling them after they are disabled (which sounds like
>> how it should be) a problem.
>>
>> both are a problem. the non-state saving version cannot be
>> used
>> recursively nor in parallel to the state-saving version.
>
> Much clear now, Thanks Mike!
>
> here's a follow up question.
>
> what about Non maskable interrupts ? disabling interrupt won't have any effect on that right ?
that really doesnt make sense by definition huh. non-maskable means
they cant be masked.
-mike
next prev parent reply other threads:[~2008-09-23 23:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <556445368AFA1C438794ABDA8901891C098AABE6@USA0300MS03.na.xerox.net>
2008-09-18 21:09 ` local_save_flags(flags) Fundu
2008-09-18 21:15 ` local_save_flags(flags) Mike Frysinger
2008-09-18 22:05 ` local_save_flags(flags) Fundu
2008-09-18 22:07 ` local_save_flags(flags) Mike Frysinger
2008-09-18 22:45 ` local_save_flags(flags) Fundu
2008-09-18 22:51 ` local_save_flags(flags) Mike Frysinger
2008-09-23 20:01 ` local_save_flags(flags) Fundu
2008-09-23 23:11 ` Mike Frysinger [this message]
2008-09-24 1:15 ` local_save_flags(flags) Fundu
2008-09-24 1:31 ` local_save_flags(flags) Mike Frysinger
2008-09-24 17:06 ` local_save_flags(flags) Fundu
2008-09-29 3:32 ` local_save_flags(flags) Robin Getz
2008-09-19 9:52 ` local_save_flags(flags) Daniel THOMPSON
2008-09-18 18:48 local_save_flags(flags) Fundu
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=8bd0f97a0809231611y48102c29u66e6f8b9f483a726@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=fundu_1999@yahoo.com \
--cc=linux-embedded@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;
as well as URLs for NNTP newsgroup(s).