Hello everybody,
This is just a reminder that the next Databases on Arm public meeting
will happen tomorrow, 23 August, at 8 AM UTC.
Yibo collected new benchmarks and data, as well as the configuration Arm
is using to build MySQL. Hopefully we will be able to discuss these
tomorrow.
Shall you have any questions, please do not hesitate to contact me.
Best regards,
Leo
Hello everybody,
This is just a reminder that the next Databases on Arm public meeting
will happen next Wednesday, 19 July, at 8 AM UTC.
The expectation is that Krunal and Yibo could share the list of issues
they have seen with MySQL on Arm platforms in the past.
Shall you have any questions, please do not hesitate to contact me.
Best regards,
Leo
Hello everybody,
A reminder about the upcoming Linaro OP-TEE contribution public meeting
next week, in case anyone is interested to discuss OP-TEE related topics.
Cheers,
Leo
-------- Forwarded Message --------
Subject: [Linaro-open-discussions] Linaro OP-TEE Contribution, LOC,
monthly meeting June 27
Date: Thu, 22 Jun 2023 13:31:58 +0200
From: Jens Wiklander via Linaro-open-discussions
<linaro-open-discussions(a)op-lists.linaro.org>
Reply-To: Jens Wiklander <jens.wiklander(a)linaro.org>
To: OP-TEE TrustedFirmware <op-tee(a)lists.trustedfirmware.org>
CC: linaro-open-discussions(a)op-lists.linaro.org
Hi,
On Tuesday, June 27 it's time for another LOC monthly meeting. For
time and connection
details see the calendar at https://www.trustedfirmware.org/meetings/
I'd like to discuss how MbedTLS is used in OP-TEE.
While trying to update to MbedTLS 3.4 on the 4.x WIP branch [1] we
have run into yet another issue with the CRT parameters used in the
RSA implementation. See [2] for more details on the CRT problem.
[1] https://github.com/jenswi-linaro/optee_os/tree/wip_4_0_0
[2] https://github.com/jenswi-linaro/optee_os/pull/9
any other topics?
Thanks,
Jens
--
Linaro-open-discussions mailing list --linaro-open-discussions(a)op-lists.linaro.org
https://collaborate.linaro.org/display/LOD/Linaro+Open+Discussions+Home
Hello everybody,
On 14 February we had our OP-TEE / S-EL2 discussions public meeting with
representatives from Linaro, Huawei, and Arm. Just as reminder, as we
decided in the last meeting, the discussions will continue from now on
on the Linaro OP-TEE Contribution (LOC) monthly meeting. The next
instance of this meeting is tomorrow. If you don't have an invite for
this meeting, you can just find one in the Trusted Firmware Public
Meetings calendar [0].
If you want to see what was discussed in the last meeting, I put my
meeting notes at [1]. There is also a recording for the meeting at the
same link, as well as a list of action items.
Please, spread the word inside your teams and let me know in case you
have any additional questions.
0.
https://calendar.google.com/calendar/embed?src=linaro.org_havjv2figrh5egaiu…
1.
https://linaro.atlassian.net/wiki/spaces/LEGSC/pages/28860186643/2023-02-14…
Best regards
Leo
-------- Forwarded Message --------
Subject: Re: Linaro OP-TEE Contribution (LOC) monthly meeting February 28
Date: Fri, 24 Feb 2023 16:03:32 +0100
From: Jérôme Forissier <jerome.forissier(a)linaro.org>
To: Jens Wiklander <jens.wiklander(a)linaro.org>
CC: OP-TEE TrustedFirmware <op-tee(a)lists.trustedfirmware.org>,
linaro-open-discussions(a)op-lists.linaro.org, Leonardo Augusto Guimarães
Garcia <leonardo.garcia(a)linaro.org>
Hi Jens,
On Fri, 24 Feb 2023 at 15:03, Jens Wiklander <jens.wiklander(a)linaro.org>
wrote:
Hi,
It's soon time for another LOC monthly meeting. For time and connection
details see the calendar at https://www.trustedfirmware.org/meetings/
I have recently seen interest in OP-TEE and S-EL2. As you may know, we
have a working setup with OP-TEE and Hafnium with most of the needed
patches upstream.
Any other topics?
Could we discuss toolchain upgrade issues related to C++ support in TAs?
For a bit of context, see:
https://github.com/OP-TEE/build/issues/624#issuecomment-1425486897
I'd like to understand if people are interested in using C++ in TAs (and
possibly doing so already), and what could be a path forward. Such as,
what would it take to produce a specific GCC toolchain for OP-TEE to
cover this use case?
Thanks,
--
Jerome
Hello everyone,
Few months ago, in our discussions around the strategy and direction of
the Linaro Data Center Group, Huawei presented a set of enhancements
they would like to see in OP-TEE. They also demonstrated interest in
S-EL2 developments. In order to discuss this topic, I just scheduled a
public meeting for us to discuss this list of enhancements. Anyone
interested in OP-TEE and S-EL2 is welcome.
The meeting is scheduled in the LDCG calendar [0] for next Tuesday, 14
February, at 12 PM UTC. If you have any difficulties accessing this
calendar, just let me know. The calendar is public and anyone should be
able to access it.
Please, spread the word so that anyone interested in the topic can join
us in this discussion.
0.
https://calendar.google.com/calendar/embed?src=linaro.org_eefhmicbj1g76uvhr…
Cheers,
Leo
Hi,
As discussed at the LDCG SC meeting in January, let's start a thread about
OpenBMC where we will try to understand if we should look into OpenBMC and
what the areas potentially could be. To get the discussion started I'm
starting the thread by asking a couple of questions. Don't feel obliged to
answer all of them. Pick the ones that are relevant for you. My goal is to
make a summary of the tread and bring it up for discussion again at a
future SC meeting.
1. Arm support
- Are there gaps in the Arm side of OpenBMC? What are those gaps?
- SBMR specification [1], what compliance levels to target? M1/M2 is one
somewhat good shape?
2. Upstreaming
- Are there sufficient upstreaming efforts for the Arm architectures?
3. Developer support
- Is source code available to developers (open source? proprietary?)?
-- SCP / MCP are not necessarily open source from vendors.
-- Arm's reference code is open source.
- Do we have the necessary hardware to be able to do development? What
hardware? How can developers get hold of it?
- Are specifications available to developers?
- What debugging capabilities exist for developers?
4. Testing
- What kind of testing do we have for OpenBMC?
- Is the testing sufficient?
- Does it require hardware or can we do testing using emulation or similar?
5. Security
- Cloud Security Industry Summit published a report [2] (A Case for a
Trustworthy BMC) where they list gaps in OpenBMC when it comes to security.
Anything in that report that we should pay attention to?
6. Anything else?
[1] https://documentation-service.arm.com/static/5fb7e810ca04df4095c1d658
[2]
https://cloudsecurityindustrysummit.s3.us-east-2.amazonaws.com/a-case-for-a…
A kind reminder that this is a public and open list.
--
Regards,
Joakim