linux-kernel - Re: [PATCH 0/4 v2] [GIT PULL][v3.2] x86: Consolidate 32 and 64 bit thread

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: <4E3CA12D.1030408@zytor.com>
Date:	Fri, 05 Aug 2011 19:04:29 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Brian Gerst <brgerst@...il.com>
Subject: Re: [PATCH 0/4 v2] [GIT PULL][v3.2] x86: Consolidate 32 and 64 bit
 thread_info

On 08/05/2011 06:11 PM, Steven Rostedt wrote:
> 
> Thomas, Ingo, and Peter(s),
> 
> On IRC, Peter Zijlstra mentioned to me the difference between
> 32bit and 64bit x86 on how thread_info is handled with interrupts.
> I mentioned that they should be more the same, and Peter agreed.
> 
> I decided to do so, and ended up with the following patches.
> I marked this for v3.2 as it should be tested a bit before going into
> mainline. I've ran several configs on it, but more testing should be done.
> 
> Some of the patches are clean ups, but the main ones are patch 3 and 4
> that do the work to convert 32bit of thread_info to be more like
> the 64bit.
> 

Hi Steven,

I'd like to wait until the merge window is over with pulling in 3.2
material ... nothing personal or technical, just to simplify management.

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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