mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Graf <graf@amazon.com>
To: <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>
Cc: The AWS Nitro Enclaves Team <aws-nitro-enclaves-devel@amazon.com>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Robin Murphy <robin.murphy@arm.com>, <linux-doc@vger.kernel.org>,
	<iommu@lists.linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Mike Rapoport <rppt@kernel.org>, <nh-open-source@amazon.com>,
	<linux-mm@kvack.org>, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 39/40] nitro_enclaves: Add NE_UPDATE_DEVICE_CONFIG
Date: Wed, 11 Nov 2026 22:59:43 +0000	[thread overview]
Message-ID: <242d156c25da512f2edddb0bd3d2f34fe727721e.1794393491.git.graf@amazon.com> (raw)
In-Reply-To: <cover.1794300002.git.graf@amazon.com>

A virtio device reports state that changes while the guest runs, such as
a network link going down, through its configuration space. Nitro
Sandboxes let the device backend in the parent write that space while
the sandbox runs through an explicit full-config-update call, which also
raises the virtio configuration-change notification inside the sandbox.

Add the NE_UPDATE_DEVICE_CONFIG ioctl on the enclave fd to give user
space an API to call with the updated config space.

Signed-off-by: Alexander Graf <graf@amazon.com>
---
 drivers/virt/nitro_enclaves/ne_misc_dev.c | 113 +++++++++++++++++++++-
 drivers/virt/nitro_enclaves/ne_pci_dev.h  |  24 +++++
 include/uapi/linux/nitro_enclaves.h       | 100 ++++++++++++++++++-
 3 files changed, 231 insertions(+), 6 deletions(-)

diff --git a/drivers/virt/nitro_enclaves/ne_misc_dev.c b/drivers/virt/nitro_enclaves/ne_misc_dev.c
index abbba71bbef06..a5550a6be86ea 100644
--- a/drivers/virt/nitro_enclaves/ne_misc_dev.c
+++ b/drivers/virt/nitro_enclaves/ne_misc_dev.c
@@ -120,6 +120,12 @@ static_assert(offsetof(struct ne_vring_call, fd) == 0);
 static_assert(offsetof(struct ne_vring_call, doorbell_offset) == 4);
 static_assert(offsetof(struct ne_vring_call, reserved) == 6);
 
+static_assert(sizeof(struct ne_update_device_config) == 24);
+static_assert(offsetof(struct ne_update_device_config, device_uid) == 0);
+static_assert(offsetof(struct ne_update_device_config, config_addr) == 8);
+static_assert(offsetof(struct ne_update_device_config, config_size) == 16);
+static_assert(offsetof(struct ne_update_device_config, config_offset) == 20);
+
 static_assert(sizeof(struct ne_create_vm_args) == 16);
 static_assert(offsetof(struct ne_create_vm_args, flags) == 0);
 static_assert(offsetof(struct ne_create_vm_args, slot_uid) == 8);
@@ -162,7 +168,7 @@ static_assert(offsetof(struct ne_caps, supported_matched_flags) == 16);
 static_assert(offsetof(struct ne_caps, max_devices) == 24);
 static_assert(offsetof(struct ne_caps, max_vqs_per_device) == 28);
 static_assert(offsetof(struct ne_caps, max_config_size) == 32);
-static_assert(offsetof(struct ne_caps, reserved) == 36);
+static_assert(offsetof(struct ne_caps, max_config_update_size) == 36);
 static_assert(offsetof(struct ne_caps, info_page_size) == 40);
 static_assert(offsetof(struct ne_caps, info_page_align) == 48);
 static_assert(offsetof(struct ne_caps, hypervisor_matched_flags) == 56);
@@ -217,6 +223,8 @@ static int ne_set_info_page_ioctl(struct ne_enclave *ne_enclave,
 				  struct ne_set_info_page_args *args);
 static int ne_add_device_ioctl(struct ne_enclave *ne_enclave,
 			       struct ne_add_device_args *args);
