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

Re: [PATCH v4 00/44] Boot modules for Hyperlaunch


  • To: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • From: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 2 Sep 2024 07:12:24 -0400
  • 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=1725275553; 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=XzbRLQO62GfHWqUyNAjWdVTfLnu/+hNrn0FRLBcHH5k=; b=eLiq+hzBoyouPa89sZl11bWeU9XJgi4MxCpUjTv8q01KLFXPr1VKCRWmsMRUERB02MMGs6TzrnCJ7cVQeyAD+fSmKiCEOdsQpo82AY8q1823kJntWx36okWvXuJNqTxw6T56DzmRA0RjLIAP+a2N+cIZT7zZKMaNFdP04kdXrUU=
  • Arc-seal: i=1; a=rsa-sha256; t=1725275553; cv=none; d=zohomail.com; s=zohoarc; b=fNiSGKxiGQtpbth64eSl2TwxP/ZIYcuS4woHjzeHtjQp39bVXu7oM1XCa5kLHpTSn9q3cA2GHyQi/DXZ7pHo2gFfzFt7FvnBc0WXQ+1o6Az3Qv1DcQ9JChxzaHzJzly/at/TQmxbWyrEl7CA2pybaFKOpDRUV5aFejk6hDqSMLQ=
  • Cc: jason.andryuk@xxxxxxx, christopher.w.clark@xxxxxxxxx
  • Delivery-date: Mon, 02 Sep 2024 11:12:55 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 8/30/24 17:46, Daniel P. Smith wrote:
The Boot Modules for Hyperlaunch series is an effort to split out preliminary
changes necessary for the introduction of the Hyperlaunch domain builder
logic. These preliminary changes revolve around introducing the struct
boot_module and struct boot_domain structures. This includes converting the
dom0 construction path to use these structures. These abstractions lay the
groundwork to transform and extend the dom0 construction logic into a limited,
but general domain builder.

The splitting of Hyperlaunch into a pair of series was twofold, to reduce the
effort in reviewing a much larger series, and to reduce the effort in handling
the knock-on effects to the construction logic from requested review changes.

A note on v4:

For v4, two significant direction changes occurred. First, the series was
pulled back from attempting to be in common and instead focused on being
purely an x86 capability. Second, the changes were broken down into much
smaller change sets and ordered to provide a more ordered evolution of the
code. To the most extent possible, it was attempted to ensure all v3 comments
were transcribed accordingly with the scope change.

As an FYI, after posting I realized I was not on the tip of staging, I have a v5 ready, which is at the tip of staging and corrects a small type issue with initrdidx in start_xen() and is 100% on CI. I'm holding off on posting back-to-back revisions of a large series, which would only results in a few code gyrations with no logical impact that would not result in different review than would have occurred on v4.

V/r,
DPS



 


Rackspace

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