From: Dan Williams <dan.j.williams@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <nvdimm@lists.linux.dev>,
<linux-pci@vger.kernel.org>, <patches@lists.linux.dev>,
<hch@lst.de>, "Jason Gunthorpe" <jgg@nvidia.com>,
Matthew Wilcox <willy@infradead.org>,
"Christoph Hellwig" <hch@infradead.org>
Subject: Re: [PATCH 33/46] resource: Introduce alloc_free_mem_region()
Date: Sun, 10 Jul 2022 14:58:06 -0700 [thread overview]
Message-ID: <62cb4b6ed3efd_35351629463@dwillia2-xfh.notmuch> (raw)
In-Reply-To: <20220630113548.000036e8@Huawei.com>
Jonathan Cameron wrote:
> On Thu, 23 Jun 2022 21:19:37 -0700
> Dan Williams <dan.j.williams@intel.com> wrote:
>
> > The core of devm_request_free_mem_region() is a helper that searches for
> > free space in iomem_resource and performs __request_region_locked() on
> > the result of that search. The policy choices of the implementation
> > conform to what CONFIG_DEVICE_PRIVATE users want which is memory that is
> > immediately marked busy, and a preference to search for the first-fit
> > free range in descending order from the top of the physical address
> > space.
> >
> > CXL has a need for a similar allocator, but with the following tweaks:
> >
> > 1/ Search for free space in ascending order
> >
> > 2/ Search for free space relative to a given CXL window
> >
> > 3/ 'insert' rather than 'request' the new resource given downstream
> > drivers from the CXL Region driver (like the pmem or dax drivers) are
> > responsible for request_mem_region() when they activate the memory
> > range.
> >
> > Rework __request_free_mem_region() into get_free_mem_region() which
> > takes a set of GFR_* (Get Free Region) flags to control the allocation
> > policy (ascending vs descending), and "busy" policy (insert_resource()
> > vs request_region()).
> >
> > Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
> > Link: https://lore.kernel.org/linux-cxl/20220420143406.GY2120790@nvidia.com/
> > Cc: Matthew Wilcox <willy@infradead.org>
> > Cc: Christoph Hellwig <hch@infradead.org>
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>
> A few things inline,
>
> Thanks,
>
> Jonathan
>
> > ---
> > include/linux/ioport.h | 2 +
> > kernel/resource.c | 174 ++++++++++++++++++++++++++++++++---------
> > mm/Kconfig | 5 ++
> > 3 files changed, 146 insertions(+), 35 deletions(-)
> >
> > diff --git a/include/linux/ioport.h b/include/linux/ioport.h
> > index ec5f71f7135b..ed03518347aa 100644
> > --- a/include/linux/ioport.h
> > +++ b/include/linux/ioport.h
> > @@ -329,6 +329,8 @@ struct resource *devm_request_free_mem_region(struct device *dev,
> > struct resource *base, unsigned long size);
> > struct resource *request_free_mem_region(struct resource *base,
> > unsigned long size, const char *name);
> > +struct resource *alloc_free_mem_region(struct resource *base,
> > + unsigned long size, unsigned long align, const char *name);
> >
> > static inline void irqresource_disabled(struct resource *res, u32 irq)
> > {
> > diff --git a/kernel/resource.c b/kernel/resource.c
> > index 53a534db350e..9fc990274106 100644
> > --- a/kernel/resource.c
> > +++ b/kernel/resource.c
>
>
> > +static bool gfr_continue(struct resource *base, resource_size_t addr,
> > + resource_size_t size, unsigned long flags)
> > +{
> > + if (flags & GFR_DESCENDING)
> > + return addr > size && addr >= base->start;
> > + return addr > addr - size &&
>
> Is this checking for wrap around? If so maybe a comment to call that out?
Yes, and ok.
>
> > + addr <= min_t(resource_size_t, base->end,
> > + (1ULL << MAX_PHYSMEM_BITS) - 1);
> > +}
> > +
> > +static resource_size_t gfr_next(resource_size_t addr, resource_size_t size,
> > + unsigned long flags)
> > +{
> > + if (flags & GFR_DESCENDING)
> > + return addr - size;
> > + return addr + size;
> > +}
> > +
> > +static void remove_free_mem_region(void *_res)
> > {
> > - resource_size_t end, addr;
> > + struct resource *res = _res;
> > +
> > + if (res->parent)
> > + remove_resource(res);
> > + free_resource(res);
> > +}
> > +
> > +static struct resource *
> > +get_free_mem_region(struct device *dev, struct resource *base,
> > + resource_size_t size, const unsigned long align,
> > + const char *name, const unsigned long desc,
> > + const unsigned long flags)
> > +{
> > + resource_size_t addr;
> > struct resource *res;
> > struct region_devres *dr = NULL;
> >
> > - size = ALIGN(size, 1UL << PA_SECTION_SHIFT);
> > - end = min_t(unsigned long, base->end, (1UL << MAX_PHYSMEM_BITS) - 1);
> > - addr = end - size + 1UL;
> > + size = ALIGN(size, align);
> >
> > res = alloc_resource(GFP_KERNEL);
> > if (!res)
> > return ERR_PTR(-ENOMEM);
> >
> > - if (dev) {
> > + if (dev && (flags & GFR_REQUEST_REGION)) {
> > dr = devres_alloc(devm_region_release,
> > sizeof(struct region_devres), GFP_KERNEL);
> > if (!dr) {
> > free_resource(res);
> > return ERR_PTR(-ENOMEM);
> > }
> > + } else if (dev) {
> > + if (devm_add_action_or_reset(dev, remove_free_mem_region, res))
> > + return ERR_PTR(-ENOMEM);
>
> slightly nicer to return whatever value you got back from devm_add_action_or_reset()
Yes, but it is known to only return -ENOMEM on failure and saves adding
a local @rc variable.
>
> > }
> >
> > write_lock(&resource_lock);
> > - for (; addr > size && addr >= base->start; addr -= size) {
> > - if (__region_intersects(addr, size, 0, IORES_DESC_NONE) !=
> > - REGION_DISJOINT)
> > + for (addr = gfr_start(base, size, align, flags);
> > + gfr_continue(base, addr, size, flags);
> > + addr = gfr_next(addr, size, flags)) {
> > + if (__region_intersects(base, addr, size, 0, IORES_DESC_NONE) !=
> > + REGION_DISJOINT)
> > continue;
> >
> > - if (__request_region_locked(res, &iomem_resource, addr, size,
> > - name, 0))
> > - break;
> > + if (flags & GFR_REQUEST_REGION) {
> > + if (__request_region_locked(res, &iomem_resource, addr,
> > + size, name, 0))
> > + break;
> >
> > - if (dev) {
> > - dr->parent = &iomem_resource;
> > - dr->start = addr;
> > - dr->n = size;
> > - devres_add(dev, dr);
> > - }
> > + if (dev) {
> > + dr->parent = &iomem_resource;
> > + dr->start = addr;
> > + dr->n = size;
> > + devres_add(dev, dr);
> > + }
> >
> > - res->desc = IORES_DESC_DEVICE_PRIVATE_MEMORY;
> > - write_unlock(&resource_lock);
> > + res->desc = desc;
> > + write_unlock(&resource_lock);
> > +
> > +
> > + /*
> > + * A driver is claiming this region so revoke any
> > + * mappings.
> > + */
> > + revoke_iomem(res);
> > + } else {
> > + res->start = addr;
> > + res->end = addr + size - 1;
> > + res->name = name;
> > + res->desc = desc;
> > + res->flags = IORESOURCE_MEM;
> > +
> > + /*
> > + * Only succeed if the resource hosts an exclusive
> > + * range after the insert
> > + */
> > + if (__insert_resource(base, res) || res->child)
> > + break;
> > +
> > + write_unlock(&resource_lock);
> > + }
> >
> > - /*
> > - * A driver is claiming this region so revoke any mappings.
> > - */
> > - revoke_iomem(res);
> > return res;
> > }
> > write_unlock(&resource_lock);
> >
> > - free_resource(res);
> > - if (dr)
> > + if (flags & GFR_REQUEST_REGION) {
> > + free_resource(res);
> > devres_free(dr);
>
> The original if (dr) was unnecessary as devres_free() checks.
>
> Looking just at this patch it looks like you aren't covering the
> corner case of dev == NULL and GFR_REQUEST_REGION.
>
> Perhaps worth a tiny comment in patch description? (doesn't seem worth
> pulling this change out as a precursor given it's so small).
> Of add the extra if (dr) back in to 'document' that no change...
Added to the changelog:
As part of the consolidation of the legacy GFR_REQUEST_REGION case with
the new default of just inserting a new resource into the free space
some minor cleanups like not checking for NULL before calling
devres_free() (which does its own check) is included.
>
>
> > + } else if (dev)
> > + devm_release_action(dev, remove_free_mem_region, res);
> >
> > return ERR_PTR(-ERANGE);
> > }
> > @@ -1854,18 +1928,48 @@ static struct resource *__request_free_mem_region(struct device *dev,
> > struct resource *devm_request_free_mem_region(struct device *dev,
> > struct resource *base, unsigned long size)
> > {
> > - return __request_free_mem_region(dev, base, size, dev_name(dev));
> > + unsigned long flags = GFR_DESCENDING | GFR_REQUEST_REGION;
> > +
> > + return get_free_mem_region(dev, base, size, GFR_DEFAULT_ALIGN,
> > + dev_name(dev),
> > + IORES_DESC_DEVICE_PRIVATE_MEMORY, flags);
> > }
> > EXPORT_SYMBOL_GPL(devm_request_free_mem_region);
> >
> > struct resource *request_free_mem_region(struct resource *base,
> > unsigned long size, const char *name)
> > {
> > - return __request_free_mem_region(NULL, base, size, name);
> > + unsigned long flags = GFR_DESCENDING | GFR_REQUEST_REGION;
> > +
> > + return get_free_mem_region(NULL, base, size, GFR_DEFAULT_ALIGN, name,
> > + IORES_DESC_DEVICE_PRIVATE_MEMORY, flags);
> > }
> > EXPORT_SYMBOL_GPL(request_free_mem_region);
> >
> > -#endif /* CONFIG_DEVICE_PRIVATE */
> > +/**
> > + * alloc_free_mem_region - find a free region relative to @base
> > + * @base: resource that will parent the new resource
> > + * @size: size in bytes of memory to allocate from @base
> > + * @align: alignment requirements for the allocation
> > + * @name: resource name
> > + *
> > + * Buses like CXL, that can dynamically instantiate new memory regions,
> > + * need a method to allocate physical address space for those regions.
> > + * Allocate and insert a new resource to cover a free, unclaimed by a
> > + * descendant of @base, range in the span of @base.
> > + */
> > +struct resource *alloc_free_mem_region(struct resource *base,
> Given the extra align parameter, does it make sense to give this a naming
> that highlights that vs the other two interfaces above?
>
> alloc_free_mem_region_aligned()
The other variants are also aligned, they just aren't variably aligned,
they are implicitly aligned to GFR_DEFAULT_ALIGN. So I think calling
this one _aligned() betrays what is happening in the other cases.
> > + unsigned long size, unsigned long align,
> > + const char *name)
> > +{
> > + /* GFR_ASCENDING | GFR_INSERT_RESOURCE */
>
> Given those flags don't exist and some fool like me might grep for them
> perhaps better to describe it in text
>
> /* Default of ascending direction and insert resource */
Ok.
next prev parent reply other threads:[~2022-07-10 21:58 UTC|newest]
Thread overview: 157+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 2:45 [PATCH 00/46] CXL PMEM Region Provisioning Dan Williams
2022-06-24 2:45 ` [PATCH 01/46] tools/testing/cxl: Fix cxl_hdm_decode_init() calling convention Dan Williams
2022-06-28 10:37 ` Jonathan Cameron
[not found] ` <CGME20220629174147uscas1p211384ae262e099484440ef285be26c75@uscas1p2.samsung.com>
2022-06-29 17:41 ` Adam Manzanares
2022-07-09 20:06 ` Dan Williams
2022-07-12 22:11 ` Adam Manzanares
2022-06-24 2:45 ` [PATCH 02/46] cxl/port: Keep port->uport valid for the entire life of a port Dan Williams
2022-06-24 3:37 ` Alison Schofield
2022-06-28 11:47 ` Jonathan Cameron
2022-06-28 14:27 ` Dan Williams
[not found] ` <CGME20220629174622uscas1p2236a084ce25771a3ab57c6f006632f35@uscas1p2.samsung.com>
2022-06-29 17:46 ` Adam Manzanares
2022-06-24 2:45 ` [PATCH 03/46] cxl/hdm: Use local hdm variable Dan Williams
2022-06-24 3:38 ` Alison Schofield
2022-06-28 15:16 ` Jonathan Cameron
[not found] ` <CGME20220629200312uscas1p292303b9325dcbfe59293f002dc9e6b03@uscas1p2.samsung.com>
2022-06-29 20:03 ` Adam Manzanares
2022-06-24 2:45 ` [PATCH 04/46] cxl/core: Rename ->decoder_range ->hpa_range Dan Williams
2022-06-24 3:39 ` Alison Schofield
2022-06-28 15:17 ` Jonathan Cameron
[not found] ` <CGME20220629200652uscas1p2c1da644ea63a5de69e14e046379779b1@uscas1p2.samsung.com>
2022-06-29 20:06 ` Adam Manzanares
2022-06-24 2:45 ` [PATCH 05/46] cxl/core: Drop ->platform_res attribute for root decoders Dan Williams
2022-06-28 15:24 ` Jonathan Cameron
2022-07-09 23:33 ` Dan Williams
[not found] ` <CGME20220629202117uscas1p2892fb68ae60c4754e2f7d26882a92ae5@uscas1p2.samsung.com>
2022-06-29 20:21 ` Adam Manzanares
2022-07-09 23:38 ` Dan Williams
2022-06-24 2:45 ` [PATCH 06/46] cxl/core: Drop is_cxl_decoder() Dan Williams
2022-06-24 3:48 ` Alison Schofield
2022-06-28 15:25 ` Jonathan Cameron
[not found] ` <CGME20220629203448uscas1p264a7f79a1ed7f9257eefcb3064c7d943@uscas1p2.samsung.com>
2022-06-29 20:34 ` Adam Manzanares
2022-06-24 2:45 ` [PATCH 07/46] cxl: Introduce cxl_to_{ways,granularity} Dan Williams
2022-06-28 15:36 ` Jonathan Cameron
2022-07-09 23:52 ` Dan Williams
2022-06-24 2:45 ` [PATCH 08/46] cxl/core: Define a 'struct cxl_switch_decoder' Dan Williams
2022-06-28 16:12 ` Jonathan Cameron
2022-06-30 10:56 ` Jonathan Cameron
2022-07-10 0:49 ` Dan Williams
2022-07-10 0:33 ` Dan Williams
2022-06-24 2:46 ` [PATCH 09/46] cxl/acpi: Track CXL resources in iomem_resource Dan Williams
2022-06-28 16:43 ` Jonathan Cameron
2022-07-10 2:12 ` Dan Williams
2022-07-19 14:24 ` Jonathan Cameron
2022-06-24 2:46 ` [PATCH 10/46] cxl/core: Define a 'struct cxl_root_decoder' for tracking CXL window resources Dan Williams
2022-06-28 16:49 ` Jonathan Cameron
2022-07-10 2:20 ` Dan Williams
2022-06-28 16:53 ` Jonathan Cameron
2022-06-24 2:46 ` [PATCH 11/46] cxl/core: Define a 'struct cxl_endpoint_decoder' for tracking DPA resources Dan Williams
2022-06-28 16:55 ` Jonathan Cameron
2022-07-10 2:40 ` Dan Williams
2022-06-24 2:46 ` [PATCH 12/46] cxl/mem: Convert partition-info to resources Dan Williams
2022-06-28 17:02 ` Jonathan Cameron
2022-06-24 2:46 ` [PATCH 13/46] cxl/hdm: Require all decoders to be enumerated Dan Williams
2022-06-28 17:04 ` Jonathan Cameron
2022-06-24 2:46 ` [PATCH 14/46] cxl/hdm: Enumerate allocated DPA Dan Williams
2022-06-29 14:43 ` Jonathan Cameron
2022-07-10 3:03 ` Dan Williams
2022-07-19 14:25 ` Jonathan Cameron
2022-06-24 2:46 ` [PATCH 15/46] cxl/Documentation: List attribute permissions Dan Williams
2022-06-28 3:16 ` Alison Schofield
2022-06-29 14:59 ` Jonathan Cameron
2022-06-24 2:46 ` [PATCH 16/46] cxl/hdm: Add 'mode' attribute to decoder objects Dan Williams
2022-06-29 15:28 ` Jonathan Cameron
2022-07-10 3:45 ` Dan Williams
2022-06-24 2:47 ` [PATCH 17/46] cxl/hdm: Track next decoder to allocate Dan Williams
2022-06-29 15:31 ` Jonathan Cameron
2022-07-10 3:55 ` Dan Williams
2022-07-19 14:27 ` Jonathan Cameron
2022-07-10 16:34 ` Dan Williams
2022-06-24 2:47 ` [PATCH 18/46] cxl/hdm: Add support for allocating DPA to an endpoint decoder Dan Williams
2022-06-29 15:56 ` Jonathan Cameron
2022-07-10 16:53 ` Dan Williams
2022-06-24 2:47 ` [PATCH 19/46] cxl/debug: Move debugfs init to cxl_core_init() Dan Williams
2022-06-29 15:58 ` Jonathan Cameron
2022-06-24 2:47 ` [PATCH 20/46] cxl/mem: Add a debugfs version of 'iomem' for DPA, 'dpamem' Dan Williams
2022-06-29 16:08 ` Jonathan Cameron
2022-07-10 17:09 ` Dan Williams
2022-06-24 2:47 ` [PATCH 21/46] tools/testing/cxl: Move cxl_test resources to the top of memory Dan Williams
2022-06-29 16:11 ` Jonathan Cameron
2022-07-10 17:19 ` Dan Williams
2022-06-24 2:47 ` [PATCH 22/46] tools/testing/cxl: Expand CFMWS windows Dan Williams
2022-06-29 16:14 ` Jonathan Cameron
2022-06-24 2:47 ` [PATCH 23/46] tools/testing/cxl: Add partition support Dan Williams
2022-06-29 16:20 ` Jonathan Cameron
2022-06-24 2:48 ` [PATCH 24/46] tools/testing/cxl: Fix decoder default state Dan Williams
2022-06-29 16:22 ` Jonathan Cameron
2022-07-10 17:33 ` Dan Williams
2022-06-24 2:48 ` [PATCH 25/46] cxl/port: Record dport in endpoint references Dan Williams
2022-06-29 16:49 ` Jonathan Cameron
2022-07-10 18:40 ` Dan Williams
2022-06-24 4:19 ` [PATCH 26/46] cxl/port: Record parent dport when adding ports Dan Williams
2022-06-29 17:02 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 27/46] cxl/port: Move 'cxl_ep' references to an xarray per port Dan Williams
2022-06-29 17:19 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 28/46] cxl/port: Move dport tracking to an xarray Dan Williams
2022-06-30 9:18 ` Jonathan Cameron
2022-07-10 19:06 ` Dan Williams
2022-06-24 4:19 ` [PATCH 29/46] cxl/port: Cache CXL host bridge data Dan Williams
2022-06-30 9:21 ` Jonathan Cameron
2022-07-10 19:09 ` Dan Williams
2022-06-24 4:19 ` [PATCH 30/46] cxl/hdm: Add sysfs attributes for interleave ways + granularity Dan Williams
2022-06-30 9:26 ` Jonathan Cameron
2022-07-10 20:40 ` Dan Williams
2022-07-19 14:32 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 31/46] cxl/hdm: Initialize decoder type for memory expander devices Dan Williams
2022-06-30 9:33 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 32/46] cxl/mem: Enumerate port targets before adding endpoints Dan Williams
2022-06-30 9:48 ` Jonathan Cameron
2022-07-10 21:01 ` Dan Williams
2022-06-24 4:19 ` [PATCH 33/46] resource: Introduce alloc_free_mem_region() Dan Williams
2022-06-30 10:35 ` Jonathan Cameron
2022-07-10 21:58 ` Dan Williams [this message]
2022-06-24 4:19 ` [PATCH 34/46] cxl/region: Add region creation support Dan Williams
2022-06-30 13:17 ` Jonathan Cameron
2022-07-11 0:08 ` Dan Williams
2022-07-19 14:42 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 35/46] cxl/region: Add a 'uuid' attribute Dan Williams
2022-06-28 10:29 ` Jonathan Cameron
2022-06-28 14:24 ` Dan Williams
2022-06-24 4:19 ` [PATCH 36/46] cxl/region: Add interleave ways attribute Dan Williams
2022-06-30 13:44 ` Jonathan Cameron
2022-07-11 0:32 ` Dan Williams
2022-07-19 14:47 ` Jonathan Cameron
2022-07-19 22:15 ` Dan Williams
2022-07-20 9:59 ` Jonathan Cameron
2022-06-30 13:45 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 37/46] cxl/region: Allocate host physical address (HPA) capacity to new regions Dan Williams
2022-06-30 13:56 ` Jonathan Cameron
2022-07-11 0:47 ` Dan Williams
2022-06-24 4:19 ` [PATCH 38/46] cxl/region: Enable the assignment of endpoint decoders to regions Dan Williams
2022-06-30 14:31 ` Jonathan Cameron
2022-07-11 1:12 ` Dan Williams
2022-06-24 4:19 ` [PATCH 39/46] cxl/acpi: Add a host-bridge index lookup mechanism Dan Williams
2022-06-30 15:48 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 40/46] cxl/region: Attach endpoint decoders Dan Williams
2022-06-24 18:25 ` Jonathan Cameron
2022-06-24 18:49 ` Dan Williams
2022-06-24 20:51 ` Dan Williams
2022-06-24 23:21 ` Dan Williams
2022-06-30 16:34 ` Jonathan Cameron
2022-07-11 2:02 ` Dan Williams
2022-06-24 4:19 ` [PATCH 41/46] cxl/region: Program target lists Dan Williams
2022-06-24 4:19 ` [PATCH 42/46] cxl/hdm: Commit decoder state to hardware Dan Williams
2022-06-30 17:05 ` Jonathan Cameron
2022-07-11 3:02 ` Dan Williams
2022-06-24 4:19 ` [PATCH 43/46] cxl/region: Add region driver boiler plate Dan Williams
2022-06-30 17:09 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 44/46] cxl/pmem: Delete unused nvdimm attribute Dan Williams
2022-06-30 17:10 ` Jonathan Cameron
2022-06-24 4:19 ` [PATCH 45/46] cxl/pmem: Fix offline_nvdimm_bus() to offline by bridge Dan Williams
2022-06-30 17:14 ` Jonathan Cameron
2022-07-11 19:49 ` Dan Williams
2022-06-24 4:19 ` [PATCH 46/46] cxl/region: Introduce cxl_pmem_region objects Dan Williams
2022-06-30 17:34 ` Jonathan Cameron
2022-07-11 20:05 ` Dan Williams
2022-06-24 15:13 ` [PATCH 00/46] CXL PMEM Region Provisioning Jonathan Cameron
2022-06-24 15:32 ` Dan Williams
2022-06-28 3:12 ` Alison Schofield
2022-06-28 3:34 ` Dan Williams
2022-07-02 2:26 ` Alison Schofield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62cb4b6ed3efd_35351629463@dwillia2-xfh.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=patches@lists.linux.dev \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).