From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: LinuxPPC-dev list <linuxppc-dev@ozlabs.org>,
tglx@linutronix.de, Chris Snook <csnook@redhat.com>,
linux-kernel Kernel <linux-kernel@vger.kernel.org>,
maxk@qualcomm.com
Subject: Re: default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)
Date: Fri, 24 Oct 2008 12:39:58 -0500 [thread overview]
Message-ID: <4902086E.6030900@freescale.com> (raw)
In-Reply-To: <5967704E-0117-46B8-8505-6A002502C38C@kernel.crashing.org>
Kumar Gala wrote:
> So why not just have x86 startup code set irq_default_affinity =
> CPU_MASK_ALL than?
That doesn't really solve the problem, as a user could still manually
set an invalid affinity. The MPIC driver should reduce the affinity
itself to what the hardware can handle.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Chris Snook <csnook@redhat.com>,
LinuxPPC-dev list <linuxppc-dev@ozlabs.org>,
tglx@linutronix.de,
linux-kernel Kernel <linux-kernel@vger.kernel.org>,
maxk@qualcomm.com
Subject: Re: default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)
Date: Fri, 24 Oct 2008 12:39:58 -0500 [thread overview]
Message-ID: <4902086E.6030900@freescale.com> (raw)
In-Reply-To: <5967704E-0117-46B8-8505-6A002502C38C@kernel.crashing.org>
Kumar Gala wrote:
> So why not just have x86 startup code set irq_default_affinity =
> CPU_MASK_ALL than?
That doesn't really solve the problem, as a user could still manually
set an invalid affinity. The MPIC driver should reduce the affinity
itself to what the hardware can handle.
-Scott
next prev parent reply other threads:[~2008-10-24 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 12:45 default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems) Kumar Gala
2008-10-24 12:45 ` Kumar Gala
2008-10-24 15:17 ` Chris Snook
2008-10-24 15:17 ` Chris Snook
2008-10-24 15:39 ` Kumar Gala
2008-10-24 15:39 ` Kumar Gala
2008-10-24 16:09 ` Chris Snook
2008-10-24 16:09 ` Chris Snook
2008-10-24 16:36 ` Kumar Gala
2008-10-24 16:36 ` Kumar Gala
2008-10-24 17:39 ` Scott Wood [this message]
2008-10-24 17:39 ` Scott Wood
2008-10-24 18:18 ` Chris Snook
2008-10-24 18:18 ` Chris Snook
2008-10-24 18:26 ` Scott Wood
2008-10-24 18:26 ` Scott Wood
2008-10-24 17:51 ` Chris Snook
2008-10-24 17:51 ` Chris Snook
2008-10-24 23:18 ` David Miller
2008-10-24 23:18 ` David Miller
2008-11-19 6:43 ` Max Krasnyansky
2008-11-19 6:43 ` Max Krasnyansky
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=4902086E.6030900@freescale.com \
--to=scottwood@freescale.com \
--cc=csnook@redhat.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=maxk@qualcomm.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.