From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: prctl patch for fpu faults
Date: Mon, 08 Oct 2001 23:46:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805303@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805302@msgid-missing>
The rate limiting stuff really limits the usefulness of the code I think.
If you want to get notified of faults, you probably want all of them, and
you want to know the ip for each occurence. If you just get some, it
doesn't help you debug your code. Maybe there could be a NOTIFY option or
something that would get printed only once if the app generated a fault?
Thanks,
Jesse
On Mon, 8 Oct 2001, David Mosberger wrote:
> >>>>> On Mon, 8 Oct 2001 14:57:00 -0700, Jesse Barnes <jbarnes@sgi.com> said:
>
> Jesse> I think you mentioned awhile ago that a patch like this might be
> Jesse> welcome. Well, here it is. It's diff'd against 2.4.10 with the ia64
> Jesse> patch. Please let me know if you find problems with it.
>
> The patch looks mostly good to me. However, why did you get rid of
> the rate limiting code? I think we still want that.
>
> --david
>
next prev parent reply other threads:[~2001-10-08 23:46 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 [this message]
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
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-105590698805303@msgid-missing \
--to=jbarnes@sgi.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