On 22.03.2023 08:32, Luca Fancellu wrote:
> While I was browsing the code, I spotted a possible bug in x86/dom0_build.c,
> in
> parse_dom0_param(...) if an option is not recognised we set rc = -EINVAL, but
> we don’t
> stop the loop and we continue to parse.
> Is it the intended behaviour?
My vi
> On 20 Mar 2023, at 09:13, Jan Beulich wrote:
>
> On 17.03.2023 14:19, Luca Fancellu wrote:
>> --- a/docs/misc/xen-command-line.pandoc
>> +++ b/docs/misc/xen-command-line.pandoc
>> @@ -1005,6 +1005,19 @@ restrictions set up here. Note that the values to be
>> specified here are
>> ACPI PXM on
On 17.03.2023 14:19, Luca Fancellu wrote:
> --- a/docs/misc/xen-command-line.pandoc
> +++ b/docs/misc/xen-command-line.pandoc
> @@ -1005,6 +1005,19 @@ restrictions set up here. Note that the values to be
> specified here are
> ACPI PXM ones, not Xen internal node numbers. `relaxed` sets up vCPU
>
Add a command line parameter to allow Dom0 the use of SVE resources,
the command line parameter dom0_sve controls the feature on this
domain and sets the maximum SVE vector length for Dom0.
Signed-off-by: Luca Fancellu
---
Changes from v2:
- xen_domctl_createdomain field has changed into sve_vl