[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ypfjw/5xiKZKWWNu@iweiny-desk3>
Date: Wed, 1 Jun 2022 15:10:11 -0700
From: Ira Weiny <ira.weiny@...el.com>
To: Alison Schofield <alison.schofield@...el.com>
Cc: "Williams, Dan J" <dan.j.williams@...el.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
"Verma, Vishal L" <vishal.l.verma@...el.com>,
"Jiang, Dave" <dave.jiang@...el.com>,
Ben Widawsky <ben@...dawsk.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-cxl@...r.kernel.org" <linux-cxl@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH V9 7/9] cxl/port: Introduce cxl_cdat_valid()
On Tue, May 31, 2022 at 10:21:46AM -0700, Alison Schofield wrote:
> On Tue, May 31, 2022 at 08:26:30AM -0700, Ira Weiny wrote:
> > From: Ira Weiny <ira.weiny@...el.com>
> >
> > The CDAT data is protected by a checksum and should be the proper
> > length.
> >
> > Introduce cxl_cdat_valid() to validate the data. While at it check and
> > store the sequence number.
> >
> Store it for ?
To see if a subsequent read shows new data.
>
> >
> > +static bool cxl_cdat_valid(struct device *dev, struct cxl_cdat *cdat)
> > +{
>
> snip
>
> > +
> > + seq = FIELD_GET(CDAT_HEADER_DW3_SEQUENCE, table[3]);
> > + /* Store the sequence for now. */
> > + if (cdat->seq != seq) {
> > + dev_info(dev, "CDAT seq change %x -> %x\n", cdat->seq, seq);
> > + cdat->seq = seq;
> > + }
> > +
>
> Wondering when does/will this sequence number come into play?
>
Not until we start reacting to changes in CDAT.
Ira
Powered by blists - more mailing lists