From: Lepton Wu <ytht.net@gmail.com>
To: virtualization@lists.linux-foundation.org
Cc: Lepton Wu <ytht.net@gmail.com>
Subject: Proof of concept for GPU forwarding for Linux guest on Linux host.
Date: Wed, 3 Apr 2019 17:31:50 -0700 [thread overview]
Message-ID: <20190404003151.253837-1-ytht.net@gmail.com> (raw)
Hi,
This is a proof of concept of GPU forwarding for Linux guest on Linux host.
I'd like to get comments and suggestions from community before I put more
time on it. To summarize what it is:
1. It's a solution to bring GPU acceleration for Linux vm guest on Linux host.
It could works with different GPU although the current proof of concept only
works with Intel GPU.
2. The basic idea is: under Linux, most applications use GPU acceleration with
help of MESA library. And MESA library interacts with kernel GPU driver by
operating on some special character device file exported by kernel GPU driver.
MESA library opens some special files in system and operations on GPU are done
by ioctl/mmap system call and regular memory operations.
We just write a kernel driver for guest Linux kernel and let it exports same
interface to user space like the real Linux GPU kernel driver. So it's an API proxy
between host and VM guest. We just proxy API at system call level.
3. Some nasty things was done in guest kernel as a quick dirty hack so we don't need
to touch user space (wayland/mesa etc) now.
4. You can check tools/forward/README for instructions.
Thanks!
Lepton Wu (1):
proof of concept for GPU forwarding
arch/x86/configs/x86_64_defconfig | 5 +
drivers/char/Makefile | 1 +
drivers/char/forwarder/Makefile | 8 +
drivers/char/forwarder/forwarder.h | 103 ++
drivers/char/forwarder/forwarder_drv.c | 2104 ++++++++++++++++++++++++
fs/open.c | 18 +
include/uapi/linux/virtwl.h | 64 +
tools/forward/Makefile | 2 +
tools/forward/README | 58 +
tools/forward/qemu.diff | 1117 +++++++++++++
tools/forward/wayland-proxy-main.c | 58 +
tools/forward/wayland-proxy.c | 297 ++++
12 files changed, 3835 insertions(+)
create mode 100644 drivers/char/forwarder/Makefile
create mode 100644 drivers/char/forwarder/forwarder.h
create mode 100644 drivers/char/forwarder/forwarder_drv.c
create mode 100644 include/uapi/linux/virtwl.h
create mode 100644 tools/forward/Makefile
create mode 100644 tools/forward/README
create mode 100644 tools/forward/qemu.diff
create mode 100644 tools/forward/wayland-proxy-main.c
create mode 100644 tools/forward/wayland-proxy.c
--
2.21.0.392.gf8f6787159e-goog
next reply other threads:[~2019-04-04 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 0:31 Lepton Wu [this message]
2019-04-04 0:31 ` [PATCH 1/1] proof of concept for GPU forwarding Lepton Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190404003151.253837-1-ytht.net@gmail.com \
--to=ytht.net@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).