Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 7, 2015 at 12:48 PM, Richard W.M. Jones wrote: > > I just pushed a (very early) WIP branch that contains changes to > libguestfs to add an LKL backend: > > https://github.com/rwmjones/libguestfs/tree/lkl > > Read the README file in the libguestfs sources before starting, > followed

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sun, Nov 8, 2015 at 4:42 PM, yalin wang wrote: > > On Nov 4, 2015, at 07:06, Octavian Purdila > wrote: > > On Tue, Nov 3, 2015 at 11:40 PM, Richard Weinberger > wrote: > > Hi Richard, > > On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila > wrote: > > LKL (Linux Kernel Library) is aiming to

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sun, Nov 8, 2015 at 4:42 PM, yalin wang wrote: > > On Nov 4, 2015, at 07:06, Octavian Purdila > wrote: > > On Tue, Nov 3, 2015 at 11:40 PM, Richard Weinberger > wrote: > > Hi Richard, > > On Tue, Nov 3, 2015

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 7, 2015 at 12:48 PM, Richard W.M. Jones wrote: > > I just pushed a (very early) WIP branch that contains changes to > libguestfs to add an LKL backend: > > https://github.com/rwmjones/libguestfs/tree/lkl > > Read the README file in the libguestfs sources before

Re: [RFC PATCH 00/28] Linux Kernel Library

Hello Octavian, At Tue, 3 Nov 2015 22:20:31 +0200, Octavian Purdila wrote: > > > Q: How is LKL different from LibOS? > A: LibOS re-implements high-level kernel APIs for timers, softirqs, > scheduling, sysctl, SLAB/SLUB, etc. LKL behaves like any arch port, > implementing the arch level

Re: [RFC PATCH 00/28] Linux Kernel Library

Hello Octavian, At Tue, 3 Nov 2015 22:20:31 +0200, Octavian Purdila wrote: > > > Q: How is LKL different from LibOS? > A: LibOS re-implements high-level kernel APIs for timers, softirqs, > scheduling, sysctl, SLAB/SLUB, etc. LKL behaves like any arch port, > implementing the arch level

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 7, 2015 at 2:35 AM, Richard Weinberger wrote: > Am 04.11.2015 um 15:15 schrieb Octavian Purdila: >> We could redefine the syscalls/libc symbols to call lkl_sys_ functions >> in launch-lkl, e.g.: >> >> int opendir(const char *path) >> { >>return lkl_opendir(new_path) >> } > > To

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 7, 2015 at 2:35 AM, Richard Weinberger wrote: > Am 04.11.2015 um 15:15 schrieb Octavian Purdila: >> We could redefine the syscalls/libc symbols to call lkl_sys_ functions >> in launch-lkl, e.g.: >> >> int opendir(const char *path) >> { >>return lkl_opendir(new_path) >> } > > To

Re: [RFC PATCH 00/28] Linux Kernel Library

I just pushed a (very early) WIP branch that contains changes to libguestfs to add an LKL backend: https://github.com/rwmjones/libguestfs/tree/lkl Read the README file in the libguestfs sources before starting, followed by the instructions in the commit message:

Re: [RFC PATCH 00/28] Linux Kernel Library

