intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, 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 14:03:32 +0100	[thread overview]
Message-ID: <5481AD24.3000703@redhat.com> (raw)
In-Reply-To: <1417769421.11297.37.camel@nilsson.home.kraxel.org>



On 05/12/2014 09:50, Gerd Hoffmann wrote:
> 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.

I'll add that the patch is basically impossible to review with all the
XenGT bits still in.  For example, the x86 emulator seems to be
unnecessary for KVMGT, but I am not 100% sure.

I would like a clear understanding of why/how Andrew Barnes was able to
do i915 passthrough (GVT-d) without hacking the ISA bridge, and why this
does not apply to GVT-g.

Paolo

>  * 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
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-12-05 13:03 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
2014-12-05 13:03   ` Paolo Bonzini [this message]
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=5481AD24.3000703@redhat.com \
    --to=pbonzini@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=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;
as well as URLs for NNTP newsgroup(s).