public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: eranian@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	ak@suse.de, tony.luck@intel.com
Subject: Re: is TIF_NOTIFY_RESUME used?
Date: Tue, 22 May 2007 09:02:10 -0700	[thread overview]
Message-ID: <20070522090210.1388ff3e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070522124713.GB27428@frankl.hpl.hp.com>

On Tue, 22 May 2007 05:47:13 -0700
Stephane Eranian <eranian@hpl.hp.com> wrote:

> Hello,
> 
> For perfmon, we need a couple of TIF bits. It seems that with 2.6.22-rc2
> there is now a TIF_RESTORE_SIGMASK which uses the last remaining bit in the
> first 7 bits of the thread flag. Many architectures, including IA-64, rely
> on the fact that some of the TIF flags (TIF_ALL_WORKMASK or TIF_ALL_WORK)
> tested on kernel exit reside in the low 8-bit or 7-bit because they use
> instructions (such as add r1=imm8,r2 on IA-64) which operate on 8 or 7 bit
> immediate.
> 
> On IA-64, adding that one perfmon flag (as bit 7) would cause some
> restructuring in the kernel exit path but also in all the lightweight syscall
> handlers.
> 
> I looked at all the low order TIF flags and found that TIF_NOTIFY_RESUME 
> was never set nor used anywhere in any architecture. Is that really the case?
> 
> If so, we could get rid of it and free up one low-order TIF bit.
> 

My grepping argees with yours.  The only place where TIF_NOTIFY_RESUME gets
altered is in ./arch/ia64/kernel/perfmon.c.

  reply	other threads:[~2007-05-22 16:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 12:47 is TIF_NOTIFY_RESUME used? Stephane Eranian
2007-05-22 16:02 ` Andrew Morton [this message]
2007-05-22 16:07   ` Stephane Eranian
2007-05-22 16:15     ` Andrew Morton
2007-05-22 22:51       ` Stephane Eranian
2007-05-22 23:02         ` Andrew Morton
2007-05-23  9:57           ` [PATCH] remove unused TIF_NOTIFY_RESUME flag Stephane Eranian
2007-05-22 18:20   ` [PATCH 1/2] Define new percpu interface for shared data -- version 3 Fenghua Yu
2007-05-23 17:49     ` Andrew Morton
2007-05-23 18:26       ` Yu, Fenghua
2007-05-23 18:57         ` Ravikiran G Thirumalai
2007-05-23 19:09           ` Yu, Fenghua
2007-05-23 19:20             ` Ravikiran G Thirumalai
2007-05-23 19:31               ` Andrew Morton
2007-05-23 21:13                 ` Yu, Fenghua
2007-05-25  9:43                   ` Russell King
2007-05-25 15:24                     ` Yu, Fenghua
2007-05-24  9:03           ` Martin Schwidefsky
2007-05-24 10:16             ` Ravikiran G Thirumalai

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=20070522090210.1388ff3e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ak@suse.de \
    --cc=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /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