linux-kernel - Re: [PATCH 09/30] x86_64: ifdef out struct 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] [day] [month] [year] [list]

Message-ID: <20090410111733.GA3311@x200.localdomain>
Date:	Fri, 10 Apr 2009 15:17:33 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Matt Helsley <matthltc@...ibm.com>, Tejun Heo <tj@...nel.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	akpm@...ux-foundation.org, containers@...ts.linux-foundation.org,
	xemul@...allels.com, linux-kernel@...r.kernel.org,
	dave@...ux.vnet.ibm.com, hch@...radead.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH 09/30] x86_64: ifdef out struct thread_struct::ip

On Fri, Apr 10, 2009 at 11:19:31AM +0200, Ingo Molnar wrote:
> 
> * Matt Helsley <matthltc@...ibm.com> wrote:
> 
> > On Fri, Apr 10, 2009 at 06:35:22AM +0400, Alexey Dobriyan wrote:
> > > struct thread_struct::ip isn't used on x86_64, struct pt_regs::ip is used
> > > instead. 
> > > 
> > > kgdb should be reading 0, but I can't check it.
> > > 
> > > Signed-off-by: Alexey Dobriyan <adobriyan@...il.com>
> > > ---
> > > 
> > >  arch/x86/include/asm/processor.h |    2 ++
> > >  arch/x86/kernel/kgdb.c           |    2 +-
> > >  2 files changed, 3 insertions(+), 1 deletion(-)
> > > 
> > > --- a/arch/x86/include/asm/processor.h
> > > +++ b/arch/x86/include/asm/processor.h
> > > @@ -421,7 +421,9 @@ struct thread_struct {
> > >  	unsigned short		fsindex;
> > >  	unsigned short		gsindex;
> > >  #endif
> > > +#ifdef CONFIG_X86_32
> > >  	unsigned long		ip;
> > > +#endif
> > >  #ifdef CONFIG_X86_64
> > >  	unsigned long		fs;
> > >  #endif
> > 
> > Do these make struct thread_struct behave better in cachelines 
> > (smaller, less aliasing)? Can we really fit more in the slab du 
> > jour?
> > 
> > Otherwise it seems like we're littering these structs with #ifdefs 
> > and not really saving anything. [...]
> 
> Removing fields always saves memory (even if it does not show up 
> currently due to allocators cache-aligning sizes).
> 
> But the #ifdef ugliness is a real worry.

You should have thought about it when i386/x86_64 unification was
introduced.

pagefault code was full of ifdefs (it's less now), and this is trivial
ifdef in a header.

> > [...] If these #ifdefs don't save any 
> > space why not just put in a comment:
> > 
> > >  	unsigned long		ip; /* Used only on i386 */
> 
> Yes.
> 
> > Or maybe even:
> > 
> > 	union {
> > 	  	unsigned long		ip; /* Used only on i386 */
> > 	  	unsigned long		fs; /* Used only on x86_64 */
> > 	};
> 
> Maybe. If this ever gets misunderstood somewhere in platform code we 
> will get ugly failure modes and zero compiler help.
--
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/