+static int ne_update_device_config_ioctl(struct ne_enclave *ne_enclave,
+					 struct ne_update_device_config *args);
 static const struct file_operations ne_fops = {
 	.owner		= THIS_MODULE,
 	.llseek		= noop_llseek,
@@ -3229,6 +3237,39 @@ static long ne_enclave_do_ioctl(struct file *file, unsigned int cmd, unsigned lo
 		return ne_set_vring_call(ne_enclave, &args);
 	}
 
+	case NE_EA_IOCTL(NE_UPDATE_DEVICE_CONFIG): {
+		struct ne_update_device_config __user *uargs = (void __user *)arg;
+		unsigned int usize = _IOC_SIZE(cmd);
+		struct ne_update_device_config args;
+		int rc;
+
+		if (usize < offsetofend(struct ne_update_device_config, config_offset))
+			return -EINVAL;
+
+		rc = copy_struct_from_user(&args, sizeof(args), uargs, usize);
+		if (rc)
+			return rc;
+
+		rc = mutex_lock_killable(&ne_enclave->enclave_info_mutex);
+		if (rc)
+			return rc;
+
+		if (ne_enclave->state != NE_STATE_RUNNING) {
+			dev_err_ratelimited(ne_misc_dev.this_device,
+					    "Enclave is not in running state\n");
+
+			mutex_unlock(&ne_enclave->enclave_info_mutex);
+
+			return -NE_ERR_NOT_IN_RUNNING_STATE;
+		}
+
+		rc = ne_update_device_config_ioctl(ne_enclave, &args);
+
+		mutex_unlock(&ne_enclave->enclave_info_mutex);
+
+		return rc;
+	}
+
 	default:
 		return -ENOTTY;
 	}
@@ -3858,6 +3899,9 @@ static long ne_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
 		caps.max_vqs_per_device = NE_MAX_VQS;
 		caps.max_config_size = sizeof_field(struct ne_add_device_args,
 						    device_config);
+		caps.max_config_update_size =
+			sizeof_field(struct slot_update_device_config_req,
+				     config_data);
 		caps.info_page_size = NE_INFO_PAGE_SIZE;
 		caps.info_page_align = NE_INFO_PAGE_ALIGN;
 
@@ -5598,6 +5642,73 @@ static int ne_add_device_ioctl(struct ne_enclave *ne_enclave,
 	return rc;
 }
 
+/**
+ * ne_update_device_config_ioctl() - Write part of the configuration space of a
+ *				     device the enclave is driving.
+ * @ne_enclave:	Private data associated with the current enclave.
+ * @args:	Where the bytes to write are, how many of them there are and
+ *		where in the device's configuration space they go.
+ *
+ * The bytes are copied out of the caller before the request is built, so what
+ * the caller does with its buffer afterwards does not reach the device, and a
+ * call that is refused here sends the device nothing.
+ *
+ * Context: Process context. This function is called with the ne_enclave mutex held.
+ * Return:
+ * * 0 on success.
+ * * Negative return value on failure.
+ */
+static int ne_update_device_config_ioctl(struct ne_enclave *ne_enclave,
+					 struct ne_update_device_config *args)
+{
+	struct slot_update_device_config_req req = {};
+	struct ne_pci_dev_cmd_reply cmd_reply = {};
+	int rc;
+
+	if (!args->config_size) {
+		dev_err_ratelimited(ne_misc_dev.this_device,
+				    "The configuration write is empty\n");
+
+		return -EINVAL;
+	}
+
+	/*
+	 * The request carries the bytes in a fixed array and tells the device
+	 * separately where in its configuration space to put them, so what the
+	 * request bounds is how many bytes one call moves. How far into the
+	 * space a write may reach is the device's to bound, out of the
+	 * configuration space it was given for that device.
+	 */
+	if (args->config_size > sizeof(req.config_data)) {
+		dev_err_ratelimited(ne_misc_dev.this_device,
+				    "The configuration write is longer than %zu bytes\n",
+				    sizeof(req.config_data));
+
+		return -EINVAL;
+	}
+
+	if (copy_from_user(req.config_data, u64_to_user_ptr(args->config_addr),
+			   args->config_size))
+		return -EFAULT;
+
+	req.slot_uid = ne_enclave->slot_uid;
+	req.device_uid = args->device_uid;
+	req.config_size = args->config_size;
+	req.config_offset = args->config_offset;
+
+	rc = ne_do_request(ne_devs.ne_pci_dev->pdev, SLOT_UPDATE_DEVICE_CONFIG,
+			   &req, sizeof(req), &cmd_reply, sizeof(cmd_reply));
+	if (rc < 0) {
+		dev_err_ratelimited(ne_misc_dev.this_device,
+				    "Error in slot update device config [rc=%d]\n",
+				    rc);
+
+		return rc;
+	}
+
+	return 0;
+}
+
 #if defined(CONFIG_NITRO_ENCLAVES_MISC_DEV_TEST)
 #include "ne_misc_dev_test.c"
 #endif
