All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Daniel P. Smith" <dpsmith@apertussolutions.com>
Cc: jason.andryuk@amd.com, christopher.w.clark@gmail.com,
	stefano.stabellini@amd.com,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH 14/15] x86/hyperlaunch: add max vcpu parsing of hyperlaunch device tree
Date: Thu, 12 Dec 2024 12:37:46 +0100	[thread overview]
Message-ID: <18fd3e13-2e36-4d64-b56f-1227049bfb30@suse.com> (raw)
In-Reply-To: <18da1057-9874-44b0-a25c-f1ce733611f8@apertussolutions.com>

On 11.12.2024 20:49, Daniel P. Smith wrote:
> On 12/2/24 07:19, Jan Beulich wrote:
>> On 23.11.2024 19:20, Daniel P. Smith wrote:
>>> --- a/xen/arch/x86/dom0_build.c
>>> +++ b/xen/arch/x86/dom0_build.c
>>> @@ -617,6 +617,9 @@ int __init construct_dom0(struct boot_domain *bd)
>>>       if ( !get_memsize(&dom0_max_size, LONG_MAX) && bd->max_pages )
>>>           dom0_size.nr_pages = bd->max_pages;
>>>   
>>> +    if ( opt_dom0_max_vcpus_max == UINT_MAX && bd->max_vcpus )
>>> +        opt_dom0_max_vcpus_max = bd->max_vcpus;
>>
>> Isn't this kind of backwards? I.e. aren't you meaning to move us towards
>> boot-domains?
> 
> Prior to domain builder, available construction parameters for dom0 were 
> exposed as command line parameters. This allowed for boot-time 
> adjustments to the parameters. With domain builder, there are now two 
> sources for dom0 construction parameters. Those coming from the device 
> tree and those coming from the command line. For most x86 platforms, the 
> device tree parameters can only be constructed prior to booting Xen. 
> Whereas the command line parameters allow boot-time adjustments, at 
> least for dom0. That is the thinking at least. Now if there is interest 
> in being able to retire the command line options, that would definitely 
> simplify things.

No, retiring command line options is out of question imo. Yet that also
wasn't my point. Instead I was wondering why we wouldn't make bd->* the
ultimate source of truth. However, ...

>> Also, what about the counterpart opt_dom0_max_vcpus_min? That wants to be
>> controllable from DT too, I would think?
> 
> Yes, in theory we will eventually be able to do requested/min/max as 
> well as cpu pinning/affinity. For now it was requested we focus on 
> implementing only requested vcpus.

... that's pretty much only a reasonable option if these were converted
at the same time, to avoid becoming inconsistent for perhaps an extended
period of time.

