Hi,
On 23/03/2022 13:58, Luca Fancellu wrote:
On 22 Mar 2022, at 14:01, Julien Grall wrote:
Hi,
On 22/03/2022 09:52, Luca Fancellu wrote:
Can you document why this is necessary on x86 but not on other architectures?
Hi Julien,
I received the warning by Juergen here:
https://patchwork.kern
> On 22 Mar 2022, at 14:01, Julien Grall wrote:
>
> Hi,
>
> On 22/03/2022 09:52, Luca Fancellu wrote:
>
> Can you document why this is necessary on x86 but not on other
> architectures?
Hi Julien,
I received the warning by Juergen here:
https://patchwork.kernel.or
On Tue, 22 Mar 2022, Luca Fancellu wrote:
> >> +- cpupool-sched (optional)
> >> +
> >> +Must be a string having the name of a Xen scheduler, it has no effect
> >> when
> >> +used in conjunction of a cpupool-id equal to zero, in that case the
> >> +default Xen scheduler is selected (sch
Hi,
On 22/03/2022 09:52, Luca Fancellu wrote:
Can you document why this is necessary on x86 but not on other architectures?
Hi Julien,
I received the warning by Juergen here:
https://patchwork.kernel.org/comment/24740762/ that at least on x86 there could
be
some problems if cpu0 is not in cp
>>>
>>> Can you document why this is necessary on x86 but not on other
>>> architectures?
>> Hi Julien,
>> I received the warning by Juergen here:
>> https://patchwork.kernel.org/comment/24740762/ that at least on x86 there
>> could be
>> some problems if cpu0 is not in cpupool0, I tested it on
Hi Julien,
> On 22 Mar 2022, at 10:16, Julien Grall wrote:
>
> Hi,
>
> On 22/03/2022 08:47, Bertrand Marquis wrote:
>> Hi Julien,
>>> On 22 Mar 2022, at 09:35, Bertrand Marquis wrote:
>>>
>>> Hi Julien,
>>>
On 21 Mar 2022, at 18:44, Julien Grall wrote:
Hi Bertrand,
>>>
Hi,
On 22/03/2022 08:47, Bertrand Marquis wrote:
Hi Julien,
On 22 Mar 2022, at 09:35, Bertrand Marquis wrote:
Hi Julien,
On 21 Mar 2022, at 18:44, Julien Grall wrote:
Hi Bertrand,
On 21/03/2022 17:19, Bertrand Marquis wrote:
On 21 Mar 2022, at 17:36, Julien Grall wrote:
So I don’t kn
>> +- cpupool-sched (optional)
>> +
>> +Must be a string having the name of a Xen scheduler, it has no effect
>> when
>> +used in conjunction of a cpupool-id equal to zero, in that case the
>> +default Xen scheduler is selected (sched=<...> boot argument).
>> +Check the sched=<...
Hi Julien,
> On 22 Mar 2022, at 09:35, Bertrand Marquis wrote:
>
> Hi Julien,
>
>> On 21 Mar 2022, at 18:44, Julien Grall wrote:
>>
>> Hi Bertrand,
>>
>> On 21/03/2022 17:19, Bertrand Marquis wrote:
On 21 Mar 2022, at 17:36, Julien Grall wrote:
> So I don’t know why on x86 we must
Hi Julien,
> On 21 Mar 2022, at 18:44, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 21/03/2022 17:19, Bertrand Marquis wrote:
>>> On 21 Mar 2022, at 17:36, Julien Grall wrote:
So I don’t know why on x86 we must have cpu0 in cpupool0, maybe x86
maintainer have more knowledge about tha
On Fri, 18 Mar 2022, 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
Hi Bertrand,
On 21/03/2022 17:19, Bertrand Marquis wrote:
On 21 Mar 2022, at 17:36, Julien Grall wrote:
So I don’t know why on x86 we must have cpu0 in cpupool0, maybe x86 maintainer
have more knowledge about that and
I can put a comment here.
On Arm, we are not yet supporting all the CPU f
Hi Julien,
> On 21 Mar 2022, at 17:36, Julien Grall wrote:
>
> Hi,
>
> On 21/03/2022 15:58, Luca Fancellu wrote:
>>> On 18 Mar 2022, at 16:12, Julien Grall wrote:
>>>
>>> Hi Luca,
>>>
>>> I only skimmed through the series. I have one question below:
>>>
>>> On 18/03/2022 15:25, Luca Fancell
Hi,
On 21/03/2022 15:58, Luca Fancellu wrote:
On 18 Mar 2022, at 16:12, Julien Grall wrote:
Hi Luca,
I only skimmed through the series. I have one question below:
On 18/03/2022 15:25, Luca Fancellu wrote:
+void __init btcpupools_allocate_pools(void)
+{
+unsigned int i;
+bool add_
> On 18 Mar 2022, at 16:12, Julien Grall wrote:
>
> Hi Luca,
>
> I only skimmed through the series. I have one question below:
>
> On 18/03/2022 15:25, Luca Fancellu wrote:
>> +void __init btcpupools_allocate_pools(void)
>> +{
>> +unsigned int i;
>> +bool add_extra_cpupool = false;
>>
> On 21 Mar 2022, at 09:10, Jan Beulich wrote:
>
> On 18.03.2022 16:25, Luca Fancellu wrote:
>> --- a/xen/common/Makefile
>> +++ b/xen/common/Makefile
>> @@ -1,5 +1,6 @@
>> obj-$(CONFIG_ARGO) += argo.o
>> obj-y += bitmap.o
>> +obj-$(CONFIG_BOOT_TIME_CPUPOOLS) += boot_cpupools.o
>
> By the loo
On 18.03.2022 16:25, Luca Fancellu wrote:
> --- a/xen/common/Makefile
> +++ b/xen/common/Makefile
> @@ -1,5 +1,6 @@
> obj-$(CONFIG_ARGO) += argo.o
> obj-y += bitmap.o
> +obj-$(CONFIG_BOOT_TIME_CPUPOOLS) += boot_cpupools.o
By the looks of it you appear to want to specify boot_cpupools.init.o
here
Hi Luca,
I only skimmed through the series. I have one question below:
On 18/03/2022 15:25, Luca Fancellu wrote:
+void __init btcpupools_allocate_pools(void)
+{
+unsigned int i;
+bool add_extra_cpupool = false;
+
+/*
+ * If there are no cpupools, the value of next_pool_id is zer
18 matches
Mail list logo
