From: Julian Stecklina <julian.stecklina@cyberus-technology.de>
To: intel-gvt-dev@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
zhiyuan.lv@intel.com, hang.yuan@intel.com,
Julian Stecklina <julian.stecklina@cyberus-technology.de>
Subject: [RFC PATCH 0/4] Support for out-of-tree hypervisor modules in i915/gvt
Date: Thu, 9 Jan 2020 19:13:53 +0200 [thread overview]
Message-ID: <20200109171357.115936-1-julian.stecklina@cyberus-technology.de> (raw)
In-Reply-To: <4079ce7c26a2d2a3c7e0828ed1ea6008d6e2c805.camel@cyberus-technology.de>
These patch series removes the dependency of i915/gvt hypervisor
backends on the driver internals of the i915 driver. Instead, we add a
small public API that hypervisor backends can use.
This enables out-of-tree hypervisor backends for the Intel graphics
virtualization and simplifies development. At the same time, it
creates at least a bit of a barrier to including more i915 internals
into kvmgt, which is nice in itself.
The first two patches are pretty much general cleanup and could be
merged without the rest.
Any feedback is welcome.
Julian Stecklina (4):
drm/i915/gvt: make gvt oblivious of kvmgt data structures
drm/i915/gvt: remove unused vblank_done completion
drm/i915/gvt: define a public interface to gvt
drm/i915/gvt: move public gvt headers out into global include
drivers/gpu/drm/i915/gvt/Makefile | 2 +-
drivers/gpu/drm/i915/gvt/debug.h | 2 +-
drivers/gpu/drm/i915/gvt/display.c | 26 ++
drivers/gpu/drm/i915/gvt/display.h | 27 --
drivers/gpu/drm/i915/gvt/gtt.h | 2 -
drivers/gpu/drm/i915/gvt/gvt.h | 65 +--
drivers/gpu/drm/i915/gvt/gvt_public.c | 154 +++++++
drivers/gpu/drm/i915/gvt/kvmgt.c | 413 ++++++++++--------
drivers/gpu/drm/i915/gvt/mpt.h | 3 -
drivers/gpu/drm/i915/gvt/reg.h | 2 -
include/drm/i915_gvt.h | 104 +++++
.../drm/i915_gvt_hypercall.h | 13 +-
12 files changed, 537 insertions(+), 276 deletions(-)
create mode 100644 drivers/gpu/drm/i915/gvt/gvt_public.c
create mode 100644 include/drm/i915_gvt.h
rename drivers/gpu/drm/i915/gvt/hypercall.h => include/drm/i915_gvt_hypercall.h (92%)
--
2.24.1
next parent reply other threads:[~2020-01-09 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4079ce7c26a2d2a3c7e0828ed1ea6008d6e2c805.camel@cyberus-technology.de>
2020-01-09 17:13 ` Julian Stecklina [this message]
2020-01-09 17:13 ` [RFC PATCH 1/4] drm/i915/gvt: make gvt oblivious of kvmgt data structures Julian Stecklina
2020-01-20 6:22 ` Zhenyu Wang
2020-01-20 6:33 ` Zhenyu Wang
2020-01-20 17:25 ` [PATCH] " Julian Stecklina
2020-01-09 17:13 ` [RFC PATCH 2/4] drm/i915/gvt: remove unused vblank_done completion Julian Stecklina
2020-01-20 6:23 ` Zhenyu Wang
2020-01-09 17:13 ` [RFC PATCH 3/4] drm/i915/gvt: define a public interface to gvt Julian Stecklina
2020-01-09 17:13 ` [RFC PATCH 4/4] drm/i915/gvt: move public gvt headers out into global include Julian Stecklina
2020-01-15 15:22 ` Greg KH
2020-01-16 14:13 ` Julian Stecklina
2020-01-16 14:23 ` Greg KH
2020-01-16 15:05 ` Julian Stecklina
2020-01-16 19:48 ` Greg KH
2020-01-17 2:15 ` Zhenyu Wang
2020-01-14 9:18 ` [RFC PATCH 0/4] Support for out-of-tree hypervisor modules in i915/gvt Christoph Hellwig
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=20200109171357.115936-1-julian.stecklina@cyberus-technology.de \
--to=julian.stecklina@cyberus-technology.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=hang.yuan@intel.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhiyuan.lv@intel.com \
/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).