Jan


  reply	other threads:[~2024-12-12 11:38 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23 18:20 [PATCH 00/15] Hyperlaunch device tree for dom0 Daniel P. Smith
2024-11-23 18:20 ` [PATCH 01/15] x86/boot: introduce boot domain Daniel P. Smith
2024-12-02  9:57   ` Jan Beulich
2024-12-04 19:16     ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 02/15] x86/boot: introduce domid field to struct boot_domain Daniel P. Smith
2024-11-23 18:20 ` [PATCH 03/15] x86/boot: add cmdline " Daniel P. Smith
2024-11-25 15:36   ` Jason Andryuk
2024-12-11  2:56     ` Daniel P. Smith
2024-12-02  9:49   ` Jan Beulich
2024-12-11  3:01     ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 04/15] kconfig: introduce option to independently enable libfdt Daniel P. Smith
2024-11-25 15:42   ` Jason Andryuk
2024-12-11  3:03     ` Daniel P. Smith
2024-11-26 10:03   ` Jan Beulich
2024-11-26 10:05     ` Jan Beulich
2024-12-11  3:05       ` Daniel P. Smith
2024-12-11  3:04     ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 05/15] kconfig: introduce domain builder config option Daniel P. Smith
2024-11-25 17:55   ` Jason Andryuk
2024-12-11  3:13     ` Daniel P. Smith
2024-11-26 10:09   ` Jan Beulich
2024-12-11  3:15     ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 06/15] x86/hyperlaunch: introduce the domain builder Daniel P. Smith
2024-11-25 17:52   ` Jason Andryuk
2024-11-25 20:23     ` Jason Andryuk
2024-12-02  9:55     ` Jan Beulich
2024-12-02 15:31       ` Jason Andryuk
2024-12-11 11:14     ` Daniel P. Smith
2024-12-02 10:10   ` Jan Beulich
2024-12-11 12:36     ` Daniel P. Smith
2024-12-12 11:06       ` Jan Beulich
2024-12-12 15:24         ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 07/15] x86/hyperlaunch: initial support for hyperlaunch device tree Daniel P. Smith
2024-11-25 20:11   ` Jason Andryuk
2024-12-11 12:49     ` Daniel P. Smith
2024-12-02 11:37   ` Jan Beulich
2024-12-11 12:55     ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 08/15] x86/hyperlaunch: locate dom0 kernel with hyperlaunch Daniel P. Smith
2024-11-25 22:54   ` Jason Andryuk
2024-12-11 14:19     ` Daniel P. Smith
2024-12-02 11:53   ` Jan Beulich
2024-12-11 15:41     ` Daniel P. Smith
2024-12-12 11:25       ` Jan Beulich
2024-11-23 18:20 ` [PATCH 09/15] x86/hyperlaunch: obtain cmdline from device tree Daniel P. Smith
2024-11-25 23:12   ` Jason Andryuk
2024-12-11 15:46     ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 10/15] x86/hyperlaunch: locate dom0 initrd with hyperlaunch Daniel P. Smith
2024-11-25 23:34   ` Jason Andryuk
2024-12-11 15:49     ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 11/15] x86/hyperlaunch: add domain id parsing to domain config Daniel P. Smith
2024-11-25 23:45   ` Jason Andryuk
2024-12-02 12:00     ` Jan Beulich
2024-12-11 16:07       ` Daniel P. Smith
2024-12-11 16:06     ` Daniel P. Smith
2024-12-02 12:02   ` Jan Beulich
2024-12-11 16:21     ` Daniel P. Smith
2024-12-19 16:40       ` Daniel P. Smith
2024-11-23 18:20 ` [PATCH 12/15] x86/hyperlaunch: specify dom0 mode with device tree Daniel P. Smith
2024-11-25 23:52   ` Jason Andryuk
2024-12-11 16:24     ` Daniel P. Smith
2024-12-02 12:05   ` Jan Beulich
2024-12-11 16:31     ` Daniel P. Smith
2024-12-02 12:06   ` Jan Beulich
2024-12-11 17:48     ` Daniel P. Smith
2024-12-12 11:31       ` Jan Beulich
2024-11-23 18:20 ` [PATCH 13/15] x86/hyperlaunch: add memory parsing to domain config Daniel P. Smith
2024-11-26  0:03   ` Jason Andryuk
2024-12-11 17:59     ` Daniel P. Smith
2024-12-26 16:16       ` Daniel P. Smith
2024-12-02 12:14   ` Jan Beulich
2024-12-11 18:02     ` Daniel P. Smith
2024-12-12 11:34       ` Jan Beulich
2024-11-23 18:20 ` [PATCH 14/15] x86/hyperlaunch: add max vcpu parsing of hyperlaunch device tree Daniel P. Smith
2024-11-26  0:05   ` Jason Andryuk
2024-12-11 18:05     ` Daniel P. Smith
2024-12-02 12:19   ` Jan Beulich
2024-12-11 19:49     ` Daniel P. Smith
2024-12-12 11:37       ` Jan Beulich [this message]
2024-11-23 18:20 ` [PATCH 15/15] x86/hyperlaunch: add capabilities to boot domain Daniel P. Smith
2024-11-26  0:09   ` Jason Andryuk
2024-12-11 19:51     ` Daniel P. Smith
2024-12-02 12:23   ` Jan Beulich
2024-12-11 19:56     ` Daniel P. Smith
2024-12-12 11:40       ` Jan Beulich
2024-11-26  0:11 ` [PATCH 00/15] Hyperlaunch device tree for dom0 Jason Andryuk
2024-12-11 19:57   ` Daniel P. Smith

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=18fd3e13-2e36-4d64-b56f-1227049bfb30@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=christopher.w.clark@gmail.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=jason.andryuk@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@amd.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.