From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: zhenyuw@linux.intel.com, zhi.a.wang@intel.com,
intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
yan.y.zhao@intel.com
Subject: Re: Regression: gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error
Date: Tue, 13 Apr 2021 09:43:58 +0800 [thread overview]
Message-ID: <20210413014358.GB14309@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20210412192347.042fbc14@x1.home.shazbot.org>
[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]
On 2021.04.12 19:23:47 -0600, Alex Williamson wrote:
> On Mon, 12 Apr 2021 10:32:14 -0600
> Alex Williamson <alex.williamson@redhat.com> wrote:
>
> > Running a Windows guest on a i915-GVTg_V4_2 from an HD 5500 IGD on
> > v5.12-rc6 results in host logs:
> >
> > gvt: vgpu 1: lrm access to register (20c0)
> > gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error
> > gvt: vgpu 1: cmd parser error
> > 0x0
> > 0x29
> >
> > gvt: vgpu 1: scan wa ctx error
> > gvt: vgpu 1: failed to submit desc 0
> > gvt: vgpu 1: fail submit workload on ring rcs0
> > gvt: vgpu 1: fail to emulate MMIO write 00002230 len 4
> >
> > The guest goes into a boot loop triggering this error before reaching
> > the desktop and rebooting. Guest using Intel driver 20.19.15.5171
> > dated 11/4/2020 (from driver file 15.40.5171).
> >
> > This VM works well with the same guest and userspace software stack on
> > Fedora's kernel 5.11.11-200.fc33.x86_64. Thanks,
>
> Bisected to:
Looks we didn't hit this one on Broadwell with recent testing. I'll double
check, maybe Broadwell missed something after our cmd parser rework.
Thanks for reporting!
>
> commit f18d417a57438498e0de481d3a0bc900c2b0e057
> Author: Yan Zhao <yan.y.zhao@intel.com>
> Date: Wed Dec 23 11:45:08 2020 +0800
>
> drm/i915/gvt: filter cmds "srm" and "lrm" in cmd_handler
>
> do not allow "srm" and "lrm" except for GEN8_L3SQCREG4 and 0x21f0.
>
> Cc: Colin Xu <colin.xu@intel.com>
> Cc: Kevin Tian <kevin.tian@intel.com>
> Signed-off-by: Yan Zhao <yan.y.zhao@intel.com>
> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
> Link: http://patchwork.freedesktop.org/patch/msgid/20201223034508.17031-1-yan.y.zhao@intel.com
> Reviewed-by: Zhenyu Wang <zhenyuw@linux.intel.com>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-04-13 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 16:32 Regression: gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error Alex Williamson
2021-04-13 1:23 ` Alex Williamson
2021-04-13 1:43 ` Zhenyu Wang [this message]
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=20210413014358.GB14309@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yan.y.zhao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox