| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <64f7f96c1850f_1e8e78294a9@iweiny-mobl.notmuch>
Date: Tue, 5 Sep 2023 21:00:44 -0700
From: Ira Weiny <ira.weiny@...el.com>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Ira Weiny <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 12/18] cxl/region: Notify regions of DC changes
Jonathan Cameron wrote:
> On Mon, 28 Aug 2023 22:21:03 -0700
> Ira Weiny <ira.weiny@...el.com> wrote:
>
> > In order for a user to use dynamic capacity effectively they need to
> > know when dynamic capacity is available. Thus when Dynamic Capacity
> > (DC) extents are added or removed by a DC device the regions affected
> > need to be notified. Ultimately the DAX region uses the memory
> > associated with DC extents. However, remember that CXL DAX regions
> > maintain any interleave details between devices.
> >
> > When a DCD event occurs, iterate all CXL endpoint decoders and notify
> > regions which contain the endpoints affected by the event. In turn
> > notify the DAX regions of the changes to the DAX region extents.
> >
> > For now interleave is handled by creating simple 1:1 mappings between
> > the CXL DAX region and DAX region layers. Future implementations will
> > need to resolve when to actually surface a DAX region extent and pass
> > the notification along.
> >
> > Remember that adding capacity is safe because there is no chance of the
> > memory being in use. Also remember at this point releasing capacity is
> > straight forward because DAX devices do not yet have references to the
> > extents. Future patches will handle that complication.
> >
> > Signed-off-by: Ira Weiny <ira.weiny@...el.com>
> >
>
> A few trivial comments on this. Lot here so I'll take a closer look
> at some point after doing a light pass over the rest of the series.
>
I agree this is a lot. I thought about splitting the notification into 2
layers. Notify from device to CXL region then a separate patch from CXL
region to DAX region. In the end I channeled Dan and kept it all together
because without interleaving there is not much for the CXL region to do
but pass the notification up. So that patch would have been kind of
awkward.
>
>
>
> > diff --git a/drivers/cxl/mem.c b/drivers/cxl/mem.c
> > index 80cffa40e91a..d3c4c9c87392 100644
> > --- a/drivers/cxl/mem.c
> > +++ b/drivers/cxl/mem.c
> > @@ -104,6 +104,55 @@ static int cxl_debugfs_poison_clear(void *data, u64 dpa)
> > DEFINE_DEBUGFS_ATTRIBUTE(cxl_poison_clear_fops, NULL,
> > cxl_debugfs_poison_clear, "%llx\n");
> >
> > +static int match_ep_decoder_by_range(struct device *dev, void *data)
> > +{
> > + struct cxl_dc_extent_data *extent = data;
> > + struct cxl_endpoint_decoder *cxled;
> > +
> > + if (!is_endpoint_decoder(dev))
> > + return 0;
>
> blank line
Done.
>
> > + cxled = to_cxl_endpoint_decoder(dev);
> > + return cxl_dc_extent_in_ed(cxled, extent);
> > +}
> > +
> > +static struct cxl_endpoint_decoder *cxl_find_ed(struct cxl_memdev_state *mds,
> > + struct cxl_dc_extent_data *extent)
> > +{
> > + struct cxl_memdev *cxlmd = mds->cxlds.cxlmd;
> > + struct cxl_port *endpoint = cxlmd->endpoint;
> > + struct device *dev;
> > +
> > + dev = device_find_child(&endpoint->dev, extent,
> > + match_ep_decoder_by_range);
> > + if (!dev) {
> > + dev_dbg(mds->cxlds.dev, "Extent DPA:%llx LEN:%llx not mapped\n",
> > + extent->dpa_start, extent->length);
> > + return NULL;
> > + }
> > +
> > + return to_cxl_endpoint_decoder(dev);
> > +}
> > +
> > +static int cxl_mem_notify(struct device *dev, struct cxl_drv_nd *nd)
> > +{
> > + struct cxl_memdev *cxlmd = to_cxl_memdev(dev);
> > + struct cxl_memdev_state *mds = to_cxl_memdev_state(cxlmd->cxlds);
> > + struct cxl_endpoint_decoder *cxled;
> > + struct cxl_dc_extent_data *extent;
> > + int rc = 0;
> > +
> > + extent = nd->extent;
> > + dev_dbg(dev, "notify DC action %d DPA:%llx LEN:%llx\n",
> > + nd->event, extent->dpa_start, extent->length);
> > +
> > + cxled = cxl_find_ed(mds, extent);
> > + if (!cxled)
> > + return 0;
> Blank line.
Done.
>
> > + rc = cxl_ed_notify_extent(cxled, nd);
> > + put_device(&cxled->cxld.dev);
> > + return rc;
> > +}
> > +
> > static int cxl_mem_probe(struct device *dev)
> > {
> > struct cxl_memdev *cxlmd = to_cxl_memdev(dev);
> > @@ -247,6 +296,7 @@ __ATTRIBUTE_GROUPS(cxl_mem);
> > static struct cxl_driver cxl_mem_driver = {
> > .name = "cxl_mem",
> > .probe = cxl_mem_probe,
> > + .notify = cxl_mem_notify,
> > .id = CXL_DEVICE_MEMORY_EXPANDER,
> > .drv = {
> > .dev_groups = cxl_mem_groups,
> > diff --git a/drivers/dax/cxl.c b/drivers/dax/cxl.c
> > index 057b00b1d914..44cbd28668f1 100644
> > --- a/drivers/dax/cxl.c
> > +++ b/drivers/dax/cxl.c
> > @@ -59,6 +59,29 @@ static int cxl_dax_region_create_extent(struct dax_region *dax_region,
> > return 0;
> > }
> >
> > +static int cxl_dax_region_add_extent(struct cxl_dax_region *cxlr_dax,
> > + struct cxl_dr_extent *cxl_dr_ext)
> > +{
>
> Why not have this helper in the earlier patch that introduced the code
> this is factoring out? Will reduce churn in the set whilst not much hurting
> readability of that patch.
Because this logic appeared in only 1 place in that patch. Here we are
using this same logic 2x so it got factored out.
I see where you are coming from because this is a straight up copy of the
code. I'll go ahead and do that.
>
> > + /*
> > + * get not zero is important because this is racing with the
> > + * region driver which is racing with the memory device which
> > + * could be removing the extent at the same time.
> > + */
> > + if (cxl_dr_extent_get_not_zero(cxl_dr_ext)) {
> > + struct dax_region *dax_region;
> > + int rc;
> > +
> > + dax_region = dev_get_drvdata(&cxlr_dax->dev);
> > + dev_dbg(&cxlr_dax->dev, "Creating HPA:%llx LEN:%llx\n",
> > + cxl_dr_ext->hpa_offset, cxl_dr_ext->hpa_length);
> > + rc = cxl_dax_region_create_extent(dax_region, cxl_dr_ext);
> > + cxl_dr_extent_put(cxl_dr_ext);
> > + if (rc)
> > + return rc;
> > + }
> > + return 0;
> Perhaps flip logic
> if (!cxl_dr_extent_get_not_zero())
> return 0;
>
> etc to reduce the code indent.
That is ok. But in this case I do kind of like the indent. I'll change
it to your way because I think it is slightly better.
Done in the previous patch.
> > +}
> > +
> > static int cxl_dax_region_create_extents(struct cxl_dax_region *cxlr_dax)
> > {
> > struct cxl_dr_extent *cxl_dr_ext;
> > @@ -66,27 +89,68 @@ static int cxl_dax_region_create_extents(struct cxl_dax_region *cxlr_dax)
> >
> > dev_dbg(&cxlr_dax->dev, "Adding extents\n");
> > xa_for_each(&cxlr_dax->extents, index, cxl_dr_ext) {
> > - /*
> > - * get not zero is important because this is racing with the
> > - * region driver which is racing with the memory device which
> > - * could be removing the extent at the same time.
> > - */
> > - if (cxl_dr_extent_get_not_zero(cxl_dr_ext)) {
> > - struct dax_region *dax_region;
> > - int rc;
> > -
> > - dax_region = dev_get_drvdata(&cxlr_dax->dev);
> > - dev_dbg(&cxlr_dax->dev, "Found OFF:%llx LEN:%llx\n",
> > - cxl_dr_ext->hpa_offset, cxl_dr_ext->hpa_length);
> > - rc = cxl_dax_region_create_extent(dax_region, cxl_dr_ext);
> > - cxl_dr_extent_put(cxl_dr_ext);
> > - if (rc)
> > - return rc;
> > - }
> > + int rc;
> > +
> > + rc = cxl_dax_region_add_extent(cxlr_dax, cxl_dr_ext);
> > + if (rc)
> > + return rc;
> > }
> > return 0;
> > }
> >
> > +static int match_cxl_dr_extent(struct device *dev, void *data)
> > +{
> > + struct dax_reg_ext_dev *dr_reg_ext_dev;
> > + struct dax_region_extent *dr_extent;
> > +
> > + if (!is_dr_ext_dev(dev))
> > + return 0;
> > +
> > + dr_reg_ext_dev = to_dr_ext_dev(dev);
> > + dr_extent = dr_reg_ext_dev->dr_extent;
> > + return data == dr_extent->private_data;
> > +}
> > +
> > +static int cxl_dax_region_rm_extent(struct cxl_dax_region *cxlr_dax,
> > + struct cxl_dr_extent *cxl_dr_ext)
> > +{
> > + struct dax_reg_ext_dev *dr_reg_ext_dev;
> > + struct dax_region *dax_region;
> > + struct device *dev;
> > +
> > + dev = device_find_child(&cxlr_dax->dev, cxl_dr_ext,
> > + match_cxl_dr_extent);
> > + if (!dev)
> > + return -EINVAL;
>
> blank line.
Done.
>
> > + dr_reg_ext_dev = to_dr_ext_dev(dev);
> > + put_device(dev);
> > + dax_region = dev_get_drvdata(&cxlr_dax->dev);
> > + dax_region_ext_del_dev(dax_region, dr_reg_ext_dev);
> blank line
Done.
>
> > + return 0;
> > +}
> > +
> > +static int cxl_dax_region_notify(struct device *dev,
> > + struct cxl_drv_nd *nd)
> > +{
> > + struct cxl_dax_region *cxlr_dax = to_cxl_dax_region(dev);
> > + struct cxl_dr_extent *cxl_dr_ext = nd->cxl_dr_ext;
> > + int rc = 0;
> > +
> > + switch (nd->event) {
> > + case DCD_ADD_CAPACITY:
> > + rc = cxl_dax_region_add_extent(cxlr_dax, cxl_dr_ext);
> > + break;
>
> Early returns in here will perhaps make this more readable and definitely
> make it more compact.
Yep. done.
Thanks again for the review!
Ira
Powered by blists - more mailing lists