From: Paul Jackson <pj@sgi.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Joe Korty <joe.korty@ccur.com>, Andrew Morton <akpm@osdl.org>
Subject: Broken big-endian SMP /proc/irq/prof_cpu_mask (2.6.0-mm1)?
Date: Thu, 8 Jan 2004 05:39:01 -0800 [thread overview]
Message-ID: <20040108053901.70ef9012.pj@sgi.com> (raw)
Are you running 2.6.0-mm1 or later on a big-endian SMP box?
If so, I probably broke your file /proc/irq/prof_cpu_mask file
(and /proc/irq/<pid>/smp_affinity files as well ...).
Could you cat out /proc/irq/prof_cpu_mask for me, if you have
such a box, and tell me if the bytes are backward? Please also
indicate your hardware architecture and number of CPUs, just
so I can be sure I am on track here.
If say you have 4 CPUs, then seeing something in the range of "1" to "f"
would be good news, but seeing some multiple of 1000000 would be bad
news.
For further details, see the lkml thread started yesterday
by joe.korty@ccur.com:
Subject: seperator error in __mask_snprintf_len
If I have broken this as I suspect, I will prepare a patch for Andrew
shortly that fixes it.
Thanks for you assistance.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
reply other threads:[~2004-01-08 13:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040108053901.70ef9012.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).