Hi Julien, > -----Original Message----- > From: Julien Grall <jul...@xen.org> > Sent: 2021年8月27日 22:33 > To: Wei Chen <wei.c...@arm.com>; xen-devel@lists.xenproject.org; > sstabell...@kernel.org; jbeul...@suse.com > Cc: Bertrand Marquis <bertrand.marq...@arm.com> > Subject: Re: [XEN RFC PATCH 38/40] xen/arm: enable device tree based NUMA > in system init > > Hi Wei, > > On 11/08/2021 11:24, Wei Chen wrote: > > Everything is ready, we can remove the fake NUMA node and > > depends on device tree to create NUMA system. > > So you just added code a few patches before that are now completely > rewritten. Can you please re-order this series so it doesn't happen? > > This may mean that CONFIG_NUMA is only selected until late in this series. >
Why I did like this is because my original concerns are: 1. When I introduced the CONFIG_NUMA. Users will be using a code base on this commit by accident. 2. If users select CONFIG_NUMA, but not all NUMA data are not initialized properly. The system may not work properly. 3. So I created the fake node to initialize the NUMA data, before we parser real data from DTB. 4. In this case, user can work well with CONFIG_NUMA is enabled, without this series is completed. It seems I thought too much. If these concerns are not necessary. I am OK to re-order this series. > Cheers, > > -- > Julien Grall
