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 v2 10/15] x86/hyperlaunch: locate dom0 initrd with hyperlaunch
Date: Thu, 30 Jan 2025 17:39:48 +0100 [thread overview]
Message-ID: <0e36634f-3854-4e64-8514-5c7bdc78c43c@suse.com> (raw)
In-Reply-To: <20241226165740.29812-11-dpsmith@apertussolutions.com>
On 26.12.2024 17:57, Daniel P. Smith wrote:
> Look for a subnode of type `multiboot,ramdisk` within a domain node. If
> found, process the reg property for the MB1 module index.
Unlike for cmdline it doesn't look to be mix-and-match here.
> --- a/xen/arch/x86/domain-builder/fdt.c
> +++ b/xen/arch/x86/domain-builder/fdt.c
> @@ -119,6 +119,32 @@ static int __init process_domain_node(
> if ( ret > 0 )
> bd->kernel->fdt_cmdline = true;
> }
> +
> + continue;
> + }
> + else if (
> + fdt_node_check_compatible(fdt, node, "multiboot,ramdisk") == 0 )
I'm sorry, but this isn't style we use. Perhaps
else if ( fdt_node_check_compatible(
fdt, node, "multiboot,ramdisk") == 0 )
if you dislike
else if ( fdt_node_check_compatible(fdt, node,
"multiboot,ramdisk") == 0 )
> + {
> + int idx = dom0less_module_node(fdt, node, size_size, address_size);
> + if ( idx < 0 )
Nit: Blank line between declaration(s) and statement(s) please. (Again
at least once elsewhere in this patch.)
> + {
> + printk(" failed processing ramdisk module for domain %s\n",
> + name);
> + return -EINVAL;
> + }
> +
> + if ( idx > bi->nr_modules )
> + {
> + printk(" invalid ramdisk module index for domain node (%d)\n",
> + bi->nr_domains);
> + return -EINVAL;
> + }
See comments on similar printk()s in an earlier patch.
> @@ -2141,22 +2141,25 @@ void asmlinkage __init noreturn __start_xen(void)
> cpu_has_nx ? XENLOG_INFO : XENLOG_WARNING "Warning: ",
> cpu_has_nx ? "" : "not ");
>
> - /*
> - * At this point all capabilities that consume boot modules should have
> - * claimed their boot modules. Find the first unclaimed boot module and
> - * claim it as the initrd ramdisk. Do a second search to see if there are
> - * any remaining unclaimed boot modules, and report them as unusued initrd
> - * candidates.
> - */
> - initrdidx = first_boot_module_index(bi, BOOTMOD_UNKNOWN);
> - if ( initrdidx < MAX_NR_BOOTMODS )
> + if ( !bi->hyperlaunch_enabled )
Can't this be "if ( !bi->hyperlaunch_enabled && initrdidx < MAX_NR_BOOTMODS )"
and then all of the churn here can be avoided? An unnecessary call to
first_boot_module_index() is unlikely to be the end of the world. Otherwise ...
> {
> - bi->mods[initrdidx].type = BOOTMOD_RAMDISK;
> - bi->domains[0].ramdisk = &bi->mods[initrdidx];
> - if ( first_boot_module_index(bi, BOOTMOD_UNKNOWN) < MAX_NR_BOOTMODS )
> - printk(XENLOG_WARNING
> - "Multiple initrd candidates, picking module #%u\n",
> - initrdidx);
> + /*
> + * At this point all capabilities that consume boot modules should have
> + * claimed their boot modules. Find the first unclaimed boot module and
> + * claim it as the initrd ramdisk. Do a second search to see if there are
> + * any remaining unclaimed boot modules, and report them as unusued initrd
> + * candidates.
> + */
> + unsigned int initrdidx = first_boot_module_index(bi, BOOTMOD_UNKNOWN);
> + if ( initrdidx < MAX_NR_BOOTMODS )
> + {
> + bi->mods[initrdidx].type = BOOTMOD_RAMDISK;
> + bi->domains[0].ramdisk = &bi->mods[initrdidx];
> + if ( first_boot_module_index(bi, BOOTMOD_UNKNOWN) < MAX_NR_BOOTMODS )
> + printk(XENLOG_WARNING
> + "Multiple initrd candidates, picking module #%u\n",
> + initrdidx);
> + }
... please pay attention to line length when re-indenting. (If you still need
to re-indent, perhaps also s/unusued/unused/ in the comment, while you touch
it.)
Jan
next prev parent reply other threads:[~2025-01-30 16:40 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 16:57 [PATCH v2 00/15] Hyperlaunch device tree for dom0 Daniel P. Smith
2024-12-26 16:57 ` [PATCH v2 01/15] x86/boot: introduce boot domain Daniel P. Smith
2025-01-30 13:45 ` Jan Beulich
2025-04-05 0:04 ` Daniel P. Smith
2025-04-07 7:10 ` Jan Beulich
2025-04-09 23:55 ` Daniel P. Smith
2025-04-10 6:37 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 02/15] x86/boot: introduce domid field to struct boot_domain Daniel P. Smith
2025-01-30 13:51 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 03/15] x86/boot: add cmdline " Daniel P. Smith
2025-01-10 19:52 ` Jason Andryuk
2025-01-15 17:22 ` Daniel P. Smith
2025-01-15 19:50 ` Jason Andryuk
2025-01-30 14:15 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 04/15] kconfig: introduce option to independently enable libfdt Daniel P. Smith
2025-01-30 14:19 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 05/15] kconfig: introduce domain builder config option Daniel P. Smith
2025-01-10 19:55 ` Jason Andryuk
2025-01-15 17:24 ` Daniel P. Smith
2025-01-30 14:30 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 06/15] x86/hyperlaunch: introduce the domain builder Daniel P. Smith
2025-01-08 21:54 ` Jason Andryuk
2025-01-15 17:25 ` Daniel P. Smith
2025-01-30 14:52 ` Jan Beulich
2025-04-01 18:01 ` Jason Andryuk
2025-04-02 9:25 ` Jan Beulich
2025-04-02 19:44 ` Jason Andryuk
2024-12-26 16:57 ` [PATCH v2 07/15] x86/hyperlaunch: initial support for hyperlaunch device tree Daniel P. Smith
2025-01-10 22:20 ` Jason Andryuk
2025-01-15 17:47 ` Daniel P. Smith
2025-01-30 15:01 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 08/15] x86/hyperlaunch: locate dom0 kernel with hyperlaunch Daniel P. Smith
2025-01-10 23:06 ` Jason Andryuk
2025-01-30 15:42 ` Jan Beulich
2025-01-30 21:14 ` Stefano Stabellini
2025-01-31 6:36 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 09/15] x86/hyperlaunch: obtain cmdline from device tree Daniel P. Smith
2025-01-15 16:38 ` Jason Andryuk
2025-01-30 15:58 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 10/15] x86/hyperlaunch: locate dom0 initrd with hyperlaunch Daniel P. Smith
2025-01-15 16:43 ` Jason Andryuk
2025-01-30 16:39 ` Jan Beulich [this message]
2024-12-26 16:57 ` [PATCH v2 11/15] x86/hyperlaunch: add domain id parsing to domain config Daniel P. Smith
2025-01-30 16:49 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 12/15] x86/hyperlaunch: specify dom0 mode with device tree Daniel P. Smith
2025-01-15 19:42 ` Jason Andryuk
2025-01-30 16:55 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 13/15] x86/hyperlaunch: add memory parsing to domain config Daniel P. Smith
2025-01-15 16:55 ` Jason Andryuk
2025-01-30 17:01 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 14/15] x86/hyperlaunch: add max vcpu parsing of hyperlaunch device tree Daniel P. Smith
2025-01-15 19:40 ` Jason Andryuk
2025-01-30 17:04 ` Jan Beulich
2024-12-26 16:57 ` [PATCH v2 15/15] x86/hyperlaunch: add capabilities to boot domain Daniel P. Smith
2025-02-04 11:13 ` Jan Beulich
2025-02-04 15:40 ` Jason Andryuk
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=0e36634f-3854-4e64-8514-5c7bdc78c43c@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.