docs: fusa: Add dom0less domain configuration requirements
PATCH 1/1 docs: fusa: Add dom0less domain configuration requirements
From: Michal Orzel <[email protected]>
Add requirements for dom0less domain creation.
--- .../arm64/dom0less_domain_config.rst | 267 ++++++++++++++++++ docs/fusa/reqs/market-reqs/reqs.rst | 15 + docs/fusa/reqs/product-reqs/arm64/reqs.rst | 20 ++ 3 files changed, 302 insertions(+) create mode 100644 docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +267 -0
@@ -0,0 +1,267 @@ +.. SPDX-License-Identifier: CC-BY-4.0 + +Dom0less Domain configuration requirements +========================================== + +The following are the requirements related to dom0less domain configuration for +Arm64 domains. + +Specify Arm64 Linux kernel image +---------------------------------- + +`XenSwdgn~arm64_specify_kernel_linux_image~1` + +Description: +Xen shall create a domain with a Arm64 Linux kernel image. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify Arm64 Gzip Linux kernel image +--------------------------------------- + +`XenSwdgn~arm64_specify_kernel_gzip_image~1` + +Description: +Xen shall create a domain with a Arm64 Gzip compressed Linux kernel image. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify kernel with uImage header +--------------------------------- + +`XenSwdgn~arm64_specify_kernel_uimage~1` + +Description: +Xen shall create a domain with a kernel containing uImage header. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify Gzip kernel with uImage header +-------------------------------------- + +`XenSwdgn~arm64_specify_gzip_kernel_uimage~1` + +Description: +Xen shall create a domain with a Gzip compressed kernel containing uImage +header. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify passthrough device tree +------------------------------- + +`XenSwdgn~arm64_specify_passthrough_dt~1` + +Description: +Xen shall support direct assignment of devices to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify kernel command line arguments +------------------------------------- + +`XenSwdgn~arm64_specify_kernel_cmd_line_args~1` + +Description: +Xen shall pass kernel command line arguments to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify initial ramdisk +----------------------- + +`XenSwdgn~arm64_specify_initial_ramdisk~1` + +Description: +Xen shall provide initial ramdisk to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify amount of memory +------------------------ + +`XenSwdgn~arm64_specify_memory~1` + +Description: +Xen shall create a domain with specified amount of memory. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Assign a single vCPU +-------------------- + +`XenSwdgn~arm64_assign_single_vcpu~1` + +Description: +Xen shall assign a single vCPU to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Assign multiple vCPUs +--------------------- + +`XenSwdgn~arm64_assign_multiple_vcpus~1` + +Description: +Xen shall assign multiple vCPUs to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Assign vCPUs from CPU pool +-------------------------- + +`XenSwdgn~arm64_assign_vcpus_cpu_pool~1` + +Description: +Xen shall assign vCPUs to a domain from a CPU pool. + +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. + +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. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of SPIs +---------------------- + +`XenSwdgn~arm64_specify_num_spis~1` + +Description: +Xen shall allocate a specified number of shared peripheral interrupts for a +domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify grant table version for a domain +---------------------------------------- + +`XenSwdgn~arm64_specify_grant_table_version~1` + +Description: +Xen shall create a domain with a specified version of grant table structure + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of grant table frames for a domain +------------------------------------------------- + +`XenSwdgn~arm64_specify_num_grant_table_frames~1` + +Description: +Xen shall create a domain with a specified number of grant table frames. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of grant maptrack frames for a domain +---------------------------------------------------- + +`XenSwdgn~arm64_specify_num_grant_maptrack_frames~1` + +Description: +Xen shall create a domain with a specified number of grant maptrack frames. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +| [1] https://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/device-tree/booting.txt +| [2] https://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/device-tree/cpupools.txt
docs/fusa/reqs/market-reqs/reqs.rst +15 -0
@@ -47,3 +47,18 @@ Comments: Needs: - XenProd + +Static VM definition +-------------------- + +`XenMkt~static_vm_definition~1` + +Description: +Xen shall support specifying resources for a domain. + +Rationale: + +Comments: + +Needs: + - XenProd
docs/fusa/reqs/product-reqs/arm64/reqs.rst +20 -0
@@ -40,3 +40,23 @@ Covers: Needs: - XenSwdgn + +Configure static domains +------------------------ + +`XenProd~static_domains_configuration~1` + +Description: +Xen shall support specifying the resources required for a domain. + +Rationale: + +Comments: + +Rationale: + +Covers: + - `XenMkt~static_vm_definition~1` + +Needs: + - XenSwdgn
Signature · 1 line
2.25.1
Quoted 7 lines · On October 18, 2024 Ayan Kumar Halder <[email protected]> wrote:
From: Michal Orzel <[email protected]>
Add requirements for dom0less domain creation.
Signed-off-by Michal Orzel <[email protected]>Signed-off-by Ayan Kumar Halder <[email protected]>---
Minor: in lines like
- Xen shall assign multiple vCPUs to a domain
- Xen shall assign a CPU pool scheduler to a domain
is it better with 'specified'? E.g. "specified number of vCPUs" and so on.
-- Artem
Hi,
Quoted 24 lines · Ayan Kumar Halder
From: Michal Orzel <[email protected]>
Add requirements for dom0less domain creation.
Signed-off-by Michal Orzel <[email protected]>Signed-off-by Ayan Kumar Halder <[email protected]>--- .../arm64/dom0less_domain_config.rst | 267 ++++++++++++++++++ docs/fusa/reqs/market-reqs/reqs.rst | 15 + docs/fusa/reqs/product-reqs/arm64/reqs.rst | 20 ++ 3 files changed, 302 insertions(+)create mode 100644
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rstdocs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0@@ -0,0 +1,267 @@ +.. SPDX-License-Identifier: CC-BY-4.0 + +Dom0less Domain configuration requirements +========================================== +
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 15
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+The following are the requirements related to dom0less domain configuration for +Arm64 domains. + +Specify Arm64 Linux kernel image +---------------------------------- + +`XenSwdgn~arm64_specify_kernel_linux_image~1` + +Description: +Xen shall create a domain with a Arm64 Linux kernel image.
A link to the specification would be useful when you are referring to an external format.
Quoted 111 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +111
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify Arm64 Gzip Linux kernel image +--------------------------------------- + +`XenSwdgn~arm64_specify_kernel_gzip_image~1` + +Description: +Xen shall create a domain with a Arm64 Gzip compressed Linux kernel image. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify kernel with uImage header +--------------------------------- + +`XenSwdgn~arm64_specify_kernel_uimage~1` + +Description: +Xen shall create a domain with a kernel containing uImage header. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify Gzip kernel with uImage header +-------------------------------------- + +`XenSwdgn~arm64_specify_gzip_kernel_uimage~1` + +Description: +Xen shall create a domain with a Gzip compressed kernel containing uImage +header. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify passthrough device tree +------------------------------- + +`XenSwdgn~arm64_specify_passthrough_dt~1` + +Description: +Xen shall support direct assignment of devices to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify kernel command line arguments +------------------------------------- + +`XenSwdgn~arm64_specify_kernel_cmd_line_args~1` + +Description: +Xen shall pass kernel command line arguments to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify initial ramdisk +----------------------- + +`XenSwdgn~arm64_specify_initial_ramdisk~1` + +Description: +Xen shall provide initial ramdisk to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify amount of memory +------------------------ + +`XenSwdgn~arm64_specify_memory~1` + +Description: +Xen shall create a domain with specified amount of memory. + +Rationale: + +Comments: +
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 136
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+Covers: + - `XenProd~static_domains_configuration~1` + +Assign a single vCPU +-------------------- + +`XenSwdgn~arm64_assign_single_vcpu~1` + +Description: +Xen shall assign a single vCPU to a domain.
This wording is a bit ambiguous. You don't assign a vCPU to a domain. You create a domain with "N vCPUs". It is also not clear why we are making the distinction between one and ...
Quoted 5 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +Rationale: + +Comments: +
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 151
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+Covers: + - `XenProd~static_domains_configuration~1` + +Assign multiple vCPUs +--------------------- + +`XenSwdgn~arm64_assign_multiple_vcpus~1` + +Description: +Xen shall assign multiple vCPUs to a domain.
... multiple one. From Xen PoV there is no differences.
Quoted 5 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +Rationale: + +Comments: +
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 166
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+Covers: + - `XenProd~static_domains_configuration~1` + +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. You also assign pCPU to a CPU pool.
But I am not sure about if this requirement is actually necessary given ...
Quoted 5 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +Rationale: + +Comments: +
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 181
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+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.
Quoted 5 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +Rationale: + +Comments: +
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 196
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+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?
Quoted 21 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +21
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of SPIs +---------------------- + +`XenSwdgn~arm64_specify_num_spis~1` + +Description: +Xen shall allocate a specified number of shared peripheral interrupts for a +domain. + +Rationale: + +Comments: +
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 227
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+Covers: + - `XenProd~static_domains_configuration~1` + +Specify grant table version for a domain +---------------------------------------- + +`XenSwdgn~arm64_specify_grant_table_version~1` + +Description: +Xen shall create a domain with a specified version of grant table structure
Realistically grant table v2 is not supported for Arm and I am not convinced it makes any sense for x86 in embedded system. It is mainly useful when you have a guest with a large amount of address space (IIRC > 4TB).
Quoted 46 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +40
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of grant table frames for a domain +------------------------------------------------- + +`XenSwdgn~arm64_specify_num_grant_table_frames~1` + +Description: +Xen shall create a domain with a specified number of grant table frames. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of grant maptrack frames for a domain +---------------------------------------------------- + +`XenSwdgn~arm64_specify_num_grant_maptrack_frames~1` + +Description: +Xen shall create a domain with a specified number of grant maptrack frames. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +| [1] https://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/device-tree/booting.txt +| [2] https://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/device-tree/cpupools.txtdocs/fusa/reqs/market-reqs/reqs.rst +0
-0@@ -47,3 +47,18 @@ Comments:
docs/fusa/reqs/market-reqs/reqs.rst Comments: · line 57
Quoted 10 lines
docs/fusa/reqs/market-reqs/reqs.rst +8
-0Needs: - XenProd + +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?
Quoted 27 lines
docs/fusa/reqs/market-reqs/reqs.rst +7
-0+ +Rationale: + +Comments: + +Needs: + - XenProddocs/fusa/reqs/product-reqs/arm64/reqs.rst +11
-0@@ -40,3 +40,23 @@ Covers: Needs: - XenSwdgn + +Configure static domains +------------------------ + +`XenProd~static_domains_configuration~1` + +Description: +Xen shall support specifying the resources required for a domain. + +Rationale: +
docs/fusa/reqs/product-reqs/arm64/reqs.rst Covers: · line 62
Quoted 10 lines
docs/fusa/reqs/product-reqs/arm64/reqs.rst +9
-0+Comments: + +Rationale: + +Covers: + - `XenMkt~static_vm_definition~1` + +Needs: + - XenSwdgn
Missing a newline.
Signature · 1 line
Julien Grall
Quoted 1 line · Julien Grall
Hi,
Hi Julien,
Quoted 193 lines · Ayan Kumar Halder
Quoted 26 lines
From: Michal Orzel <[email protected]>
Add requirements for dom0less domain creation.
Signed-off-by Michal Orzel <[email protected]>Signed-off-by Ayan Kumar Halder <[email protected]>---
.../arm64/dom0less_domain_config.rst | 267 ++++++++++++++++++ docs/fusa/reqs/market-reqs/reqs.rst | 15 + docs/fusa/reqs/product-reqs/arm64/reqs.rst | 20 ++3 files changed, 302 insertions(+)create mode 100644
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rstdocs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +6
-0@@ -0,0 +1,267 @@ +.. SPDX-License-Identifier: CC-BY-4.0 + +Dom0less Domain configuration requirements +========================================== + +The following are the requirements related to dom0less domainconfiguration for
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 15
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+Arm64 domains. + +Specify Arm64 Linux kernel image +---------------------------------- + +`XenSwdgn~arm64_specify_kernel_linux_image~1` + +Description: +Xen shall create a domain with a Arm64 Linux kernel image.A link to the specification would be useful when you are referring to an external format.
Quoted 113 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +15
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify Arm64 Gzip Linux kernel image +--------------------------------------- + +`XenSwdgn~arm64_specify_kernel_gzip_image~1` + +Description: +Xen shall create a domain with a Arm64 Gzip compressed Linux kernelimage.
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +30
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify kernel with uImage header +--------------------------------- + +`XenSwdgn~arm64_specify_kernel_uimage~1` + +Description: +Xen shall create a domain with a kernel containing uImage header. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify Gzip kernel with uImage header +-------------------------------------- + +`XenSwdgn~arm64_specify_gzip_kernel_uimage~1` + +Description: +Xen shall create a domain with a Gzip compressed kernel containinguImage
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +66
-0+header. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify passthrough device tree +------------------------------- + +`XenSwdgn~arm64_specify_passthrough_dt~1` + +Description: +Xen shall support direct assignment of devices to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify kernel command line arguments +------------------------------------- + +`XenSwdgn~arm64_specify_kernel_cmd_line_args~1` + +Description: +Xen shall pass kernel command line arguments to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify initial ramdisk +----------------------- + +`XenSwdgn~arm64_specify_initial_ramdisk~1` + +Description: +Xen shall provide initial ramdisk to a domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify amount of memory +------------------------ + +`XenSwdgn~arm64_specify_memory~1` + +Description: +Xen shall create a domain with specified amount of memory. + +Rationale: + +Comments: +docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 136
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+Covers: + - `XenProd~static_domains_configuration~1` + +Assign a single vCPU +-------------------- + +`XenSwdgn~arm64_assign_single_vcpu~1` + +Description: +Xen shall assign a single vCPU to a domain.This wording is a bit ambiguous. You don't assign a vCPU to a domain. You create a domain with "N vCPUs". It is also not clear why we are making the distinction between one and ...
Quoted 5 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +Rationale: + +Comments: +docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 151
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+Covers: + - `XenProd~static_domains_configuration~1` + +Assign multiple vCPUs +--------------------- + +`XenSwdgn~arm64_assign_multiple_vcpus~1` + +Description: +Xen shall assign multiple vCPUs to a domain.... multiple one. From Xen PoV there is no differences.
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Assign vCPUs from CPU pool
Quoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 166
Quoted 6 lines
+--------------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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.
(which of the two looks better to you if we keep the next requirement ?)
Comments:
Here N is determined by the device tree configuration provided by the user.
Quoted 13 lines
You also assign pCPU to a CPU pool.
But I am not sure about if this requirement is actually necessary given ...
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify CPU pool scheduler
Quoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 181
Quoted 6 lines
+--------------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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.
Quoted 10 lines
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Assign virtual UART
Quoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 196
Quoted 6 lines
+-------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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.
Quoted 28 lines
Quoted 28 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +15
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of SPIs +---------------------- + +`XenSwdgn~arm64_specify_num_spis~1` + +Description: +Xen shall allocate a specified number of shared peripheralinterrupts for a
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +11
-0+domain. + +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify grant table version for a domain +----------------------------------------
Quoted 8 lines
Quoted 6 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`XenSwdgn~arm64_specify_grant_table_version~1` + +Description: +Xen shall create a domain with a specified version of grant tablestructure
Realistically grant table v2 is not supported for Arm and I am not convinced it makes any sense for x86 in embedded system. It is mainly useful when you have a guest with a large amount of address space (IIRC > 4TB).
We can put this detail in comments.
Quoted 54 lines
Quoted 54 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +15
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of grant table frames for a domain +------------------------------------------------- + +`XenSwdgn~arm64_specify_num_grant_table_frames~1` + +Description: +Xen shall create a domain with a specified number of grant tableframes.
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +15
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify number of grant maptrack frames for a domain +---------------------------------------------------- + +`XenSwdgn~arm64_specify_num_grant_maptrack_frames~1` + +Description: +Xen shall create a domain with a specified number of grant maptrackframes.
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +| [1]https://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/device-tree/booting.txt
+| [2]
https://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=docs/misc/arm/device-tree/cpupools.txtdocs/fusa/reqs/market-reqs/reqs.rst +0
-0@@ -47,3 +47,18 @@ Comments:Needs:
- XenProddocs/fusa/reqs/market-reqs/reqs.rst +2
-0+ +Static VM definition
Quoted 8 lines
docs/fusa/reqs/market-reqs/reqs.rst Comments: · line 57
Quoted 6 lines
+--------------------
docs/fusa/reqs/market-reqs/reqs.rst +5
-0+ +`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 ?
Quoted 31 lines
Quoted 31 lines
docs/fusa/reqs/market-reqs/reqs.rst +7
-0+ +Rationale: + +Comments: + +Needs: + - XenProddocs/fusa/reqs/product-reqs/arm64/reqs.rst +0
-0@@ -40,3 +40,23 @@ Covers:Needs:
- XenSwdgndocs/fusa/reqs/product-reqs/arm64/reqs.rst +15
-0+ +Configure static domains +------------------------ + +`XenProd~static_domains_configuration~1` + +Description: +Xen shall support specifying the resources required for a domain. + +Rationale: + +Comments: + +Rationale: +
Quoted 8 lines
docs/fusa/reqs/product-reqs/arm64/reqs.rst Covers: · line 62
Quoted 6 lines
docs/fusa/reqs/product-reqs/arm64/reqs.rst +5
-0+Covers: + - `XenMkt~static_vm_definition~1` + +Needs: + - XenSwdgnMissing a newline.
- Ayan
Hi Ayan,
Quoted 10 lines · Ayan Kumar Halder
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 166
Quoted 7 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +7
-0+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.
Quoted 7 lines
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 ...
Quoted 2 lines
(which of the two looks better to you if we keep the next requirement ?)
... by the next one.
Quoted 45 lines
Comments:
Here N is determined by the device tree configuration provided by the user.
Quoted 13 lines
You also assign pCPU to a CPU pool.
But I am not sure about if this requirement is actually necessary given ...
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify CPU pool schedulerQuoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 181
Quoted 6 lines
+--------------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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.
Quoted 10 lines
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Assign virtual UARTQuoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 196
Quoted 6 lines
+-------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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?
Quoted 1 line
virtual PL011.
Is it possible to specify it in the market requirements?
[...]
Quoted 11 lines
Quoted 10 lines
docs/fusa/reqs/market-reqs/reqs.rst Comments: · line 57
Quoted 8 lines
docs/fusa/reqs/market-reqs/reqs.rst +8
-0+ +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?
Quoted 5 lines
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).
Cheers,
Signature · 1 line
Julien Grall
Quoted 1 line · Julien Grall
Hi Ayan,
Hi Julien,
Quoted 14 lines · Ayan Kumar Halder
Quoted 12 lines
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 166
Quoted 7 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +7
-0+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
Quoted 7 lines
Quoted 5 lines
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 ...
Ok, I will keep this.
Quoted 51 lines
Quoted 3 lines
(which of the two looks better to you if we keep the next requirement ?)
... by the next one.
Quoted 45 lines
Comments:
Here N is determined by the device tree configuration provided by the user.
Quoted 13 lines
You also assign pCPU to a CPU pool.
But I am not sure about if this requirement is actually necessary given ...
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify CPU pool schedulerQuoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 181
Quoted 6 lines
+--------------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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.
Quoted 18 lines
Quoted 6 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +Rationale: + +Comments: +docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 196
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+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?
Quoted 3 lines
Quoted 1 line
virtual PL011.
Is it possible to specify it in the market requirements?
We are talking about Xen's ability to **specify** virtual PL011 to a domain.
So, it should be a part of design requirement. Please see further ...
Quoted 14 lines
[...]
Quoted 11 lines
Quoted 10 lines
docs/fusa/reqs/market-reqs/reqs.rst Comments: · line 57
Quoted 8 lines
docs/fusa/reqs/market-reqs/reqs.rst +8
-0+ +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?
Quoted 7 lines
Quoted 5 lines
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).
In this case, the market requirement is "Xen shall support *specifying* resources for a domain".
Here, it doesn't really matter what the resources are. What matters, is Xen's ability to specify resources for creating a domain.
Now, if you look at the design requirements, we say Xen shall support specifying uImage, zImage, vpl011, ramdisk, no of spis, etc. So these are the resources that can be specified.
Tomorrow, we can add more resources which will imply that new design requirements will be created/modified. However, the market requirement stays the same.
Please let me know if it makes sense ?
- Ayan
Hi Ayan and Julien,
Quoted 83 lines · Julien Grall
Hi Ayan,
Quoted 9 lines · Ayan Kumar Halder
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 166
Quoted 7 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +7
-0+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.
Quoted 4 lines
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 ...
Quoted 1 line
(which of the two looks better to you if we keep the next requirement ?)
... by the next one.
Quoted 42 lines
Comments:
Here N is determined by the device tree configuration provided by the user.Quoted 13 lines
You also assign pCPU to a CPU pool.
But I am not sure about if this requirement is actually necessary given ...
Quoted 9 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Specify CPU pool schedulerQuoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 181
Quoted 6 lines
+--------------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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.
Quoted 10 lines
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +9
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` + +Assign virtual UARTQuoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 196
Quoted 6 lines
+-------------------
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +`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?
Quoted 1 line
virtual PL011.
Is it possible to specify it in the market requirements?
[...]
Quoted 10 lines
Quoted 10 lines
docs/fusa/reqs/market-reqs/reqs.rst Comments: · line 57
Quoted 8 lines
docs/fusa/reqs/market-reqs/reqs.rst +8
-0+ +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?
Quoted 5 lines
Quoted 3 lines
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
Quoted 5 lines
Cheers,
Signature · 1 line
Julien Grall
Quoted 1 line · Bertrand Marquis
Hi Ayan and Julien,
Hi,
Quoted 76 lines
Quoted 76 lines · Julien Grall
Hi Ayan,
Quoted 8 lines · Ayan Kumar Halder
Quoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 166
Quoted 7 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +7
-0+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.
Quoted 4 lines
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 ...
Quoted 1 line
(which of the two looks better to you if we keep the next requirement ?)
... by the next one.
Quoted 39 lines
Comments:
Here N is determined by the device tree configuration provided by the user.Quoted 4 lines
You also assign pCPU to a CPU pool.
But I am not sure about if this requirement is actually necessary given ...
Quoted 16 lines
Quoted 5 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +5
-0+ +Rationale: + +Comments: +docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 181
Quoted 10 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +10
-0+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.
Quoted 8 lines
Quoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +8
-0+ +Rationale: + +Comments: + +Covers: + - `XenProd~static_domains_configuration~1` +Quoted 8 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst line 196
Quoted 7 lines
docs/fusa/reqs/design-reqs/arm64/dom0less_domain_config.rst new file +7
-0+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?
Quoted 1 line
virtual PL011.
Is it possible to specify it in the market requirements?
[...]
Quoted 9 lines
Quoted 9 lines
docs/fusa/reqs/market-reqs/reqs.rst Comments: · line 57
Quoted 8 lines
docs/fusa/reqs/market-reqs/reqs.rst +8
-0+ +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?
Quoted 6 lines
Quoted 4 lines
Quoted 3 lines
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.
As per our discussion , the market requirement should be
Xen shall support assigning peripherals to various domains.
Comment: /* we need to define peripheral */
Peripheral implies an iomem (input output memory) and/or interrupts.
(This aligns with our definition of market requirement where we specify the capabilities of Xen at a high level.)
And the product requirements should be
1. Xen shall support assigning iomem to a domain.
2. Xen shall support forwarding interrupts to a domain.
(Here, we try to describe the interface between Xen and domain. So, domains unterstand how Xen will interact with them.)
The design requirements will be
1. Xen shall create a mapping for iomem in stage 2 page tables.
2. Xen shall route the interrupts to the domains.
3. Xen shall add iommu master (if present) for the iomem, to the domain's device tree.
4. Xen shall add the iomem to its iommu master.
5. Xen shall allow assignment of iomem without iommu protection.
The design requirements are still a bit high level ie it does not describe the details (at register level or granular level) of how Xen creates a mapping (for eg).
The advantage is that the requirements will be linked to the top level functions. It will allow the underneath functions to change without requiring us to modify the requirements.
Besides, it will help us to provide some justification for the missing coverage at the lower level (ie we can say that we don't really care if Xen chooses to perform a manual translation vs hardware translation. )
- Ayan
Quoted 8 lines
Cheers
BertrandQuoted 4 lines
Cheers,
Signature · 1 line
Julien Grall