Re: [PATCH v4] s390/iomem: register initrd as an iomem resource when retain_initrd is set

[Ilya Leoshkevich <iii@linux.ibm.com>]

On 8/19/26 08:40, Ilya Leoshkevich wrote:
> 
> 
> On 8/18/26 19:57, Joseph Cathcart wrote:
>> Currently, /proc/iomem contains no reference to initrd memory, even
>> when initrd is retained and still held in RAM. This makes the memory
>> ranges invisible from userspace, and unusable to programs such as
>> kexec. (A sysfs bin file is created for initrd, but this doesn't
>> help programs which need the explicit memory ranges)
>>
>> Add initrd to standard_resources[] unconditionally. Add initrd as a
>> child of iomem_resources only if retain_initrd is specified.
>>
>> strstr() could match substrings like "retain_initrd=0" or
>> "no_retain_initrd", but this is how PPC chose to check for
>> "retain_initrd" param too. (arch/powerpc/kexec/ranges.c)
>>
>> Signed-off-by: Joseph Cathcart <josephc@linux.ibm.com>
>> ---
>>   arch/s390/kernel/setup.c | 22 ++++++++++++++++++++++
>>   1 file changed, 22 insertions(+)

[...]

> Cc: Christian and Alexander.
> 
> I wonder if it would make sense to move initrd resource creation to
> do_populate_rootfs(), right after /sys/firmware/initrd creation,
> enabling this feature on all architectures?

Ping.