On 20.04.22 16:00, Luca Fancellu wrote:
On 13 Apr 2022, at 08:22, Jan Beulich wrote:
On 13.04.2022 09:15, Luca Fancellu wrote:
No, I'm not suggesting a new menu. I was merely wondering whether the
Kconfig contents wouldn't location-wise better match where the
respective source file
> On 13 Apr 2022, at 08:22, Jan Beulich wrote:
>
> On 13.04.2022 09:15, Luca Fancellu wrote:
>>
No, I'm not suggesting a new menu. I was merely wondering whether the
Kconfig contents wouldn't location-wise better match where the
respective source file lives.
>>>
>>> It
On 13.04.2022 09:15, Luca Fancellu wrote:
>
>>>
>>> No, I'm not suggesting a new menu. I was merely wondering whether the
>>> Kconfig contents wouldn't location-wise better match where the
>>> respective source file lives.
>>
>> It could be in xen/common/sched/Kconfig at the beginning of the file
>>
>> No, I'm not suggesting a new menu. I was merely wondering whether the
>> Kconfig contents wouldn't location-wise better match where the
>> respective source file lives.
>
> It could be in xen/common/sched/Kconfig at the beginning of the file
> before creating the new "Schedulers" menu,
On Tue, 12 Apr 2022, Jan Beulich wrote:
> On 12.04.2022 11:50, Luca Fancellu wrote:
> >>> ---
> >>> MAINTAINERS | 2 +-
> >>> docs/misc/arm/device-tree/cpupools.txt | 140 +
> >>> xen/arch/arm/domain_build.c | 5 +-
> >>> xen/arch/arm/include/asm/smp.h | 3 +
> >>> xen/common/Kconfig |
On 12.04.2022 11:50, Luca Fancellu wrote:
>
>>> ---
>>> MAINTAINERS | 2 +-
>>> docs/misc/arm/device-tree/cpupools.txt | 140 +
>>> xen/arch/arm/domain_build.c | 5 +-
>>> xen/arch/arm/include/asm/smp.h | 3 +
>>> xen/common/Kconfig | 7 +
>>
>> For consistency, should the addition
>> ---
>> MAINTAINERS | 2 +-
>> docs/misc/arm/device-tree/cpupools.txt | 140 +
>> xen/arch/arm/domain_build.c | 5 +-
>> xen/arch/arm/include/asm/smp.h | 3 +
>> xen/common/Kconfig | 7 +
>
> For consistency, should the addition here - with ...
>
>> xen/common/sched/Makefile | 1 +
On 11.04.2022 17:20, Luca Fancellu wrote:
> Introduce a way to create different cpupools at boot time, this is
> particularly useful on ARM big.LITTLE system where there might be the
> need to have different cpupools for each type of core, but also
> systems using NUMA can have different cpu pools
Introduce a way to create different cpupools at boot time, this is
particularly useful on ARM big.LITTLE system where there might be the
need to have different cpupools for each type of core, but also
systems using NUMA can have different cpu pools for each node.
The feature on arm relies on a
