From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ia64@vger.kernel.org, Stephane Eranian <eranian@hpl.hp.com>,
ak@suse.de, akpm@linux-foundation.org, tony.luck@intel.com
Subject: is TIF_NOTIFY_RESUME used?
Date: Tue, 22 May 2007 12:47:13 +0000 [thread overview]
Message-ID: <20070522124713.GB27428@frankl.hpl.hp.com> (raw)
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.
Thanks.
--
-Stephane
next reply other threads:[~2007-05-22 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 12:47 Stephane Eranian [this message]
2007-05-22 16:02 ` is TIF_NOTIFY_RESUME used? Andrew Morton
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-07-30 9:30 ` [PATCH] remove unused TIF_NOTIFY_RESUME (take 2) Stephane Eranian
2007-07-30 17:21 ` Andrew Morton
2007-07-30 17:42 ` Stephane Eranian
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=20070522124713.GB27428@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--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