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]

Message-ID: <14abe1165b144fe3d1139ad3b631eddd@www.loen.fr>
Date:	Fri, 02 May 2014 14:47:28 +0100
From:	Marc Zyngier <marc.zyngier@....com>
To:	Mj Embd <mj.embd@...il.com>
Cc:	kernelnewbies <kernelnewbies@...nelnewbies.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: Linux Interrupt Context maps to ARM CPSR.mode  = IRQ

On 2014-05-02 13:34, Mj Embd wrote:
> 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.

Well, none of this is completely true.

Process context exists both in USR (process in user mode) and SVC 
(process in kernel mode, executing a syscall for example).

As for interrupts, the processor indeed starts executing the interrupt 
in IRQ mode, but this is a useless complication as far as Linux is 
concerned, and we quickly switch to SVC (see the definition of the 
vector_stub macro in arch/arm/kernel/entry-armv.S).

Hope this helps.

         M.
-- 
Fast, cheap, reliable. Pick two.
--
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/