public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-s390@vger.kernel.org, tony.luck@intel.com,
	linux-ia64@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86 TS_RESTORE_SIGMASK
Date: Mon, 31 Mar 2008 15:01:06 +0200	[thread overview]
Message-ID: <20080331130106.GA15198@elte.hu> (raw)
In-Reply-To: <20080329031451.D2E1226FA1D@magilla.localdomain>


* Roland McGrath <roland@redhat.com> wrote:

> Replace TIF_RESTORE_SIGMASK with TS_RESTORE_SIGMASK and define our own 
> set_restore_sigmask() function.  This saves the costly SMP-safe 
> set_bit operation, which we do not need for the sigmask flag since 
> TIF_SIGPENDING always has to be set too.
> 
> Signed-off-by: Roland McGrath <roland@redhat.com>
> ---
>  arch/x86/ia32/ia32_signal.c      |    2 +-
>  arch/x86/kernel/signal_32.c      |   19 ++++++++++---------
>  arch/x86/kernel/signal_64.c      |   16 +++++++++-------
>  include/asm-x86/thread_info_32.h |   13 +++++++++++--
>  include/asm-x86/thread_info_64.h |   13 +++++++++++--
>  5 files changed, 42 insertions(+), 21 deletions(-)

the x86 bits look nice - but i guess this all wants to go into 2.6.26 
via -mm (or linux-next), due to its cross-arch nature?

	Ingo

  reply	other threads:[~2008-03-31 13:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  0:12 [PATCH 1/4] set_restore_sigmask Roland McGrath
2008-03-29  0:13 ` [PATCH 2/4] set_restore_sigmask TIF_SIGPENDING Roland McGrath
2008-03-29  0:53   ` Linus Torvalds
2008-03-29  2:24     ` Roland McGrath
2008-03-29  2:52       ` Linus Torvalds
2008-03-29  3:12         ` Roland McGrath
2008-03-29  3:11       ` [PATCH 1/2] HAVE_SET_RESTORE_SIGMASK Roland McGrath
2008-04-09 11:45         ` David Woodhouse
2008-04-10 20:32           ` Russell King
2008-04-11 13:40             ` David Woodhouse
2008-03-29  3:14       ` Roland McGrath
2008-03-29  3:14         ` [PATCH 2/2] x86 TS_RESTORE_SIGMASK Roland McGrath
2008-03-31 13:01           ` Ingo Molnar [this message]
2008-03-31 19:30             ` Roland McGrath
2008-03-30 10:53     ` [PATCH 2/4] set_restore_sigmask TIF_SIGPENDING Paul Mackerras
2008-04-08 11:35     ` Oleg Nesterov
2008-04-08 14:53       ` Linus Torvalds
2008-04-08 19:51       ` Roland McGrath
2008-04-09 11:16       ` David Woodhouse
2008-04-09 11:39         ` Oleg Nesterov
2008-04-09 12:57           ` Petr Tesarik
2008-04-09 16:14           ` David Woodhouse
2008-04-09 16:22             ` Oleg Nesterov
2008-04-09 18:40               ` David Woodhouse
2008-03-29  0:14 ` [PATCH 3/4] s390 renumber TIF_RESTORE_SIGMASK Roland McGrath
2008-03-31  7:53   ` Martin Schwidefsky
2008-03-29  0:14 ` [PATCH 4/4] ia64 " Roland McGrath

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=20080331130106.GA15198@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.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