From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: <dan.j.williams@intel.com>, <ira.weiny@intel.com>,
<fan.ni@samsung.com>, <a.manzanares@samsung.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 2/3] cxl/mbox: Wire up interrupts for background completion
Date: Tue, 4 Apr 2023 10:22:53 +0100 [thread overview]
Message-ID: <20230404102253.00004432@Huawei.com> (raw)
In-Reply-To: <20230403175224.00004c3f@Huawei.com>
On Mon, 3 Apr 2023 17:52:24 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:
> On Fri, 24 Feb 2023 11:44:42 -0800
> Davidlohr Bueso <dave@stgolabs.net> wrote:
>
> > Notify when the background operation is done.
> >
> > Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> Hi Davidlohr,
>
> One trivial inline.
>
> Also, the interrupt setup for the PCI cap is missing I think.
> See handling in ct3_realize()
Should have said, for more minor stuff I'm fine just fixing these
up in my staging tree directly. You can either feedback here or
when I post that series for upstream merge.
Jonathan
>
>
>
> Jonathan
>
> > ---
> > hw/cxl/cxl-device-utils.c | 10 +++++++++-
> > hw/cxl/cxl-mailbox-utils.c | 11 +++++++++++
> > include/hw/cxl/cxl_device.h | 1 +
> > 3 files changed, 21 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/cxl/cxl-device-utils.c b/hw/cxl/cxl-device-utils.c
> > index 4bb4e85dae19..a4a2c6a80004 100644
> > --- a/hw/cxl/cxl-device-utils.c
> > +++ b/hw/cxl/cxl-device-utils.c
> > @@ -272,10 +272,18 @@ static void device_reg_init_common(CXLDeviceState *cxl_dstate)
> >
> > static void mailbox_reg_init_common(CXLDeviceState *cxl_dstate)
> > {
> > - /* 2048 payload size, with no interrupt */
> > + const uint8_t msi_n = 9;
> > +
> > + /* 2048 payload size */
> > ARRAY_FIELD_DP32(cxl_dstate->mbox_reg_state32, CXL_DEV_MAILBOX_CAP,
> > PAYLOAD_SIZE, CXL_MAILBOX_PAYLOAD_SHIFT);
> > cxl_dstate->payload_size = CXL_MAILBOX_MAX_PAYLOAD_SIZE;
> > + /* irq support */
> > + ARRAY_FIELD_DP32(cxl_dstate->mbox_reg_state32, CXL_DEV_MAILBOX_CAP,
> > + BG_INT_CAP, 1);
> > + ARRAY_FIELD_DP32(cxl_dstate->mbox_reg_state32, CXL_DEV_MAILBOX_CAP,
> > + MSI_N, msi_n);
> > + cxl_dstate->mbox_msi_n = msi_n;
> > }
> >
> > static void memdev_reg_init_common(CXLDeviceState *cxl_dstate) { }
> > diff --git a/hw/cxl/cxl-mailbox-utils.c b/hw/cxl/cxl-mailbox-utils.c
> > index 82923bb84eb0..61f0b8d675bc 100644
> > --- a/hw/cxl/cxl-mailbox-utils.c
> > +++ b/hw/cxl/cxl-mailbox-utils.c
> > @@ -8,6 +8,8 @@
> > */
> >
> > #include "qemu/osdep.h"
> > +#include "hw/pci/msi.h"
> > +#include "hw/pci/msix.h"
> > #include "hw/cxl/cxl.h"
> > #include "hw/cxl/cxl_events.h"
> > #include "hw/pci/pci.h"
> > @@ -984,9 +986,18 @@ static void bg_timercb(void *opaque)
> > cxl_dstate->mbox_reg_state64[R_CXL_DEV_BG_CMD_STS] = bg_status_reg;
> >
> > if (cxl_dstate->bg.complete_pct == 100) {
> > + CXLType3Dev *ct3d = container_of(cxl_dstate, CXLType3Dev, cxl_dstate);
> > + PCIDevice *pdev = &ct3d->parent_obj;
>
> Should be casting it rather than directly accessing the parent_obj
> PCI_DEVICE(ct3d) should work.
>
> There is an open question about whether we should be doing similar for the
> cxl_dstate. I've not figured out the answer yet, but it may well affect this.
>
>
> > +
> > cxl_dstate->bg.starttime = 0;
> > /* registers are updated, allow new bg-capable cmds */
> > cxl_dstate->bg.runtime = 0;
> > +
> > + if (msix_enabled(pdev)) {
> > + msix_notify(pdev, cxl_dstate->mbox_msi_n);
> > + } else if (msi_enabled(pdev)) {
> > + msi_notify(pdev, cxl_dstate->mbox_msi_n);
> > + }
> > }
> > }
> >
> > diff --git a/include/hw/cxl/cxl_device.h b/include/hw/cxl/cxl_device.h
> > index dbb8a955723b..f986651b6ead 100644
> > --- a/include/hw/cxl/cxl_device.h
> > +++ b/include/hw/cxl/cxl_device.h
> > @@ -189,6 +189,7 @@ typedef struct cxl_device_state {
> > struct {
> > MemoryRegion mailbox;
> > uint16_t payload_size;
> > + uint8_t mbox_msi_n;
> > union {
> > uint8_t mbox_reg_state[CXL_MAILBOX_REGISTERS_LENGTH];
> > uint16_t mbox_reg_state16[CXL_MAILBOX_REGISTERS_LENGTH / 2];
>
>
next prev parent reply other threads:[~2023-04-04 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 19:44 [PATCH -qemu 0/3] cxl: Background commands and device sanitation Davidlohr Bueso
2023-02-24 19:44 ` [PATCH 1/3] cxl/mbox: Add support for background operations Davidlohr Bueso
2023-03-01 19:00 ` Fan Ni
2023-03-01 20:45 ` Davidlohr Bueso
2023-04-03 16:47 ` Jonathan Cameron
2023-04-07 18:05 ` Davidlohr Bueso
2023-04-14 13:49 ` Jonathan Cameron
2023-04-11 19:06 ` Davidlohr Bueso
2023-04-14 13:51 ` Jonathan Cameron
2023-02-24 19:44 ` [PATCH 2/3] cxl/mbox: Wire up interrupts for background completion Davidlohr Bueso
2023-04-03 16:52 ` Jonathan Cameron
2023-04-04 9:22 ` Jonathan Cameron [this message]
2023-04-12 2:22 ` Davidlohr Bueso
2023-04-14 13:43 ` Jonathan Cameron
2023-02-24 19:44 ` [PATCH 3/3] cxl: Add support for device sanitation Davidlohr Bueso
2023-04-14 14:15 ` Jonathan Cameron
2023-04-16 2:32 ` Davidlohr Bueso
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=20230404102253.00004432@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.