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

Re: [PATCH v8 3/3] xen/domain: introduce CONFIG_MAX_DOMID


  • To: dmkhn@xxxxxxxxx
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Mon, 2 Jun 2025 09:13:24 +0200
  • Autocrypt: addr=jbeulich@xxxxxxxx; keydata= xsDiBFk3nEQRBADAEaSw6zC/EJkiwGPXbWtPxl2xCdSoeepS07jW8UgcHNurfHvUzogEq5xk hu507c3BarVjyWCJOylMNR98Yd8VqD9UfmX0Hb8/BrA+Hl6/DB/eqGptrf4BSRwcZQM32aZK 7Pj2XbGWIUrZrd70x1eAP9QE3P79Y2oLrsCgbZJfEwCgvz9JjGmQqQkRiTVzlZVCJYcyGGsD /0tbFCzD2h20ahe8rC1gbb3K3qk+LpBtvjBu1RY9drYk0NymiGbJWZgab6t1jM7sk2vuf0Py O9Hf9XBmK0uE9IgMaiCpc32XV9oASz6UJebwkX+zF2jG5I1BfnO9g7KlotcA/v5ClMjgo6Gl MDY4HxoSRu3i1cqqSDtVlt+AOVBJBACrZcnHAUSuCXBPy0jOlBhxPqRWv6ND4c9PH1xjQ3NP nxJuMBS8rnNg22uyfAgmBKNLpLgAGVRMZGaGoJObGf72s6TeIqKJo/LtggAS9qAUiuKVnygo 3wjfkS9A3DRO+SpU7JqWdsveeIQyeyEJ/8PTowmSQLakF+3fote9ybzd880fSmFuIEJldWxp Y2ggPGpiZXVsaWNoQHN1c2UuY29tPsJgBBMRAgAgBQJZN5xEAhsDBgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQoDSui/t3IH4J+wCfQ5jHdEjCRHj23O/5ttg9r9OIruwAn3103WUITZee e7Sbg12UgcQ5lv7SzsFNBFk3nEQQCACCuTjCjFOUdi5Nm244F+78kLghRcin/awv+IrTcIWF hUpSs1Y91iQQ7KItirz5uwCPlwejSJDQJLIS+QtJHaXDXeV6NI0Uef1hP20+y8qydDiVkv6l IreXjTb7DvksRgJNvCkWtYnlS3mYvQ9NzS9PhyALWbXnH6sIJd2O9lKS1Mrfq+y0IXCP10eS FFGg+Av3IQeFatkJAyju0PPthyTqxSI4lZYuJVPknzgaeuJv/2NccrPvmeDg6Coe7ZIeQ8Yj t0ARxu2xytAkkLCel1Lz1WLmwLstV30g80nkgZf/wr+/BXJW/oIvRlonUkxv+IbBM3dX2OV8 AmRv1ySWPTP7AAMFB/9PQK/VtlNUJvg8GXj9ootzrteGfVZVVT4XBJkfwBcpC/XcPzldjv+3 HYudvpdNK3lLujXeA5fLOH+Z/G9WBc5pFVSMocI71I8bT8lIAzreg0WvkWg5V2WZsUMlnDL9 mpwIGFhlbM3gfDMs7MPMu8YQRFVdUvtSpaAs8OFfGQ0ia3LGZcjA6Ik2+xcqscEJzNH+qh8V m5jjp28yZgaqTaRbg3M/+MTbMpicpZuqF4rnB0AQD12/3BNWDR6bmh+EkYSMcEIpQmBM51qM EKYTQGybRCjpnKHGOxG0rfFY1085mBDZCH5Kx0cl0HVJuQKC+dV2ZY5AqjcKwAxpE75MLFkr wkkEGBECAAkFAlk3nEQCGwwACgkQoDSui/t3IH7nnwCfcJWUDUFKdCsBH/E5d+0ZnMQi+G0A nAuWpQkjM1ASeQwSHEeAWPgskBQL
  • Cc: andrew.cooper3@xxxxxxxxxx, anthony.perard@xxxxxxxxxx, julien@xxxxxxx, michal.orzel@xxxxxxx, roger.pau@xxxxxxxxxx, sstabellini@xxxxxxxxxx, teddy.astie@xxxxxxxxxx, dmukhin@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 02 Jun 2025 07:13:26 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 22.05.2025 20:08, dmkhn@xxxxxxxxx wrote:
> On Thu, May 22, 2025 at 09:01:51AM +0200, Jan Beulich wrote:
>> On 22.05.2025 02:09, dmkhn@xxxxxxxxx wrote:
>>> On Wed, May 21, 2025 at 09:31:34AM +0200, Jan Beulich wrote:
>>>> On 21.05.2025 02:00, dmkhn@xxxxxxxxx wrote:
>>>>> --- a/xen/common/Kconfig
>>>>> +++ b/xen/common/Kconfig
>>>>> @@ -576,4 +576,11 @@ config BUDDY_ALLOCATOR_SIZE
>>>>>     Amount of memory reserved for the buddy allocator to serve Xen heap,
>>>>>     working alongside the colored one.
>>>>>
>>>>> +config MAX_DOMID
>>>>> + int "Maximum number of user domains"
>>>>> + range 1 32752
>>>>> + default 32752
>>>>> + help
>>>>> +   Specifies the maximum number of domains a user can create.
>>>>
>>>> My prior comment remains: The description and help needs to be accurate, in
>>>> order to not cause any confusion. In a true dom0less environment I'm not
>>>> sure the "user" can create any domains (post boot, that is). And when there
>>>> is Dom0 (or late hwdom), the number specified already isn't the number of
>>>> domains one can create (again, post boot, which is how I understand "user
>>>> domains"). If someone picked 1 as the value here, it's unclear to me how
>>>> late hwdom or dom0less would work in the first place.
>>>
>>> Do you think something like the following will be more accurate?
>>>
>>>     config MAX_DOMID
>>>        int "Maximum number of domains"
>>>        range 1 32752
>>>        default 32752
>>>        help
>>>          Specifies the maximum number of domains: dom0 or late hwdom,
>>>          predefined domains, post-boot domains, excluding Xen system domains
>>>          (domid >= DOMID_FIRST_RESERVED).
>>
>> Especially the mention of DOMID_FIRST_RESERVED is too much of an 
>> implementation
>> detail here, imo. Beyond that - maybe, but I'm not overly happy this way 
>> either.
> 
> Will the following description will be satisfactory?
> 
> config MAX_DOMID
>        int "Maximum domain ID"
>        range 1 32752
>        default 32752
>        help
>          Specifies the maximum domain ID (dom0 or late hwdom, predefined
>          domains, post-boot domains, excluding Xen system domains).

This is better, yes, yet ...

>> As an aside - MAX_DOMID and "Maximum number of domains" are conflicting
>> with one another, too: Do you mean "maximum ID" or "maximum number of"? The 
>> two
>> are different by 1.
> 
> That would be "maximum ID", thank you.

... imo asking for "maximum" of something is perhaps a little odd. Asking for
"number of" is the more usual thing imo.

Yet as before - I remain unconvinced we need such a Kconfig setting in the first
place.

Jan



 


Rackspace

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