linux-kernel - Re: [PATCH 1/3] x86: Add 'percpu_read_stable()' interface for cacheable accesses

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: <20090803061608.GA21564@elte.hu>
Date:	Mon, 3 Aug 2009 08:16:08 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Tejun Heo <tj@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] x86: Add 'percpu_read_stable()' interface for
	cacheable accesses


* H. Peter Anvin <hpa@...or.com> wrote:

> Ingo Molnar wrote:
>> * Tejun Heo <tj@...nel.org> wrote:
>>
>>> H. Peter Anvin wrote:
>>>> Tejun Heo wrote:
>>>>> Ingo, these patches might as well go through x86 tree.  If you think
>>>>> that would be better, please let me know.
>>>>>
>>>> Makes sense to me.  I'll pull them into x86/percpu.
>>> Cool, dropping from my tree then.
>>
>> We can delegate the contents of x86/percpu to you (the topic branch  
>> contains no patches over mainline right now) - i.e. we can pull those 
>> bits from you and they could also be in your tree to keep your testing 
>> & integration consistent.
>>
>
> I just pushed out these branches into tip:x86/percpu.

Thanks! (I'll test it and push it out into -tip:master.)

> [...]  We can zap those if there is a tree head you'd rather use.

It's fine this way i think.

Tejun: in the future you might want to offer up new x86-only bits 
based on tip:x86/percpu as git pulls.

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