linux-kernel - Linux Interrupt Context maps to ARM CPSR.mode = IRQ

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPUj1OMJ8cE1cNTe8CjgBP2GTCXzi__Yg0+OoomME6=TShgqJg@mail.gmail.com>
Date:	Fri, 2 May 2014 17:15:49 +0530
From:	Mj Embd <mj.embd@...il.com>
To:	kernelnewbies <kernelnewbies@...nelnewbies.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Linux Interrupt Context maps to ARM CPSR.mode = IRQ

Hi,

As per a lot of linux documentation some components work in process
context and some work in interrupt context.

If we try to map these contexts to ARM processor modes then is it
safely to assume that
Process Context : CPSR.mode = SVC
Interrupt Context : CPSR.mode = IRQ

If not how to define interrupt context properly. Confusing at times.

-- 
-mj
--
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/