From: Valdis.Kletnieks@vt.edu
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 11:17:03 -0400 [thread overview]
Message-ID: <5048.1256224623@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 22 Oct 2009 04:10:49 PDT." <f22d86810910220410r33002b5ei403ddf6632254472@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On Thu, 22 Oct 2009 04:10:49 PDT, "Leonidas ." said:
> My use case is to get process id from any context with CONFIG_4KSTACKS = 0 or 1.
You *do* realize that if you're in interrupt context, the value of 'current'
probably has absolutely nothing to do with the interrupt? The process/thread
that is responsible for an I/O interrupt is probably in a blocked state waiting
for the I/O to complete, and the *running* process is often some other process.
And for some interrupts (timer, etc), all bets are off...
So given that the process ID is quite often totally pointless, what were you
trying to accomplish by getting the process ID?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2009-10-22 15:17 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
2009-10-22 15:17 ` Valdis.Kletnieks [this message]
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=5048.1256224623@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox