Re: [osv-dev] OSv and C applications

2019-07-01 Thread Waldek Kozaczuk
Hi, On Monday, July 1, 2019 at 12:30:05 PM UTC-4, Nadav Har'El wrote: > > On Mon, Jul 1, 2019 at 4:01 PM DOR Nelly > wrote: > >> Hello, >> >> I'm trying to use OSv with non-included C programs, so I naturally tried >> running OSv with one of the applications that are present in the OSv bundle >

Re: [osv-dev] [PATCH] hpet: handle wrap-around with 32-bit counter

2019-07-01 Thread Waldek Kozaczuk
My previous "enable 32-bit hpet" patch you applied makes possible to run OSv on hyperkit for ~ 8 minutes. So honestly, I am just aiming to extend this 8-minutes to something longer with as little coding as possible ;-) As somebody said nobody will ever run OSv with hpet in production. But it i

Re: [osv-dev] [PATCH] hpet: Enhance 64-bit hpet clock to handle non-monotonic reads of the main counter

2019-07-01 Thread Waldek Kozaczuk
No, I have never been able to reproduce this issue for a year or so. I would typically happen in a nested virtualization scenario. My understanding was that for some reason the hypervisor (in this case qemu without KVM) would violate the promise of monotonic reads of the counter and based on h

[osv-dev] [COMMIT osv master] firecracker: bumped the version to 0.17.0

2019-07-01 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Waldemar Kozaczuk Branch: master firecracker: bumped the version to 0.17.0 Signed-off-by: Waldemar Kozaczuk --- diff --git a/scripts/firecracker.py b/scripts/firecracker.py --- a/scripts/firecracker.py +++ b/scripts/firecracker.py @@ -93,7 +93,8 @@ def conf

Re: [osv-dev] [PATCH] procfs: populate maps file with i-node numbers

2019-07-01 Thread Waldek Kozaczuk
I have just applied a patch fixing it. Now depending on which filesystem OSv runs we get same or different major:minor: ./scripts/manifest_from_host.sh -w cat && ./scripts/build -j4 fs=rofs --append-manifest && ./scripts/run.py -e '/cat /proc/self/maps' ... OSv v0.53.0-43-gef0696c5 eth0: 192.168

Re: [osv-dev] [PATCH] procfs: populate maps file with i-node numbers

2019-07-01 Thread Waldek Kozaczuk
I have just applied a patch fixing it. Now depending on which filesystem OSv runs we get same or different major:minor: ./scripts/manifest_from_host.sh -w cat && ./scripts/build -j4 fs=rofs --append-manifest && ./scripts/run.py -e '/cat /proc/self/maps' ... OSv v0.53.0-43-gef0696c5 eth0: 192.168

[osv-dev] [COMMIT osv master] procfs: Add device ID information to the maps file

2019-07-01 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Waldemar Kozaczuk Branch: master procfs: Add device ID information to the maps file Signed-off-by: Waldemar Kozaczuk --- diff --git a/core/mmu.cc b/core/mmu.cc --- a/core/mmu.cc +++ b/core/mmu.cc @@ -1687,6 +1687,7 @@ file_vma::file_vma(addr_range range, un

Re: [osv-dev] [PATCH] procfs: populate maps file with i-node numbers

2019-07-01 Thread Nadav Har'El
On Mon, Jul 1, 2019 at 7:26 AM Waldek Kozaczuk wrote: > Also where would I get the values for this xx:yy pair from? > > On Sunday, June 30, 2019 at 7:37:09 AM UTC-4, Waldek Kozaczuk wrote: >> >> We could. But that could be a separate patch. For now I do not care about >> it. >> > >> Do you have s

[osv-dev] [COMMIT osv master] procfs: populate maps file with i-node numbers

2019-07-01 Thread Commit Bot
From: Waldemar Kozaczuk Committer: Nadav Har'El Branch: master procfs: populate maps file with i-node numbers This patch refines the implementation of procfs to generate maps file that contains correct file i-node numbers instead of 0s for file VMAs as shown below: 0-0 ---p 00:00 0 1

Re: [osv-dev] OSv and C applications

2019-07-01 Thread Nadav Har'El
On Mon, Jul 1, 2019 at 4:01 PM DOR Nelly wrote: > Hello, > > I'm trying to use OSv with non-included C programs, so I naturally tried > running OSv with one of the applications that are present in the OSv bundle > first (eg groonga, cassandra, the java hello example, etc). To see a really minim

[osv-dev] OSv and C applications

2019-07-01 Thread DOR Nelly
Hello, I'm trying to use OSv with non-included C programs, so I naturally tried running OSv with one of the applications that are present in the OSv bundle first (eg groonga, cassandra, the java hello example, etc). I did follow the instructions on the README.md from the osv and the osv/apps f