diff --git a/drivers/virt/nitro_enclaves/ne_pci_dev.h b/drivers/virt/nitro_enclaves/ne_pci_dev.h
index 44491e451082a..74728d2a15472 100644
--- a/drivers/virt/nitro_enclaves/ne_pci_dev.h
+++ b/drivers/virt/nitro_enclaves/ne_pci_dev.h
@@ -256,6 +256,8 @@ static_assert(NE_MUX_MAX_BITS / BITS_PER_TYPE(u64) * sizeof(u64) <= PAGE_SIZE,
  *				device runs a slot out of.
  * @SLOT_POOL_GET_LIMITS:	Report how many slots each half of the pool has
  *				room for.
+ * @SLOT_UPDATE_DEVICE_CONFIG:	Write part of the configuration space of a
+ *				device a slot is driving.
  * @SLOT_POOL_BASE_DONATE:	Donate the base run of the slot pool.
  * @MAX_CMD:			A gatekeeper for max possible command type.
  */
@@ -277,6 +279,7 @@ enum ne_pci_dev_cmd_type {
 	SLOT_ADD_DEVICE		= 14,
 	SLOT_POOL_DONATE	= 16,
 	SLOT_POOL_SHUTDOWN	= 17,
+	SLOT_UPDATE_DEVICE_CONFIG = 24,
 	SLOT_POOL_BASE_DONATE	= 25,
 	SLOT_POOL_MEM_DONATE	= 26,
 	SLOT_POOL_GET_LIMITS	= 27,
@@ -502,6 +505,27 @@ struct slot_add_device_req {
 } __packed;
 static_assert(sizeof(struct slot_add_device_req) <= NE_SEND_DATA_SIZE);
 
+/**
+ * struct slot_update_device_config_req - SLOT_UPDATE_DEVICE_CONFIG request.
+ * @slot_uid:			Slot unique id mapped to the slot driving the
+ *				device.
+ * @device_uid:			Device to write the configuration of.
+ * @config_size:		Number of bytes of @config_data the device
+ *				reads.
+ * @config_offset:		Byte offset within the device's configuration
+ *				space the device is to place @config_data at.
+ * @config_data:		Configuration to write into the device's
+ *				configuration space.
+ */
+struct slot_update_device_config_req {
+	u64	slot_uid;
+	u64	device_uid;
+	u32	config_size;
+	u32	config_offset;
+	u8	config_data[64];
+} __packed;
+static_assert(sizeof(struct slot_update_device_config_req) <= NE_SEND_DATA_SIZE);
+
 /**
  * struct slot_pool_donate_req - SLOT_POOL_DONATE and SLOT_POOL_BASE_DONATE
  *				 request.
diff --git a/include/uapi/linux/nitro_enclaves.h b/include/uapi/linux/nitro_enclaves.h
index f8eeacd2e7062..4a0a8eb30caa4 100644
--- a/include/uapi/linux/nitro_enclaves.h
+++ b/include/uapi/linux/nitro_enclaves.h
@@ -204,8 +204,8 @@ struct ne_create_vm_args {
 
 /**
  * NE_CAP_DEVICES - This kernel implements %NE_SET_INFO_PAGE,
- *			 %NE_ADD_DEVICE, %NE_SET_NOTIFY_EVENTFD and
- *			 %NE_SET_VRING_CALL.
+ *			 %NE_ADD_DEVICE, %NE_SET_NOTIFY_EVENTFD,
+ *			 %NE_SET_VRING_CALL and %NE_UPDATE_DEVICE_CONFIG.
  */
 #define NE_CAP_DEVICES			(1ULL << 1)
 
@@ -240,7 +240,15 @@ struct ne_create_vm_args {
  *			request and %NE_ADD_DEVICE is what answers.
  * @max_vqs_per_device:	Largest @num_vqs %NE_ADD_DEVICE takes (out).
  * @max_config_size:	Largest @config_size %NE_ADD_DEVICE takes (out).
- * @reserved:		Zero (out).
+ * @max_config_update_size:	Largest @config_size one %NE_UPDATE_DEVICE_CONFIG
+ *			call takes (out). It bounds how many bytes a call moves,
+ *			not how far into the configuration space they go: a write
+ *			carries its own offset, and how far a device lets one
+ *			reach is bounded by the configuration space that device
+ *			was given in @device_config. It is reported apart from
+ *			@max_config_size because the size of @device_config is
+ *			part of the ABI while this one is not, so this value can
+ *			grow without a new argument structure.
  * @info_page_size:	Size the %NE_SET_INFO_PAGE allocation has to have (out).
  * @info_page_align:	Alignment it has to have (out).
  * @hypervisor_matched_flags: The launch flags inside
@@ -264,7 +272,7 @@ struct ne_caps {
 	__u32	max_devices;
 	__u32	max_vqs_per_device;
 	__u32	max_config_size;
-	__u32	reserved;
+	__u32	max_config_update_size;
 	__u64	info_page_size;
 	__u64	info_page_align;
 	__u64	hypervisor_matched_flags;
@@ -806,7 +814,11 @@ struct ne_shm_region {
  * @padding:		Must be zero.
  * @device_features:	Feature bits the parent offers the enclave for the
  *			device.
- * @device_config:	Type-specific configuration of the device.
+ * @device_config:	The opening bytes of the device's configuration space, as
+ *			the enclave first sees it. It is the device-specific
+ *			configuration space a virtio driver reads, not PCI
+ *			configuration space, and @max_config_size bounds how much
+ *			of it may be handed over here.
  * @shm_regions_ptr:	Address of @num_shm_regions struct ne_shm_region.
  * @device_uid:		Id the device gave the new device (out).
  * @vq_info:		How the enclave reaches the device's first @num_vqs
@@ -1200,6 +1212,13 @@ struct ne_add_device_args {
  * NE_ERR_ZERO_REGION - The enclave's memory layout has a region of size zero.
  */
 #define NE_ERR_ZERO_REGION			(302)
+/**
+ * NE_ERR_NOT_IN_RUNNING_STATE - The enclave has not been started yet, or has
+ *				 already exited, when writing the configuration
+ *				 of one of its devices. The first code of the
+ *				 driver-only range.
+ */
+#define NE_ERR_NOT_IN_RUNNING_STATE		(1024)
 
 /**
  * DOC: Image load info flags
@@ -1426,4 +1445,75 @@ struct ne_vring_call {
 	__u16	reserved;
 };
 
+/**
+ * NE_UPDATE_DEVICE_CONFIG - The command is used to write part of the
+ *			     configuration space of a device an enclave is
+ *			     already driving, so that the device backend in the
+ *			     parent tells the driver in the enclave about state
+ *			     that moved after the device was attached. The
+ *			     hypervisor raises a configuration-change
+ *			     notification inside the enclave for the write.
+ *			     The parent holds the only copy of the space: no
+ *			     command reads a device's configuration back, so a
+ *			     caller that changes fields which do not sit next to
+ *			     each other either writes each of them on its own or
+ *			     writes the whole range out of the copy it already
+ *			     has.
+ *			     The ioctl waits for the reply of the device. When
+ *			     none comes, the outcome of the write is unknown and
+ *			     the driver sends that device no further command.
+ *			     The driver reads the
+ *			     bytes at @config_addr before it builds the request,
+ *			     so writing to the buffer afterwards changes nothing,
+ *			     and it serialises the calls of one enclave against
+ *			     each other and
+ *			     every call against the other commands it sends the
+ *			     NE PCI device. A call the driver refuses sends nothing, so
+ *			     the device keeps the configuration the last accepted
+ *			     write left it.
+ *			     What the enclave sees while a write is applied is
+ *			     not specified: whether the driver inside it can read
+ *			     part of a range, whether every accepted write raises
+ *			     a notification of its own, and what a write leaves
+ *			     the bytes outside it holding, are the hypervisor's
+ *			     to answer.
+ *			     The ioctl can be invoked on the enclave fd, after an
+ *			     enclave is started.
+ *
+ * Context: Process context.
+ * Return:
+ * * 0					- Logic successfully completed.
+ * * -1					- There was a failure in the ioctl logic.
+ * On failure, errno is set to:
+ * * ENODEV				- The NE PCI device is not available.
+ * * EFAULT				- Argument or @config_addr read failure.
+ * * EINVAL				- The argument does not reach through
+ *					  @config_offset, @config_size is zero, or
+ *					  @config_size is larger than
+ *					  @max_config_update_size.
+ * * E2BIG				- The argument is longer than this kernel knows
+ *					  about and the excess is not all zero.
+ * * NE_ERR_NOT_IN_RUNNING_STATE	- The enclave is not running.
+ * * Error codes from the NE PCI device request.
+ */
+#define NE_UPDATE_DEVICE_CONFIG		_IOW(0xAE, 0x2C, struct ne_update_device_config)
+
+/**
+ * struct ne_update_device_config - Configuration to write to a device an
+ *				    enclave is already driving (in).
+ * @device_uid:		The device to write the configuration of, as
+ *			%NE_ADD_DEVICE reported it.
+ * @config_addr:	User space address of the @config_size bytes to write.
+ * @config_size:	Number of bytes to write, at least one and at most the
+ *			@max_config_update_size %NE_GET_CAPS reports.
+ * @config_offset:	Byte offset within the device's configuration space to
+ *			write them at.
+ */
+struct ne_update_device_config {
+	__u64	device_uid;
+	__u64	config_addr;
+	__u32	config_size;
+	__u32	config_offset;
+};
+
 #endif /* _UAPI_LINUX_NITRO_ENCLAVES_H_ */
-- 
2.47.1


  parent reply	other threads:[~2026-11-11 23:13 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 22:41 [PATCH 00/40] nitro_enclaves: Add support for Nitro Sandboxes Alexander Graf
2026-11-11 22:41 ` [PATCH 01/40] nitro_enclaves: Allow the CPU pool to span NUMA nodes Alexander Graf
2026-11-11 22:41 ` [PATCH 02/40] nitro_enclaves: Add NE_ADD_ANY_VCPU Alexander Graf
2026-11-11 22:41 ` [PATCH 03/40] nitro_enclaves: Expose CPU pool state under sysfs Alexander Graf
2026-11-11 22:41 ` [PATCH 04/40] nitro_enclaves: Document multi-NUMA CPU pools Alexander Graf
2026-11-11 22:41 ` [PATCH 05/40] dma-contiguous: add dma_get_numa_cma_area() accessor Alexander Graf
2026-11-11 22:41 ` [PATCH 06/40] nitro_enclaves: Add NE_ALLOC_MEMORY ioctl Alexander Graf
2026-11-11 22:41 ` [PATCH 07/40] nitro_enclaves: Add NE_MEMORY_SHARED Alexander Graf
2026-11-11 22:41 ` [PATCH 08/40] nitro_enclaves: Add NE_ADD_MEMORY_REGION Alexander Graf
2026-11-11 22:41 ` [PATCH 09/40] nitro_enclaves: Document the memory pool Alexander Graf
2026-11-11 22:41 ` [PATCH 10/40] nitro_enclaves: Add NE_CREATE_VM2 with a launch flag word Alexander Graf
2026-11-11 22:41 ` [PATCH 11/40] nitro_enclaves: Add NE_ENCLAVE_PCIE_MODE launch flag Alexander Graf
2026-11-11 22:41 ` [PATCH 12/40] nitro_enclaves: Name the device's error codes in the UAPI header Alexander Graf
2026-11-11 22:41 ` [PATCH 13/40] nitro_enclaves: Log a reached device limit at info level Alexander Graf
2026-11-11 22:56 ` [PATCH 14/40] nitro_enclaves: Add NE_SET_INFO_PAGE Alexander Graf
2026-11-11 22:59 ` [PATCH 15/40] nitro_enclaves: Document the info page in the memory pool Alexander Graf
2026-11-11 22:59 ` [PATCH 16/40] nitro_enclaves: Turn the command reply into a per-command union Alexander Graf
2026-11-11 22:59 ` [PATCH 17/40] nitro_enclaves: Add the slot pool donation commands Alexander Graf
2026-11-11 22:59 ` [PATCH 18/40] nitro_enclaves: Donate memory for the slot pool Alexander Graf
2026-11-11 22:59 ` [PATCH 19/40] nitro_enclaves: Add the slot pool growth commands Alexander Graf
2026-11-11 22:59 ` [PATCH 20/40] nitro_enclaves: Add a helper to grow the slot pool Alexander Graf
2026-11-11 22:59 ` [PATCH 21/40] nitro_enclaves: Document " Alexander Graf
2026-11-11 22:59 ` [PATCH 22/40] nitro_enclaves: Expose slot pool state under sysfs Alexander Graf
2026-11-11 22:59 ` [PATCH 23/40] nitro_enclaves: Add the device add command Alexander Graf
2026-11-11 22:59 ` [PATCH 24/40] nitro_enclaves: Add NE_ADD_DEVICE Alexander Graf
2026-11-11 22:59 ` [PATCH 25/40] nitro_enclaves: Read the interrupt multiplexer geometry at probe Alexander Graf
2026-11-11 22:59 ` [PATCH 26/40] nitro_enclaves: Donate a bitmap page per multiplexed vector Alexander Graf
2026-11-11 22:59 ` [PATCH 27/40] nitro_enclaves: Dispatch multiplexed interrupts to per-queue bindings Alexander Graf
2026-11-11 22:59 ` [PATCH 28/40] nitro_enclaves: Add NE_SET_NOTIFY_EVENTFD Alexander Graf
2026-11-11 22:59 ` [PATCH 29/40] nitro_enclaves: Report the device's info notification Alexander Graf
2026-11-11 22:59 ` [PATCH 30/40] nitro_enclaves: Count multiplexed interrupts under debugfs Alexander Graf
2026-11-11 22:59 ` [PATCH 31/40] nitro_enclaves: Map the doorbell window at probe Alexander Graf
2026-11-11 22:59 ` [PATCH 32/40] nitro_enclaves: Add NE_SET_VRING_CALL Alexander Graf
2026-11-11 22:59 ` [PATCH 33/40] nitro_enclaves: Assert the layout of the ioctl argument structs Alexander Graf
2026-11-11 22:59 ` [PATCH 34/40] nitro_enclaves: Pass on the Nitro Sandbox launch flags Alexander Graf
2026-11-11 22:59 ` [PATCH 35/40] nitro_enclaves: Add NE_ENCLAVE_DIRECT_MODE Alexander Graf
2026-11-11 22:59 ` [PATCH 36/40] nitro_enclaves: Add NE_ENCLAVE_PCIE_HOTPLUG_MODE Alexander Graf
2026-11-11 22:59 ` [PATCH 37/40] nitro_enclaves: Add NE_ENCLAVE_CPU_OVERCOMMIT_MODE Alexander Graf
2026-11-11 22:59 ` [PATCH 38/40] nitro_enclaves: Add NE_GET_CAPS Alexander Graf
2026-11-11 22:59 ` Alexander Graf [this message]
2026-11-11 22:59 ` [PATCH 40/40] nitro_enclaves: Document the driver side of Nitro Sandboxes Alexander Graf

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=242d156c25da512f2edddb0bd3d2f34fe727721e.1794393491.git.graf@amazon.com \
    --to=graf@amazon.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=aws-nitro-enclaves-devel@amazon.com \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=nh-open-source@amazon.com \
    --cc=rdunlap@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=rppt@kernel.org \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®