[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YtB1aE/xUnoeuOtp@iweiny-desk3>
Date: Thu, 14 Jul 2022 12:58:32 -0700
From: Ira Weiny <ira.weiny@...el.com>
To: Dan Williams <dan.j.williams@...el.com>
CC: Bjorn Helgaas <bhelgaas@...gle.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Lukas Wunner <lukas@...ner.de>,
"Alison Schofield" <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Ben Widawsky <bwidawsk@...nel.org>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>,
<linux-pci@...r.kernel.org>
Subject: Re: [PATCH V13 9/9] cxl/port: Parse out DSMAS data from CDAT table
On Thu, Jul 14, 2022 at 09:32:03AM -0700, Dan Williams wrote:
> ira.weiny@ wrote:
> > From: Ira Weiny <ira.weiny@...el.com>
> >
> > CXL Ports with memory devices attached need the information from the
> > Device Scoped Memory Affinity Structure (DSMAS). This information is
> > contained within the CDAT table buffer which is cached in the port
> > device.
> >
> > If CDAT data is available, parse and cache DSMAS data from the table.
> > Store this data in unmarshaled struct dsmas data structures for ease of
> > use later. Ensure DSMAS headers are not malicious or ill formed so as
> > to cause buffer overflow errors.
> >
>
> Per patch 6 the parsing needs to move to a refactored version of the
> ACPI table parsing,
I'm not seeing that parsing ATM but I'll figure out what you mean.
> but for now it can just be dropped.
Dropped.
Ira
Powered by blists - more mailing lists