From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [Qemu-devel] [PATCH v3 03/35] ppc/xive: introduce the XiveFabric interface
Date: Tue, 24 Apr 2018 16:46:29 +1000 [thread overview]
Message-ID: <20180424064629.GP19804@umbus.fritz.box> (raw)
In-Reply-To: <8d1cb270-d62f-f08f-9167-3f130906f910@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 7101 bytes --]
On Mon, Apr 23, 2018 at 09:58:43AM +0200, Cédric Le Goater wrote:
> On 04/23/2018 08:46 AM, David Gibson wrote:
> > On Thu, Apr 19, 2018 at 02:42:59PM +0200, Cédric Le Goater wrote:
> >> The XiveFabric offers a simple interface, between the XiveSourve
> >> object and the device model owning the interrupt sources, to forward
> >> an event notification to the XIVE interrupt controller of the machine
> >> and if the owner is the controller, to call directly the routing
> >> sub-engine.
> >>
> >> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> >> ---
> >> hw/intc/xive.c | 37 ++++++++++++++++++++++++++++++++++++-
> >> include/hw/ppc/xive.h | 25 +++++++++++++++++++++++++
> >> 2 files changed, 61 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/hw/intc/xive.c b/hw/intc/xive.c
> >> index 060976077dd7..b4c3d06c1219 100644
> >> --- a/hw/intc/xive.c
> >> +++ b/hw/intc/xive.c
> >> @@ -17,6 +17,21 @@
> >> #include "hw/ppc/xive.h"
> >>
> >> /*
> >> + * XIVE Fabric
> >> + */
> >> +
> >> +static void xive_fabric_route(XiveFabric *xf, int lisn)
> >> +{
> >> +
> >> +}
> >> +
> >> +static const TypeInfo xive_fabric_info = {
> >> + .name = TYPE_XIVE_FABRIC,
> >> + .parent = TYPE_INTERFACE,
> >> + .class_size = sizeof(XiveFabricClass),
> >> +};
> >> +
> >> +/*
> >> * XIVE Interrupt Source
> >> */
> >>
> >> @@ -97,11 +112,19 @@ static bool xive_source_pq_trigger(XiveSource *xsrc, uint32_t srcno)
> >>
> >> /*
> >> * Forward the source event notification to the associated XiveFabric,
> >> - * the device owning the sources.
> >> + * the device owning the sources, or perform the routing if the device
> >> + * is the interrupt controller.
> >> */
> >> static void xive_source_notify(XiveSource *xsrc, int srcno)
> >> {
> >>
> >> + XiveFabricClass *xfc = XIVE_FABRIC_GET_CLASS(xsrc->xive);
> >> +
> >> + if (xfc->notify) {
> >> + xfc->notify(xsrc->xive, srcno + xsrc->offset);
> >> + } else {
> >> + xive_fabric_route(xsrc->xive, srcno + xsrc->offset);
> >> + }
> >
> > Why 2 cases? Can't the XiveFabric object just make its notify equal
> > to xive_fabric_route if that's what it wants?
> Under sPAPR, all the sources, IPIs and virtual device interrupts,
> generate events which are directly routed by xive_fabric_route().
> There is no need of an extra hop. Indeed.
Ok.
> Under PowerNV, some sources forward the notification to the routing
> engine using a specific MMIO load on a notify address which is stored
> in one of the controller registers. So we need a hop to reach the
> device model, owning the sources, and do that load :
Hm. So you're saying that in pnv some sources send their notification
to some other unit, that would then (after possible masking) forward
on to the overall xive fabric?
That seems like a property of the source object, rather than a
property of the fabric. Indeed varying this by source object would
require the objects have a different xive pointer, when I thought the
idea was that the XiveFabric was global.
> static void pnv_psi_notify(XiveFabric *xf, uint32_t lisn)
> {
> PnvPsi *psi = PNV_PSI(xf);
> uint64_t notif_port =
> psi->regs[PSIHB_REG(PSIHB9_ESB_NOTIF_ADDR)];
> bool valid = notif_port & PSIHB9_ESB_NOTIF_VALID;
> uint64_t notify_addr = notif_port & ~PSIHB9_ESB_NOTIF_VALID;
> uint32_t data = cpu_to_be32(lisn);
>
> if (valid) {
> cpu_physical_memory_write(notify_addr, &data, sizeof(data));
> }
> }
>
> The PnvXive model handles the load and forwards to the fabric again.
>
> The IPIs under PowerNV do not need an extra hop so they reach the
> routing routine directly without the extra notify() hop.
>
> However, PowerNV at the end should be using xive_fabric_route()
> but there are some differences on how the NVT registers are
> updated (HV vs. OS mode) and it's not handled yet so it uses a
> notify() handler. But is should disappear and call directly
> xive_fabric_route() in a near future.
>
>
> May be, XiveFabricNotifier would be a better name for this feature ?
> I am adding a few ops later which are more related to routing.
>
> Thanks,
>
> C.
>
>
> >
> >> }
> >>
> >> /*
> >> @@ -302,6 +325,17 @@ static void xive_source_reset(DeviceState *dev)
> >> static void xive_source_realize(DeviceState *dev, Error **errp)
> >> {
> >> XiveSource *xsrc = XIVE_SOURCE(dev);
> >> + Object *obj;
> >> + Error *local_err = NULL;
> >> +
> >> + obj = object_property_get_link(OBJECT(dev), "xive", &local_err);
> >> + if (!obj) {
> >> + error_propagate(errp, local_err);
> >> + error_prepend(errp, "required link 'xive' not found: ");
> >> + return;
> >> + }
> >> +
> >> + xsrc->xive = XIVE_FABRIC(obj);
> >>
> >> if (!xsrc->nr_irqs) {
> >> error_setg(errp, "Number of interrupt needs to be greater than 0");
> >> @@ -376,6 +410,7 @@ static const TypeInfo xive_source_info = {
> >> static void xive_register_types(void)
> >> {
> >> type_register_static(&xive_source_info);
> >> + type_register_static(&xive_fabric_info);
> >> }
> >>
> >> type_init(xive_register_types)
> >> diff --git a/include/hw/ppc/xive.h b/include/hw/ppc/xive.h
> >> index 0b76dd278d9b..4fcae2c763e6 100644
> >> --- a/include/hw/ppc/xive.h
> >> +++ b/include/hw/ppc/xive.h
> >> @@ -12,6 +12,8 @@
> >>
> >> #include "hw/sysbus.h"
> >>
> >> +typedef struct XiveFabric XiveFabric;
> >> +
> >> /*
> >> * XIVE Interrupt Source
> >> */
> >> @@ -46,6 +48,8 @@ typedef struct XiveSource {
> >> hwaddr esb_base;
> >> uint32_t esb_shift;
> >> MemoryRegion esb_mmio;
> >> +
> >> + XiveFabric *xive;
> >> } XiveSource;
> >>
> >> /*
> >> @@ -143,4 +147,25 @@ static inline void xive_source_irq_set(XiveSource *xsrc, uint32_t srcno,
> >> xsrc->status[srcno] |= lsi ? XIVE_STATUS_LSI : 0;
> >> }
> >>
> >> +/*
> >> + * XIVE Fabric
> >> + */
> >> +
> >> +typedef struct XiveFabric {
> >> + Object parent;
> >> +} XiveFabric;
> >> +
> >> +#define TYPE_XIVE_FABRIC "xive-fabric"
> >> +#define XIVE_FABRIC(obj) \
> >> + OBJECT_CHECK(XiveFabric, (obj), TYPE_XIVE_FABRIC)
> >> +#define XIVE_FABRIC_CLASS(klass) \
> >> + OBJECT_CLASS_CHECK(XiveFabricClass, (klass), TYPE_XIVE_FABRIC)
> >> +#define XIVE_FABRIC_GET_CLASS(obj) \
> >> + OBJECT_GET_CLASS(XiveFabricClass, (obj), TYPE_XIVE_FABRIC)
> >> +
> >> +typedef struct XiveFabricClass {
> >> + InterfaceClass parent;
> >> + void (*notify)(XiveFabric *xf, uint32_t lisn);
> >> +} XiveFabricClass;
> >> +
> >> #endif /* PPC_XIVE_H */
> >
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-24 7:48 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 12:42 [Qemu-devel] [PATCH v3 00/35] ppc: support for the XIVE interrupt controller (POWER9) Cédric Le Goater
2018-04-19 12:42 ` [Qemu-devel] [PATCH v3 01/35] ppc/xive: introduce a XIVE interrupt source model Cédric Le Goater
2018-04-20 7:10 ` David Gibson
2018-04-20 8:27 ` Cédric Le Goater
2018-04-23 3:59 ` David Gibson
2018-04-23 7:11 ` Cédric Le Goater
2018-04-24 1:24 ` David Gibson
2018-04-19 12:42 ` [Qemu-devel] [PATCH v3 02/35] ppc/xive: add support for the LSI interrupt sources Cédric Le Goater
2018-04-23 6:44 ` David Gibson
2018-04-23 7:31 ` Cédric Le Goater
2018-04-24 6:41 ` David Gibson
2018-04-24 8:11 ` Cédric Le Goater
2018-04-26 3:28 ` David Gibson
2018-04-26 12:16 ` Cédric Le Goater
2018-04-27 2:43 ` David Gibson
2018-05-04 14:25 ` Cédric Le Goater
2018-05-05 4:32 ` David Gibson
2018-04-19 12:42 ` [Qemu-devel] [PATCH v3 03/35] ppc/xive: introduce the XiveFabric interface Cédric Le Goater
2018-04-23 6:46 ` David Gibson
2018-04-23 7:58 ` Cédric Le Goater
2018-04-24 6:46 ` David Gibson [this message]
2018-04-24 9:33 ` Cédric Le Goater
2018-04-26 3:54 ` David Gibson
2018-04-26 10:30 ` Cédric Le Goater
2018-04-27 6:32 ` David Gibson
2018-05-02 15:28 ` Cédric Le Goater
2018-05-03 5:13 ` David Gibson
2018-05-23 10:12 ` Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 04/35] spapr/xive: introduce a XIVE interrupt controller for sPAPR Cédric Le Goater
2018-04-24 6:51 ` David Gibson
2018-04-24 9:46 ` Cédric Le Goater
2018-04-26 4:20 ` David Gibson
2018-04-26 10:43 ` Cédric Le Goater
2018-05-03 5:22 ` David Gibson
2018-05-03 16:50 ` Cédric Le Goater
2018-05-04 3:33 ` David Gibson
2018-05-04 13:05 ` Cédric Le Goater
2018-05-05 4:26 ` David Gibson
2018-05-09 7:23 ` Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 05/35] spapr/xive: add a single source block to the sPAPR XIVE model Cédric Le Goater
2018-04-24 6:58 ` David Gibson
2018-04-24 8:19 ` Cédric Le Goater
2018-04-26 4:46 ` David Gibson
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 06/35] spapr/xive: introduce a XIVE interrupt presenter model Cédric Le Goater
2018-04-26 7:11 ` David Gibson
2018-04-26 9:27 ` Cédric Le Goater
2018-04-26 17:15 ` Cédric Le Goater
2018-05-03 5:39 ` David Gibson
2018-05-03 15:10 ` Cédric Le Goater
2018-05-04 4:44 ` David Gibson
2018-05-04 14:15 ` Cédric Le Goater
2018-05-03 5:35 ` David Gibson
2018-05-03 16:06 ` Cédric Le Goater
2018-05-04 4:51 ` David Gibson
2018-05-04 13:11 ` Cédric Le Goater
2018-05-05 4:27 ` David Gibson
2018-05-09 7:27 ` Cédric Le Goater
2018-05-02 7:39 ` Cédric Le Goater
2018-05-03 5:43 ` David Gibson
2018-05-03 14:42 ` Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 07/35] spapr/xive: introduce the XIVE Event Queues Cédric Le Goater
2018-04-26 7:25 ` David Gibson
2018-04-26 9:48 ` Cédric Le Goater
2018-05-03 5:45 ` David Gibson
2018-05-03 6:07 ` Cédric Le Goater
2018-05-03 6:25 ` David Gibson
2018-05-03 14:37 ` Cédric Le Goater
2018-05-04 5:19 ` David Gibson
2018-05-04 13:29 ` Cédric Le Goater
2018-05-05 4:29 ` David Gibson
2018-05-09 8:01 ` Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 08/35] spapr: push the XIVE EQ data in OS event queue Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 09/35] spapr: notify the CPU when the XIVE interrupt priority is more privileged Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 10/35] spapr: add support for the SET_OS_PENDING command (XIVE) Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 11/35] spapr: introduce a 'xive_exploitation' option to enable XIVE Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 12/35] spapr: add a sPAPRXive object to the machine Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 13/35] spapr: add hcalls support for the XIVE exploitation interrupt mode Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 14/35] spapr: add device tree support for the XIVE exploitation mode Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 15/35] sysbus: add a sysbus_mmio_unmap() helper Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 16/35] spapr: introduce a helper to map the XIVE memory regions Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 17/35] spapr: add XIVE support to spapr_qirq() Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 18/35] spapr: introduce a spapr_icp_create() helper Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 19/35] spapr: toggle the ICP depending on the selected interrupt mode Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 20/35] spapr: add support to dump XIVE information Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 21/35] spapr: advertise XIVE exploitation mode in CAS Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 22/35] spapr: add classes for the XIVE models Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 23/35] target/ppc/kvm: add Linux KVM definitions for XIVE Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 24/35] spapr/xive: add common realize routine for KVM Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 25/35] spapr/xive: add KVM support Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 26/35] spapr/xive: add a XIVE KVM device to the machine Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 27/35] migration: discard non-migratable RAMBlocks Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 28/35] intc: introduce a CPUIntc interface Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 29/35] spapr/xive, xics: use the CPU_INTC handlers to reset KVM Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 30/35] spapr/xive, xics: reset KVM at machine reset Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 31/35] spapr/xive: raise migration priority of the machine Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 32/35] ppc/pnv: introduce a pnv_icp_create() helper Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 33/35] ppc: externalize ppc_get_vcpu_by_pir() Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 34/35] ppc/pnv: add XIVE support Cédric Le Goater
2018-04-19 12:43 ` [Qemu-devel] [PATCH v3 35/35] ppc/pnv: add a PSI bridge model for POWER9 processor Cédric Le Goater
2018-04-19 13:28 ` [Qemu-devel] [PATCH v3 00/35] ppc: support for the XIVE interrupt controller (POWER9) no-reply
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=20180424064629.GP19804@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).