From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] fpswa patch(es)
Date: Fri, 14 Dec 2001 22:35:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805697@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805632@msgid-missing>
>>>>> On Thu, 06 Dec 2001 15:44:19 -0600, Brian Sumner <bls@sgi.com> said:
Brian> The following patch is really 3 patches rolled into one.
Brian> I've found all 3 useful during application porting and debugging.
I see that this could be useful for certain debugging/hacking
activities, but I don't think it's generally useful enough to warrant
more kernel bloat. I'd rather keep this patch separate from the
official tree. On a side note, it seems to there are some race
conditions in incrementing the counters.
We could include more info in /proc/cpuinfo. E.g., we could include a
count of the total number of fpswa and unaligned faults (on a per CPU
basis). (Alpha Linux does this, if you want to look for an example).
If someone sent me a patch to do that, I'd be much more inclined to
apply it.
--david
prev parent reply other threads:[~2001-12-14 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 21:44 [Linux-ia64] fpswa patch(es) Brian Sumner
2001-12-14 22:35 ` David Mosberger [this message]
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-105590698805697@msgid-missing \
--to=davidm@hpl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.