From: Daniel Vetter <daniel@ffwll.ch>
To: "Zhao, Yakui" <yakui.zhao@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Specify bsd rings through exec flag
Date: Wed, 6 Aug 2014 09:45:05 +0200 [thread overview]
Message-ID: <CAKMK7uEt5osY7MKHcYhELb07S3zHn332uVpUFJ_X=R3U65+VRw@mail.gmail.com> (raw)
In-Reply-To: <1407288722.2043.66.camel@genxdev-ykzhao.sh.intel.com>
On Wed, Aug 6, 2014 at 3:32 AM, Zhao, Yakui <yakui.zhao@intel.com> wrote:
> >After the GPU hang occurs on BSD ring during decoding, it needs to
> specify the corresponding BSD ring to read the decoding status registers
> related with the BSD ring.
>
> Can this be regarded as one open-source usage scenario?
Sure, but I'm not sure whether this is the correct way to do this - if
some other libva client does an execbuf in-between couldn't these
register get overwritten? It sounds like the kernel should capture
these registers for userspace in a race-free way and then provide them
with maybe an extension to the reset-stats ioctl?
I definitely want to see how this is used in libva before signing up
for a new kernel interface.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-08-06 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 7:54 [PATCH] drm/i915: Specify bsd rings through exec flag Zhipeng Gong
2014-08-05 8:28 ` Chris Wilson
[not found] ` <A0A308111D30BF46A5A1E3C3D8A187A801139816@SHSMSX103.ccr.corp.intel.com>
2014-08-06 3:19 ` Gong, Zhipeng
2014-08-05 8:44 ` Daniel Vetter
2014-08-06 1:32 ` Zhao, Yakui
2014-08-06 7:45 ` Daniel Vetter [this message]
[not found] <CABVU7+uxdZEiH77CtdtveJtKi5x0mTAxuPiXT8389Y2EKRsRfQ@mail.gmail.com>
2014-11-17 11:06 ` Rodrigo Vivi
2014-11-17 18:58 ` Daniel Vetter
2014-11-18 7:39 ` shuang.he
2014-12-10 2:04 Zhipeng Gong
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='CAKMK7uEt5osY7MKHcYhELb07S3zHn332uVpUFJ_X=R3U65+VRw@mail.gmail.com' \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yakui.zhao@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.