This is an automated email from the ASF dual-hosted git repository.

mssun pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave-website.git

commit 42155dd653c5d9b924b071a1758ef215136edccb
Author: Mingshen Sun <[email protected]>
AuthorDate: Fri Jun 25 10:47:01 2021 -0700

    Meetup #5 blog
---
 site/blog/2021-06-24-teaclave-meetup-5.md          |  50 +++++++++++++++++++++
 site/blog/img/teaclave-meetup-5-webassembly.png    | Bin 0 -> 164338 bytes
 site/blog/img/teaclave-meetup-5-zoom.png           | Bin 0 -> 1973622 bytes
 ...-meetup-5-executing-webassembly-in-teaclave.pdf | Bin 0 -> 60416 bytes
 4 files changed, 50 insertions(+)

diff --git a/site/blog/2021-06-24-teaclave-meetup-5.md 
b/site/blog/2021-06-24-teaclave-meetup-5.md
new file mode 100644
index 0000000..56c20db
--- /dev/null
+++ b/site/blog/2021-06-24-teaclave-meetup-5.md
@@ -0,0 +1,50 @@
+---
+title: "Teaclave Meetup #5"
+date: 2021-06-24
+author: Mingshen Sun
+---
+
+In Jun 24, we gathered in Zoom for the fifth monthly Teaclave meetup. In this
+meetup, we're glad to have Hongbo (@ya0guang) talking about his contributions 
on
+adding WebAssembly Micro Runtime to Teaclave as an executor (PR:
+[#504](https://github.com/apache/incubator-teaclave/pull/504),
+[#512](https://github.com/apache/incubator-teaclave/pull/512)).
+
+
+![Teaclave Meetup #5](./img/teaclave-meetup-5-zoom.png)
+
+## Schedule
+
+- Recent update of Teaclave, Mingshen (5m)
+- Executing WebAssembly in Teaclve, Hongbo (40m)
+- Open discussion
+
+## Notes
+
+### Recent Update of Teaclave
+
+**Teaclave TrustZone SDK version 0.1.0 released**
+- Vote result: 
[https://lists.apache.org/thread.html/r441addf283f6c8780326f372e39a9d723164f6d910184ea3686a5c4a%40%3Cdev.teaclave.apache.org%3E](https://lists.apache.org/thread.html/r441addf283f6c8780326f372e39a9d723164f6d910184ea3686a5c4a%40%3Cdev.teaclave.apache.org%3E)
+- Release notes: 
<https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.1.0>
+- Download link: <https://teaclave.apache.org/download/>
+
+**Linaro OP-TEE Contributions meeting**
+- Recording: 
[https://linaro-org.zoom.us/rec/share/0o3Ku4zaXSrP-Ep0WI5P-XB-KAiP5d94kXbKmg43VqrnRHUmsLV_sv1wI01JbL0C.kSM-_ov2pc9Sggf_](https://linaro-org.zoom.us/rec/share/0o3Ku4zaXSrP-Ep0WI5P-XB-KAiP5d94kXbKmg43VqrnRHUmsLV_sv1wI01JbL0C.kSM-_ov2pc9Sggf_),
 Passcode: 9c.&%KR6
+- Slides: 
[https://drive.google.com/file/d/1YPig8k-xRyeRxuu1ALTmkqY-nxtH5upR/view?usp=sharing](https://drive.google.com/file/d/1YPig8k-xRyeRxuu1ALTmkqY-nxtH5upR/view?usp=sharing)
+
+### Executing WebAssembly in Teaclave
+
+![Executing WebAssembly in Teaclave](./img/teaclave-meetup-5-webassembly.png)
+
+- [Slides](./pdf/teaclave-meetup-5-executing-webassembly-in-teaclave.pdf)
+
+Some question and discussion:
+
+- Can we reuse the WebAssembly runtime to improve the performance of startup?
+- Bridging `tlibc` functions into WAMR.
+
+### Open Discussion
+
+- ARM CCA: 
<https://www.arm.com/why-arm/architecture/security-features/arm-confidential-compute-architecture>
+- EdgelessSys mablerun: <https://github.com/edgelesssys/marblerun>
+- Attestation mechanism in Google Cloud Confidential Computing
diff --git a/site/blog/img/teaclave-meetup-5-webassembly.png 
b/site/blog/img/teaclave-meetup-5-webassembly.png
new file mode 100644
index 0000000..de3af11
Binary files /dev/null and b/site/blog/img/teaclave-meetup-5-webassembly.png 
differ
diff --git a/site/blog/img/teaclave-meetup-5-zoom.png 
b/site/blog/img/teaclave-meetup-5-zoom.png
new file mode 100644
index 0000000..9f994da
Binary files /dev/null and b/site/blog/img/teaclave-meetup-5-zoom.png differ
diff --git 
a/site/blog/pdf/teaclave-meetup-5-executing-webassembly-in-teaclave.pdf 
b/site/blog/pdf/teaclave-meetup-5-executing-webassembly-in-teaclave.pdf
new file mode 100644
index 0000000..65c6130
Binary files /dev/null and 
b/site/blog/pdf/teaclave-meetup-5-executing-webassembly-in-teaclave.pdf differ

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to