I just pushed a (very early) WIP branch that contains changes to libguestfs to add an LKL backend: https://github.com/rwmjones/libguestfs/tree/lkl Read the README file in the libguestfs sources before starting, followed by the instructions in the commit message:

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 7, 2015 at 2:35 AM, Richard Weinberger wrote: > Am 04.11.2015 um 15:15 schrieb Octavian Purdila: >> We could redefine the syscalls/libc symbols to call lkl_sys_ functions >> in launch-lkl, e.g.: >> >> int opendir(const char *path) >> { >>return

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 7, 2015 at 2:35 AM, Richard Weinberger wrote: > Am 04.11.2015 um 15:15 schrieb Octavian Purdila: >> We could redefine the syscalls/libc symbols to call lkl_sys_ functions >> in launch-lkl, e.g.: >> >> int opendir(const char *path) >> { >>return

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 07, 2015 at 01:35:36AM +0100, Richard Weinberger wrote: > Am 04.11.2015 um 15:15 schrieb Octavian Purdila: > > We could redefine the syscalls/libc symbols to call lkl_sys_ functions > > in launch-lkl, e.g.: > > > > int opendir(const char *path) > > { > >return

Re: [RFC PATCH 00/28] Linux Kernel Library

Am 04.11.2015 um 15:15 schrieb Octavian Purdila: > We could redefine the syscalls/libc symbols to call lkl_sys_ functions > in launch-lkl, e.g.: > > int opendir(const char *path) > { >return lkl_opendir(new_path) > } To get a better feeling how LKL behaves I've started with a tool to mount

Re: [RFC PATCH 00/28] Linux Kernel Library

Am 04.11.2015 um 15:15 schrieb Octavian Purdila: > We could redefine the syscalls/libc symbols to call lkl_sys_ functions > in launch-lkl, e.g.: > > int opendir(const char *path) > { >return lkl_opendir(new_path) > } To get a better feeling how LKL behaves I've started with a tool to mount

Re: [RFC PATCH 00/28] Linux Kernel Library

On Sat, Nov 07, 2015 at 01:35:36AM +0100, Richard Weinberger wrote: > Am 04.11.2015 um 15:15 schrieb Octavian Purdila: > > We could redefine the syscalls/libc symbols to call lkl_sys_ functions > > in launch-lkl, e.g.: > > > > int opendir(const char *path) > > { > >return

Re: [RFC PATCH 00/28] Linux Kernel Library

On Wed, Nov 4, 2015 at 3:50 PM, Richard W.M. Jones wrote: > On Wed, Nov 04, 2015 at 01:24:03AM +0200, Octavian Purdila wrote: >> Thanks for the pointers Richard, I am going to take a look at it. > > Now I've had a chance to look at some of the example LKL tools, here's > what this actually

Re: [RFC PATCH 00/28] Linux Kernel Library

On Wed, Nov 04, 2015 at 01:24:03AM +0200, Octavian Purdila wrote: > Thanks for the pointers Richard, I am going to take a look at it. Now I've had a chance to look at some of the example LKL tools, here's what this actually involves. It's not actually a great deal of work, it could probably be

Re: [RFC PATCH 00/28] Linux Kernel Library

On 2015-11-03 18:24, Octavian Purdila wrote: On Wed, Nov 4, 2015 at 12:45 AM, Richard W.M. Jones wrote: I'm dubious that a lib-based approach could support LVM, partioning, ntfs-3g, qcow2, vmdk and all the other libguestfs stuff that relies on userspace tools + qemu as well as just the kernel

Re: [RFC PATCH 00/28] Linux Kernel Library

On Wed, Nov 4, 2015 at 3:50 PM, Richard W.M. Jones wrote: > On Wed, Nov 04, 2015 at 01:24:03AM +0200, Octavian Purdila wrote: >> Thanks for the pointers Richard, I am going to take a look at it. > > Now I've had a chance to look at some of the example LKL tools, here's > what

Re: [RFC PATCH 00/28] Linux Kernel Library

On 2015-11-03 18:24, Octavian Purdila wrote: On Wed, Nov 4, 2015 at 12:45 AM, Richard W.M. Jones wrote: I'm dubious that a lib-based approach could support LVM, partioning, ntfs-3g, qcow2, vmdk and all the other libguestfs stuff that relies on userspace tools + qemu as well

Re: [RFC PATCH 00/28] Linux Kernel Library

On Wed, Nov 04, 2015 at 01:24:03AM +0200, Octavian Purdila wrote: > Thanks for the pointers Richard, I am going to take a look at it. Now I've had a chance to look at some of the example LKL tools, here's what this actually involves. It's not actually a great deal of work, it could probably be

Re: [RFC PATCH 00/28] Linux Kernel Library

On Wed, Nov 4, 2015 at 12:45 AM, Richard W.M. Jones wrote: > On Tue, Nov 03, 2015 at 10:40:29PM +0100, Richard Weinberger wrote: >> On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila >> wrote: >> > LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code >> > as extensively as

Re: [RFC PATCH 00/28] Linux Kernel Library

At Tue, 3 Nov 2015 22:45:45 +, Richard W.M. Jones wrote: > > > * cptofs/cpfromfs - a tool that copies files to/from a filesystem image > > > > Seeing forward to have a libguestfs port. :-) > > Thanks - I was keeping an eye on libos (and on the NetBSD rump kernel > stuff before), ready to

Re: [RFC PATCH 00/28] Linux Kernel Library

On Tue, Nov 3, 2015 at 11:40 PM, Richard Weinberger wrote: Hi Richard, > On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila > wrote: >> LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code >> as extensively as possible with minimal effort and reduced maintenance >>

Re: [RFC PATCH 00/28] Linux Kernel Library

On Tue, Nov 03, 2015 at 10:40:29PM +0100, Richard Weinberger wrote: > On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila > wrote: > > LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code > > as extensively as possible with minimal effort and reduced maintenance > > overhead.

Re: [RFC PATCH 00/28] Linux Kernel Library

On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila wrote: > LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code > as extensively as possible with minimal effort and reduced maintenance > overhead. > > Examples of how LKL can be used are: creating userspace applications >

[RFC PATCH 00/28] Linux Kernel Library

LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code as extensively as possible with minimal effort and reduced maintenance overhead. Examples of how LKL can be used are: creating userspace applications (running on Linux and other operating systems) that can read or write

Re: [RFC PATCH 00/28] Linux Kernel Library

On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila wrote: > LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code > as extensively as possible with minimal effort and reduced maintenance > overhead. > > Examples of how LKL can be used are: creating

Re: [RFC PATCH 00/28] Linux Kernel Library

On Tue, Nov 3, 2015 at 11:40 PM, Richard Weinberger wrote: Hi Richard, > On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila > wrote: >> LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code >> as extensively as

Re: [RFC PATCH 00/28] Linux Kernel Library

On Tue, Nov 03, 2015 at 10:40:29PM +0100, Richard Weinberger wrote: > On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila > wrote: > > LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code > > as extensively as possible with minimal effort and

[RFC PATCH 00/28] Linux Kernel Library

LKL (Linux Kernel Library) is aiming to allow reusing the Linux kernel code as extensively as possible with minimal effort and reduced maintenance overhead. Examples of how LKL can be used are: creating userspace applications (running on Linux and other operating systems) that can read or write

Re: [RFC PATCH 00/28] Linux Kernel Library

On Wed, Nov 4, 2015 at 12:45 AM, Richard W.M. Jones wrote: > On Tue, Nov 03, 2015 at 10:40:29PM +0100, Richard Weinberger wrote: >> On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila >> wrote: >> > LKL (Linux Kernel Library) is aiming to allow reusing

Re: [RFC PATCH 00/28] Linux Kernel Library

At Tue, 3 Nov 2015 22:45:45 +, Richard W.M. Jones wrote: > > > * cptofs/cpfromfs - a tool that copies files to/from a filesystem image > > > > Seeing forward to have a libguestfs port. :-) > > Thanks - I was keeping an eye on libos (and on the NetBSD rump kernel > stuff before), ready to