On Tue, Nov 3, 2015 at 9:20 PM, Octavian Purdila <[email protected]> wrote: > Host independent implementation for virtio block devices. The host > dependent part of the host library must provide an implementation for > lkl_dev_block_ops. > > Disks can be added to the LKL configuration via lkl_disk_add(), a new > LKL application API. > > Signed-off-by: Octavian Purdila <[email protected]> > --- > tools/lkl/include/lkl.h | 20 ++++++++ > tools/lkl/include/lkl_host.h | 21 ++++++++ > tools/lkl/lib/virtio_blk.c | 116 > +++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 157 insertions(+) > create mode 100644 tools/lkl/lib/virtio_blk.c
Can you please outline what the differences between this driver and UML's block driver are? While UML and LKL have different goals they could at least share some drivers. UML also has networking drivers you could reuse. Maybe it would make sense to integrate LKL completely into arch/um if we find a nice way to combine them. CONFIG_UML_LIBRARY, hmm? Would be a nice opportunity to clear away some dung from arch/um and refactor it. :-) -- Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
