From: "H. Peter Anvin" <hpa@zytor.com>
To: Joe Korty <joe.korty@ccur.com>
Cc: mingo@elte.hu, tglx@linutronix.de, sdietrich@novell.com,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
jason.baietto@ccur.com
Subject: Re: [PATCH] create /proc/all-interrupts
Date: Thu, 26 Jul 2007 11:56:56 -0700 [thread overview]
Message-ID: <46A8EE78.4040702@zytor.com> (raw)
In-Reply-To: <20070726180522.GA1486@tsunami.ccur.com>
Joe Korty wrote:
> Create /proc/all-interrupts for some architectures.
>
> Create a version of /proc/interrupts that displays _every_
> IRQ vector, not just those that someone thought might be
> interesting, and add an entry in the commentary column
> for those vectors which lacked such a comment.
>
> Rationale: /proc/interrupts is not truly useful unless it
> displays every IRQ vector, not just those somebody thought
> would be interesting. For example, since /proc/interrupts
> does not display the rescheduling interrupt, the occurance
> of rescheduling interrupt floods ends up affecting
> latencies, yet without an entry in /proc/interrupts, it
> is difficult to discern why latencies are being affected.
>
> Rather than modify /proc/interrupts, this patch creates
> a new version of /proc/interrupts, on the off-chance
> that adding new lines to /proc/interrupts, and appending
> new fields to the end of old lines, might break some
> longstanding script. However, these kinds of changes
> traditionally do not affect scripts, so it might be
> reasonable to fold /proc/all-interrupts back into
> /proc/interrupts.
I think that would be the right thing to do. We have added things to
/proc/interrupts in the past.
-hpa
next prev parent reply other threads:[~2007-07-26 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 18:05 [PATCH] create /proc/all-interrupts Joe Korty
2007-07-26 18:56 ` H. Peter Anvin [this message]
2007-07-30 17:33 ` Sven-Thorsten Dietrich
2007-07-30 19:32 ` Andrew Morton
2007-07-30 19:42 ` Joe Korty
2007-07-31 0:17 ` [PATCH] expand /proc/interrupts to include missing vectors, v2 Joe Korty
2007-07-31 0:48 ` Gabriel C
2007-07-31 1:48 ` Andrew Morton
2007-07-31 14:19 ` [PATCH] expand /proc/interrupts to include missing vectors, v3 Joe Korty
2007-07-31 17:02 ` Andi Kleen
2007-07-31 20:29 ` Joe Korty
2007-07-31 21:06 ` [PATCH] expand /proc/interrupts to include missing vectors, v4 Joe Korty
2007-08-01 13:29 ` [PATCH] expand /proc/interrupts to include missing vectors, v2 Lennart Sorensen
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=46A8EE78.4040702@zytor.com \
--to=hpa@zytor.com \
--cc=jason.baietto@ccur.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.de \
/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