Hi,
Current Hafnium build and test configs cover both cases of non-VHE (HCR_EL2.E2H=0) and VHE (HCR_EL2.E2H=1). From an Arm architecture perspective the latter is a superset of the former. We get to know that non-VHE becomes a legacy, and other projects in general tend to always enable Armv8.1 VHE extension early at boot. Our focus being S-EL2 (Armv8.4+) it looks reasonable to assume Armv8.1's VHE is present on chipsets loading and booting Hafnium. That said we're exploring the possibility to abandon 'non-vhe' builds, and focus build and test on vhe-enabled builds. The intent to simplify build configurations, and improve build and test time.
Joao made experiments in 2 steps, first on removing the said build configurations, and then runtime checks. This gives good results at least in terms of build time , and simplification in build/test scripts. https://review.trustedfirmware.org/c/hafnium/hafnium/+/18925/ https://review.trustedfirmware.org/c/hafnium/project/reference/+/18926/
This message is to poll the community for feedback, as to whether this is foreseen as an issue (or not!) for on going deployments, before we engage further in this refactoring.
Thanks & Regards, Olivier.
+1. Looks good to me.
-----Original Message----- From: Olivier Deprez via Hafnium hafnium@lists.trustedfirmware.org Sent: Friday, January 20, 2023 8:45 AM To: hafnium@lists.trustedfirmware.org Subject: [Hafnium] deprecating non vhe builds
Hi,
Current Hafnium build and test configs cover both cases of non-VHE (HCR_EL2.E2H=0) and VHE (HCR_EL2.E2H=1). From an Arm architecture perspective the latter is a superset of the former. We get to know that non-VHE becomes a legacy, and other projects in general tend to always enable Armv8.1 VHE extension early at boot. Our focus being S-EL2 (Armv8.4+) it looks reasonable to assume Armv8.1's VHE is present on chipsets loading and booting Hafnium. That said we're exploring the possibility to abandon 'non-vhe' builds, and focus build and test on vhe-enabled builds. The intent to simplify build configurations, and improve build and test time.
Joao made experiments in 2 steps, first on removing the said build configurations, and then runtime checks. This gives good results at least in terms of build time , and simplification in build/test scripts. https://review.trustedfirmware.org/c/hafnium/hafnium/+/18925/ https://review.trustedfirmware.org/c/hafnium/project/reference/+/18926/
This message is to poll the community for feedback, as to whether this is foreseen as an issue (or not!) for on going deployments, before we engage further in this refactoring.
Thanks & Regards, Olivier.
-- Hafnium mailing list -- hafnium@lists.trustedfirmware.org To unsubscribe send an email to hafnium-leave@lists.trustedfirmware.org
Changes are merged now https://review.trustedfirmware.org/q/topic:%22ja%252Fvhe_config%22+(status:o...)
Thanks Joao for making it. ________________________________ From: Raghu Krishnamurthy via Hafnium hafnium@lists.trustedfirmware.org Sent: 04 February 2023 17:58 To: Olivier Deprez Olivier.Deprez@arm.com; hafnium@lists.trustedfirmware.org hafnium@lists.trustedfirmware.org Subject: [Hafnium] Re: deprecating non vhe builds
+1. Looks good to me.
-----Original Message----- From: Olivier Deprez via Hafnium hafnium@lists.trustedfirmware.org Sent: Friday, January 20, 2023 8:45 AM To: hafnium@lists.trustedfirmware.org Subject: [Hafnium] deprecating non vhe builds
Hi,
Current Hafnium build and test configs cover both cases of non-VHE (HCR_EL2.E2H=0) and VHE (HCR_EL2.E2H=1). From an Arm architecture perspective the latter is a superset of the former. We get to know that non-VHE becomes a legacy, and other projects in general tend to always enable Armv8.1 VHE extension early at boot. Our focus being S-EL2 (Armv8.4+) it looks reasonable to assume Armv8.1's VHE is present on chipsets loading and booting Hafnium. That said we're exploring the possibility to abandon 'non-vhe' builds, and focus build and test on vhe-enabled builds. The intent to simplify build configurations, and improve build and test time.
Joao made experiments in 2 steps, first on removing the said build configurations, and then runtime checks. This gives good results at least in terms of build time , and simplification in build/test scripts. https://review.trustedfirmware.org/c/hafnium/hafnium/+/18925/ https://review.trustedfirmware.org/c/hafnium/project/reference/+/18926/
This message is to poll the community for feedback, as to whether this is foreseen as an issue (or not!) for on going deployments, before we engage further in this refactoring.
Thanks & Regards, Olivier.
-- Hafnium mailing list -- hafnium@lists.trustedfirmware.org To unsubscribe send an email to hafnium-leave@lists.trustedfirmware.org
-- Hafnium mailing list -- hafnium@lists.trustedfirmware.org To unsubscribe send an email to hafnium-leave@lists.trustedfirmware.org
hafnium@lists.trustedfirmware.org
-
Olivier Deprez -
raghu.ncstate＠icloud.com