From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, torvalds@osdl.org, maxk@qualcomm.com,
tglx@linutronix.de, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] genirq: Set initial default irq affinity to just CPU0
Date: Tue, 28 Oct 2008 07:27:16 +1100 [thread overview]
Message-ID: <1225139236.8004.21.camel@pasglop> (raw)
In-Reply-To: <8440180C-A3B1-4436-9CDF-C6BA9A01F8CD@kernel.crashing.org>
On Mon, 2008-10-27 at 08:43 -0500, Kumar Gala wrote:
>
> While we have the comment the code appears not to really follow it.
> We appear to write 1 << hard_smp_processor_id().
That code is called by each CPU that gets onlined and OR's it's
bit in the mask.
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: David Miller <davem@davemloft.net>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, torvalds@osdl.org, maxk@qualcomm.com,
tglx@linutronix.de
Subject: Re: [PATCH] genirq: Set initial default irq affinity to just CPU0
Date: Tue, 28 Oct 2008 07:27:16 +1100 [thread overview]
Message-ID: <1225139236.8004.21.camel@pasglop> (raw)
In-Reply-To: <8440180C-A3B1-4436-9CDF-C6BA9A01F8CD@kernel.crashing.org>
On Mon, 2008-10-27 at 08:43 -0500, Kumar Gala wrote:
>
> While we have the comment the code appears not to really follow it.
> We appear to write 1 << hard_smp_processor_id().
That code is called by each CPU that gets onlined and OR's it's
bit in the mask.
Ben.
next prev parent reply other threads:[~2008-10-27 20:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 15:57 [PATCH] genirq: Set initial default irq affinity to just CPU0 Kumar Gala
2008-10-24 15:57 ` Kumar Gala
2008-10-24 23:18 ` David Miller
2008-10-24 23:18 ` David Miller
2008-10-25 21:33 ` Benjamin Herrenschmidt
2008-10-25 21:33 ` Benjamin Herrenschmidt
2008-10-25 22:53 ` Kevin Diggs
2008-10-26 4:05 ` David Miller
2008-10-27 17:36 ` Chris Friesen
2008-10-27 18:28 ` David Miller
2008-10-27 19:10 ` Chris Friesen
2008-10-27 19:25 ` David Miller
2008-10-28 3:46 ` Chris Friesen
2008-10-27 19:43 ` Kumar Gala
2008-10-27 19:49 ` David Miller
2008-10-27 20:46 ` Kumar Gala
2008-10-26 6:48 ` Benjamin Herrenschmidt
2008-10-26 7:16 ` David Miller
2008-10-26 8:29 ` Benjamin Herrenschmidt
2008-10-27 2:30 ` Kevin Diggs
2008-10-27 2:49 ` Benjamin Herrenschmidt
2008-10-26 4:04 ` David Miller
2008-10-26 4:04 ` David Miller
2008-10-26 6:33 ` Benjamin Herrenschmidt
2008-10-26 6:33 ` Benjamin Herrenschmidt
2008-10-27 13:43 ` Kumar Gala
2008-10-27 13:43 ` Kumar Gala
2008-10-27 20:27 ` Benjamin Herrenschmidt [this message]
2008-10-27 20:27 ` Benjamin Herrenschmidt
2008-10-27 20:45 ` Kumar Gala
2008-10-27 20:45 ` Kumar Gala
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=1225139236.8004.21.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=maxk@qualcomm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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 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.