>-----Original Message-----
>From: Shiju Jose <shiju.jose@xxxxxxxxxx>
>Sent: 01 August 2025 18:29
>To: Daniel Ferguson <danielf@xxxxxxxxxxxxxxxxxxxxxx>; rafael@xxxxxxxxxx;
>linux-edac@xxxxxxxxxxxxxxx; linux-acpi@xxxxxxxxxxxxxxx; linux-
>doc@xxxxxxxxxxxxxxx; bp@xxxxxxxxx; tony.luck@xxxxxxxxx; lenb@xxxxxxxxxx;
>leo.duran@xxxxxxx; Yazen.Ghannam@xxxxxxx; mchehab@xxxxxxxxxx
>Cc: Jonathan Cameron <jonathan.cameron@xxxxxxxxxx>; linux-
>mm@xxxxxxxxx; Linuxarm <linuxarm@xxxxxxxxxx>; rientjes@xxxxxxxxxx;
>jiaqiyan@xxxxxxxxxx; Jon.Grimm@xxxxxxx; dave.hansen@xxxxxxxxxxxxxxx;
>naoya.horiguchi@xxxxxxx; james.morse@xxxxxxx; jthoughton@xxxxxxxxxx;
>somasundaram.a@xxxxxxx; erdemaktas@xxxxxxxxxx; pgonda@xxxxxxxxxx;
>duenwen@xxxxxxxxxx; gthelen@xxxxxxxxxx;
>wschwartz@xxxxxxxxxxxxxxxxxxx; dferguson@xxxxxxxxxxxxxxxxxxx;
>wbs@xxxxxxxxxxxxxxxxxxxxxx; nifan.cxl@xxxxxxxxx; tanxiaofei
><tanxiaofei@xxxxxxxxxx>; Zengtao (B) <prime.zeng@xxxxxxxxxxxxx>; Roberto
>Sassu <roberto.sassu@xxxxxxxxxx>; kangkang.shen@xxxxxxxxxxxxx;
>wanghuiqiang <wanghuiqiang@xxxxxxxxxx>;
>vanshikonda@xxxxxxxxxxxxxxxxxxxxxx
>Subject: RE: [PATCH v9 2/2] ras: mem: Add memory ACPI RAS2 driver
>
>>-----Original Message-----
>>From: Daniel Ferguson <danielf@xxxxxxxxxxxxxxxxxxxxxx>
[...]
>>3) This is a special case of #2. During driver load, ras2_probe issues
>>a GET_PATROL_PARAMETERS using a base and size equal to 0. The base and
>>size are zero because requested_address_range is allocated with
>>kzalloc. In this case, we may not be getting the initial values from the correct
>range.
>In the probe stage, while issue GET_PATROL_PARAMETERS, driver has no
>information about the 'requested_address_range' supposed to set other than
>set to 0 because
>RAS2 ('RAS2 Platform Communication Channel Shared Memory Region' table?)
>does not define fields for the platform to advertise the supported full address
>range for a scrubber.
Please ignore this as it was solved.
>>
>>Proposed Solution:
>>What we propose, is to instead of zeroing out the base and size after
>>an error, use the full range of the current NUMA node. We believe that
>>a superset of a currently active scrub range can properly report all
>>the relevant and correct information.
>>To be compliant with the specification, FW should set "Flags" field if
>>there is any on-demand scrub in progress on any memory range in the
>>NUMA node. Again, this solution assumes that the driver does not allow
>>more than one scrubber to run within a single NUMA node. All three
>>problems can be solved in the same way.
>>
>>What do you think?
>Hi Daniel,
>
>Please check the v10 of the RAS2 series sent with changes for your
>requirements.
>and request please test in your system and share the feedback.
>
>https://lore.kernel.org/all/20250801172040.2175-1-shiju.jose@xxxxxxxxxx/
>>
>>Regards,
>>~Daniel
>
>Thanks,
>Shiju
