From: Rashmica <rashmicy@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
mpe@ellerman.id.au, paulus@samba.org, nfont@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/5] powerpc/pseries: Drop support for MPIC in pseries
Date: Tue, 31 May 2016 11:34:24 +1000 [thread overview]
Message-ID: <574CEA20.5070809@gmail.com> (raw)
In-Reply-To: <1464593541.3078.192.camel@kernel.crashing.org>
On 30/05/16 17:32, Benjamin Herrenschmidt wrote:
> On Mon, 2016-05-30 at 16:18 +1000, Rashmica Gupta wrote:
>> MPIC was only used by Power3 which is now unsupported, so drop support
>> for MPIC. XICS is now the only supported interrupt controller for
>> pSeries so make the XICS functions generic.
> The second half I'm not sure ... XIVE is around the corner...
>
> Cheers,
> Ben.
>
I thought XIVE was replacing XICS? And so then we can just simply
replace all the specific XICS code such as xics_init() and
xics_smp_probe() with the relevant XIVE functions?
By "make the XICS functions generic" I meant that if there is only one
interrupt controller for pseries then we don't need to have both static
void __init pseries_xics_init_IRQ(void) and static void __init
pSeries_init_IRQ(void), etc.
next prev parent reply other threads:[~2016-05-31 1:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 6:18 [PATCH 1/5] powerpc/pseries: Drop support for MPIC in pseries Rashmica Gupta
2016-05-30 6:18 ` [PATCH 2/5] powerpc/pseries: Remove MPIC from pseries smp Rashmica Gupta
2016-05-30 6:18 ` [PATCH 3/5] powerpc/pseries: Remove MPIC from pseries kexec Rashmica Gupta
2016-05-30 6:18 ` [PATCH 4/5] powerpc/pseries: Remove MPIC from pseries cpu hotplug Rashmica Gupta
2016-05-30 6:18 ` [PATCH 5/5] powerpc/pseries: Remove MPIC from pseries event sources Rashmica Gupta
2016-05-30 7:32 ` [PATCH 1/5] powerpc/pseries: Drop support for MPIC in pseries Benjamin Herrenschmidt
2016-05-31 1:34 ` Rashmica [this message]
2016-05-31 2:48 ` Rashmica
2016-05-31 4:52 ` Benjamin Herrenschmidt
2016-05-31 5:04 ` Michael Ellerman
2016-05-31 5:30 ` Benjamin Herrenschmidt
2016-05-31 3:00 ` Benjamin Herrenschmidt
2016-06-15 12:39 ` [1/5] " Michael Ellerman
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=574CEA20.5070809@gmail.com \
--to=rashmicy@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.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).