[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v3 4/6] xen/cpupool: Create different cpupools at boot time


  • To: Julien Grall <julien@xxxxxxx>
  • From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
  • Date: Tue, 22 Mar 2022 09:28:09 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=K4Ed22QyPFVFW9dzBUoCNppqa0LRw0wPhkWhS2Th3NY=; b=aPnOtHTqUezGN5nz+r8zCdHnX4ZA0XGxnwqUW4myO2eBJILInuejWJ13TPoWakqx5PPvOr3q/DF93F8tJ9BTslmsBQnmWY4bMphbZQ/RcYqxSw2pcAhpgk0JHkqBAEeWHVa3TkO5EMlhxDlmAm8fK9lAwJl4Gn4sa02rMkajEf+PoGLZypkxbfMN80SZC2cE497NX8C2mdWoeMQKGelSVuwnFXCzNJaR8MTJaKk1tbbP2K0p+oU0Axe66HMEsBFC4sAM8Bc4dyOzvLhJIjT4itJQXajj3tf/cM6ggrT6f29o2zKgbbMstMictYEvuJVnURThBn/LM4ok7JE29xFocA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bhhEOIYaMDuekYV/yinU/KwQsfZwIStNK+0rWgcRLnMEurkTouRtKBevAJHjz5QzQOGVVz40ewxT3bvndsuf3D9m3R0rIaituNmZZo5RGtG7YFyue6oG/ezPhL+D9QG2GVES8c/vHd84s2XO5upNCs4S/DPBWWUUwzij5AdfVlnGD1f6wAXDpnVglbqM+63YRBMD0g0C0mBG1IEvyISIw/dc8EoZvRlBGrKOzSvsSQD0fSVEO9wTUwyPebNbVTSc5o0p0M1qBTS+aEHHbLhTaSnG/H/LUO26OEBXoXC1voLjZcTNGOUHSWPck7Wac2lRnv2YHG/uIEgeE+qEEnKwiQ==
  • Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Cc: Luca Fancellu <Luca.Fancellu@xxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Wei Chen <Wei.Chen@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Wei Liu <wl@xxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Dario Faggioli <dfaggioli@xxxxxxxx>
  • Delivery-date: Tue, 22 Mar 2022 09:28:29 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHYOtyBwlLK7ts4vEKxgpEPsRlgQ6zFUCoAgASzLwCAAAp/AIAADB+AgAAHFICAAPi1AIAAA2QAgAAIDACAAANfAA==
  • Thread-topic: [PATCH v3 4/6] xen/cpupool: Create different cpupools at boot time

Hi Julien,

> On 22 Mar 2022, at 10:16, Julien Grall <julien@xxxxxxx> wrote:
> 
> Hi,
> 
> On 22/03/2022 08:47, Bertrand Marquis wrote:
>> Hi Julien,
>>> On 22 Mar 2022, at 09:35, Bertrand Marquis <bertrand.marquis@xxxxxxx> wrote:
>>> 
>>> Hi Julien,
>>> 
>>>> On 21 Mar 2022, at 18:44, Julien Grall <julien@xxxxxxx> wrote:
>>>> 
>>>> Hi Bertrand,
>>>> 
>>>> On 21/03/2022 17:19, Bertrand Marquis wrote:
>>>>>> On 21 Mar 2022, at 17:36, Julien Grall <julien@xxxxxxx> 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 features that x86 supports 
>>>>>> (e.g. CPU hotplug, suspend/resume...). So I a am bit concerned that the 
>>>>>> restriction is just not there yet (or possibly hidden).
>>>>>> 
>>>>>> Therefore, before lifting the restriction on Arm (and other arch), I 
>>>>>> would like us to understand why it is necessary on x86.
>>>>>> 
>>>>>> We may not have the answer quickly, so is it going to be a problem to 
>>>>>> keep the restriction on Arm?
>>>>> I am ok to keep the limitation to have dom0 always running on cpu0.
>>>>> Only limitation I can see is that on a big little system, dom0 needs to 
>>>>> stay on the type of core of the first booted core.
>>>> 
>>>> Where does this limitation come from?
>>> 
>>> If dom0 must run on core0 and core0 is Little then you cannot build a 
>>> system where dom0 is running on big cores.
>>> If the limitation is not there, you can build such a configuration without 
>>> any dependency to the boot core type.
>> This might not be completely clear so let me rephrase:
>> In the current system:
>> - dom0 must run on cpupool-0
> 
> I don't think we need this restriction. In fact, with this series it will 
> become more a problem because the cpupool ID will based on how we parse the 
> Device-Tree.
> 
> So for dom0, we need to specify explicitely the cpupool to be used.
> 
>> - cpupool-0 must contain the boot core
>> - consequence: dom0 must run on the boot core
>> If boot core is little, you cannot build as system where dom0 runs only on 
>> the big cores.
>> Removing the second limitation (which is not required on arm) is making it 
>> possible.
> 
> IMHO removing the second restriction is a lot more risky than removing the 
> first one.

So keeping boot core in cpupool-0 but allow Dom-0 to be in any pool.
Interesting, we will check that.

Cheers
Bertrand

> 
> Cheers,
> 
> -- 
> Julien Grall


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.