From: Scott Wood <scottwood@freescale.com>
To: Gopalakrishnan Raman <graman@arubanetworks.com>
Cc: "rgkwstl@gmail.com" <rgkwstl@gmail.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Question about MPIC_SINGLE_DEST_CPU on P1020 (e500 core) SMP
Date: Mon, 11 Jun 2012 10:54:23 -0500 [thread overview]
Message-ID: <4FD614AF.70108@freescale.com> (raw)
In-Reply-To: <802E1C77E421D345A43385A6BFAC7AC4BE502C@ROYALGORGE.arubanetworks.com>
On 06/10/2012 03:37 PM, Gopalakrishnan Raman wrote:
> Hi
>=20
> The P1020 manual states (in the PIC chapter) that in the =93Internal
> Interrupt Destination=94 register, only 1 CPU (and not both) can be
> selected as the IRQ destination.
Right.
> How then can we achieve =93interrupt
> spraying=94 for the PCI interrupt (we want interrupts to be sent
> alternately to CPU0 and CPU1).
You'll have to implement it in software by changing the destination each
time (and be careful to follow the documented sequence for making such
changes).
Why do you want to do this? Won't it cause a bunch of cache misses as
the IRQ-relevant data structures bounce between CPUs? Distributing
different devices' interrupts among multiple CPUs is probably good for
load balancing, but distributing a single device's interrupts may not be
so good.
> Also, we changed the code to ignore the
> MPIC_SINGLE_DEST_CPU flag and set both CPUs in the destination of the
> PIC_IIDRn register. This does seem to work.
What specifically does it seem to do?
> But we=92re not sure if we can
> rely on this behavior and whether it will cause other problems.
You cannot rely on this. It is not a supported configuration.
-Scott
prev parent reply other threads:[~2012-06-11 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 20:37 Question about MPIC_SINGLE_DEST_CPU on P1020 (e500 core) SMP Gopalakrishnan Raman
2012-06-11 9:36 ` Li Yang-R58472
2012-06-11 15:54 ` Scott Wood [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=4FD614AF.70108@freescale.com \
--to=scottwood@freescale.com \
--cc=graman@arubanetworks.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rgkwstl@gmail.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).