From: Arjan van de Ven <arjan@infradead.org>
To: "Leonidas ." <leonidas137@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Can current macro be accessed from interrupt context?
Date: Thu, 22 Oct 2009 06:45:38 -0700 [thread overview]
Message-ID: <20091022064538.25837421@infradead.org> (raw)
In-Reply-To: <f22d86810910220410r33002b5ei403ddf6632254472@mail.gmail.com>
On Thu, 22 Oct 2009 04:10:49 -0700
"Leonidas ." <leonidas137@gmail.com> wrote:
> Hello,
>
> Going through UTLK, it says that current macro makes sense only in
> case of process context,
> in case of interrupt context it is invalid.
>
> But current would still be pointing to interrupted process right? The
> pointer would still be valid?
> Can I safely assume that whether or not interrupt handlers are
> executing on separate stacks or
> interrupted threads stack, current macro can be accessed from
> interrupt context?
not for interrupt threads, and that's where things are moving to.
for interrupt stacks you ought to be fine (current is just a pointer on
the stack, and last I looked we copied that pointer for each interrupt
to the irq stack)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-10-22 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 11:10 Can current macro be accessed from interrupt context? Leonidas .
2009-10-22 11:27 ` Frederic Weisbecker
2009-10-22 11:43 ` Leonidas .
2009-10-22 11:49 ` Leonidas .
2009-10-22 12:06 ` Frederic Weisbecker
2009-10-22 13:37 ` Leonidas .
2009-10-22 13:45 ` Arjan van de Ven [this message]
2009-10-22 15:17 ` Valdis.Kletnieks
2009-10-22 17:46 ` Leonidas .
2009-10-22 18:12 ` Leonidas .
2009-10-23 8:13 ` Clemens Ladisch
2009-10-23 9:34 ` Leonidas .
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=20091022064538.25837421@infradead.org \
--to=arjan@infradead.org \
--cc=leonidas137@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.