[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 00/15] Hyperlaunch device tree for dom0
- To: Jason Andryuk <jason.andryuk@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- From: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Dec 2024 14:57:43 -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=1733947067; 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=oOUBIxcz6spn5xEIpbInUoIhgQ+SLADcKx0oqmYW8yY=; b=CoOzH0ubjodqmTz66ABEz0PsU4k27WtQbnRb34qxwN0liUiqsGppGXyrdSSdnrRlxUgKW5ENXXEQSdBEhqRi7zFP6OQdRgabqNG95z6pk0XN5rEfoPNwmVN/xMqYGLQRAxEsuyPJ8alJLbO1+HIT4sxPVmRBHRXDy/Y1KYJ2XDU=
- Arc-seal: i=1; a=rsa-sha256; t=1733947067; cv=none; d=zohomail.com; s=zohoarc; b=ePy9CWlfLu5meR+GmYVtPGmH1wA2rX1YpPAqoFU5ssSW71SnencKFAhS2gGfzeJPnWZHxqfuDi3zZtK0x3ugNJyB7ZiN0BVDpDmZ4IST0UcHGwAMbAvD89JwrFYjS9zREek0Ft7q92LDV2qHzaGikT3KDWl9wpFOnmqQQbr1t8Y=
- Cc: christopher.w.clark@xxxxxxxxx, stefano.stabellini@xxxxxxx
- Delivery-date: Wed, 11 Dec 2024 19:57:56 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 11/25/24 19:11, Jason Andryuk wrote:
On 2024-11-23 13:20, Daniel P. Smith wrote:
The Hyperlaunch device tree for dom0 series is the second split out
for the
introduction of the Hyperlaunch domain builder logic. These changes
focus on
introducing the ability to express a domain configuration that is then
used to
populate the struct boot_domain structure for dom0. This ability to
express a
domain configuration provides the next step towards a general domain
builder.
The splitting of Hyperlaunch into a set of series are 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.
Having gone through this, I think you want to ensure that docs/designs/
launch/hyperlaunch-devicetree.rst is updated with each patch adding a
property to ensure they stay in sync.
Ack.
v/r,
dps
|
