From: Henry Wang <xin.wang2@amd.com>
To: Jason Andryuk <jason.andryuk@amd.com>, <xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony@xenproject.org>,
George Dunlap <george.dunlap@citrix.com>,
Nick Rosbrook <rosbrookn@gmail.com>,
"Juergen Gross" <jgross@suse.com>
Subject: Re: [PATCH v2 4/8] tools/arm: Introduce the "nr_spis" xl config entry
Date: Tue, 21 May 2024 07:19:50 +0800 [thread overview]
Message-ID: <db6c9b30-e63b-4979-976c-9171a2942e81@amd.com> (raw)
In-Reply-To: <0a87ccc8-4262-4122-8142-2f64a174bab2@amd.com>
Hi Jason,
On 5/21/2024 3:13 AM, Jason Andryuk wrote:
>> +
>> +=item B<nr_spis="NR_SPIS">
>> +
>> +A 32-bit optional integer parameter specifying the number of SPIs
>> (Shared
>
> I'd phrase it "An optional 32-but integer"
>
>> +Peripheral Interrupts) to allocate for the domain. If the `nr_spis`
>> parameter
>> +is missing, the max number of SPIs calculated by the toolstack based
>> on the
>> +devices allocated for the domain will be used.
>
> This text says the maximum only applies if xl.cfg nr_spis is not setup.
>
>> +
>> +=back
>> +
>> =head3 x86
>> =over 4
>
>> diff --git a/tools/libs/light/libxl_arm.c b/tools/libs/light/libxl_arm.c
>> index 1cb89fa584..a4029e3ac8 100644
>> --- a/tools/libs/light/libxl_arm.c
>> +++ b/tools/libs/light/libxl_arm.c
>> @@ -181,8 +181,8 @@ int libxl__arch_domain_prepare_config(libxl__gc *gc,
>> LOG(DEBUG, "Configure the domain");
>> - config->arch.nr_spis = nr_spis;
>> - LOG(DEBUG, " - Allocate %u SPIs", nr_spis);
>> + config->arch.nr_spis = max(nr_spis,
>> d_config->b_info.arch_arm.nr_spis);
>> + LOG(DEBUG, " - Allocate %u SPIs", config->arch.nr_spis);
>
> But this is always taking the max. Should it instead be:
>
> config->arch.nr_spis = d_config->b_info.arch_arm.nr_spis ?: nr_spis;
>
> However, I don't know if that makes sense for ARM. Does the hardware
> nr_spis need to be a minimum for a domain?
>
> Really, we just want the documentation to match the code.
Before you pointed this out, I didn't realize the ambiguity in the doc
about the "max". The "max" in the doc have different meanings compared
to the "max()" in the code. I will drop the "max" in the doc and reword
the doc to "If the `nr_spis` parameter is missing, the number of SPIs
calculated by the toolstack based on the devices allocated for the
domain will be used.". Thanks for pointing it out.
Kind regards,
Henry
>
> Thanks,
> Jason
next prev parent reply other threads:[~2024-05-20 23:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 10:03 [PATCH v2 0/8] Remaining patches for dynamic node programming using overlay dtbo Henry Wang
2024-05-16 10:03 ` [PATCH v2 1/8] xen/common/dt-overlay: Fix lock issue when add/remove the device Henry Wang
2024-05-19 10:04 ` Julien Grall
2024-05-16 10:03 ` [PATCH v2 2/8] tools/xl: Correct the help information and exit code of the dt-overlay command Henry Wang
2024-05-20 18:48 ` Jason Andryuk
2024-05-16 10:03 ` [PATCH v2 3/8] xen/arm, doc: Add a DT property to specify IOMMU for Dom0less domUs Henry Wang
2024-05-19 10:17 ` Julien Grall
2024-05-20 0:41 ` Henry Wang
2024-05-20 1:38 ` Henry Wang
2024-05-20 1:40 ` Henry Wang
2024-05-16 10:03 ` [PATCH v2 4/8] tools/arm: Introduce the "nr_spis" xl config entry Henry Wang
2024-05-20 19:13 ` Jason Andryuk
2024-05-20 23:19 ` Henry Wang [this message]
2024-05-16 10:03 ` [PATCH v2 5/8] xen/arm/gic: Allow routing/removing interrupt to running VMs Henry Wang
2024-05-17 6:03 ` Henry Wang
2024-05-19 11:08 ` Julien Grall
2024-05-20 1:01 ` Henry Wang
2024-05-20 9:50 ` Julien Grall
2024-05-21 2:29 ` Stefano Stabellini
2024-05-16 10:03 ` [PATCH v2 6/8] xen/arm: Add XEN_DOMCTL_dt_overlay DOMCTL and related operations Henry Wang
2024-05-16 12:31 ` Jan Beulich
2024-05-17 1:36 ` Henry Wang
2024-05-17 7:11 ` Jan Beulich
2024-05-16 10:03 ` [PATCH v2 7/8] tools: Introduce the "xl dt-overlay {attach,detach}" commands Henry Wang
2024-05-20 19:41 ` Jason Andryuk
2024-05-20 23:21 ` Henry Wang
2024-05-16 10:03 ` [PATCH v2 8/8] docs: Add device tree overlay documentation Henry Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db6c9b30-e63b-4979-976c-9171a2942e81@amd.com \
--to=xin.wang2@amd.com \
--cc=anthony@xenproject.org \
--cc=george.dunlap@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=jgross@suse.com \
--cc=rosbrookn@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.