[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 07/15] x86/hyperlaunch: initial support for hyperlaunch device tree
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Dec 2024 07:55:52 -0500
- Arc-authentication-results: i=1; mx.zohomail.com; dkim=pass header.i=apertussolutions.com; spf=pass smtp.mailfrom=dpsmith@xxxxxxxxxxxxxxxxxxxx; dmarc=pass header.from=<dpsmith@xxxxxxxxxxxxxxxxxxxx>
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1733921756; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=WqCnRw5mQECy6J4x3YUdWuo+CzPSZcc+qQtrCAgcYAs=; b=f5bzd4Se7mPy/M/1tVaw3YbZvjaxeyal0DVmJFIzrHyIgDC+xXPjAqsIunOixkpXK52hfYwQBAs/pHeXAPlyvfwgMAeQxEbYGcdLPHLEtTax3jQSJmzUq3+W3uUjGtkum6TBE1tSjMpw4HkhinC8Kd1Osi7ANxyTcINU2yXwBds=
- Arc-seal: i=1; a=rsa-sha256; t=1733921756; cv=none; d=zohomail.com; s=zohoarc; b=Lsl2ylJLN41Tku0prPda7vepjA4owF1bl6PyPeFIFS4+UK17HBb/W0zKhBRqi7djk+DK9/sUy8pX80expII4tfop5QZ4iMK9PbAgL/2ltWjSQHLKB7mN+jfYbVePNSqCkNYmYPuRPBIJyzms9nwqcBAtUdVYICs7FLghXR90hw0=
- Cc: jason.andryuk@xxxxxxx, christopher.w.clark@xxxxxxxxx, stefano.stabellini@xxxxxxx, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Wed, 11 Dec 2024 12:56:13 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 12/2/24 06:37, Jan Beulich wrote:
On 23.11.2024 19:20, Daniel P. Smith wrote:
Add the ability to detect both a formal hyperlaunch device tree or a dom0less
device tree. If the hyperlaunch device tree is found, then count the number of
domain entries, reporting if more than one is found.
"reporting" reads like informational logging, when comment and printk() in
walk_hyperlaunch_fdt() indicate this is actually an error (for now).
That is not a shared assumptive reading. It is equally correct to say I
will report info and I will report an error. With that said, I can make
it explicit.
--- a/xen/arch/x86/domain_builder/fdt.c
+++ b/xen/arch/x86/domain_builder/fdt.c
@@ -14,14 +14,76 @@
#include "fdt.h"
+static int __init find_hyperlaunch_node(void *fdt)
+{
+ int hv_node = fdt_path_offset(fdt, "/chosen/hypervisor");
+ if ( hv_node >= 0 )
Nit: Blank line between declaration(s) and statement(s) please (also
elsewhere).
ack.
--- a/xen/arch/x86/domain_builder/fdt.h
+++ b/xen/arch/x86/domain_builder/fdt.h
@@ -11,11 +11,16 @@
#ifdef CONFIG_DOMAIN_BUILDER
int has_hyperlaunch_fdt(struct boot_info *bi);
+int walk_hyperlaunch_fdt(struct boot_info *bi);
#else
static inline int __init has_hyperlaunch_fdt(struct boot_info *bi)
{
return -EINVAL;
}
+static int __init walk_hyperlaunch_fdt(struct boot_info *bi)
inline?
Should have been.
v/r,
dps
|
