From: Alexander Graf <graf@amazon.com>
To: <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>, <nh-open-source@amazon.com>,
"The AWS Nitro Enclaves Team"
<aws-nitro-enclaves-devel@amazon.com>
Subject: [PATCH 00/19] nitro_enclaves: Fix enclave release, command retries and the CPU pool
Date: Wed, 11 Nov 2026 13:49:49 +0000 [thread overview]
Message-ID: <cover.1794300000.git.graf@amazon.com> (raw)
While working with AI on the nitro_enclaves driver, it stumbled over a few
issues in the code. None of them are out of the ordinary, but they all fix
legit corner cases that are better to have fixed upstream.
While at it, I also realized that the MAINTAINERS file is outdated.
Alexandru Ciobotaru no longer works on Nitro Enclaves. I'm taking over
the maintainer role instead.
Alex
Alexander Graf (19):
nitro_enclaves: Release the reference on a rejected region page
nitro_enclaves: Split freeing the slot from freeing the enclave
nitro_enclaves: Ignore the reply of a failed slot info command
nitro_enclaves: Retry a command the device asks us to retry
nitro_enclaves: Stop sending commands to a broken device
nitro_enclaves: Set up the device state before requesting its
interrupts
nitro_enclaves: Wait for file operations before unbinding the PCI
device
nitro_enclaves: Let the region tracking arrays fall back to vmalloc
nitro_enclaves: Do not return enclave threads to a replaced CPU pool
nitro_enclaves: Do not report a torn down CPU pool as set
nitro_enclaves: Keep the CPU pool when the new CPU list does not parse
nitro_enclaves: Put the CPU pool back when the new CPU list is refused
nitro_enclaves: Initialise the CPU pool mutex statically
nitro_enclaves: Build the boot-time CPU pool once the CPUs are online
nitro_enclaves: Set up the CPU pool under the CPU hotplug read lock
nitro_enclaves: Let 32-bit processes use the ioctl interface
nitro_enclaves: Index CPU pool cores by sibling mask
nitro_enclaves: Time the wait for the device to turn off by the clock
MAINTAINERS: Take over the Nitro Enclaves driver
MAINTAINERS | 2 +-
drivers/virt/nitro_enclaves/ne_misc_dev.c | 658 +++++++++++++++-------
drivers/virt/nitro_enclaves/ne_misc_dev.h | 24 +-
drivers/virt/nitro_enclaves/ne_pci_dev.c | 236 +++++++-
drivers/virt/nitro_enclaves/ne_pci_dev.h | 4 +
5 files changed, 688 insertions(+), 236 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.47.1
next reply other threads:[~2026-11-11 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 13:49 Alexander Graf [this message]
2026-11-11 13:49 ` [PATCH 01/19] nitro_enclaves: Release the reference on a rejected region page Alexander Graf
2026-11-11 13:49 ` [PATCH 02/19] nitro_enclaves: Split freeing the slot from freeing the enclave Alexander Graf
2026-11-11 13:49 ` [PATCH 03/19] nitro_enclaves: Ignore the reply of a failed slot info command Alexander Graf
2026-11-11 13:49 ` [PATCH 04/19] nitro_enclaves: Retry a command the device asks us to retry Alexander Graf
2026-11-11 13:49 ` [PATCH 05/19] nitro_enclaves: Stop sending commands to a broken device Alexander Graf
2026-11-11 13:49 ` [PATCH 06/19] nitro_enclaves: Set up the device state before requesting its interrupts Alexander Graf
2026-11-11 13:49 ` [PATCH 07/19] nitro_enclaves: Wait for file operations before unbinding the PCI device 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=cover.1794300000.git.graf@amazon.com \
--to=graf@amazon.com \
--cc=arnd@arndb.de \
--cc=aws-nitro-enclaves-devel@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nh-open-source@amazon.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
all inboxes | Powered by JetHome®