linux-kernel - Re: [GIT PATCH] x86,percpu: fix pageattr handling with remap allocator

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]

Message-ID: <4A120B47.8060200@kernel.org>
Date:	Tue, 19 May 2009 10:28:39 +0900
From:	Tejun Heo <tj@...nel.org>
To:	suresh.b.siddha@...el.com
CC:	"H. Peter Anvin" <hpa@...or.com>,
	"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>,
	"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:
> This %gs:absolute type accesses are for static percpu data.
> 
> But what I was referring to is the dynamic percpu data(accessed through
> per_cpu_ptr()). Instead of combining some part of the dynamic percpu
> data into  the static percpu data(first percpu chunk), we can use
> different chunks for dynamic percpu data and governed by a different
> per_cpu_dynamic_offset[NR_CPUS] array.
> 
> Then we can use large-page kernel direct mappings for static percpu data
> (or %gs:offset) and small-page vmalloc mappings for dynamic percpu data.

Hmmm... I can't really follow what you're suggesting.  Can you please
explain it in more detailed way?

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/