Explore >> Select a destination
|
You are here 
|
jborza.com | ||
| | | | |
sergioprado.blog
|
|
| | | | | A Trusted Execution Environment (TEE) is an environment where the code executed and the data accessed is isolated and protected in terms of confidentiality (no one have access to the data) and integrity (no one can change the code and its behavior). | |
| | | | |
cpu.land
|
|
| | | | | Curious exactly what happens when you run a program on your computer? Learn how multiprocessing works, what system calls really are, how computers manage memory with hardware interrupts, and how Linux loads executables. | |
| | | | |
danielmangum.com
|
|
| | | | | This is part of a series on the blog where we explore RISC-V by breaking down real programs and explaining how they work. You can view all posts in this series on the RISC-V Bytes page. It has been a bit since our last post, but today we are going to begin our journey into some of the more interesting areas of RISC-V systems. In the first post in the series, we installed our RISC-V toolchain, which included QEMU. | |
| | | | |
lwn.net
|
|
| | | While the kernel has had support for asynchronous I/O (AIO) since the 2.5 development cycle, it [...] | ||
