Re: [PATCH v5 16/27] vfio/cxl: Create the CXL memdev and set media ready at bind

[Alex Williamson <alex@shazbot.org>]

On Thu, 17 Sep 2026 00:05:29 +0530
<mhonap@nvidia.com> wrote:

> From: Manish Honap <mhonap@nvidia.com>
> 
> At bind, build the CXL memory device for the passed-through Type-2
> accelerator so it joins the CXL topology and its HDM region resolves to a
> host physical range. A Type-2 device has no mailbox, so there is no
> media-ready register to poll: set media ready directly once the component
> registers validate (mirroring drivers/net/ethernet/sfc/efx_cxl.c)
> 
> As per current vfio-cxl support, reject a device with:
> - more than one HDM decoder
> - interleaving enabled
> - whose reset the host cannot service
> 
> The CXL-core allocations are grouped with devres so a failed bind unwinds
> them: init failure falls back to plain vfio-pci with the device still
> bound, so devm would otherwise hold them until unbind.
> 
> A low-power transition would reset the CXL Type-2 function and lose
> its CXL.mem contents, so keep it in D0 while it is assigned.

Is it the configuration or the mem contents?  Isn't it the user's
problem if they put the device in low power state and lose their own
data?  If it's our problem, what are we protecting?  It's not clear to
me how we can save and restore the HDM state around reset, but can't
allow low power.

This also undercuts your patch 12 justification for the open/close
hooks under the rationale that we cannot sample the hardware while it
might be in a low power state.

If we do block the low power features (less desirable), it should also
be at the probe and dispatch level (-ENOTTY) rather than failing the
SET operation with -EINVAL while reporting the feature available via
PROBE.  Thanks,

Alex