All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, Zhi Wang <zhi.a.wang@intel.com>
Cc: Intel graphics driver community testing & development
	<intel-gfx@lists.freedesktop.org>,
	Matthew Auld <matthew.auld@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Disable lazy PPGTT page table optimization for vGPU
Date: Fri, 20 Oct 2017 12:03:59 +0300	[thread overview]
Message-ID: <1508490239.5349.2.camel@linux.intel.com> (raw)
In-Reply-To: <20171019024822.zn735mr56vm7m3j5@zhen-hp.sh.intel.com>

Yesterday, Zhi was still looking if this could be fixed by a small
modification in the GVT-g side, which would be much preferred.

Zhi, What's the status there?

Regards, Joonas

On Thu, 2017-10-19 at 10:48 +0800, Zhenyu Wang wrote:
> On 2017.10.18 13:25:43 +0300, Joonas Lahtinen wrote:
> > When running under virtualization (vGPU active), we must disable
> > the azy PPGTT page table initialization optimization introduced by:
> > 
> > 14826673247e ("drm/i915: Only initialize partially filled pagetables")
> > 
> > We must do this because GVT-g makes unduly assumptions about guest
> > behaviour, which this optimization breaks. This results in following
> > looking errors in the host:
> > 
> > ERROR gvt: guest page write error -22, gfn 0x7ada8, pa 0x7ada89a8, var 0x6, len 1
> > 
> > The real fix is to not to depend on i915 driver behaviour, but instead
> > either rely on only the contracts that i915 has with the hardware, or
> > add some paravirtualization. While the real fix is en route, it won't
> > be finished in time for 4.15, so the best option is to disable the
> > optimization for now when vGPU is active to avoid breaking 4.15 guests
> > in existing VM environments.
> > 
> > Fixes: 14826673247e ("drm/i915: Only initialize partially filled pagetables")
> > Suggested-by: Xiaolin Zhang <xiaolin.zhang@intel.com>
> > Signed-off-by: Xiaolin Zhang <xiaolin.zhang@intel.com>
> > [Joonas: Rewrote the commit message and added tags.]
> > Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Zhenyu Wang <zhenyuw@linux.intel.com>
> > Cc: Zhi Wang <zhi.a.wang@intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>

<SNIP>
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-20  9:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 10:25 [PATCH] drm/i915: Disable lazy PPGTT page table optimization for vGPU Joonas Lahtinen
2017-10-18 10:29 ` Chris Wilson
2017-10-18 11:18 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-18 18:26 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-19  2:48 ` [PATCH] " Zhenyu Wang
2017-10-20  9:03   ` Joonas Lahtinen [this message]
2017-10-20  9:06     ` Wang, Zhi A

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=1508490239.5349.2.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.