From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, Greg Kurz <groug@kaod.org>,
Suraj Jitindar Singh <sjitindarsingh@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 08/10] ppc/xive: Extend XiveTCTX with an router object pointer
Date: Fri, 12 Jul 2019 11:15:27 +1000 [thread overview]
Message-ID: <20190712011527.GB2561@umbus.fritz.box> (raw)
In-Reply-To: <08faf669-72a7-8f30-d33c-2e285405005c@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 6078 bytes --]
On Wed, Jul 03, 2019 at 07:54:57AM +0200, Cédric Le Goater wrote:
> On 03/07/2019 04:07, David Gibson wrote:
> > On Sun, Jun 30, 2019 at 10:45:59PM +0200, Cédric Le Goater wrote:
> >> This is to perform lookups in the NVT table when a vCPU is dispatched
> >> and possibly resend interrupts.
> >
> > I'm slightly confused by this one. Aren't there multiple router
> > objects, each of which can deliver to any thread? In which case what
> > router object is associated with a specific TCTX?
>
> when a vCPU is dispatched on a HW thread, the hypervisor does a store
> on the CAM line to store the VP id. At that time, it checks the IPB in
> the associated NVT structure and notifies the thread if an interrupt is
> pending.
>
> We need to do a NVT lookup, just like the presenter in HW, hence the
> router pointer. You should look at the following patch which clarifies
> the resend sequence.
Hm, ok.
> >> Future XIVE chip will use a different class for the model of the
> >> interrupt controller. So use an 'Object *' instead of a 'XiveRouter *'.
> >
> > This seems odd to me, shouldn't it be an interface pointer or
> > something in that case?
>
> I have duplicated most of the XIVE models for P10 because the internal
> structures have changed. I managed to keep the XiveSource and XiveTCTX
> but we now have a Xive10Router, this is the reason why.
Right, but XiveRouter and Xive10Router must have something in common
if they can both be used here. Usually that's expressed as a shared
QOM interface - in which case you can use a pointer to the interface,
rathe than using Object * which kind of implies *anything* can go
here.
>
> If I was to duplicate XiveTCTX also, I will switch it back to a XiveRouter
> pointer in the P9 version.
>
> C.
>
>
> >> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> >
> >> ---
> >> include/hw/ppc/xive.h | 4 +++-
> >> hw/intc/xive.c | 11 ++++++++++-
> >> hw/ppc/pnv.c | 2 +-
> >> hw/ppc/spapr_irq.c | 2 +-
> >> 4 files changed, 15 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/include/hw/ppc/xive.h b/include/hw/ppc/xive.h
> >> index d922524982d3..b764e1e4e6d4 100644
> >> --- a/include/hw/ppc/xive.h
> >> +++ b/include/hw/ppc/xive.h
> >> @@ -321,6 +321,8 @@ typedef struct XiveTCTX {
> >> qemu_irq os_output;
> >>
> >> uint8_t regs[XIVE_TM_RING_COUNT * XIVE_TM_RING_SIZE];
> >> +
> >> + Object *xrtr;
> >> } XiveTCTX;
> >>
> >> /*
> >> @@ -416,7 +418,7 @@ void xive_tctx_tm_write(XiveTCTX *tctx, hwaddr offset, uint64_t value,
> >> uint64_t xive_tctx_tm_read(XiveTCTX *tctx, hwaddr offset, unsigned size);
> >>
> >> void xive_tctx_pic_print_info(XiveTCTX *tctx, Monitor *mon);
> >> -Object *xive_tctx_create(Object *cpu, XiveRouter *xrtr, Error **errp);
> >> +Object *xive_tctx_create(Object *cpu, Object *xrtr, Error **errp);
> >>
> >> static inline uint32_t xive_nvt_cam_line(uint8_t nvt_blk, uint32_t nvt_idx)
> >> {
> >> diff --git a/hw/intc/xive.c b/hw/intc/xive.c
> >> index f7ba1c3b622f..56700681884f 100644
> >> --- a/hw/intc/xive.c
> >> +++ b/hw/intc/xive.c
> >> @@ -573,6 +573,14 @@ static void xive_tctx_realize(DeviceState *dev, Error **errp)
> >> Object *obj;
> >> Error *local_err = NULL;
> >>
> >> + obj = object_property_get_link(OBJECT(dev), "xrtr", &local_err);
> >> + if (!obj) {
> >> + error_propagate(errp, local_err);
> >> + error_prepend(errp, "required link 'xrtr' not found: ");
> >> + return;
> >> + }
> >> + tctx->xrtr = obj;
> >> +
> >> obj = object_property_get_link(OBJECT(dev), "cpu", &local_err);
> >> if (!obj) {
> >> error_propagate(errp, local_err);
> >> @@ -657,7 +665,7 @@ static const TypeInfo xive_tctx_info = {
> >> .class_init = xive_tctx_class_init,
> >> };
> >>
> >> -Object *xive_tctx_create(Object *cpu, XiveRouter *xrtr, Error **errp)
> >> +Object *xive_tctx_create(Object *cpu, Object *xrtr, Error **errp)
> >> {
> >> Error *local_err = NULL;
> >> Object *obj;
> >> @@ -666,6 +674,7 @@ Object *xive_tctx_create(Object *cpu, XiveRouter *xrtr, Error **errp)
> >> object_property_add_child(cpu, TYPE_XIVE_TCTX, obj, &error_abort);
> >> object_unref(obj);
> >> object_property_add_const_link(obj, "cpu", cpu, &error_abort);
> >> + object_property_add_const_link(obj, "xrtr", xrtr, &error_abort);
> >> object_property_set_bool(obj, true, "realized", &local_err);
> >> if (local_err) {
> >> goto error;
> >> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
> >> index b87e01e5b925..11916dc273c2 100644
> >> --- a/hw/ppc/pnv.c
> >> +++ b/hw/ppc/pnv.c
> >> @@ -765,7 +765,7 @@ static void pnv_chip_power9_intc_create(PnvChip *chip, PowerPCCPU *cpu,
> >> * controller object is initialized afterwards. Hopefully, it's
> >> * only used at runtime.
> >> */
> >> - obj = xive_tctx_create(OBJECT(cpu), XIVE_ROUTER(&chip9->xive), &local_err);
> >> + obj = xive_tctx_create(OBJECT(cpu), OBJECT(&chip9->xive), &local_err);
> >> if (local_err) {
> >> error_propagate(errp, local_err);
> >> return;
> >> diff --git a/hw/ppc/spapr_irq.c b/hw/ppc/spapr_irq.c
> >> index b2b01e850de8..5b3c3c50967b 100644
> >> --- a/hw/ppc/spapr_irq.c
> >> +++ b/hw/ppc/spapr_irq.c
> >> @@ -353,7 +353,7 @@ static void spapr_irq_cpu_intc_create_xive(SpaprMachineState *spapr,
> >> Object *obj;
> >> SpaprCpuState *spapr_cpu = spapr_cpu_state(cpu);
> >>
> >> - obj = xive_tctx_create(OBJECT(cpu), XIVE_ROUTER(spapr->xive), &local_err);
> >> + obj = xive_tctx_create(OBJECT(cpu), OBJECT(spapr->xive), &local_err);
> >> if (local_err) {
> >> error_propagate(errp, local_err);
> >> return;
> >
>
--
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:[~2019-07-12 1:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 20:45 [Qemu-devel] [PATCH 00/10] ppc/pnv: add XIVE support for KVM guests Cédric Le Goater
2019-06-30 20:45 ` [Qemu-devel] [PATCH 01/10] ppc/xive: Force the Physical CAM line value to group mode Cédric Le Goater
2019-07-01 5:26 ` David Gibson
2019-06-30 20:45 ` [Qemu-devel] [PATCH 02/10] ppc/xive: Make the PIPR register readonly Cédric Le Goater
2019-07-01 5:27 ` David Gibson
2019-06-30 20:45 ` [Qemu-devel] [PATCH 03/10] ppc/pnv: Rework cache watch model of PnvXIVE Cédric Le Goater
2019-07-01 5:32 ` David Gibson
2019-06-30 20:45 ` [Qemu-devel] [PATCH 04/10] ppc/xive: Fix TM_PULL_POOL_CTX special operation Cédric Le Goater
2019-07-01 5:32 ` David Gibson
2019-06-30 20:45 ` [Qemu-devel] [PATCH 05/10] ppc/xive: Implement TM_PULL_OS_CTX special command Cédric Le Goater
2019-06-30 20:45 ` [Qemu-devel] [PATCH 06/10] ppc/xive: Provide escalation support Cédric Le Goater
2019-06-30 20:45 ` [Qemu-devel] [PATCH 07/10] ppc/xive: Improve 'info pic' support Cédric Le Goater
2019-06-30 20:45 ` [Qemu-devel] [PATCH 08/10] ppc/xive: Extend XiveTCTX with an router object pointer Cédric Le Goater
2019-07-03 2:07 ` David Gibson
2019-07-03 5:54 ` Cédric Le Goater
2019-07-12 1:15 ` David Gibson [this message]
2019-07-15 15:45 ` Cédric Le Goater
2019-07-17 2:08 ` David Gibson
2019-07-17 8:35 ` Cédric Le Goater
2019-06-30 20:46 ` [Qemu-devel] [PATCH 09/10] ppc/xive: Synthesize interrupt from the saved IPB in the NVT Cédric Le Goater
2019-06-30 20:46 ` [Qemu-devel] [PATCH 10/10] ppc/pnv: Dump the XIVE NVT table Cédric Le Goater
2019-07-03 2:10 ` [Qemu-devel] [PATCH 00/10] ppc/pnv: add XIVE support for KVM guests David Gibson
2019-07-03 5:56 ` 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=20190712011527.GB2561@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sjitindarsingh@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).