| 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: Sun, 17 May 2009 00:16:40 +0900 From: Tejun Heo <tj@...nel.org> To: suresh.b.siddha@...el.com CC: "JBeulich@...ell.com" <JBeulich@...ell.com>, "andi@...stfloor.org" <andi@...stfloor.org>, "mingo@...e.hu" <mingo@...e.hu>, "linux-kernel-owner@...r.kernel.org" <linux-kernel-owner@...r.kernel.org>, "hpa@...or.com" <hpa@...or.com>, "tglx@...utronix.de" <tglx@...utronix.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [GIT PATCH] x86,percpu: fix pageattr handling with remap allocator Hello, Suresh. Suresh Siddha wrote: > Tejun, Can you please educate me why we need to map this first > percpu chunk (which is pre-allocated during boot and is physically > contiguous) into vmalloc area? To make areas for each cpu congruent such that the address offset of a percpu symbol for CPU N is always the same from the address for CPU 0. > Perhaps even for the other dynamically allocated secondary chunks? > (as far as I can see, all the chunk allocations seems to be > physically contiguous and later mapped into vmalloc area).. > > That should simplify these things quite a bit(atleast for first > percpu chunk). I am missing something obvious I guess. Hmm... Sorry I don't really follow. Can you please elaborate the question? thanks. -- tejun -- 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