linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Ingo Molnar <mingo@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Paul Mundt <paul.mundt@gmail.com>,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3]  Move ARCH specific fpu_counter out of task_struct
Date: Thu, 10 Oct 2013 18:32:41 +0530	[thread overview]
Message-ID: <5256A571.3070600@synopsys.com> (raw)
In-Reply-To: <1381218389-16585-1-git-send-email-vgupta@synopsys.com>

On 10/08/2013 01:16 PM, Vineet Gupta wrote:
> Hi,
> 
> When debugging a ARC SMP 3.11 build failure due to a ST insn dealing with
> task_struct.thread going out of range, I spotted @fpu_counter in task_struct
> which only SH/x86 happen to use, and can be easily moved out into corresponding
> ARCH specific thread_struct. This saves 4 bytes per task_struct instantiated,
> for all the other 18 arches.
> 
> While the change is relatively strightforward, I've failed to connect with
> SH arch folks / Paul Mundt, latter's SH email keeps bouncing back.
> Hence I'm taking the liberty to use his alternate email (as listed on his
> github page) and I appologize in advance if this causes any inconvenience.
> 
> Changes in v2:
> - Rabased to 3.12-rc4
> - Added ACK from Ingo on patch 2/3
> 
> Version 1 can be found here:
> https://lkml.org/lkml/2013/9/17/49
> 
> Thx,
> -Vineet
> 
> 
> Vineet Gupta (3):
>   sh: Move fpu_counter into ARCH specific thread_struct
>   x86: Move fpu_counter into ARCH specific thread_struct
>   sched: Remove ARCH specific fpu_counter from task_struct
> 
>  arch/sh/include/asm/fpu.h           |  2 +-
>  arch/sh/include/asm/processor_32.h  | 10 ++++++++++
>  arch/sh/include/asm/processor_64.h  | 10 ++++++++++
>  arch/sh/kernel/cpu/fpu.c            |  2 +-
>  arch/sh/kernel/process_32.c         |  6 +++---
>  arch/x86/include/asm/fpu-internal.h | 10 +++++-----
>  arch/x86/include/asm/processor.h    |  9 +++++++++
>  arch/x86/kernel/i387.c              |  2 +-
>  arch/x86/kernel/process_32.c        |  4 ++--
>  arch/x86/kernel/process_64.c        |  2 +-
>  arch/x86/kernel/traps.c             |  2 +-
>  include/linux/sched.h               |  9 ---------
>  12 files changed, 44 insertions(+), 24 deletions(-)
> 

Ingo, Andrew - do you think this series can be merged for 3.13. Is there anything
else I need to do here.

-Vineet

      parent reply	other threads:[~2013-10-10 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  7:46 [PATCH v2 0/3] Move ARCH specific fpu_counter out of task_struct Vineet Gupta
2013-10-08  7:46 ` [PATCH v2 1/3] sh: Move fpu_counter into ARCH specific thread_struct Vineet Gupta
2013-10-08  7:46   ` Vineet Gupta
2013-10-08  7:46 ` [PATCH v2 3/3] sched: Remove ARCH specific fpu_counter from task_struct Vineet Gupta
2013-10-08  7:46   ` Vineet Gupta
2013-10-08  8:02   ` Ingo Molnar
2013-10-08  8:02     ` Ingo Molnar
2013-10-08 20:14 ` [PATCH v2 0/3] Move ARCH specific fpu_counter out of task_struct Andrew Morton
2013-10-09  5:55   ` Vineet Gupta
2013-10-09  5:39 ` [PATCH v2 2/3] x86: Move fpu_counter into ARCH specific thread_struct Vineet Gupta
2013-10-10 13:02 ` Vineet Gupta [this message]

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=5256A571.3070600@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.mundt@gmail.com \
    --cc=peterz@infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).