From: Khalid Aziz <khalid@fc.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: prctl patch for fpu faults
Date: Wed, 10 Oct 2001 22:53:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805326@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805302@msgid-missing>
That sounds interesting. You could use it on init task as David
suggested and set the behavior for all tasks. But how would you
implement it form a user space tool like "prctl". sys_prctl() operates
on the current task only. Are you planning to add another system call?
--
Khalid
Jesse Barnes wrote:
>
> I was thinking of hacking up the 'prctl' tool to take a PID as an
> argument, that way it could set the flags for any task. It would allow
> an initscript to set init's flags, among other things. Would such a
> change qualify as a cleaner solution?
>
> Jesse
>
==================================
Khalid Aziz Linux Systems Operation R&D
(970)898-9214 Hewlett-Packard
khalid@fc.hp.com Fort Collins, CO
next prev parent reply other threads:[~2001-10-10 22:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 23:42 [Linux-ia64] Re: prctl patch for fpu faults David Mosberger
2001-10-08 23:46 ` Jesse Barnes
2001-10-08 23:54 ` David Mosberger
2001-10-08 23:55 ` Jesse Barnes
2001-10-08 23:57 ` Jesse Barnes
2001-10-09 0:11 ` Jesse Barnes
2001-10-09 21:40 ` Jesse Barnes
2001-10-10 13:59 ` Jack Steiner
2001-10-10 14:18 ` n0ano
2001-10-10 16:34 ` Jesse Barnes
2001-10-10 20:18 ` Mallick, Asit K
2001-10-10 20:26 ` David Mosberger
2001-10-10 20:42 ` Keith Fish
2001-10-10 22:27 ` David Mosberger
2001-10-10 22:31 ` Jesse Barnes
2001-10-10 22:51 ` David Mosberger
2001-10-10 22:53 ` Khalid Aziz [this message]
2001-10-10 22:57 ` Jesse Barnes
2001-10-10 23:05 ` David Mosberger
2001-10-11 3:11 ` Mallick, Asit K
2001-10-11 3:21 ` David Mosberger
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=marc-linux-ia64-105590698805326@msgid-missing \
--to=khalid@fc.hp.com \
--cc=linux-ia64@vger.kernel.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