Hello all,
We will be upgrading the TF LAVA instance to the latest 2024.09 release
this Thursday (14/11) at 10:30AM UTC. Both the server and workers will
be upgraded.
Expected downtime is around 30 minutes. We will let you know once
everything is back online.
Thanks for your collaboration.
Regards,
--
Luís Tonicha <luis.tonicha(a)linaro.org>
Hello all,
I'd like to apologize for any spam email messages you may have received
from 'developer.trustedfirmware.org' recently.
This was a server that had been retired several months that used to house
the project's wiki. In an attempt to recover a document the server was put
back online a short while ago. Unfortunately the mail service was left
operational, and the web application began catching up on a backlog of
messages and notifications.
Once the problem was discovered, I shutdown the mail daemon on the server
and have blocked all outbound mail traffic while I attempt to remove
additional unsent messages.
I apologize for the oversight that let this happen, and want to assure you
that this was a unique event.
Please reach out to me if you have any concerns.
Thanks,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
Hello all,
We are currently undergoing infrastructure (Kubernetes) maintenance
currently, which will affect the LAVA instance. The instance will be
taken down in about 10 minutes and the expected downtime should be of
around 45 minutes.
Thanks for your collaboration. Once the maintenance is finished, we will
announce.
Regards,
--
Luís Tonicha <luis.tonicha(a)linaro.org>
Hi All,
We are pleased to announce the formal release of Trusted Firmware-A version 2.10 bundle of project deliverables.
This includes Trusted Firmware-A, Trusted Firmware-A Tests, Hafnium, RMM and TF-A OpenCI Scripts/Jobs 2.10 releases involving the tagging of multiple repositories.
These went live on 22nd November 2023.
Please find references to tags and change logs at the end of this email.
Many thanks to the community for the active engagement in delivering this release!
Notable Features of the Version 2.10 Release are as follows:
TF-A/EL3 Root World
* New Features:
* Firmware handoff library support
* Improvements to BL31 runtime exception handling
* Context management refactoring for RME/4 worlds
* Gelas, Nevis & Travis CPUs support
* V8.9 features enabled (FEAT_ HAFT, RPRFM, LRCPC3, MTE_PERM)
TF-A Boot BL1/BL2
* New Features
* Trusted Boot support for ECDSA (Elliptic Curve Digital Signature Algorithm)
* Migrated to PSA crypto API’s
* Improved the GUID Partition Table (GPT) parser.
* Various security Improvements and threat Model updates for ARM CCA
* Signer id extraction Implementation
Hafnium/SEL2 SPM
* New Features:
* FF-A v1.2: FFA_YIELD with time-out; EL3 SPMDs LSPs communication; memory sharing updates.
* Memory region relative base address field support in SP manifests.
* Interrupt re-configuration hypervisor calls.
* Memory management: S2 PT NS/S IPA split
* SMCCCv1.2+ compliance fixes.
* Feature parity test improvements, EL3 SPMC and Hafnium (S-EL2 SPMC)
TF-RMM/REL2
* New Feature/Support
* Fenimore v1.0 EAC5 aligned implementation.
* TFTF Enhancements for RME testing
* Initial CBMC support
* NS SME support in RMM
* BTI support for RMM
Errata
* Errata implemented (1xCortex-X2/ Matterhorn-ELP, 1xCortex-A710/Matterhorn, 1xNeoverse N2/Perseus, 2xNeoverse V2/Demeter, Makalu ELP/Cortex X3, Klein/Cortex-A510)
* Fix some minor defects with version in a few errata that applies for some follow up revisions of the CPUs. (Neoverse V1, Cortex-X2, Cortex-A710)
TF-A Tests
* Core
* Added errata management firmware interface tests.
* Added firmware handoff tests.
* Introduced RAS KFH support test.
* SPM/FF-A
* Support SMCCCv1.2 extended GP registers set.
* Test SMCCC compliance at the non-secure physical instance.
* Test secure eSPI interrupt handling.
* Test FF-A v1.2 FFA_PARTITION_INFO_GET_REGS interface.
* RMM
* Added FPU/SVE/SME tests
* Added multiple REC single CPU tests.
* Added PAuth support in Realms tests.
* Added PMU tests.
Platform Support
* New platforms added:
* Aspeed AST2700, NXP IMX93, Intel Agilex5, Nuvoton NPCM845x, QTI MDM9607, MSM8909, MSM8939, ST STM32MP2
Release tags across repositories:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tag/?h=v2.10https://git.trustedfirmware.org/TF-A/tf-a-tests.git/tag/?h=v2.10https://git.trustedfirmware.org/ci/tf-a-ci-scripts.git/tag/?h=v2.10https://git.trustedfirmware.org/ci/tf-a-job-configs.git/tag/?h=v2.10https://git.trustedfirmware.org/hafnium/hafnium.git/tag/?h=v2.10https://git.trustedfirmware.org/ci/hafnium-ci-scripts.git/tag/?h=v2.10https://git.trustedfirmware.org/ci/hafnium-job-configs.git/tag/?h=v2.10https://git.trustedfirmware.org/TF-RMM/tf-rmm.git/tag/?h=tf-rmm-v0.4.0
Change logs:
https://trustedfirmware-a.readthedocs.io/en/v2.10/change-log.html#id1https://trustedfirmware-a-tests.readthedocs.io/en/v2.10/change-log.html#ver…https://hafnium.readthedocs.io/en/latest/change-log.html#v2-10https://tf-rmm.readthedocs.io/en/tf-rmm-v0.4.0/about/change-log.html#v0-4-0
Regards,
Olivier.
Greetings, Yesterday the gerrit server on review.trustedfirmware.org
experienced
significant downtime outside of any announced or scheduled maintenance windows
starting around 5pm UTC.
The downtime was caused by ansible deployment that was run to make some
configuration changes and install a plugin. The deployment made several
unintentional upgrades to other external plugins which were incompatible
with our environment and prevented gerrit from restarting.
As a result, for a 12 hour period the gerrit server was either off line or
highly unstable. As of 5am UTC today, gerrit had been returned to its
original state and resumed stable operation.
I apologize for the unannounced downtime and any inconvenience that it
caused, and we are reviewing the events to ensure a similar situation
doesn't occur again,
Regards,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
FYI at the weekend I ran an OpenCI Performance test to see if the Tuxsuite AWS changes for running FVP based TF-A tests helps with the management of load and execution times over running the FVP tests on physical servers.
In short it does help!
See https://discord.com/channels/1106321706588577904/1210643193834508338 for details and analysis.
Joanna
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hello all,
My name is Luís and I'm part of the Deployments team.
We will be migrating the TF LAVA instance from its current deployment to
our new, Kubernetes-based platform, this Friday (09/02) at 9:30 (AM) UTC.
This means that the tf.validation.linaro.org service will be down for
the expected downtime of 2 to 3 hours. This is just a migration so no
down/upgrades or configuration changes to LAVA will happen.
Once the service is back online we'll announce it. Thanks for your
collaboration.
Regards,
--
Luís Tonicha <luis.tonicha(a)linaro.org>
Greetings All,
The Jenkins servers on ci-staging.trustedfirmware ci.trustedfirmware.org
and mbedtls.trustedfirmware.org will all be put into safe mode in a few
moments in preparation for a shutdown around 6pm UTC today.
The purpose of this is to perform an upgrade to the server to address a
critical CVE discovered for the version of Jenkins running on all servers.
Regards,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
Dear Colleagues,
Thanks for your patience while the latest TuxSuite integration issues
were worked our during recent weeks. Last of the systematic FVP
integration issues were addressed end of last week, and since the last
weekend, the system was in the "soft launch" mode to see if there're any
remaining issues. Some intermittent issues were addressed during this
week. As of now, all the main TF-A CI jobs should be converted,
specifically:
* Mainline daily builds
* Mainline L1/L2 patch builds
* LTS2.8 daily builds
* LTS2.8 L1/L2 patch builds
Smaller related issues should also be addressed by now (in particular
https://linaro.atlassian.net/browse/TFC-573 "Make sure that Tux test
failure leads to Jenkins build being set to Failed status" which a
subject of explicit request). But thanks for understanding that we may
still need some tweaks here and there during the coming week(s).
We're launching integration with the highly scalable TuxSuite backend
well in advance of the next mainline release, and just in time for the
anticipated second LTS branch being forked. All that hopefully gives us
enough time to test the new system further and make any following
adjustments as needed. But my testing shows that the main "selling
points" of the new system are already at play - higher scalability and
improved stability due to avoidance of common testing bottlenecks we
experienced during recent times as TF CI coverage and load grew in high
tempo.
Please feel free to share your feedback and/or questions.
Thanks,
Linaro TF CI maintenance team
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
