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
| ||
|
Date: Wed, 7 Mar 2012 14:08:11 -0800 From: Greg KH <gregkh@...uxfoundation.org> To: John Stultz <john.stultz@...aro.org> Cc: lkml <linux-kernel@...r.kernel.org>, Colin Cross <ccross@...roid.com>, Android Kernel Team <kernel-team@...roid.com> Subject: Re: [PATCH 08/13] android: persistent_ram: handle reserving and mapping memory On Wed, Mar 07, 2012 at 01:58:18PM -0800, John Stultz wrote: > From: Colin Cross <ccross@...roid.com> > > Replace the ioremapped memory passed in from the drivers with > a memblock_reserve and vmap. Adds a new function, > persistent_ram_early_init, designed to be called from the machine > init_early callback, that calls memblock_remove and saves the > provided persistent ram area layout. > > Drivers only pass in their struct device * and ecc settings. > Locating and mapping the memory is now handled entirely within > persistent_ram. > > Also, convert ram_console to the new persistent_ram_init > parameters that only take a struct device * and ecc settings. > > CC: Greg KH <gregkh@...uxfoundation.org> > CC: Android Kernel Team <kernel-team@...roid.com> > Change-Id: Ibc87ec27b70ed1c928eaa487503469e199973058 > Change-Id: I12b018381a2ed5965a8a4b0da40c3e640f92b6cf > Signed-off-by: Colin Cross <ccross@...roid.com> > [jstultz: Fix pr_info casting issues on 64bit, folded two > patches as the build breaks if they are apart. Also replaced > phys_to_page() w/ pfn_to_page(addr>>PAGE_SHIFT), as phys_to_page > is only on a few arches.] Please put your comments above the signed-off-by area, it makes it easier on tools that parse this area. thanks, greg k-h -- 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