[osv-dev] [PATCH] aarch64: handle exceptions on dedicated stack

2022-04-28 Thread Waldemar Kozaczuk
This patch changes exception handling mechanism to use dedicated exception stack instead of the default stack provided for kernel and application threads. This is critical to support Golang apps which are known to use tiny stacks in coroutines and exception handler of svc instruction cannnot use si

[osv-dev] [PATCH] aarch64: handle system calls

2022-04-28 Thread Waldemar Kozaczuk
This patch enhances the aarch64 port to support handling system call instruction - SVC. On aarch64 the system calls are handled as synchronous exceptions triggered by executing the SVC instruction. Per syscall specification described in https://man7.org/linux/man-pages/man2/syscall.2.html, the cal

[osv-dev] [PATCH] aarch64: enable tst-ifaddrs.so

2022-04-28 Thread Waldemar Kozaczuk
Signed-off-by: Waldemar Kozaczuk --- modules/tests/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/tests/Makefile b/modules/tests/Makefile index 9ea648f7..ca489341 100644 --- a/modules/tests/Makefile +++ b/modules/tests/Makefile @@ -133,7 +133,7 @@ tests :

[osv-dev] [PATCH] aarch64: adapt tst-syscall.cc to work on aarch64

2022-04-28 Thread Waldemar Kozaczuk
Signed-off-by: Waldemar Kozaczuk --- tests/tst-syscall.cc | 46 +--- 1 file changed, 39 insertions(+), 7 deletions(-) diff --git a/tests/tst-syscall.cc b/tests/tst-syscall.cc index 79332ad6..12722f1b 100644 --- a/tests/tst-syscall.cc +++ b/tests/tst-syscal

[osv-dev] [PATCH V2] aarch64: move kernel to 63rd GB of virtual memory

2022-04-28 Thread Waldemar Kozaczuk
This patch modifies the aarch64 port to move the kernel from the 2nd to 63rd GB or virtual memory. It also adjusts the early preboot and boot assembly to dynamically adjust the early phys/virt mapping tables to make it work regardless where in physical memory the kernel and DTB is loaded. This allo

[osv-dev] Image not running using capstan

2022-04-28 Thread Shambo Bose
Hi All, I am trying to build one package with a simple nodejs app. I already built the image and seems like it is running fine without any errors but I don't see any running instances nor any service is listening on the port 3000. Please find screenshots below: ubuntu@unikern:~/calc$ cat meta/