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

Arm EFI boot issue for Dom0 module listed inside subnode of chosen


  • To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Luca Fancellu <luca.fancellu@xxxxxxx>
  • Date: Tue, 2 Nov 2021 17:24:59 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; 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=KgGEOf2yrrWlWZ4dCBkN+ubidTyXthqjZaIJs0xrf/8=; b=nSTjpmEugWFJZim4oXun088HU2KlTe5X82hdn8W4VF26G9wjH6AqdP/laB6pRThY8zeGUo4h8sWvng6A+ZdCQsxzEEzdtSHtjLMP2tor1zxU/9vS/sXxgRqKKHBoJBdbbPeW7PKA+LcFZSacT7/UdsjWygInjav/JaEzTEBXz1lBxgFGHyJ541vTIL5Gy+K5yUbl4z7f5SR9qQxJqKqofsvf1+4KOiGbwZ8Y5rxPpM+ZUZ/+bEIb6R4WeijyDvWv/nQxjjq3K/+2dk0//O12QHPAqD+IGXZrJqXPoyFrJEFIbpsytJIGl3P0IcoFZQuKwBA7bagYrmh6QV3F/sggkA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iUuU0vudO60TFWEoc6hoikGP/fhCQ6P10sA9JnWyodOlaayGMlmTlKSaHUDaVg4H+XGnP9ooF4IJWT/Qve38O2yFxizrEIyOLNtiOKa3UkPJfAIyCx0ufguAgLzL2BGMeVE/gjIbq2VrVbX5Pt2wcEXRCRA/IO3VQNG548UrrBlHG7h1SHOnv5saJ39NBhG8T5bKUbE4282PPHgDcrO0u4fyqMcBHSxO+8DN+IiLAF2X18HMEy5WrTCcbqJsVPr6hQ69tYsdRMBgZurZUjJq5Z4nP4FU+cPKZico8n6R+TV7NTK2MDRV3aGlRARr0Ghpf8PZWz3RFmNM7EDm3U+WdA==
  • Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Cc: Julien Grall <julien@xxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, wei.chen@xxxxxxx
  • Delivery-date: Tue, 02 Nov 2021 17:25:26 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;

Hi all,

We recently discovered that there is a way to list Dom0 modules that is not 
supported by the EFI boot,
It’s happened browsing some Wiki pages like this one:
https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Lager

In that page the Dom0 modules are listed inside a subnode of the /chosen node:

chosen {

    modules {
        #address-cells = <1>;
        #size-cells = <1>;

        module@0x72000000 {
            compatible = "multiboot,kernel", "multiboot,module";
            reg = <0x72000000 0x2fd158>;
        };

        module@0x74000000 {
            compatible = "xen,xsm-policy", "multiboot,module";
            reg = <0x74000000 0x2559>;
        };
    };
};

Instead for how it is implemented now in the EFI code and described in:
1) https://xenbits.xen.org/docs/unstable/misc/arm/device-tree/booting.txt
2) https://xenbits.xen.org/docs/unstable/misc/efi.html

Only the following approach is supported, so Dom0 modules must be a direct 
child of /chosen:

chosen {
    #address-cells = <1>;
    #size-cells = <1>;

    module@0x72000000 {
        compatible = "multiboot,kernel", "multiboot,module";
        reg = <0x72000000 0x2fd158>;
    };

    module@0x74000000 {
        compatible = "xen,xsm-policy", "multiboot,module";
        reg = <0x74000000 0x2559>;
    };
};

Is this a problem that needs a fix?

Thank you.

Cheers,
Luca


 


Rackspace

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