From: Gerd Hoffmann <kraxel@redhat.com>
To: Jike Song <jike.song@intel.com>
Cc: 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: [ANNOUNCE][RFC] KVMGT - the implementation of Intel GVT-g(full GPU virtualization) for KVM
Date: Fri, 05 Dec 2014 09:50:21 +0100 [thread overview]
Message-ID: <1417769421.11297.37.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <547FC5DE.4010701@intel.com>
Hi,
> In KVMGT, we need to register an iodev only *after* BAR registers are
> written by guest.
Oh, the guest can write the bar register at any time. Typically it
happens at boot only, but it can also happen at runtime, for example on
reboot.
I've also seen the kernel redoing the pci mappings created by the bios,
due to buggy _crs declarations in the qemu acpi tables.
> https://www.usenix.org/conference/atc14/technical-sessions/presentation/tian
/me goes read this.
A few comments on the kernel stuff (brief look so far, also
compile-tested only, intel gfx on my test machine is too old).
* Noticed the kernel bits don't even compile when configured as
module. Everything (vgt, i915, kvm) must be compiled into the
kernel.
* Design approach still seems to be i915 on vgt not the other way
around.
Qemu/SeaBIOS bits:
I've seen the host bridge changes identity from i440fx to
copy-pci-ids-from-host. Guess the reason for this is that seabios uses
this device to figure whenever it is running on i440fx or q35. Correct?
What are the exact requirements for the device? Must it match the host
exactly, to not confuse the guest intel graphics driver? Or would
something more recent -- such as the q35 emulation qemu has -- be good
enough to make things work (assuming we add support for the
graphic-related pci config space registers there)?
The patch also adds a dummy isa bridge at 0x1f. Simliar question here:
What exactly is needed here? Would things work if we simply use the q35
lpc device here?
more to come after I've read the paper linked above ...
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-05 8:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 2:24 [ANNOUNCE][RFC] KVMGT - the implementation of Intel GVT-g(full GPU virtualization) for KVM Jike Song
2014-12-04 19:56 ` Igor Gnatenko
2014-12-05 8:50 ` Gerd Hoffmann [this message]
2014-12-05 13:03 ` Paolo Bonzini
2014-12-06 4:30 ` Jike Song
2014-12-09 2:49 ` 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 ` 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
2014-12-09 2:51 ` Tian, Kevin
2014-12-09 9:54 ` Jan Kiszka
2014-12-10 6:31 ` Jike Song
2014-12-10 6:34 ` 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=1417769421.11297.37.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=david.j.cowperthwaite@intel.com \
--cc=eddie.dong@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jike.song@intel.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;
as well as URLs for NNTP newsgroup(s).