All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	hpa@zytor.com, tglx@linutronix.de, andi@firstfloor.org,
	hch@infradead.org, linux-kernel@vger.kernel.org,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [patch 1/2] x86, fpu: split FPU state from task struct - v5
Date: Tue, 11 Mar 2008 13:22:40 -0700	[thread overview]
Message-ID: <20080311202239.GF15909@linux-os.sc.intel.com> (raw)
In-Reply-To: <20080311101126.GY25110@elte.hu>

On Tue, Mar 11, 2008 at 11:11:26AM +0100, Ingo Molnar wrote:
> 
> * Alexey Dobriyan <adobriyan@gmail.com> wrote:
> 
> > On 3/11/08, Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > * Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > >
> > > > > -	extern void __bad_fxsave_alignment(void);
> > > > > -
> > > > > -	if (offsetof(struct task_struct, thread.i387.fxsave) & 15)
> > > > > -	__bad_fxsave_alignment();
> > > >
> > > > I think removal of such checks needs giving necessary alignment to
> > > > cache. Previously it worked because of __aligned((16)) and
> > > > L1_CACHE_SHIFT combo.
> > >
> > > it's still checked, just elsewhere:
> > >
> > > > + WARN_ON((unsigned long)dst->thread.xstate & 15);
> > >
> > > i'd not expect us to ever align worse than 16 bytes in the future
> > 
> > But sysfs tells me alignment of "xstate" is 8 now. Object size is 512 
> > which is masking it.
> 
> ok - you are right, that needs to be solved then. (object size could 
> change anytime someone adds a few fields for debugging or whatever)

Which sysfs file are we referring here?

  reply	other threads:[~2008-03-11 20:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 22:28 [patch 1/2] x86, fpu: split FPU state from task struct - v5 Suresh Siddha
2008-03-10 22:28 ` [patch 2/2] x86, fpu: lazy allocation of FPU area " Suresh Siddha
2008-03-11  9:08   ` Ingo Molnar
2008-03-11 20:57     ` Suresh Siddha
2008-03-10 22:56 ` [patch 1/2] x86, fpu: split FPU state from task struct " Andi Kleen
2008-03-11  5:07 ` Alexey Dobriyan
2008-03-11  8:35   ` Ingo Molnar
2008-03-11 10:09     ` Alexey Dobriyan
2008-03-11 10:11       ` Ingo Molnar
2008-03-11 20:22         ` Suresh Siddha [this message]
2008-03-11 20:19   ` Suresh Siddha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080311202239.GF15909@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=adobriyan@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.