linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 2 May 2014 18:04:53 +0530
From:	Mj Embd <mj.embd@...il.com>
To:	kernelnewbies <kernelnewbies@...nelnewbies.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Marc Zyngier <marc.zyngier@....com>
Subject: Re: Linux Interrupt Context maps to ARM CPSR.mode = IRQ

Adding Marc to comment
Marc Please clarify the doubt



On Fri, May 2, 2014 at 5:15 PM, Mj Embd <mj.embd@...il.com> wrote:
> 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



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