linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jike Song <jike.song@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	Andrew Barnes <umbramalison@gmail.com>
Subject: Re: [ANNOUNCE][RFC] KVMGT - the implementation of Intel GVT-g(full GPU virtualization) for KVM
Date: Sat, 06 Dec 2014 12:30:39 +0800	[thread overview]
Message-ID: <5482866F.70500@intel.com> (raw)
In-Reply-To: <5481AD24.3000703@redhat.com>

CC Andy :)

On 12/05/2014 09:03 PM, Paolo Bonzini wrote:
>
> 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.
>

This is not ready for merge yet, please wait for a while, we'll have
Xen/KVM specific code separated.

BTW, definitely you are right, the emulator is unnecessary for KVMGT,
and ... unnecessary for XenGT :)

> 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.

AFAIK, the graphics drivers need to figure out the offset of
some MMIO registers, by the IDs of this ISA bridge. It simply won't work
without this information.

Talked with Andy about the pass-through but I don't have his implementation,
CC Andy for his advice :)

>
> Paolo
>

Thanks for review. Would you please also have a look at the issues I mentioned
in the original email? they are most KVM-related: the SRCU trickiness, domid,
and the memslot created in kernel.

Thank you!

--
Thanks,
Jike

  reply	other threads:[~2014-12-06  4:33 UTC|newest]

Thread overview: 23+ 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-05  8:50 ` Gerd Hoffmann
2014-12-05 13:03   ` Paolo Bonzini
2014-12-06  4:30     ` Jike Song [this message]
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       ` [Intel-gfx] " 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   ` [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=5482866F.70500@intel.com \
    --to=jike.song@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=umbramalison@gmail.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).