From: Scott Wood <scottwood@freescale.com>
To: Stuart Yoder <b08248@gmail.com>
Cc: Varun Sethi <Varun.Sethi@freescale.com>, Linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/4] powerpc/mpic: Use the MPIC_LARGE_VECTORS flag for FSL MPIC.
Date: Tue, 27 Mar 2012 13:47:26 -0500 [thread overview]
Message-ID: <4F720B3E.3040809@freescale.com> (raw)
In-Reply-To: <4F720A90.1040600@freescale.com>
On 03/27/2012 01:44 PM, Scott Wood wrote:
> On 03/27/2012 10:21 AM, Stuart Yoder wrote:
>> On Tue, Mar 27, 2012 at 8:30 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>>
>>> On Mar 27, 2012, at 7:15 AM, Varun Sethi wrote:
>>>
>>>> FSL MPIC supports 16 bit vectors so our vector number space isn't
>>>> restricted to 256 vectors. We should use the MPIC_LARG_VECTORS flag
>>>> while intializing the MPIC. This also prevents us from eating in to
>>>> hardware vector number space (MSIs) while setting up internal sources.
>>>
>>> What is driving this change?
>>
>> Whats driving the change is proper handling of error interrupts. Right
>> now error interrupts (muxed on int 16) are treated as a shared
>> interrupt source. We want each to be handled as a individual interrupt
>> source...thus the desire to support more than 256 interrupts.
>
> We don't actually need more than 256 interrupts for this (the individual
> error interrupts are not counted against this). But unless we change
> how vectors are allocated, we need vectors >= 256, since we have MSIs
> close enough to 256 that under the current scheme the IPIs, timers, and
> such collide with the third MSI bank.
Sorry, I misremembered -- the error interrupts do count against the 256,
but only for Linux IRQ numbering purposes (not hardware vector assignment).
-Scott
next prev parent reply other threads:[~2012-03-27 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 12:15 [PATCH 2/4] powerpc/mpic: Use the MPIC_LARGE_VECTORS flag for FSL MPIC Varun Sethi
2012-03-27 13:30 ` Kumar Gala
2012-03-27 13:59 ` Sethi Varun-B16395
2012-03-27 15:21 ` Stuart Yoder
2012-03-27 18:44 ` Scott Wood
2012-03-27 18:47 ` Scott Wood [this message]
2012-03-27 19:16 ` Scott Wood
2012-03-28 14:52 ` 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=4F720B3E.3040809@freescale.com \
--to=scottwood@freescale.com \
--cc=Linuxppc-dev@lists.ozlabs.org \
--cc=Varun.Sethi@freescale.com \
--cc=b08248@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).