[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 00/15] Hyperlaunch device tree for dom0
- To: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Jason Andryuk <jason.andryuk@xxxxxxx>
- Date: Mon, 25 Nov 2024 19:11:04 -0500
- 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=mPUn3Jo/A2ZL2CVrQ2ghv1LmOegn4bY6NabzGL/9xLI=; b=B8uFjTZJxvrWszzELmsu18R5Kza30bsf+W1NPegnJjOC1FOTzuZspQ53EYmORSp+RJtX4oUl7vAlq2cPYkOmopkP/+CBBv0wGBeTbgVSGhfKxQUdHib6Hox8aA/2PVKVxC/RB0YcGHSGS6r2URSudFS0pIAYy9ums90eCC/bDcJ91EuIOr87DizIPwV2baIw6jdcJHua0APE/6H7ZUViwGTeoltZaath19NIMH/NHkosh56EcIac6BRIrHcsPX52rCJRZVv+3nwd3l0BEdcF38+ORrELHZy7ll5HvFoeFyp3SIJMuyregCHrKXkgKKuVNjS6VFE6f/ANDQ9a/fYYtQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=TbJFEvKL0DNtxpp9t7zJJaj0rj7FFG7iMrYBR7B/UXaSWLF6McTJ9gSHCx/YFuvAhx1tdVtebtMGt61KjMWflOI+aZMbtJ5NMRKfHqNnlLhlsQIDxxjneIkzboTIULNdsYFDmUcJYpG1lkyJDlamgyuGlPKEe9Q7v28OCNjkQ83FKGEvNAgmhRn/MiG1+CTSFj0E3U7WFjCIk4AJGZUCPUgR5OUFdMS3p+gylNm9oe7bROVeSgIZ1wcsf2qdAw2nvYGvw+ucj2PmVVCIKMQAgkgmJKgED+RpyuOpAr3D187XHfnWt9GfYIXmd3H03M30YBcL/cTHxOLjvEs3fS0JEg==
- Cc: <christopher.w.clark@xxxxxxxxx>, <stefano.stabellini@xxxxxxx>
- Delivery-date: Tue, 26 Nov 2024 01:53:03 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
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.
Regards,
Jason
|
