From: Sethi Varun-B16395 <B16395@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: RE: [PATCH 2/3 v2] powerpc/mpic: Use the MPIC_LARGE_VECTORS flag for FSL MPIC.
Date: Mon, 9 Jul 2012 14:41:18 +0000 [thread overview]
Message-ID: <C5ECD7A89D1DC44195F34B25E172658D139409@039-SN2MPN1-013.039d.mgd.msft.net> (raw)
In-Reply-To: <179D14E1-CF74-4502-80B7-FC44A28175D2@kernel.crashing.org>
> -----Original Message-----
> From: Kumar Gala [mailto:galak@kernel.crashing.org]
> Sent: Monday, July 09, 2012 7:58 PM
> To: Sethi Varun-B16395
> Cc: linuxppc-dev@lists.ozlabs.org
> Subject: Re: [PATCH 2/3 v2] powerpc/mpic: Use the MPIC_LARGE_VECTORS flag
> for FSL MPIC.
>=20
>=20
> On Jul 9, 2012, at 3:46 AM, Varun Sethi wrote:
>=20
> > We should use the MPIC_LARG_VECTORS flag while intializing the MPIC.
> > This prevents us from eating in to hardware vector number space (MSIs)
> > while setting up internal sources.
> >
> > Signed-off-by: Varun Sethi <Varun.Sethi@freescale.com>
> > ---
> > arch/powerpc/sysdev/mpic.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
>=20
> Can you remind me the issue here w/running into the MSIs?
Vector numbers for internal interrupt sources like timers/ipis are
taken from the hardware vector number space. Currently we specify=20
number of interrupt sources as 256 and extract 12 vectors from here
for internal interrupt sources. In process we end up eating vector numbers
meant for MSIs. With this patch we are basically expanding our vector
number space.
-Varun
next prev parent reply other threads:[~2012-07-09 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 8:46 [PATCH 2/3 v2] powerpc/mpic: Use the MPIC_LARGE_VECTORS flag for FSL MPIC Varun Sethi
2012-07-09 14:27 ` Kumar Gala
2012-07-09 14:41 ` Sethi Varun-B16395 [this message]
2012-07-10 12:23 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2012-06-03 7:43 Varun Sethi
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=C5ECD7A89D1DC44195F34B25E172658D139409@039-SN2MPN1-013.039d.mgd.msft.net \
--to=b16395@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).