riginal Message-
From: Joonas Lahtinen [mailto:joonas.lahti...@linux.intel.com]
Sent: Monday, October 2, 2017 12:03 PM
To: Zhang, Xiaolin ;
intel-gvt-...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
Cc: Zhenyu Wang ; Wang, Zhi A
Subject: Re: [Intel-gfx] [PATCH v1] drm/i915: Enhanced
+ Zhenyu and Zhi
On Sat, 2017-09-30 at 02:58 +, Zhang, Xiaolin wrote:
> On 09/28/2017 10:25 PM, Joonas Lahtinen wrote:
> > On Thu, 2017-09-28 at 10:09 +0800, Xiaolin Zhang wrote:
> > > if vgpu active, the page table entry should be initialized after
> > > allocation and then the hypersivor can
On 09/28/2017 10:25 PM, Joonas Lahtinen wrote:
On Thu, 2017-09-28 at 10:09 +0800, Xiaolin Zhang wrote:
if vgpu active, the page table entry should be initialized after
allocation and then the hypersivor can ping pages succesuffly,
otherwise hypervisor will ping pages failed and the host will pri
On Thu, 2017-09-28 at 10:09 +0800, Xiaolin Zhang wrote:
> if vgpu active, the page table entry should be initialized after
> allocation and then the hypersivor can ping pages succesuffly,
> otherwise hypervisor will ping pages failed and the host will print
> a lot of annoying errors such as “ERROR
if vgpu active, the page table entry should be initialized after
allocation and then the hypersivor can ping pages succesuffly,
otherwise hypervisor will ping pages failed and the host will print
a lot of annoying errors such as “ERROR gvt: guest page write error -22,
gfn 0x7ada8, pa 0x7ada89a8, va
