Re: [PATCH] syscall: Add a C syscall example

Working on it. On Sun, Aug 28, 2016 at 4:57 PM, Nadav Har'El wrote: > Hi Benoit, > > Please add this test to the existing tests/tst-syscall.cc - instead of a > separate application - so we can have this in the regression test. > > Please use something other than exit() for

Re: [PATCH] syscall: Add a C syscall example

Hi Benoit, Please add this test to the existing tests/tst-syscall.cc - instead of a separate application - so we can have this in the regression test. Please use something other than exit() for several good reasons: 1. SYS_exit is not actually implemented yet - only in your branch (see a few

[PATCH] syscall: Add a C syscall example

This C syscall example is just doing exit(42) Signed-off-by: Benoît Canet --- syscall/Makefile | 9 + syscall/module.py| 3 +++ syscall/syscall.c| 16 syscall/usr.manifest | 1 + 4 files changed, 29 insertions(+) create mode 100644

Jenkins build is back to normal : osv-build #1115

See -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[COMMIT osv master] x64: 'syscall' instruction support

From: Benoit Canet Committer: Nadav Har'El Branch: master x64: 'syscall' instruction support Enable "fast system calls" via the 'syscall' instruction on OSv. The instruction is used by Go programs on Linux/x86-64 for system calls. Fixes #590

Re: [PATCH v5 1/2] x64: 'syscall' instruction support

On Sun, Aug 28, 2016 at 4:26 PM, Benoît Canet wrote: > > I opted for a signal frame because linux does it for the syscall > instruction handler. > Ok. It's a bit strange, but I'll commit this for now and we can fix later if we want. -- You received this message

[PATCH] pthread: implement pthread_key_delete()

Implement pthread_key_delete(). Currently, it will not mark the key available for re-use. The danger in allowing re-use is that if we leave data with that key (the pthread_key_delete(3P) manpage explains why this happens), we can get a new destructor running on old unrelated data. The

[PATCH] RFC: run pthread TSD destructors before resetting app runtime

The change to osv::run() (and friends) to reuse the calling thread rather than start a new one to run a new shared-object introduced a new problem: The new shared object may use pthread_key_create() to add destructors to run when closing threads. There is (currently) a global list of these

Re: [PATCH 2/2] app: return main thread id to the caller

By the way, a question: When running with "-V" (--verbose), do you see a warning about a stubbed "pthread_key_delete" function? -- Nadav Har'El n...@scylladb.com On Sun, Aug 28, 2016 at 12:42 PM, Nadav Har'El wrote: > > On Fri, Aug 26, 2016 at 2:55 PM, Justin Cinkelj

Re: [PATCH 1/2] x64: 'syscall' instruction support

Hi Benoit, sorry for all these iterations, but there are some important issues below (especialy the last one). On Sun, Aug 28, 2016 at 1:11 PM, Benoit Canet < benoit.canet.cont...@gmail.com> wrote: > Enable "fast system calls" via the 'syscall' instruction on OSv. The > instruction is used by Go

[COMMIT osv master] update apps submodule

From: Nadav Har'El Committer: Nadav Har'El Branch: master update apps submodule Signed-off-by: Nadav Har'El --- diff --git a/apps b/apps --- a/apps +++ b/apps @@ -1 +1 @@ -Subproject commit 211e58ba3e0f729b445f464cc9d09f42086d4124