lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 May 2007 14:45:43 +0800 From: "Dong Feng" <middle.fengdong@...il.com> To: "pradeep singh" <2500.pradeep@...il.com> Cc: "Bahadir Balban" <bahadir.balban@...il.com>, "Learning Linux" <learninglinux4@...il.com>, kernelnewbies@...linux.org, linux-newbie@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Why can't we sleep in an ISR? > > good enough, but i have a query regarding this then. > On a 8K kernel stack system, doesn't interrupts share the stack associated > with the current process which was interrupted? Yes, I think so. > Doesn't interrupt steals the CPU slice time allocated to the running process > to run? I don't think so but I am not sure. > Doesn't it run in current process's context ? > No. I think the concept of process context is a higher-level logical concept. Though the interrupt share stack with the interrupted process, in my opinion it logically does not share the context with the process. > What am i missing here? > > Thanks > ~psr > But I do not see the exact relationship between your specific queries and the original question. Could you elaborate? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists