On Mon, Apr 09, 2018 at 12:35:10PM +0200, Gerd Hoffmann wrote: > This little series adds three drivers, for demo-ing and testing vfio > display interface code. There is one mdev device for each interface > type (mdpy.ko for region and mbochs.ko for dmabuf). Perhaps a very basic question - but why do this in the kernel as opposed to say outside the kernel - as a standalone process for example? > > mdpy-fb.ko is guest driver for mdpy.ko (guest driver is not required, > without guest driver mdpy.ko simply shows a static test image). > > mbochs.ko is compatible with bochs-drm.ko on the guest side. > > Gerd Hoffmann (3): > sample: vfio mdev display - host device > sample: vfio mdev display - guest driver > sample: vfio bochs vbe display (host device for bochs-drm) > > samples/vfio-mdev/mdpy-defs.h | 19 + > samples/vfio-mdev/mbochs.c | 1379 +++++++++++++++++++++++++++++++++++++++++ > samples/vfio-mdev/mdpy-fb.c | 232 +++++++ > samples/vfio-mdev/mdpy.c | 791 +++++++++++++++++++++++ > samples/Kconfig | 30 + > samples/vfio-mdev/Makefile | 3 + > 6 files changed, 2454 insertions(+) > create mode 100644 samples/vfio-mdev/mdpy-defs.h > create mode 100644 samples/vfio-mdev/mbochs.c > create mode 100644 samples/vfio-mdev/mdpy-fb.c > create mode 100644 samples/vfio-mdev/mdpy.c > > -- > 2.9.3 >
