From: Joshua Lant <joshualant@gmail.com>
To: linux-cxl@vger.kernel.org
Cc: jic23@kernel.org, Joshua Lant <joshualant@gmail.com>
Subject: [QEMU PATCH 0/2] cxl: fixes for hot-removal of devices
Date: Wed, 20 May 2026 15:16:46 +0100 [thread overview]
Message-ID: <20260520141816.3240010-2-joshualant@gmail.com> (raw)
As requested from the discussion in:
https://lore.kernel.org/linux-cxl/20260429135717.3048713-1-joshualant@gmail.com/T/#t
Two bugs have been found when testing cxl topologies for managed
hot-remove of a device:
Patch 1 properly unmaps the backend memory device, allowing it to be
remapped if the removed device is re-added.
Patch 2 sets the power controller present capability in the downstream
port. This is required to notify the device from the guest of removal.
Modifications from linked RFC (patches 3 & 4):
- Originally patch 3 (1 here) unmaps only on exit. It should also unmap in the
error goto in the realize function.
- "Fixes:" tags added to commit messages.
Joshua Lant (2):
cxl-type3: Properly unmap the memory-backend on device exit
cxl_downstream: enable power controller present capability.
hw/mem/cxl_type3.c | 6 ++++++
hw/pci-bridge/cxl_downstream.c | 2 ++
2 files changed, 8 insertions(+)
--
2.47.3
next reply other threads:[~2026-05-20 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 14:16 Joshua Lant [this message]
2026-05-20 14:16 ` [QEMU PATCH 1/2] cxl-type3: Properly unmap the memory-backend on device exit Joshua Lant
2026-05-20 14:16 ` [QEMU PATCH 2/2] cxl_downstream: enable power controller present capability Joshua Lant
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=20260520141816.3240010-2-joshualant@gmail.com \
--to=joshualant@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.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