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

Re: [PATCH v5 01/44] x86/boot: move x86 boot module counting into a new boot_info struct


  • To: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Jason Andryuk <jason.andryuk@xxxxxxx>
  • Date: Mon, 7 Oct 2024 13:57:45 -0400
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=apertussolutions.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=kw0w3/mNYMUZ902W+Tw8z6DhauJJdrSRxtFWJbURlv0=; b=HpBguyLzRcTkeC8TM5ROA6zaT0Rrsj3tpUa1zMXNfqhYCr/jc4u5r8SVQ4bSYYLuoZiUdLzbE765/FkjouCCfhWOjYMoVwstrpYV6/2bPGr8yD/tyY9k6ajhVcZ/gJ5u7T3ago0WYa45L7OMsNjlJ3KvsbC0NJGI+XnBgWPizkIrHaeilI6YBCGSRJjcmGWlk8RjpqR3swE6REa84YpoKjkCQkBWVuXfj8RBQ0v6Fe2drYd3uKvsr3eNl52yWnx1ghiTNAW/kfH+RSzWpa4XGPlQEHv8EfUA6dXvMZcU2AOH5N0FmnM1TJR+KPclg1pFu+E0eqCJgKC1IuTLUhFPpA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=V1BdmLSraNUSL51R9np04LUwIHK5L4PMLX7AIq29B/DoS4YXgPcKIp96mZ9rbcL5XVj76G1m04yNs0pr1Kizo7WgwZkTC5MIdVbUDI5Lw7LbFG6OLNOQ6FeWesfGe0aemGUU42Lmr4a2q70aprho6UupUVtGsyTacC0HH7/w1WzPXmtnReuyb5A8P5zE54+DuV4zIyTyhBSJZre6y1gTlsgOow/OzsgKOsaet+dMeTTyib9DITWmWZ7CTnUWVlRgo5WcNPXiK9LpSoQQjgltrIqWOfJY/z6fwosqmMB+oFhe7THkjgtauVt/5N53ZRPdDRKeYv5BRnCzEt3da69Grg==
  • Cc: Christopher Clark <christopher.w.clark@xxxxxxxxx>, <stefano.stabellini@xxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Delivery-date: Mon, 07 Oct 2024 17:58:03 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 2024-10-06 17:49, Daniel P. Smith wrote:
From: Christopher Clark <christopher.w.clark@xxxxxxxxx>

An initial step towards a non-multiboot internal representation of boot
modules for common code, starting with x86 setup and converting the fields
that are accessed for the startup calculations.

Introduce a new header, <asm/bootinfo.h>, and populate it with a new boot_info
structure initially containing a count of the number of boot modules.

No functional change intended.

Signed-off-by: Christopher Clark <christopher.w.clark@xxxxxxxxx>
Signed-off-by: Daniel P. Smith <dpsmith@xxxxxxxxxxxxxxxxxxxx>
---
  xen/arch/x86/include/asm/bootinfo.h | 29 +++++++++++++
  xen/arch/x86/include/asm/setup.h    |  2 +
  xen/arch/x86/setup.c                | 64 ++++++++++++++++++-----------
  3 files changed, 71 insertions(+), 24 deletions(-)
  create mode 100644 xen/arch/x86/include/asm/bootinfo.h

diff --git a/xen/arch/x86/include/asm/bootinfo.h 
b/xen/arch/x86/include/asm/bootinfo.h
new file mode 100644
index 000000000000..a649500ee3a2
--- /dev/null
+++ b/xen/arch/x86/include/asm/bootinfo.h
@@ -0,0 +1,29 @@
+/* SPDX-License-Identifier: GPL-2.0-or-later */
+/*
+ * Copyright (c) 2024 Christopher Clark <christopher.w.clark@xxxxxxxxx>
+ * Copyright (c) 2024 Apertus Solutions, LLC
+ * Author: Daniel P. Smith <dpsmith@xxxxxxxxxxxxxxxxxxxx>
+ */
+
+#ifndef __XEN_X86_BOOTINFO_H__
+#define __XEN_X86_BOOTINFO_H__

I haven't been following closely, but I think if we follow Frediano's naming scheme, it would be:
ASM__X86__BOOTINFO_H

With that (or whatever it should be),
Reviewed-by: Jason Andryuk <jason.andryuk@xxxxxxx>

+
+/*
+ * Xen internal representation of information provided by the
+ * bootloader/environment, or derived from the information.
+ */

I guess fine for now. Should probably be expanded when it starts containing Hyperlaunch domain configs.

+struct boot_info {
+    unsigned int nr_modules;
+};
+
+#endif /* __XEN_X86_BOOTINFO_H__ */

Regards,
Jason



 


Rackspace

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