[lkml]   [2009]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Can current macro be accessed from interrupt context?
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?
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2009-10-22 17:19    [W:0.076 / U:0.648 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site