* 2.6.0 kernel: Bind interrupt question.
@ 2003-11-10 22:33 Dong V Nguyen
2003-11-10 22:46 ` [ltc-interlock] " Dave Hansen
2003-11-10 22:48 ` Anton Blanchard
0 siblings, 2 replies; 6+ messages in thread
From: Dong V Nguyen @ 2003-11-10 22:33 UTC (permalink / raw)
To: linux-kernel, LTC interlock between development, performance,
test, infrastructure, etc.
Cc: LTC interlock between development, performance, test,
infrastructure, etc.
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
===========================
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 .
Do I need any special ways to bind interrupt ?
Thanks.,
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ltc-interlock] 2.6.0 kernel: Bind interrupt question.
2003-11-10 22:33 2.6.0 kernel: Bind interrupt question Dong V Nguyen
@ 2003-11-10 22:46 ` Dave Hansen
2003-11-10 22:48 ` Anton Blanchard
1 sibling, 0 replies; 6+ messages in thread
From: Dave Hansen @ 2003-11-10 22:46 UTC (permalink / raw)
To: Dong; +Cc: Linux Kernel Mailing List, Anton Blanchard
On Mon, 2003-11-10 at 14:33, Dong V Nguyen 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
> ===========================
> 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 .
> Do I need any special ways to bind interrupt ?
Is your architecure broken?
Works fine on x86:
root@foo:/proc/irq# cat 17/smp_affinity
ffffffff
root@foo:/proc/irq# echo 1 > 17/smp_affinity
root@foo:/proc/irq# cat 17/smp_affinity
00010000
--
Dave Hansen
haveblue@us.ibm.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.0 kernel: Bind interrupt question.
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
1 sibling, 1 reply; 6+ messages in thread
From: Anton Blanchard @ 2003-11-10 22:48 UTC (permalink / raw)
To: Dong V Nguyen; +Cc: linux-kernel
Hi,
> 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).
Anton
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.0 kernel: Bind interrupt question.
2003-11-10 22:48 ` Anton Blanchard
@ 2003-11-11 14:40 ` Zwane Mwaikambo
2003-11-11 15:00 ` Zwane Mwaikambo
0 siblings, 1 reply; 6+ messages in thread
From: Zwane Mwaikambo @ 2003-11-11 14:40 UTC (permalink / raw)
To: Anton Blanchard; +Cc: Dong V Nguyen, linux-kernel
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.0 kernel: Bind interrupt question.
2003-11-11 14:40 ` Zwane Mwaikambo
@ 2003-11-11 15:00 ` Zwane Mwaikambo
0 siblings, 0 replies; 6+ messages in thread
From: Zwane Mwaikambo @ 2003-11-11 15:00 UTC (permalink / raw)
To: Anton Blanchard; +Cc: Dong V Nguyen, linux-kernel
On Tue, 11 Nov 2003, Zwane Mwaikambo wrote:
> > 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.
And here is a link; PPC64 appears to have the older version
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=uoUN.V9.15%40gated-at.bofh.it&rnum=1&prev=/groups%3Fq%3Dsmp_affinity%2Bi386%2BZwane%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3DuoUN.V9.15%2540gated-at.bofh.it%26rnum%3D1
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.0 kernel: Bind interrupt question.
@ 2003-11-10 22:58 Dong V Nguyen
0 siblings, 0 replies; 6+ messages in thread
From: Dong V Nguyen @ 2003-11-10 22:58 UTC (permalink / raw)
To: Anton Blanchard; +Cc: linux-kernel
Anton,
You're right. By defaut, the CONFIG_NR_CPUS is set to 32.
I need to reset that and rebuild the kernel to try the interrupt binding
again.
Thanks,
Anton Blanchard <anton@samba.org> on 11/10/2003 04:48:22 PM
To: Dong V Nguyen/Austin/IBM@IBMUS
cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 kernel: Bind interrupt question.
Hi,
> 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).
Anton
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-11-11 15:01 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2003-11-11 15:00 ` Zwane Mwaikambo
2003-11-10 22:58 Dong V Nguyen
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).