Re: [PATCH 0/6] cxl: Initialization reworks in support Soft Reserve Recovery and Accelerator Memory

[<dan.j.williams@intel.com>]

Alejandro Lucero Palau wrote:
[..]
> > Dan Williams (6):
> >    cxl/mem: Fix devm_cxl_memdev_edac_release() confusion
> >    cxl/mem: Arrange for always-synchronous memdev attach
> >    cxl/port: Arrange for always synchronous endpoint attach
> >    cxl/mem: Convert devm_cxl_add_memdev() to scope-based-cleanup
> >    cxl/mem: Drop @host argument to devm_cxl_add_memdev()
> >    cxl/mem: Introduce a memdev creation ->probe() operation
> >
> >   drivers/cxl/Kconfig          |   2 +-
> >   drivers/cxl/cxl.h            |   2 +
> >   drivers/cxl/cxlmem.h         |  17 ++++--
> >   drivers/cxl/core/edac.c      |  64 ++++++++++++---------
> >   drivers/cxl/core/memdev.c    | 104 ++++++++++++++++++++++++-----------
> >   drivers/cxl/mem.c            |  69 +++++++++--------------
> >   drivers/cxl/pci.c            |   2 +-
> >   drivers/cxl/port.c           |  40 ++++++++++++++
> >   tools/testing/cxl/test/mem.c |   2 +-
> >   9 files changed, 192 insertions(+), 110 deletions(-)
> >
> >
> > base-commit: ea5514e300568cbe8f19431c3e424d4791db8291
> 
> 
> I have tested this series with Type2 and it works as expected:
> 
> 
> 1) type2 fails to be installed if cxl_mem not loaded.
> 
> 2) cxl_mem, cxl_port and cxl_core not removable as type2 driver 
> installed depends on them.
> 
> 3) cxl_acpi is still possible to remove ...
> 
> 
> FWIW:
> 
> 
> Tested-by: Alejandro Lucero <alucerop@amd.com>

Thanks.

Do note that module removability does not affect the unbind path. So you
can still do all the same "remove" violence via:

"echo $device > /sys/bus/cxl/driver/$driver/unbind"

...as would be caused by:

"modprobe -r $driver"

...i.e. nothing blocks unbind even if the module is pinned.