Hi Jan,
On 13/03/2025 13:38, Jan Beulich wrote:
There's no need for each arch to invoke it directly, and there's no need
for having a stub either. With the present placement of the calls to
init_constructors() it can easily be a constructor itself.
Signed-off-by: Jan Beulich <jbeul...@suse.com>
Acked-by: Julien Grall <jgr...@amazon.com>
---
Same could then apparently be done for heap_init_late(). Thoughts?
Looking at the code, I couldn't figure out whether any of the
constructors may rely on some changes done by heap_init_late().
The only issue I can think of is scrubbing. In the case it is
synchronous, would the memory allocated before hand be scrubbed?
Cheers,
--
Julien Grall
