From: Greg KH <gregkh@linuxfoundation.org>
To: Julian Stecklina <julian.stecklina@cyberus-technology.de>
Cc: Thomas Prescher <thomas.prescher@cyberus-technology.de>,
linux-kernel@vger.kernel.org, hang.yuan@intel.com,
dri-devel@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org, zhiyuan.lv@intel.com
Subject: Re: [RFC PATCH 4/4] drm/i915/gvt: move public gvt headers out into global include
Date: Thu, 16 Jan 2020 15:23:45 +0100 [thread overview]
Message-ID: <20200116142345.GA476889@kroah.com> (raw)
In-Reply-To: <9b32e225ee680e61716e300eb1ed8387599cc0dd.camel@cyberus-technology.de>
On Thu, Jan 16, 2020 at 03:13:01PM +0100, Julian Stecklina wrote:
> Hi Greg, Christoph,
>
> On Wed, 2020-01-15 at 16:22 +0100, Greg KH wrote:
> > On Thu, Jan 09, 2020 at 07:13:57PM +0200, Julian Stecklina wrote:
> > > Now that the GVT interface to hypervisors does not depend on i915/GVT
> > > internals anymore, we can move the headers to the global include/.
> > >
> > > This makes out-of-tree modules for hypervisor integration possible.
> >
> > What kind of out-of-tree modules do you need/want for this?
>
> The mediated virtualization support in the i915 driver needs a backend to the
> hypervisor. There is currently one backend for KVM in the tree
> (drivers/gpu/drm/i915/gvt/kvmgt.c) and at least 3 other hypervisor backends out
> of tree in various states of development that I know of. We are currently
> developing one of these.
Great, then just submit this patch series as part of your patch series
when submitting yoru hypervisor code. That's the normal way to export
new symbols, we can't do so without an in-kernel user.
thanks,
greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-01-16 14:23 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 ` [RFC PATCH 0/4] Support for out-of-tree hypervisor modules in i915/gvt Julian Stecklina
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-20 17:28 ` [RFC PATCH 1/4] " 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 [this message]
2020-01-16 15:05 ` Julian Stecklina
2020-01-16 19:48 ` Greg KH
2020-01-17 2:15 ` Zhenyu Wang
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=20200116142345.GA476889@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hang.yuan@intel.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=julian.stecklina@cyberus-technology.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.prescher@cyberus-technology.de \
--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).