linux-kernel - Re: [PATCH 00/36] AArch64 Linux kernel port

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: <5003CFBA.3060108@redhat.com>
Date:	Mon, 16 Jul 2012 11:24:26 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Catalin Marinas <catalin.marinas@....com>
CC:	Pavel Machek <pavel@....cz>, Ingo Molnar <mingo@...nel.org>,
	Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Russell King <linux@....linux.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 00/36] AArch64 Linux kernel port

On 07/15/2012 03:16 PM, Catalin Marinas wrote:
> 
> The AArch32 execution mode is optional, so it depends on the actual CPU
> implementation (while AArch64 is mandatory). If the implementation
> supports it, the most likely scenario for AArch32 at kernel level is in
> virtual machines or the secure OS. I'll explain below why.
> 
> The exception (or privilege) levels on an ARMv8 architecture look like
> this:
> 
> Secure World	Normal World
> +-----+
> | EL3 |				- Secure monitor
> +-----+
> 		+-----+
> 		| EL2 |		- Hypervisor (normal world only)
> 		+-----+
> +-----+		+-----+
> | EL1 |		| EL1 |		- OS kernel (secure or normal)
> +-----+		+-----+
> +-----+		+-----+
> | EL0 |		| EL0 |		- User apps (secure or normal)
> +-----+		+-----+

Can the same kernel image run in both EL1 and EL2?  I noticed some .if
ELs in the assembler files.  I guess they could be compiled multiple
times and the correct version chosen at runtime, or patched up like x86
does with alternative().

One of the advantages kvm has to Linux distributors is that the same
kernel image can be used the hypervisor, guest, and bare metal.  I'd
like to preserve that for arm64.

-- 
error compiling committee.c: too many arguments to function


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