From: Ralf Baechle <ralf@linux-mips.org>
To: Mark E Mason <mason@broadcom.com>
Cc: Mark Mason <mmason@upwardaccess.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH] When complaining about attempting to set the irq affinity to multiple cpus,
Date: Wed, 23 Sep 2009 22:24:01 +0100 [thread overview]
Message-ID: <20090923212401.GB22516@linux-mips.org> (raw)
In-Reply-To: <BD3F7F1EFBA6D54DB056C4FFA4514008037D6641C8@SJEXCHCCR01.corp.ad.broadcom.com>
On Wed, Sep 23, 2009 at 02:09:34PM -0700, Mark E Mason wrote:
> Did we ever figure out why the kernel was attempting to set the affinity to more than one CPU? The hardware certainly supports doing that (but we're not at the moment).
The hardware semantics is a bit ususual. On Sibyte the hardware will
route an interrupt to all CPUs set in the affinity mask. On most other
systems that I'm aware of it will route the interrupt to only one of
CPUs selected by irq_chip->set_affinity(). We don't want such an
stampede so the Sibyte interrupt code clears all but the lowest set
bit from the set_affinity() argument. Either way, attempting to set
the mask to an arbitrary non-empty set is entirely legal so the warning
itself was a bug and the volume potencially made them a real problem for
a few users.
Ralf
prev parent reply other threads:[~2009-09-23 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 21:13 [PATCH] When complaining about attempting to set the irq affinity to multiple cpus, Mark Mason
2009-09-23 20:50 ` Ralf Baechle
[not found] ` <BD3F7F1EFBA6D54DB056C4FFA4514008037D6641C8@SJEXCHCCR01.corp.ad.broadcom.com>
2009-09-23 21:24 ` Ralf Baechle [this message]
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=20090923212401.GB22516@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mason@broadcom.com \
--cc=mmason@upwardaccess.com \
/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).