Re: [PATCH 00/23] further population of xen/lib/

[Julien Grall <julien@xxxxxxx>]

Hi Jan,

On 01/04/2021 11:14, Jan Beulich wrote:
> This is to dissolve / move xen/common/lib.c and xen/common/string.c.
> One benefit of moving these functions into an archive is that we can
> drop some of the related __HAVE_ARCH_* #define-s: By living in an
> archive, the per-arch functions will preempt any loading of the
> respective functions (objects) from the archive. (Down the road we
> may want to move the per-arch functions into archives as well, at
> which point the per-arch archive(s) would need to be specified ahead
> of the common one(s) to the linker.)
While I think it is a good idea to move code in xen/lib, I am not 
convinced that having a single function per file is that beneficial.
Do you have numbers showing how much Xen will shrink after this series?

Cheers,

--
Julien Grall