Gregory Price wrote:
> Device capacity intended for use as system ram should be aligned to the
> architecture-defined memory block size or that capacity will be silently
> truncated and capacity stranded.
>
> As hotplug dax memory becomes more prevelant, the memory block size
> alignment becomes more important for platform and device vendors to
> pay attention to - so this truncation should not be silent.
>
> This issue is particularly relevant for CXL Dynamic Capacity devices,
> whose capacity may arrive in spec-aligned but block-misaligned chunks.
>
> Suggested-by: David Hildenbrand <da...@redhat.com>
> Suggested-by: Dan Williams <dan.j.willi...@intel.com>
> Reviewed-by: Dan Williams <dan.j.willi...@intel.com>
> Tested-by: Alison Schofield <alison.schofi...@intel.com>
> Reviewed-by: Jonathan Cameron <jonathan.came...@huawei.com>
> Acked-by: David Hildenbrand <da...@redhat.com>
> Signed-off-by: Gregory Price <gou...@gourry.net>
Hi Andrew, please pick up this patch:
msg-id: 20250410142831.217887-1-gou...@gourry.net
...for -mm. I now notice that MAINTAINERS does not make clear that you
be Cc'd on driver/dax/ patch for eventual upstream merge.
I still support dax patches going through -mm given potential
entanglements.
