linux-kernel - Re: [PATCH v2] powerpc32: Kexec support for PPC440X chipsets

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:	Thu, 14 Jul 2011 17:40:42 +0200
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	"Suzuki K. Poulose" <suzuki@...ibm.com>
Cc:	Benjammin Herrenschmidt <benh@...nel.crashing.org>,
	Kumar Gala <galak@...nel.crashing.org>,
	Josh Boyer <jwboyer@...ux.vnet.ibm.com>,
	linux ppc dev <linuxppc-dev@...ts.ozlabs.org>,
	kexec <kexec@...ts.infradead.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Vivek Goyal <vgoyal@...hat.com>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [PATCH v2] powerpc32: Kexec support for PPC440X chipsets

* Suzuki K. Poulose | 2011-07-12 12:14:16 [+0530]:

>Changes from V1: Uses a tmp mapping in the other address space to setup
>		 the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
>
>Note: Should we do the same for kernel entry code for PPC44x ?

You have one the kernel mapping. Then you make your temporary mapping
which might be just the one valid TLB entry (after you invalidated the
others). After that you setup multiple mappings to cover 0..2GiB address
space. Since the kernel runs at 0xC.... and you need 0x0.. for the same
memory you end up at some point with two mappings for the same memory.
The reference manual says one should not have two active mappings for
piece of memory. That is why the "other address space" is should be
used.
So I think using this "other address space" for the entry code isn't a
bad idea.

However, I'm fine with this patch.

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