mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dong V Nguyen <dvnguyen@us.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 kernel: Bind interrupt question.
Date: Mon, 10 Nov 2003 15:58:45 -0700	[thread overview]
Message-ID: <OF7D31CE33.45677759-ON87256DDA.007DFB46@us.ibm.com> (raw)





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



             reply	other threads:[~2003-11-10 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 22:58 Dong V Nguyen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-10 22:33 Dong V Nguyen
2003-11-10 22:48 ` Anton Blanchard
2003-11-11 14:40   ` Zwane Mwaikambo
2003-11-11 15:00     ` Zwane Mwaikambo

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=OF7D31CE33.45677759-ON87256DDA.007DFB46@us.ibm.com \
    --to=dvnguyen@us.ibm.com \
    --cc=anton@samba.org \
    --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

Powered by JetHome