On 21.05.2025 13:40, Oleksii Kurochko wrote: > On 5/15/25 12:08 PM, Jan Beulich wrote: >> On 12.05.2025 17:55, Oleksii Kurochko wrote: >>> --- a/xen/arch/riscv/Makefile >>> +++ b/xen/arch/riscv/Makefile >>> @@ -1,5 +1,6 @@ >>> obj-y += aplic.o >>> obj-y += cpufeature.o >>> +obj-y += dom0less-build.o >> Arm uses >> >> obj-$(CONFIG_DOM0LESS_BOOT) += dom0less-build.init.o >> >> Why the two differences? > > Missed that. I have to understand why Arm uses *.init.o, but likely I should > do the same for RISC-V.
There's likely nothing Arm-specific in this. When all functions in a file are __init and all data is __initdata / __initconst, we prefer to move the remaining data (string literals being the most prominent example) to .init.* as well. That's (basically) what the *.o -> *.init.o build step does. Jan
