public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Xiaolin Zhang <xiaolin.zhang@intel.com>,
	intel-gvt-dev@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v1] drm/i915: Enhanced for initialize partially filled pagetables
Date: Thu, 28 Sep 2017 17:25:01 +0300	[thread overview]
Message-ID: <1506608701.9186.44.camel@linux.intel.com> (raw)
In-Reply-To: <20170928020904.5030-1-xiaolin.zhang@intel.com>

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 gvt: guest page write error -22,
> gfn 0x7ada8, pa 0x7ada89a8, var 0x6, len 1” when create linux guest.
> 
> Signed-off-by: Xiaolin Zhang <xiaolin.zhang@intel.com>

Why does the hypervisor try to access the entries prior to them being
made valid for hardware?

Regards, Joonas
-- 
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

  parent reply	other threads:[~2017-09-28 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28  2:09 [PATCH v1] drm/i915: Enhanced for initialize partially filled pagetables Xiaolin Zhang
2017-09-28  2:33 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-09-28  5:11 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-28 14:25 ` Joonas Lahtinen [this message]
2017-09-30  2:58   ` [PATCH v1] " Zhang, Xiaolin
2017-10-02  9:03     ` Joonas Lahtinen
2017-10-03  7:50       ` Wang, Zhi A
2017-10-25 14:52 ` ✗ Fi.CI.BAT: failure for " Patchwork

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=1506608701.9186.44.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=xiaolin.zhang@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