From mboxrd@z Thu Jan 1 00:00:00 1970 From: saeed.bishara@gmail.com (saeed bishara) Date: Mon, 7 Feb 2011 16:27:34 +0200 Subject: [PATCH v3 2/5] ARM: pm: add generic CPU suspend/resume support In-Reply-To: <20110207141734.GG31929@n2100.arm.linux.org.uk> References: <20110206191117.GA17808@n2100.arm.linux.org.uk> <20110207120103.GC31929@n2100.arm.linux.org.uk> <20110207121052.GD31929@n2100.arm.linux.org.uk> <20110207133457.GE31929@n2100.arm.linux.org.uk> <20110207141734.GG31929@n2100.arm.linux.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > As I've said, there's not much other choice here. ?We _have_ to have an > identity mapping in place to bring the MMU back online, or we'll crash. > That's non-optional. ?So if this is a problem for cpuidle, cpuidle needs > to ensure that a page table switch has happened prior to the CPU going > down which _can_ be safely modified. I fully agree with you, but what I was suggesting is to create temporary identity page table at boot time, the resume code will load that page table (Context ID will be loaded with unique ASID), enable mmu, then the original page table and Context ID will be restored. saeed