[COMMIT osv master] header files: don't include

From: Nadav Har'El Committer: Nadav Har'El Branch: master header files: don't include OSv's header files should include , not . Not only do the ones without "api/" work just as well, the extra "api/" is actually harmful: It means that if a user wants to compile an application with the regula

[COMMIT osv master] - remove _KERNEL restriction

From: Nadav Har'El Committer: Nadav Har'El Branch: master - remove _KERNEL restriction In , all of the osv::application:: API was hidden with a '#ifdef _KERNEL', probably to avoid header file conflicts in applications which include the normal Linux header files. I fixed these conflicts in the

[PATCH] gdb: allow to pass hostname:port to connect to

Patch enables debugging VMs on remote hosts. When connecting to localhost on non-default port, a ':PORT' string can be used. So almost no additonaly typing is requried. Signed-off-by: Justin Cinkelj --- scripts/loader.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/

[PATCH] run.py: add option for additional cloud-init disk

The additional disk has to be second device on (virtio) bus, as only /dev/vblk1 is tested for magic header. See also 56c6195b252b127c7fe90cb9fa46c370b384b51a Actual code provided by Gregor Berginc. Signed-off-by: Justin Cinkelj --- scripts/run.py | 11 +++ 1 file changed, 11 insertions(

Re: [RFC 2/4] app: optionaly return thread ID of newly started app

On 01/30/2017 03:24 PM, Nadav Har'El wrote: On Mon, Jan 30, 2017 at 3:26 PM, Justin Cinkelj mailto:justin.cink...@xlab.si>> wrote: On 01/29/2017 10:03 AM, Nadav Har'El wrote: On Fri, Jan 27, 2017 at 12:26 AM, Justin Cinkelj mailto:justin.cink...@xlab.si>> wrote: The

[PATCH] - remove _KERNEL restriction

In , all of the osv::application:: API was hidden with a '#ifdef _KERNEL', probably to avoid header file conflicts in applications which include the normal Linux header files. I fixed these conflicts in the previous patch, so we no longer need this _KERNEL stuff. It means that an application which

Re: [RFC 2/4] app: optionaly return thread ID of newly started app

On Mon, Jan 30, 2017 at 4:19 PM, Justin Cinkelj wrote: > > > Maybe there is one significant difference between osv_execve() befor/after > Nadav's fixed it, and the code above. > osv_execve() tried to set new thread id in the code executed inside that > new thread. So new thread was (1) initialize

Re: [RFC 2/4] app: optionaly return thread ID of newly started app

On Mon, Jan 30, 2017 at 3:26 PM, Justin Cinkelj wrote: > > > On 01/29/2017 10:03 AM, Nadav Har'El wrote: > > On Fri, Jan 27, 2017 at 12:26 AM, Justin Cinkelj > wrote: > >> The thread ID of thread running new app main() function is returned. >> >> I think this has the same bug we already solved i

Re: [RFC 2/4] app: optionaly return thread ID of newly started app

On 01/30/2017 02:26 PM, Justin Cinkelj wrote: On 01/29/2017 10:03 AM, Nadav Har'El wrote: On Fri, Jan 27, 2017 at 12:26 AM, Justin Cinkelj mailto:justin.cink...@xlab.si>> wrote: The thread ID of thread running new app main() function is returned. Signed-off-by: Justin Cinkelj mail

[PATCH] header files: don't include

OSv's header files should include , not . Not only do the ones without "api/" work just as well, the extra "api/" is actually harmful: It means that if a user wants to compile an application with the regular Linux header files *and also secondly* with OSv header files, the user might include Linux

Re: [RFC 2/4] app: optionaly return thread ID of newly started app

On 01/29/2017 10:03 AM, Nadav Har'El wrote: On Fri, Jan 27, 2017 at 12:26 AM, Justin Cinkelj mailto:justin.cink...@xlab.si>> wrote: The thread ID of thread running new app main() function is returned. Signed-off-by: Justin Cinkelj mailto:justin.cink...@xlab.si>> --- core/app