| 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
| ||
|
Message-Id: <201207200828.13128.arnd@arndb.de> Date: Fri, 20 Jul 2012 08:28:12 +0000 From: Arnd Bergmann <arnd@...db.de> To: Jon Masters <jonathan@...masters.org> Cc: Christopher Covington <cov@...eaurora.org>, Catalin Marinas <catalin.marinas@....com>, linux-kernel@...r.kernel.org, Will Deacon <will.deacon@....com> Subject: Re: [PATCH 08/36] AArch64: Kernel booting and initialisation On Friday 20 July 2012, Jon Masters wrote: > > I think it would be best to list the technical limitations, from the > > kernel's perspective, of the unsupported exception levels and the > > advantages of the supported exception levels here. If you want to guide > > system builders towards EL2, I think it'd be more convincing to document > > the relevant technical aspects (perhaps KVM needs facilities only > > available in EL2) than just providing an unexplained requirement. > > Unless you enter at EL2 you can never install a hypervisor. That's the > reason for the requirement for generally entering at EL2 when possible. How do nested hypervisors work in this scenario? Does the first-level hypervisor (counting from most priviledged) provide a guest that starts in an emulated EL2 state, or is this done differently? Arnd -- 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