[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] docs: fusa: Add dom0less domain configuration requirements
- To: Julien Grall <julien@xxxxxxx>
- From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
- Date: Tue, 19 Nov 2024 09:04:33 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=arm.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
- 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=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=1vACK1HSaHzL/mz7Rr6i7agxoMX1IUmNc6nweGCO74o=; b=QqeJDLgtSInF9JfVmut7S9zGboFvtHQB4gDKVQoEWND/wPM1SuzDPdL7uO7ycWznqBp68EZ3RxCoSz918XgJmOaENZmlUNjgSoOK8t/PcqRe4IEPcuzUY6O3Opb4mYXUxNOcoMHLPHnZylIz993K2XyiIF5Z6SCiv1U3OmWUeZ4/3oPf12KQgtpKwZJf85HMU0YPa/XXL/X9jN7XCc/mbQfBfIhXvH4oZjtbZGbMoNDs6+BJybyXhgckQmPAXPYT1EMPXm6f8EKd9psmm/HrS/BdmI6JNpZSUgdPBkd45V3Qec8SMz9jpPjCFa3X9ipythAk9rCacPriAjxEJYmuxw==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=1vACK1HSaHzL/mz7Rr6i7agxoMX1IUmNc6nweGCO74o=; b=mtP5KvSqJuCcUmK+z8efwoUQzQ6b/xWbIkG1rgVFmQ+dAgsl27QzXDJzk8YOnkUpDNvXL13MXv/4UctN2LYI4tWhu6RjaZ9JmzBcWoTW+zTNO1CrJNlAaWqIqToJxjg88RvJqlvaKggnhxgQg+v9RSsulSHU1IgIpzKpS/rqzqaLY4ch5n1O2t6zqfBM7GNohGrIF7phjEeVujXkxOLE6LFzP+OiMR62HjNz4wXlsBezYz5l3qNodRecP0cF2KhJPaRAhSBuezDl+877RV35tDJg//KByGT80tpsEDA2KXEKx76V8SfUKDz0exz+rmwBqLBJhVgOWUwyCJgQ7CkGJQ==
- Arc-seal: i=2; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=pass; b=fpk0BiHRMXQGgUplIFvioCoJo/o9L3gPojUbbQYawG7K9Gie4wrTCwzVSd4xbdfHk9VTulyrS6tdVhv28wrk/WQwZLy45oQ2odYpp8X8p5qSfeMr5cBUCAxKJI20PiRDswuiL0PfgZuQqChrqXEB8RxC82iAWdTAeGohQrpj0O9Etys3bcqQUuWKTTFy+VV0TJmA9ay87wOjLLm8hQa5diHhzHsn59ZTwzIzjnLvCzbmEoQnKSVj/U4dMsY9vL+6JxIok3vzEhBXZmQcyNUSSSYEGGjuAWWvGNk239Q+FhFYFla6x19b88N+Y673WSHyjQR+oPlR6o598KjeP0SrFA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=cpfdek2v1mrhOkPpP1H/hhK0LOlM/PN4do4N4OYB8VDl8NYq61EHCxiY06gOwzG9AmFgzNGJAaB2dt5BaoAwufrnqtnvdpcn66fZ2fudLWZpDrrY7O7ROEDM1NxiNs0Ui5ymblu+WUglxSAaAxZcEbDXrpVqn5402d0cctzXt5Squ2O8xk7lwpZTme4GYjAcgW0HOQz1YAW1T++qy5i6wfXDSYXzHk3QHKIfhUryXtf0hqmVo/8oeG45nudRilxIPk/yIGfeQlO9neNIhtgH5BHcGg6+S07lO9ktXpwVN672lKnpHzdsCYkBIgEqYBifbNb/o8s2tDgU9IQqHdAvmw==
- Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Cc: Ayan Kumar Halder <ayankuma@xxxxxxx>, Ayan Kumar Halder <ayan.kumar.halder@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Artem Mygaiev <artem_mygaiev@xxxxxxxx>, Munakata Hisao <hisao.munakata.vt@xxxxxxxxxxx>
- Delivery-date: Tue, 19 Nov 2024 09:05:02 +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: AQHbIXWuBuVgfl53Mk+cNah5xpYpeLK1GpsAgAPBuwCAAPyRAIAEqDkA
- Thread-topic: [PATCH] docs: fusa: Add dom0less domain configuration requirements
Hi Ayan and Julien,
> On 16 Nov 2024, at 10:57, Julien Grall <julien@xxxxxxx> wrote:
>
> Hi Ayan,
>
> On 15/11/2024 18:53, Ayan Kumar Halder wrote:
>>>> +Assign vCPUs from CPU pool
>>>> +--------------------------
>>>> +
>>>> +`XenSwdgn~arm64_assign_vcpus_cpu_pool~1`
>>>> +
>>>> +Description:
>>>> +Xen shall assign vCPUs to a domain from a CPU pool.
>>>
>>> Same remark about the wording. You create a domain with N vCPUs and
>>> *assign* a CPU pool to a domain.
>> Ok, so all the previous 3 requirements can be merged into
>> Xen shall create a domain with N vCPUs and assign a CPU pool to a domain.
>> Or
>> Xen shall create a domain with N vCPUs.
>
> I think this one is better because it is not mandatory for the user to select
> a CPU pool and you will have it ...
>
>> (which of the two looks better to you if we keep the next requirement ?)
>
> ... by the next one.
>
>> Comments:
>> Here N is determined by the device tree configuration provided by the user.
>>> You also assign pCPU to a CPU pool.
>>>
>>> But I am not sure about if this requirement is actually necessary given ...
>>>
>>>> +
>>>> +Rationale:
>>>> +
>>>> +Comments:
>>>> +
>>>> +Covers:
>>>> + - `XenProd~static_domains_configuration~1`
>>>> +
>>>> +Specify CPU pool scheduler
>>>> +--------------------------
>>>> +
>>>> +`XenSwdgn~arm64_specify_cpu_pool_scheduler~1`
>>>> +
>>>> +Description:
>>>> +Xen shall assign a CPU pool scheduler to a domain.
>>>
>>> ... you have th is one.
>> So, we can keep it as it is.
>>>
>>>> +
>>>> +Rationale:
>>>> +
>>>> +Comments:
>>>> +
>>>> +Covers:
>>>> + - `XenProd~static_domains_configuration~1`
>>>> +
>>>> +Assign virtual UART
>>>> +-------------------
>>>> +
>>>> +`XenSwdgn~arm64_assign_virtual_uart~1`
>>>> +
>>>> +Description:
>>>> +Xen shall assign a virtual UART to a domain.
>>>
>>> Are we talking about the virtual PL011 or the fake emulation of the real
>>> UART we do?
>> virtual PL011.
>
> Is it possible to specify it in the market requirements?
>
> [...]
>
>>>> +
>>>> +Static VM definition
>>>> +--------------------
>>>> +
>>>> +`XenMkt~static_vm_definition~1`
>>>> +
>>>> +Description:
>>>> +Xen shall support specifying resources for a domain.
>>>
>>> Compare to the other requirements, this is quite a vague. Should we list
>>> the resources?
>> The list of resources depends on what the user has provided in the device
>> tree configuration.
>> But the requirement is correct as it is. Xen allows direct assignment of
>> devices to domains (ie passthrough).
>> How do you want to write it ?
>
> This is probably a better question for Bertrand. I don't know how market
> requirements are usually described. I was making a comparison with the other
> where you explicitely listed the expected resources (e.g. CPU, Memory,
> device).
I definitely agree with Julien here, this requirement is not clear as
"resources" is not specified or defined.
I would highly suggest to be more specific by listing what we mean by resources
and maybe even split this requirement in several to make testing and linking
easier.
Cheers
Bertrand
>
> Cheers,
>
> --
> Julien Grall
|