All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-arch@vger.kernel.org
Subject: Re: [RFC PATCH REBASED 2/3] x86: Move fpu_counter into ARCH specific thread_struct
Date: Mon, 23 Sep 2013 10:33:16 +0200	[thread overview]
Message-ID: <20130923083316.GB10891@gmail.com> (raw)
In-Reply-To: <1379398639-27403-3-git-send-email-vgupta@synopsys.com>


* Vineet Gupta <Vineet.Gupta1@synopsys.com> wrote:

> Only a couple of arches (sh/x86) use fpu_counter in task_struct so it
> can be moved out into ARCH specific thread_struct, reducing the size of
> task_struct for other arches.
> 
> Compile tested i386_defconfig + gcc 4.7.3
> 
> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Cc: Suresh Siddha <suresh.b.siddha@intel.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Vincent Palatin <vpalatin@chromium.org>
> Cc: Len Brown <len.brown@intel.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
> Cc: Pekka Riikonen <priikone@iki.fi>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Dave Jones <davej@redhat.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> Cc: linux-kernel@vger.kernel.org
> ---
>  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 +-
>  6 files changed, 19 insertions(+), 10 deletions(-)

Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

  parent reply	other threads:[~2013-09-23  8:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  6:17 [RFC PATCH REBASED 0/3] Move ARCH specific fpu_counter out of task_struct Vineet Gupta
2013-09-17  6:17 ` Vineet Gupta
2013-09-17  6:17 ` [RFC PATCH REBASED 1/3] sh: Move fpu_counter into ARCH specific thread_struct Vineet Gupta
2013-09-17  6:29   ` Vineet Gupta
2013-09-17  6:17   ` Vineet Gupta
2013-09-17  8:00   ` Peter Zijlstra
2013-09-17  8:14     ` Vineet Gupta
2013-09-17  8:25       ` Peter Zijlstra
2013-09-17  8:25         ` Peter Zijlstra
2013-10-01 10:33   ` Vineet Gupta
2013-10-01 10:45     ` Vineet Gupta
2013-10-01 10:33     ` Vineet Gupta
2013-09-17  6:17 ` [RFC PATCH REBASED 2/3] x86: " Vineet Gupta
2013-09-17  6:17   ` Vineet Gupta
2013-09-17 10:34   ` Vineet Gupta
2013-09-23  6:58     ` Vineet Gupta
2013-09-18 18:12   ` Paul Gortmaker
2013-09-18 18:15     ` Paul Gortmaker
2013-09-23  8:33   ` Ingo Molnar [this message]
2013-10-04 11:24     ` Vineet Gupta
2013-09-17  6:17 ` [RFC PATCH REBASED 3/3] sched: Remove ARCH specific fpu_counter from task_struct Vineet Gupta
2013-09-17  6:17   ` Vineet Gupta

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=20130923083316.GB10891@gmail.com \
    --to=mingo@kernel.org \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=mingo@redhat.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 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.