From: Fan Ni <nifan.cxl@gmail.com>
To: ira.weiny@intel.com
Cc: Ira Weiny <ira.weiny@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Navneet Singh <navneet.singh@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
linux-btrfs@vger.kernel.org, linux-cxl@vger.kernel.org,
linux-doc@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
"Li, Ming" <ming4.li@intel.com>,
Robert Moore <robert.moore@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev
Subject: Re: [PATCH v4 00/28] DCD: Add support for Dynamic Capacity Devices (DCD)
Date: Tue, 8 Oct 2024 16:06:59 -0700 [thread overview]
Message-ID: <ZwW7E2gSUM8SHAzo@fan> (raw)
In-Reply-To: <ZwW4yQ11wYkaqdgx@fan>
On Tue, Oct 08, 2024 at 03:57:13PM -0700, Fan Ni wrote:
> On Mon, Oct 07, 2024 at 06:16:06PM -0500, Ira Weiny wrote:
> > A git tree of this series can be found here:
> >
> > https://github.com/weiny2/linux-kernel/tree/dcd-v4-2024-10-04
> >
> > Series info
> > ===========
> >
>
> Hi Ira,
>
> Based on current DC extent release logic, when the extent to release is
> in use (for example, created a dax device), no response (4803h) will be sent.
> Should we send a response with empty extent list instead?
>
> Fan
Oh. my bad. 4803h does not allow an empty extent list.
Fan
>
>
> > This series has 5 parts:
> >
> > Patch 1-3: Add %pra printk format for struct range
> > Patch 4: Add core range_overlaps() function
> > Patch 5-6: CXL clean up/prelim patches
> > Patch 7-26: Core DCD support
> > Patch 27-28: cxl_test support
> >
> > Background
> > ==========
> >
> > A Dynamic Capacity Device (DCD) (CXL 3.1 sec 9.13.3) is a CXL memory
> > device that allows memory capacity within a region to change
> > dynamically without the need for resetting the device, reconfiguring
> > HDM decoders, or reconfiguring software DAX regions.
> >
> > One of the biggest use cases for Dynamic Capacity is to allow hosts to
> > share memory dynamically within a data center without increasing the
> > per-host attached memory.
> >
> > The general flow for the addition or removal of memory is to have an
> > orchestrator coordinate the use of the memory. Generally there are 5
> > actors in such a system, the Orchestrator, Fabric Manager, the Logical
> > device, the Host Kernel, and a Host User.
> >
> > Typical work flows are shown below.
> >
> > Orchestrator FM Device Host Kernel Host User
> >
> > | | | | |
> > |-------------- Create region ----------------------->|
> > | | | | |
> > | | | |<-- Create ---|
> > | | | | Region |
> > |<------------- Signal done --------------------------|
> > | | | | |
> > |-- Add ----->|-- Add --->|--- Add --->| |
> > | Capacity | Extent | Extent | |
> > | | | | |
> > | |<- Accept -|<- Accept -| |
> > | | Extent | Extent | |
> > | | | |<- Create --->|
> > | | | | DAX dev |-- Use memory
> > | | | | | |
> > | | | | | |
> > | | | |<- Release ---| <-+
> > | | | | DAX dev |
> > | | | | |
> > |<------------- Signal done --------------------------|
> > | | | | |
> > |-- Remove -->|- Release->|- Release ->| |
> > | Capacity | Extent | Extent | |
> > | | | | |
> > | |<- Release-|<- Release -| |
> > | | Extent | Extent | |
> > | | | | |
> > |-- Add ----->|-- Add --->|--- Add --->| |
> > | Capacity | Extent | Extent | |
> > | | | | |
> > | |<- Accept -|<- Accept -| |
> > | | Extent | Extent | |
> > | | | |<- Create ----|
> > | | | | DAX dev |-- Use memory
> > | | | | | |
> > | | | |<- Release ---| <-+
> > | | | | DAX dev |
> > |<------------- Signal done --------------------------|
> > | | | | |
> > |-- Remove -->|- Release->|- Release ->| |
> > | Capacity | Extent | Extent | |
> > | | | | |
> > | |<- Release-|<- Release -| |
> > | | Extent | Extent | |
> > | | | | |
> > |-- Add ----->|-- Add --->|--- Add --->| |
> > | Capacity | Extent | Extent | |
> > | | | |<- Create ----|
> > | | | | DAX dev |-- Use memory
> > | | | | | |
> > |-- Remove -->|- Release->|- Release ->| | |
> > | Capacity | Extent | Extent | | |
> > | | | | | |
> > | | | (Release Ignored) | |
> > | | | | | |
> > | | | |<- Release ---| <-+
> > | | | | DAX dev |
> > |<------------- Signal done --------------------------|
> > | | | | |
> > | |- Release->|- Release ->| |
> > | | Extent | Extent | |
> > | | | | |
> > | |<- Release-|<- Release -| |
> > | | Extent | Extent | |
> > | | | |<- Destroy ---|
> > | | | | Region |
> > | | | | |
> >
> > Implementation
> > ==============
> >
> > The series still requires the creation of regions and DAX devices to be
> > closely synchronized with the Orchestrator and Fabric Manager. The host
> > kernel will reject extents if a region is not yet created. It also
> > ignores extent release if memory is in use (DAX device created). These
> > synchronizations are not anticipated to be an issue with real
> > applications.
> >
> > In order to allow for capacity to be added and removed a new concept of
> > a sparse DAX region is introduced. A sparse DAX region may have 0 or
> > more bytes of available space. The total space depends on the number
> > and size of the extents which have been added.
> >
> > Initially it is anticipated that users of the memory will carefully
> > coordinate the surfacing of additional capacity with the creation of DAX
> > devices which use that capacity. Therefore, the allocation of the
> > memory to DAX devices does not allow for specific associations between
> > DAX device and extent. This keeps allocations very similar to existing
> > DAX region behavior.
> >
> > To keep the DAX memory allocation aligned with the existing DAX devices
> > which do not have tags extents are not allowed to have tags. Future
> > support for tags is planned.
> >
> > Great care was taken to keep the extent tracking simple. Some xarray's
> > needed to be added but extra software objects were kept to a minimum.
> >
> > Region extents continue to be tracked as sub-devices of the DAX region.
> > This ensures that region destruction cleans up all extent allocations
> > properly.
> >
> > Some review tags were kept if a patch did not change.
> >
> > The major functionality of this series includes:
> >
> > - Getting the dynamic capacity (DC) configuration information from cxl
> > devices
> >
> > - Configuring the DC partitions reported by hardware
> >
> > - Enhancing the CXL and DAX regions for dynamic capacity support
> > a. Maintain a logical separation between hardware extents and
> > software managed region extents. This provides an
> > abstraction between the layers and should allow for
> > interleaving in the future
> >
> > - Get hardware extent lists for endpoint decoders upon
> > region creation.
> >
> > - Adjust extent/region memory available on the following events.
> > a. Add capacity Events
> > b. Release capacity events
> >
> > - Host response for add capacity
> > a. do not accept the extent if:
> > If the region does not exist
> > or an error occurs realizing the extent
> > b. If the region does exist
> > realize a DAX region extent with 1:1 mapping (no
> > interleave yet)
> > c. Support the event more bit by processing a list of extents
> > marked with the more bit together before setting up a
> > response.
> >
> > - Host response for remove capacity
> > a. If no DAX device references the extent; release the extent
> > b. If a reference does exist, ignore the request.
> > (Require FM to issue release again.)
> >
> > - Modify DAX device creation/resize to account for extents within a
> > sparse DAX region
> >
> > - Trace Dynamic Capacity events for debugging
> >
> > - Add cxl-test infrastructure to allow for faster unit testing
> > (See new ndctl branch for cxl-dcd.sh test[1])
> >
> > - Only support 0 value extent tags
> >
> > Fan Ni's upstream of Qemu DCD was used for testing.
> >
> > Remaining work:
> >
> > 1) Allow mapping to specific extents (perhaps based on
> > label/tag)
> > 1a) devise region size reporting based on tags
> > 2) Interleave support
> >
> > Possible additional work depending on requirements:
> >
> > 1) Accept a new extent which extends (but overlaps) an existing
> > extent(s)
> > 2) Release extents when DAX devices are released if a release
> > was previously seen from the device
> > 3) Rework DAX device interfaces, memfd has been explored a bit
> >
> > [1] https://github.com/weiny2/ndctl/tree/dcd-region2-2024-10-01
> >
> > ---
> > Major changes in v4:
> > - iweiny: rebase to 6.12-rc
> > - iweiny: Add qos data to regions
> > - Jonathan: Fix up shared region detection
> > - Jonathan/jgroves/djbw/iweiny: Ignore 0 value tags
> > - iweiny: Change DCD partition sysfs entries to allow for qos class and
> > additional parameters per partition
> > - Petr/Andy: s/%par/%pra/
> > - Andy: Share logic between printing struct resource and struct range
> > - Link to v3: https://patch.msgid.link/20240816-dcd-type2-upstream-v3-0-7c9b96cba6d7@intel.com
> >
> > ---
> > Ira Weiny (14):
> > test printk: Add very basic struct resource tests
> > printk: Add print format (%pra) for struct range
> > cxl/cdat: Use %pra for dpa range outputs
> > range: Add range_overlaps()
> > dax: Document dax dev range tuple
> > cxl/pci: Delay event buffer allocation
> > cxl/cdat: Gather DSMAS data for DCD regions
> > cxl/region: Refactor common create region code
> > cxl/events: Split event msgnum configuration from irq setup
> > cxl/pci: Factor out interrupt policy check
> > cxl/core: Return endpoint decoder information from region search
> > dax/bus: Factor out dev dax resize logic
> > tools/testing/cxl: Make event logs dynamic
> > tools/testing/cxl: Add DC Regions to mock mem data
> >
> > Navneet Singh (14):
> > cxl/mbox: Flag support for Dynamic Capacity Devices (DCD)
> > cxl/mem: Read dynamic capacity configuration from the device
> > cxl/core: Separate region mode from decoder mode
> > cxl/region: Add dynamic capacity decoder and region modes
> > cxl/hdm: Add dynamic capacity size support to endpoint decoders
> > cxl/mem: Expose DCD partition capabilities in sysfs
> > cxl/port: Add endpoint decoder DC mode support to sysfs
> > cxl/region: Add sparse DAX region support
> > cxl/mem: Configure dynamic capacity interrupts
> > cxl/extent: Process DCD events and realize region extents
> > cxl/region/extent: Expose region extent information in sysfs
> > dax/region: Create resources on sparse DAX regions
> > cxl/region: Read existing extents on region creation
> > cxl/mem: Trace Dynamic capacity Event Record
> >
> > Documentation/ABI/testing/sysfs-bus-cxl | 120 +++-
> > Documentation/core-api/printk-formats.rst | 13 +
> > drivers/cxl/core/Makefile | 2 +-
> > drivers/cxl/core/cdat.c | 52 +-
> > drivers/cxl/core/core.h | 33 +-
> > drivers/cxl/core/extent.c | 486 +++++++++++++++
> > drivers/cxl/core/hdm.c | 213 ++++++-
> > drivers/cxl/core/mbox.c | 605 ++++++++++++++++++-
> > drivers/cxl/core/memdev.c | 130 +++-
> > drivers/cxl/core/port.c | 13 +-
> > drivers/cxl/core/region.c | 170 ++++--
> > drivers/cxl/core/trace.h | 65 ++
> > drivers/cxl/cxl.h | 122 +++-
> > drivers/cxl/cxlmem.h | 131 +++-
> > drivers/cxl/pci.c | 123 +++-
> > drivers/dax/bus.c | 352 +++++++++--
> > drivers/dax/bus.h | 4 +-
> > drivers/dax/cxl.c | 72 ++-
> > drivers/dax/dax-private.h | 47 +-
> > drivers/dax/hmem/hmem.c | 2 +-
> > drivers/dax/pmem.c | 2 +-
> > fs/btrfs/ordered-data.c | 10 +-
> > include/acpi/actbl1.h | 2 +
> > include/cxl/event.h | 32 +
> > include/linux/range.h | 7 +
> > lib/test_printf.c | 70 +++
> > lib/vsprintf.c | 55 +-
> > tools/testing/cxl/Kbuild | 3 +-
> > tools/testing/cxl/test/mem.c | 960 ++++++++++++++++++++++++++----
> > 29 files changed, 3576 insertions(+), 320 deletions(-)
> > ---
> > base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
> > change-id: 20230604-dcd-type2-upstream-0cd15f6216fd
> >
> > Best regards,
> > --
> > Ira Weiny <ira.weiny@intel.com>
> >
>
> --
> Fan Ni
--
Fan Ni
next prev parent reply other threads:[~2024-10-08 23:07 UTC|newest]
Thread overview: 134+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 23:16 [PATCH v4 00/28] DCD: Add support for Dynamic Capacity Devices (DCD) Ira Weiny
2024-10-07 23:16 ` [PATCH v4 01/28] test printk: Add very basic struct resource tests Ira Weiny
2024-10-08 16:35 ` Andy Shevchenko
2024-10-09 12:24 ` Jonathan Cameron
2024-10-09 17:09 ` Fan Ni
2024-10-10 14:59 ` Petr Mladek
2024-10-11 14:49 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 02/28] printk: Add print format (%pra) for struct range Ira Weiny
2024-10-08 16:56 ` Andy Shevchenko
2024-10-09 12:27 ` Jonathan Cameron
2024-10-09 14:42 ` Andy Shevchenko
2024-10-09 13:30 ` Rasmus Villemoes
2024-10-09 14:41 ` Andy Shevchenko
2024-10-14 0:08 ` Ira Weiny
2024-10-11 16:54 ` Ira Weiny
2024-10-09 17:33 ` Fan Ni
2024-10-11 2:09 ` Bagas Sanjaya
2024-10-17 20:57 ` Ira Weiny
2024-10-25 12:42 ` Bagas Sanjaya
2024-10-07 23:16 ` [PATCH v4 03/28] cxl/cdat: Use %pra for dpa range outputs Ira Weiny
2024-10-09 12:33 ` Jonathan Cameron
2024-10-09 17:34 ` Fan Ni
2024-10-07 23:16 ` [PATCH v4 04/28] range: Add range_overlaps() Ira Weiny
2024-10-08 16:10 ` David Sterba
2024-10-09 14:45 ` Andy Shevchenko
2024-10-09 14:46 ` Andy Shevchenko
2024-10-14 0:12 ` Ira Weiny
2024-10-09 15:36 ` David Sterba
2024-10-09 16:04 ` Andy Shevchenko
2024-10-10 15:24 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 05/28] dax: Document dax dev range tuple Ira Weiny
2024-10-09 12:42 ` Jonathan Cameron
2024-10-11 20:40 ` Ira Weiny
2024-10-16 15:48 ` Jonathan Cameron
2024-10-07 23:16 ` [PATCH v4 06/28] cxl/pci: Delay event buffer allocation Ira Weiny
2024-10-09 17:47 ` Fan Ni
2024-10-07 23:16 ` [PATCH v4 07/28] cxl/mbox: Flag support for Dynamic Capacity Devices (DCD) ira.weiny
2024-10-07 23:16 ` [PATCH v4 08/28] cxl/mem: Read dynamic capacity configuration from the device ira.weiny
2024-10-09 12:49 ` Jonathan Cameron
2024-10-14 0:05 ` Ira Weiny
2024-10-16 15:54 ` Jonathan Cameron
2024-10-16 16:59 ` Kees Cook
2024-10-07 23:16 ` [PATCH v4 09/28] cxl/core: Separate region mode from decoder mode ira.weiny
2024-10-09 12:51 ` Jonathan Cameron
2024-10-09 18:06 ` Fan Ni
2024-10-07 23:16 ` [PATCH v4 10/28] cxl/region: Add dynamic capacity decoder and region modes ira.weiny
2024-10-07 23:16 ` [PATCH v4 11/28] cxl/hdm: Add dynamic capacity size support to endpoint decoders ira.weiny
2024-10-10 12:45 ` Jonathan Cameron
2024-10-07 23:16 ` [PATCH v4 12/28] cxl/cdat: Gather DSMAS data for DCD regions Ira Weiny
2024-10-09 14:42 ` Rafael J. Wysocki
2024-10-11 20:38 ` Ira Weiny
2024-10-14 20:52 ` Wysocki, Rafael J
2024-10-09 18:16 ` Fan Ni
2024-10-14 1:16 ` Ira Weiny
2024-10-10 12:51 ` Jonathan Cameron
2024-10-07 23:16 ` [PATCH v4 13/28] cxl/mem: Expose DCD partition capabilities in sysfs ira.weiny
2024-10-09 20:46 ` Fan Ni
2024-10-14 1:34 ` Ira Weiny
2024-10-10 13:04 ` Jonathan Cameron
2024-10-16 21:34 ` Ira Weiny
2024-10-11 2:15 ` Bagas Sanjaya
2024-10-07 23:16 ` [PATCH v4 14/28] cxl/port: Add endpoint decoder DC mode support to sysfs ira.weiny
2024-10-10 13:14 ` Jonathan Cameron
2024-10-17 17:51 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 15/28] cxl/region: Refactor common create region code Ira Weiny
2024-10-10 13:18 ` Jonathan Cameron
2024-10-17 20:29 ` Ira Weiny
2024-10-10 16:27 ` Fan Ni
2024-10-24 2:17 ` Alison Schofield
2024-10-07 23:16 ` [PATCH v4 16/28] cxl/region: Add sparse DAX region support ira.weiny
2024-10-10 13:46 ` Jonathan Cameron
2024-10-10 17:41 ` Fan Ni
2024-10-07 23:16 ` [PATCH v4 17/28] cxl/events: Split event msgnum configuration from irq setup Ira Weiny
2024-10-10 13:49 ` Jonathan Cameron
2024-10-10 17:58 ` Fan Ni
2024-10-24 2:33 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 18/28] cxl/pci: Factor out interrupt policy check Ira Weiny
2024-10-10 18:07 ` Fan Ni
2024-10-07 23:16 ` [PATCH v4 19/28] cxl/mem: Configure dynamic capacity interrupts ira.weiny
2024-10-10 14:15 ` Jonathan Cameron
2024-10-10 18:25 ` Fan Ni
2024-10-24 3:09 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 20/28] cxl/core: Return endpoint decoder information from region search Ira Weiny
2024-10-10 14:21 ` Jonathan Cameron
2024-10-10 18:29 ` Fan Ni
2024-10-24 2:30 ` Alison Schofield
2024-10-07 23:16 ` [PATCH v4 21/28] cxl/extent: Process DCD events and realize region extents ira.weiny
2024-10-09 1:56 ` Li, Ming4
2024-10-09 19:49 ` Ira Weiny
2024-10-10 3:06 ` Li, Ming4
2024-10-14 2:05 ` Ira Weiny
2024-10-10 14:50 ` Jonathan Cameron
2024-10-11 19:14 ` Fan Ni
2024-10-17 21:15 ` Ira Weiny
2024-10-18 9:03 ` Jonathan Cameron
2024-10-21 14:04 ` Ira Weiny
2024-10-21 14:47 ` Jonathan Cameron
2024-10-10 14:58 ` Jonathan Cameron
2024-10-17 21:39 ` Ira Weiny
2024-10-18 9:09 ` Jonathan Cameron
2024-10-21 18:45 ` Ira Weiny
2024-10-22 17:01 ` Jonathan Cameron
2024-10-07 23:16 ` [PATCH v4 22/28] cxl/region/extent: Expose region extent information in sysfs ira.weiny
2024-10-10 15:01 ` Jonathan Cameron
2024-10-18 18:26 ` Ira Weiny
2024-10-21 9:37 ` Jonathan Cameron
2024-10-14 16:08 ` Fan Ni
2024-10-07 23:16 ` [PATCH v4 23/28] dax/bus: Factor out dev dax resize logic Ira Weiny
2024-10-10 15:06 ` Jonathan Cameron
2024-10-21 21:16 ` Ira Weiny
2024-10-14 16:56 ` Fan Ni
2024-10-07 23:16 ` [PATCH v4 24/28] dax/region: Create resources on sparse DAX regions ira.weiny
2024-10-10 15:27 ` Jonathan Cameron
2024-10-23 1:20 ` Ira Weiny
2024-10-23 11:22 ` Jonathan Cameron
2024-10-24 3:50 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 25/28] cxl/region: Read existing extents on region creation ira.weiny
2024-10-10 15:33 ` Jonathan Cameron
2024-10-24 1:41 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 26/28] cxl/mem: Trace Dynamic capacity Event Record ira.weiny
2024-10-10 15:41 ` Jonathan Cameron
2024-10-24 1:52 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 27/28] tools/testing/cxl: Make event logs dynamic Ira Weiny
2024-10-10 15:49 ` Jonathan Cameron
2024-10-24 1:59 ` Ira Weiny
2024-10-07 23:16 ` [PATCH v4 28/28] tools/testing/cxl: Add DC Regions to mock mem data Ira Weiny
2024-10-10 15:58 ` Jonathan Cameron
2024-10-24 2:23 ` Ira Weiny
2024-10-08 22:57 ` [PATCH v4 00/28] DCD: Add support for Dynamic Capacity Devices (DCD) Fan Ni
2024-10-08 23:06 ` Fan Ni [this message]
2024-10-10 15:30 ` Ira Weiny
2024-10-10 15:31 ` Ira Weiny
2024-10-21 16:47 ` Fan Ni
2024-10-22 17:05 ` Jonathan Cameron
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=ZwW7E2gSUM8SHAzo@fan \
--to=nifan.cxl@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=acpica-devel@lists.linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=dsterba@suse.com \
--cc=ira.weiny@intel.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ming4.li@intel.com \
--cc=navneet.singh@intel.com \
--cc=nvdimm@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=vishal.l.verma@intel.com \
/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).