From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Anton Blanchard <anton@samba.org>
Cc: Dong V Nguyen <dvnguyen@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 kernel: Bind interrupt question.
Date: Tue, 11 Nov 2003 09:40:42 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0311110939050.8688@montezuma.fsmlabs.com> (raw)
In-Reply-To: <20031110224822.GE930@krispykreme>
On Tue, 11 Nov 2003, Anton Blanchard wrote:
> > Have you seen any problems with interrupt binding on 2.6.0-drv45003 ?
> > I tried this command to bind interrupt, but it does not work:
> > ============================
> > cat /proc/irq/165/smp_affinity
> > ffffffff00000000
> > echo 01 > /proc/irq/165/smp_affinity
> > cat /proc/irq/165/smp_affinity
> > ffffffff00000000
>
> This is probably a ppc64 specific issue, we can continue this on
> linuxppc64-dev@lists.linuxppc.org
>
> > There is nothing changed after binding.
> > One thing I see is it shows 16 digits "ffffffff00000000" on 2.6.0 while
> > only 8 digits in 2.4 .
>
> Its part of the support for > 32way machines, but it looks like its
> broken for some configurations (Im guessing you have CONFIG_NR_CPUS set
> to 32).
There was a fix which went in for something similar on i386 a while back.
next prev parent reply other threads:[~2003-11-11 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 22:33 2.6.0 kernel: Bind interrupt question Dong V Nguyen
2003-11-10 22:46 ` [ltc-interlock] " Dave Hansen
2003-11-10 22:48 ` Anton Blanchard
2003-11-11 14:40 ` Zwane Mwaikambo [this message]
2003-11-11 15:00 ` Zwane Mwaikambo
2003-11-10 22:58 Dong V Nguyen
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=Pine.LNX.4.53.0311110939050.8688@montezuma.fsmlabs.com \
--to=zwane@arm.linux.org.uk \
--cc=anton@samba.org \
--cc=dvnguyen@us.ibm.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).