[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v5] xen/arm, xen/common: Add Kconfig option to control Dom0 boot
- To: Jan Beulich <jbeulich@xxxxxxxx>, Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>
- From: Oleksii Moisieiev <Oleksii_Moisieiev@xxxxxxxx>
- Date: Mon, 26 Oct 2026 15:41:33 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=epam.com; dmarc=pass action=none header.from=epam.com; dkim=pass header.d=epam.com; arc=none
- 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=eFdg5ZLtLFCMoHfU8GnwoxZIZFHCyAoIbazF6uMH77g=; b=GC34slGUYUmGkstmg42+skHw9EGo9SoLoychs2LlAUF7Mb5RObZbWU3YvHNV/RwEwIcmVDJaLwVs0V2JwRg2lPtqsefS7iLvX6wPGPwJTGs3NkB2DkLz/7aOntjsNsEP2hIi9Nl6LMaDCfCmeNVWd72cfKhNzCYAiSv3U6A+HrdsmpSx0qrUm7JZdCM1iRYtwRraHvepau5jdC1dhEveJMSzfws9qxFHyCWuhT/7NeL5VXI47yBt64WVy/Go+g+7X1OJOeZCgtCaVVi5GlB9glCNvFW3KY39pEP2gqOkyZJxkhGc/62z+hQEPn28TKG2a+auEscLYnNFJcf9j34NZg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=OtBdBWghVU8KrGtV9MrknkKBq0woRTSl/YsyWh6mEzSS9o5yHAXi9RSim5ueHRJWRu9V6DVVduJnG7fYeYTovnNRz14PZKuP/oY4gCaTpTAAo4slSu5fKuBX5+kg7K3stquw6wB+ijoouDiy/8csPDC/kcdkkUmdY21P50uBrIhd6zWXCcJd8BDTT84wfMHg+HQ+zQNfm0kSsQWBYSnAhtWIvszP+tOp9f/HxcuhKWSto4RvoLpZ+53nsBJmuIekPH/moe+QDwFEAFkQkvt62PfHv2tHm6MEKaqRtsi3LMZucnOZ9OIO3ijc46DPezW/0QTKlMPTasaU5uzLwjjz5A==
- Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=selector1 header.d=epam.com header.i="@epam.com" header.h="From:Date:Subject:Message-ID:Content-Type:MIME-Version:x-ms-exchange-senderadcheck"
- Authentication-results: mx.microsoft.com 1; dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=epam.com;
- Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>, Julien Grall <julien@xxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, Roger Pau Monné <roger@xxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Teddy Astie <teddy.astie@xxxxxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Mon, 26 Oct 2026 15:41:43 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHdUnGcfnmLH64VckKy7OjAkXrKMLbuqNIAgCFle4CAAAbygIAABtAA
- Thread-topic: [PATCH v5] xen/arm, xen/common: Add Kconfig option to control Dom0 boot
On 26/10/2026 17:17, Jan Beulich wrote:
> On 26.10.2026 15:52, Oleksii Moisieiev wrote:
>> On 05/10/2026 11:52, Jan Beulich wrote:
>>> On 02.10.2026 15:26, Oleksii Moisieiev wrote:
>>>> This commit introduces a new Kconfig option, `CONFIG_DOM0_BOOT`, to
>>>> allow for building Xen without support for booting a regular domain (Dom0).
>>>> This functionality is primarily intended for the ARM architecture.
>>> I (still) wonder why this would be, but well ...
>> For v6, I'm going to describe this as a common option for legacy Dom0
>> boot, with Arm implementing the code exclusion initially. My immediate
>> use case is an Arm deployment where guests are launched through
>> dom0less and legacy Dom0 boot is not needed. I'm going to clarify that
>> this use case motivates the initial Arm implementation, rather than
>> make the interface Arm-specific. Is that scope OK?
>>>> A new Kconfig symbol, `HAS_DOM0`, has been added and is selected by
>>>> default for ARM and X86 architecture. This symbol signifies that an
>>>> architecture has the capability to support a Dom0.
>>> Oleksii - what's your take towards RISC-V here? Should it select the new
>>> symbol right away as well?
>> In the staging branch RISC-V's start_xen() does not have a legacy Dom0
>> construction path.
>> I'm therefore going to leave HAS_DOM0 unselected on RISC-V and explain
>> that selection should accompany implementation of legacy Dom0 boot.
>> Its existing HAS_DOM0LESS selection does not provide that path.
>> Does it sounds ok to you?
> FTAOD - my earlier question was to the other (RISC-V) Oleksii.
>
> Jan
Sorry...
---
Oleksii
|
