Cyril Brulebois dixit:
>Thorsten Glaser <t...@debian.org> (2023-11-27):
>> It’s not. The file documents:
>>
>> # To disable CMA allocation entirely, f.e. for a headless setup, set
>> # CMA=0
>
>Well, that's still the intent behind the commit that introduced support
>for that.
But it totally mismatches the documentation!
>And since that went into a stable release, I don't see how we
>could safely move away from CMA=0 means no cma= settings at all.
Granted, but…
>expressed, I suppose this bug report can be closed?
… definitely not.
Currently, CMA=0 is documented as “disable CMA allocation entirely”,
but it DOES NOT DO THAT. Instead it removes the cma= parameter from
the kernel command line INSTEAD of disabling CMA, which makes the
kernel use its default NONZERO allocation.
At the *very* leaast, that comment must be changed to e.g.
# To disable CMA allocation entirely, e.g. for a headless setup,
# set CMA=0M; setting CMA=0 makes the kernel use the default CMA
# size by omitting the cma parameter from the command line.
bye,
//mirabilos
--
21:41⎜«Tonnerre:#nosec» Do at least one thing every day which makes
⎜ inspirational quotes lovers sad
