From: Fan Ni <nifan.cxl@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
nifan.cxl@gmail.com, qemu-devel@nongnu.org,
linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
a.manzanares@samsung.com, dave@stgolabs.net,
nmtadam.samsung@gmail.com
Subject: Re: [PATCH 2/2] hw/cxl/cxl_event: Fix interrupt triggering for dynamic capacity events grouped via More flag
Date: Wed, 4 Sep 2024 09:50:15 -0700 [thread overview]
Message-ID: <ZtiPxyDYatbP8p98@fan> (raw)
In-Reply-To: <66d88ccd15efb_1e915829439@iweiny-mobl.notmuch>
On Wed, Sep 04, 2024 at 11:37:33AM -0500, Ira Weiny wrote:
> Jonathan Cameron wrote:
> > On Tue, 27 Aug 2024 09:40:05 -0700
> > nifan.cxl@gmail.com wrote:
> >
> > > From: Fan Ni <fan.ni@samsung.com>
> > >
> > > When inserting multiple dynamic capacity event records grouped via More flag,
> > > we should only trigger interrupt after the last record is inserted into the
> > > event log. Achieving the goal by letting cxl_event_insert return true only
> > > for the insertion of the last dynamic capacity event record in the sequence.
> >
> > I'm not sure this one is accurate. We might well have a slow
> > system provisioning capacity one extent at time (and interrupting).
> >
> > The event buffer might also not be large enough to hold all records so
> > the device might 'wait' before figuring out the next extent for there
> > to be somewhere to put the record.
> >
> > Overall I think we can interrupt on each one and it should 'work'
> > as should interrupt only once there are lots of them or
> > every (n).
>
> Indeed I think it should work. But you won't see any extents as they will
> be pending in the memdev.
>
> Did this fail in some way? I'm sorry I did not try and use qemu to test
> the more bit. Rather I used cxl_test for that.
>
> Ira
It works with or without this fix in my test. Until the last extent is
notified to the OS, the extents will be pending as you mentioned.
Fan
>
> >
> > Interrupt only fires on a 0 to >= 1 transition anyway, not
> > on repeats after that unless the log has been cleared.
> > It's up to OS to keep clearing records until it at least
> > momentarily hits 0 if it wants to get any more interrupts.
> >
> > Jonathan
> >
> >
> > >
> > > Signed-off-by: Fan Ni <fan.ni@samsung.com>
> > > ---
> > > hw/cxl/cxl-events.c | 8 ++++++++
> > > include/hw/cxl/cxl_events.h | 1 +
> > > 2 files changed, 9 insertions(+)
> > >
> > > diff --git a/hw/cxl/cxl-events.c b/hw/cxl/cxl-events.c
> > > index 12dee2e467..90536c0e68 100644
> > > --- a/hw/cxl/cxl-events.c
> > > +++ b/hw/cxl/cxl-events.c
> > > @@ -135,6 +135,14 @@ bool cxl_event_insert(CXLDeviceState *cxlds, CXLEventLogType log_type,
> > > QSIMPLEQ_INSERT_TAIL(&log->events, entry, node);
> > > cxl_event_set_status(cxlds, log_type, true);
> > >
> > > + /*
> > > + * For dynamic capacity event records grouped via More flag,
> > > + * Only raise interrupt after inserting the last record in the log.
> > > + */
> > > + if (log_type == CXL_EVENT_TYPE_DYNAMIC_CAP) {
> > > + CXLEventDynamicCapacity *dCap = (CXLEventDynamicCapacity *)event;
> > > + return (dCap->flags & MORE_FLAG) ? false : true;
> > > + }
> > > /* Count went from 0 to 1 */
> > > return cxl_event_count(log) == 1;
> >
> > If there are multiple this will fail I think as cxl_event_count(log) will go from 0
> > to X not 1.
> >
> > > }
> > > diff --git a/include/hw/cxl/cxl_events.h b/include/hw/cxl/cxl_events.h
> > > index 38cadaa0f3..b0e5cc89c0 100644
> > > --- a/include/hw/cxl/cxl_events.h
> > > +++ b/include/hw/cxl/cxl_events.h
> > > @@ -170,6 +170,7 @@ typedef struct CXLEventMemoryModule {
> > > * CXL r3.1 section Table 8-50: Dynamic Capacity Event Record
> > > * All fields little endian.
> > > */
> > > +#define MORE_FLAG BIT_MASK(0)
> > > typedef struct CXLEventDynamicCapacity {
> > > CXLEventRecordHdr hdr;
> > > uint8_t type;
> >
>
>
--
Fan Ni
prev parent reply other threads:[~2024-09-04 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 16:40 [PATCH 0/2] QEMU DCD emulation support fix nifan.cxl
2024-08-27 16:40 ` [PATCH 1/2] hw/mem/cxl_type3: Fix More flag setting for dynamic capacity event records nifan.cxl
2024-08-28 11:47 ` Jonathan Cameron
2024-08-28 11:47 ` Jonathan Cameron via
2024-08-27 16:40 ` [PATCH 2/2] hw/cxl/cxl_event: Fix interrupt triggering for dynamic capacity events grouped via More flag nifan.cxl
2024-08-28 11:39 ` Jonathan Cameron
2024-08-28 11:39 ` Jonathan Cameron via
2024-09-04 16:37 ` Ira Weiny
2024-09-04 16:50 ` Fan Ni [this message]
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=ZtiPxyDYatbP8p98@fan \
--to=nifan.cxl@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nmtadam.samsung@gmail.com \
--cc=qemu-devel@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 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.