From: Daniel Vetter <daniel@ffwll.ch>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jike Song <jike.song@intel.com>,
kvm@vger.kernel.org, "White,
Michael L" <michael.l.white@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Li, Susie" <susie.li@intel.com>,
"Cowperthwaite, David J" <david.j.cowperthwaite@intel.com>,
linux-kernel@vger.kernel.org, "Haron,
Sandra" <sandra.haron@intel.com>
Subject: Re: [Intel-gfx] [ANNOUNCE][RFC] KVMGT - the implementation of Intel GVT-g(full GPU virtualization) for KVM
Date: Mon, 8 Dec 2014 11:20:49 +0100 [thread overview]
Message-ID: <20141208102049.GO20350@phenom.ffwll.local> (raw)
In-Reply-To: <1418032501.27021.42.camel@nilsson.home.kraxel.org>
On Mon, Dec 08, 2014 at 10:55:01AM +0100, Gerd Hoffmann wrote:
> On Sa, 2014-12-06 at 12:17 +0800, Jike Song wrote:
> > I don't know that is exactly needed, we also need to have Windows
> > driver considered. However, I'm quite confident that, if things gonna
> > work for IGD passthrough, it gonna work for GVT-g.
>
> I'd suggest to focus on q35 emulation. q35 is new enough that a version
> with integrated graphics exists, so the gap we have to close is *much*
> smaller.
>
> In case guests expect a northbridge matching the chipset generation of
> the graphics device (which I'd expect is the case, after digging a bit
> in the igd and agpgart linux driver code) I think we should add proper
> device emulation for them, i.e. comply q35-pcihost with
> sandybridge-pcihost + ivybridge-pcihost + haswell-pcihost instead of
> just copying over the pci ids from the host. Most likely all those
> variants can share most of the emulation code.
I don't think i915.ko should care about either northbridge nor pch on
para-virtualized platforms. We do noodle around in there for the oddball
memory controller setting and for some display stuff. But neither of that
really applies to paravirtualized hw. And if there's any case like that we
should patch it out (like we do with some of the runtime pm code
already).
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-12-08 10:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 2:24 Jike Song
2014-12-05 8:50 ` Gerd Hoffmann
2014-12-05 13:03 ` Paolo Bonzini
2014-12-06 4:30 ` Jike Song
2014-12-09 2:49 ` [Intel-gfx] " Tian, Kevin
2014-12-10 16:59 ` Paolo Bonzini
2014-12-11 0:33 ` Tian, Kevin
2014-12-11 1:38 ` Paolo Bonzini
2014-12-05 13:54 ` [Intel-gfx] " Daniel Vetter
2014-12-06 4:32 ` Jike Song
2014-12-06 4:17 ` Jike Song
2014-12-08 9:55 ` Gerd Hoffmann
2014-12-08 10:20 ` Daniel Vetter [this message]
2014-12-09 2:51 ` [Intel-gfx] " Tian, Kevin
2014-12-09 9:54 ` Jan Kiszka
2014-12-10 6:31 ` Jike Song
2014-12-10 6:34 ` [Intel-gfx] " Jike Song
2014-12-10 7:28 ` Tian, Kevin
2015-10-27 9:36 ` Jike Song
2016-01-27 6:32 ` [ANNOUNCE] 2015-Q4 release of KVMGT (Was Re: KVMGT - the implementation of ...) Jike Song
2016-04-16 6:31 ` [ANNOUNCE] 2016-Q1 " Jike Song
2016-07-20 4:52 ` [ANNOUNCE] 2016-Q2 " Jike Song
2016-11-06 15:23 ` [ANNOUNCE] 2016-Q3 " Jike Song
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=20141208102049.GO20350@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=david.j.cowperthwaite@intel.com \
--cc=eddie.dong@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jike.song@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.l.white@intel.com \
--cc=sandra.haron@intel.com \
--cc=susie.li@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
all inboxes | Powered by JetHome®