[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH] xen/kconfig: allow LATE_HWDOM config for ARM
- To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Sergiy Kibrik <Sergiy_Kibrik@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- From: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Dec 2024 10:27:59 -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=1734535683; 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=+Rqs0nzbS1vWrlNelABBlpbx4rCRCOleHHNNPrWHr6w=; b=FiP/Gk5GRSavKf/zPWNKgrPQdpDz2eZWyFjFpB+DhbvttGo+0Sx/9xYmsY7+g+ozXo8AJbW8k/fay1jubbNiAF2Yv9JByITDgJJyDDBScN3SigPLt1oa92JQEkRKcnJct9MyecFp7HEU8oajKRK9IGYTzyzN4lSQ0t9+afQFqmU=
- Arc-seal: i=1; a=rsa-sha256; t=1734535683; cv=none; d=zohomail.com; s=zohoarc; b=QbEyCQaNltU3ja0SNrrdCtt+739ev9qitNiiGK2ST4MfryDitVYcR8ogGk4/nZpOgH95Ek580WJvLO6fDNUFVHmMxoiTJ3Okwp6JJIXem7GgLSpH9N9eItjvuVKUa67h5BR+Voc5KRdeHF8rElgCQWTI6TgxeoW0Z63fKX1RHhY=
- Cc: Anthony PERARD <anthony.perard@xxxxxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Julien Grall <julien@xxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>
- Delivery-date: Wed, 18 Dec 2024 15:28:21 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 12/18/24 05:24, Andrew Cooper wrote:
On 17/12/2024 11:47 am, Sergiy Kibrik wrote:
Allow to build ARM configuration with support for initializing hardware domain.
On ARM it is only possible to start hardware domain in multiboot mode, so
dom0less support is required. This is reflected by dependency on DOM0LESS_BOOT
instead of directly depending on ARM config option.
Signed-off-by: Sergiy Kibrik <Sergiy_Kibrik@xxxxxxxx>
---
xen/common/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/common/Kconfig b/xen/common/Kconfig
index 90268d9249..7368ca8208 100644
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -374,7 +374,7 @@ endchoice
config LATE_HWDOM
bool "Dedicated hardware domain"
default n
- depends on XSM && X86
+ depends on XSM && (X86 || DOM0LESS_BOOT)
help
Allows the creation of a dedicated hardware domain distinct from
domain 0 that manages devices without needing access to other
To ask a questions not asked elsewhere on this thread.
We are expecting Hyperlaunch to supersede and entirely replace what is
currently x86's idea of split control/hwdom, to this point where this
symbol is even removed.
Has this plan changed?
In the long term, no. In the short term, the multi-domain builder
introduces the means to differentiate, but there is still discussion to
be had around how the dummy policy should/would need to be updated.
v/r,
dps
|
