Stream: SIG-Embedded

Topic: Jan 7th 2025

view this post on Zulip Chris Woods (Jan 03 2025 at 22:52):

Happy New Year Folks !

Welcome to 2025, and our next e-sig is almost upon us (Tuesday Jan 7th @11am Eastern Time / 5pm Central European time). I’ve provided an outline agenda here:

https://github.com/bytecodealliance/meetings/blob/main/SIG-Embedded/2025/01-07-Meeting-notes.md

For next week’s agenda I’ve suggest two topics on memory handling (see below). If there is anything else, you’d like to discuss please do feel free to the agenda via the usual PR process.

All the best and chat soon,

Chris
Suggested Topics
Requests for clarification: Devices without an MCU / MMU

It is proposed that we declare that for the embedded-sig we will not address hardware which does not have some form of memory control either in the form of an MMU or an MCU.
Background

Based on the hardware platforms we selected, I couldn’t find devices which had the required amount of memory, but didn’t come with at least some form of memory protection.

Request for Hardware Requirements Clarification https://github.com/bytecodealliance/sig-embedded/issues/7
Proposed Approaches to Shared Memory

There are requests for feedback, requirements and scenarios for using shared memory on embedded systems. Not just from the WASI SDK folks, but also from the Core-WASM folks. An initial set of approaches was outlined here - Memory Sharing Discussion - https://github.com/WebAssembly/memory-control/issues/19. This should be expanded to include some use cases and we should attempt to recommend a possible approach.

meetings/SIG-Embedded/2025/01-07-Meeting-notes.md at main · bytecodealliance/meetings
Contribute to bytecodealliance/meetings development by creating an account on GitHub.
Request for clarifications regarding hardware capabilities for shared mappings · Issue #7 · bytecodealliance/sig-embedded
In the target platforms doc, there is a section explaining that the E-SIG feels comfortable assuming an MPU or MMU for efficient implementations. This is very helpful since it gives us a baseline o...
Memory Sharing Discussion · Issue #19 · WebAssembly/memory-control
Introduction and Context There have been a number of conversations and questions raised about the possibility to share subsets of memory between multiple WebAssembly instances and the host environm...

view this post on Zulip Chris Woods (Jan 07 2025 at 17:58):

This weeks call wrapped up earlier today and you can find the recording on Youtube here -> YouTube - - YouTube

view this post on Zulip Christof Petig (Jan 07 2025 at 19:17):

I will take a second look at the minutes by using the recording, but a first version is already available here: https://github.com/bytecodealliance/meetings/pull/508

Today's eSIG meeting minutes (first version before watching the recording) by ChristofPetig · Pull Request #508 · bytecodealliance/meetings
We read every piece of feedback, and take your input very seriously.

view this post on Zulip Christof Petig (Jan 20 2025 at 21:57):

I rewatched the recording, barely in time for tomorrow's meeting, and clarified one part which I didn't get in the first attempt

See https://github.com/bytecodealliance/meetings/pull/520

Tiny correction to the last SIG embedded minutes by cpetig · Pull Request #520 · bytecodealliance/meetings
I rewatched the recording and was able to clarify one part which I didn't get in my first version: Sharpen the definition of the three layers of shm implementation

Last updated: Jan 24 2025 at 00:11 UTC