[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <657794c952e19_2090d82947c@iweiny-mobl.notmuch>
Date: Mon, 11 Dec 2023 15:01:29 -0800
From: Ira Weiny <ira.weiny@...el.com>
To: Dan Williams <dan.j.williams@...el.com>,
Ira Weiny <ira.weiny@...el.com>,
Jonathan Cameron <jonathan.cameron@...wei.com>,
Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
Shiju Jose <shiju.jose@...wei.com>
CC: Yazen Ghannam <yazen.ghannam@....com>,
Davidlohr Bueso <dave@...olabs.net>,
Dave Jiang <dave.jiang@...el.com>,
Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
"Ard Biesheuvel" <ardb@...nel.org>, <linux-efi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>,
Ira Weiny <ira.weiny@...el.com>
Subject: Re: [PATCH 6/6] cxl/memdev: Register for and process CPER events
Dan Williams wrote:
> Ira Weiny wrote:
> > Dan Williams wrote:
> > > Ira Weiny wrote:
> > > > Dan Williams wrote:
> > > > > Ira Weiny wrote:
> > > >
> > >
> >
> > [snip]
> >
> > >
> > > > #define CXL_EVENT_HDR_FLAGS_REC_SEVERITY GENMASK(1, 0)
> > > > static void cxl_cper_event_call(struct cxl_cper_notifier_data *nd)
> > >
> > > Is struct cxl_cper_notifier_data needed anymore, just pass the record
> > > reference?
> >
> > I think so because the type of record is ID'ed by the GUID which is not
> > part of the common record. So the notifier data adds the cxl_event_type
> > enum.
>
> Ah, yup, but then I wonder if CPER can just do the GUID to type enum
> lookup and keep the CXL side GUID-free? I.e. just pass the type as a
> separate argument.
Just saw this after I sent V2. Yes the CXL side is GUID free, has been
since an early RFC. But the data structure has the event in it.
If you want I can change the callback signature but it seems reasonable to
me as it is in V2.
Sorry for not catching this before I sent it out,
Ira
Powered by blists - more mailing lists