| 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: <565DE289.2000105@arm.com> Date: Tue, 1 Dec 2015 18:10:17 +0000 From: "Suzuki K. Poulose" <Suzuki.Poulose@....com> To: Mark Rutland <mark.rutland@....com> Cc: linux-arm-kernel@...ts.infradead.org, marc.zyngier@....com, linux-kernel@...r.kernel.org, will.deacon@....com, catalin.marinas@....com Subject: Re: [PATCH v2 2/6] arm64: Move kill_cpu_early to smp.c On 01/12/15 17:52, Mark Rutland wrote: > On Tue, Dec 01, 2015 at 05:38:54PM +0000, Suzuki K. Poulose wrote: >> On 01/12/15 16:31, Mark Rutland wrote: > > [...] > >>> We need stuck-in-the-kernel flag to account for CPUs which didn't manage >>> to turn the MMU on (which are either in the spin-table, or failed when >>> they were individually onlined). >> >> Did you mean to say "turn the MMU off" ? > > No, I mean CPUs which were unable to turn the MMU on in the first place. > Perhaps they entered the spin-table but were never individually onlined, > perhaps they didn't support the kernel page size, etc. > > When CPUs exit the kernel via PSCI they never switch the MMU off within > the kernel. OK. So the flag will also be used for CPUs which are stuck-in-the-kernel with MMU turned on. e.g, a CPU (using spin-table) we try to bring down in kill_cpu_early(). Correct ? Thanks Suzuki -- 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