From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: "Zhang, Xiaolin" <xiaolin.zhang@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v1] drm/i915: Enhanced for initialize partially filled pagetables
Date: Mon, 02 Oct 2017 12:03:25 +0300 [thread overview]
Message-ID: <1506935005.6755.27.camel@linux.intel.com> (raw)
In-Reply-To: <073732E20AE4C540AE91DBC3F07D44607BF5F0DE@SHSMSX101.ccr.corp.intel.com>
+ Zhenyu and Zhi
On Sat, 2017-09-30 at 02:58 +0000, 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 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
>
> Hi Joonas,
> thanks your comment.
> I think what you ask is the point we got the error message in gvt since the current gvt
> implementation is that page under write protection and trapped should be valid
> with correct shadow page setup and p2m translation.
My question is that if the hardware doesn't care about them being
uninitialized at this point, how can GVT? If the GVT implementation
relies heavily on how the i915 driver currently happens to behave, not
on what contracts it has with the hardware, these breakages are bound
to happen repeatedly. The code is being transformed and optimized on
daily basis, how it currently behaves is not a solid foundation for
implementing the host side virtualization.
> Actually, to work with
> “initialize partially filled pagetables" , there is a certain refine work to do in gvt side
> (maybe less or maybe large). but before refine work done, this patch is trying to bring back
> gvt behavior as before “initialize partially filled pagetables"patch.
We should first minimize and then keep the vgpu specific checks to
minimum. So this would need to be fixed on the GVT side of code.
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
next prev parent reply other threads:[~2017-10-02 9:03 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 ` [PATCH v1] " Joonas Lahtinen
2017-09-30 2:58 ` Zhang, Xiaolin
2017-10-02 9:03 ` Joonas Lahtinen [this message]
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=1506935005.6755.27.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