[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64f7fb141d719_1e8e7829412@iweiny-mobl.notmuch>
Date: Tue, 5 Sep 2023 21:07:48 -0700
From: Ira Weiny <ira.weiny@...el.com>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
<ira.weiny@...el.com>
CC: Dan Williams <dan.j.williams@...el.com>,
Navneet Singh <navneet.singh@...el.com>,
Fan Ni <fan.ni@...sung.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>,
<linux-cxl@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC v2 15/18] cxl/mem: Trace Dynamic capacity Event Record
Jonathan Cameron wrote:
> On Mon, 28 Aug 2023 22:21:06 -0700
> ira.weiny@...el.com wrote:
>
> > From: Navneet Singh <navneet.singh@...el.com>
> >
> > CXL rev 3.0 section 8.2.9.2.1.5 defines the Dynamic Capacity Event Record
> > Determine if the event read is a Dynamic capacity event record and
> > if so trace the record for the debug purpose.
> >
> > Add DC trace points to the trace log.
>
> Probably should say why these might be useful...
>
Its kind of hidden.
"... for the debug purpose."
I suppose this could be used to react to new extents coming online to
create new dax devices in the future. But that should really be done
through udev when dax extent devices surface not these events.
I'll clarify the commit message.
Thanks,
Ira
Powered by blists - more mailing lists