From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David Gibson" <david@gibson.dropbear.id.au>,
"Cédric Le Goater" <clg@kaod.org>
Cc: linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC PATCH 1/2] powerpc/xive: guest exploitation of the XIVE interrupt controller
Date: Wed, 05 Jul 2017 09:38:20 -0500 [thread overview]
Message-ID: <1499265500.16202.70.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170705110702.GO2180@umbus.fritz.box>
On Wed, 2017-07-05 at 21:07 +1000, David Gibson wrote:
> I don't know if it helps, but we do have the ability to trigger a full
> system reset from CAS, so possibly we can do the XICS/XIVE
> instantiation in the reset path.
>
> I don't think we use that CAS reset ability yet - we just adjust the
> device tree and continue the boot. But it's there if we need it.
>
> Worst comes to worst, we might have to instantiate both XICS and XIVE
> objects, with some flags in each indicating which is active.
That could be a problem with the kernel interrupt controller. We can't
really instantiate both there I think... well, actually ... maybe we
could, though it's a bit messy...
Cheers,
Ben.
next prev parent reply other threads:[~2017-07-05 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 9:29 [RFC PATCH 0/2] guest exploitation of the XIVE interrupt controller Cédric Le Goater
2017-06-22 9:29 ` [RFC PATCH 1/2] powerpc/xive: " Cédric Le Goater
2017-06-22 12:20 ` Benjamin Herrenschmidt
2017-06-23 13:05 ` Cédric Le Goater
2017-07-03 3:55 ` David Gibson
2017-07-03 4:19 ` Benjamin Herrenschmidt
2017-07-03 7:11 ` Cédric Le Goater
2017-07-05 11:07 ` David Gibson
2017-07-05 14:38 ` Benjamin Herrenschmidt [this message]
2017-07-05 15:13 ` Cédric Le Goater
2017-07-05 17:31 ` Cédric Le Goater
2017-06-22 9:29 ` [RFC PATCH 2/2] powerpc/xive: add XIVE exploitation mode to CAS Cédric Le Goater
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=1499265500.16202.70.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).