From: Ben Widawsky <widawsky@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: benjamin.widawsky@linux.intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] drm/i915: context support unit test
Date: Thu, 30 Dec 2010 12:21:19 -0800 [thread overview]
Message-ID: <20101230202118.GA4813@snipes.kumite> (raw)
In-Reply-To: <e422031f05cf8e51af8ab1f9153cc3d0.squirrel@www.ffwll.ch>
On Thu, Dec 30, 2010 at 01:48:36PM +0100, Daniel Vetter wrote:
> This way userspace doesn't have to track a list of context bos and the
> kernel gem stays in full control. And specifying the context relation of
> a bo toghether with the relocation that actually uses it is probably the
> clearest solution.
I'll need to research this one more.
>
> And wrt restoring the gtt offset: I think to guarantee this, we need
> ppGTT. In the GGTT we might get unlucky and a scanout buffer sits at
> the desired spot. So at least for bring-up (until ppGTT works) we need
> to be able to bail out in the kernel and politely ask userspace to fix up
> the mess ;)
I agree with this. Depending on what the HW does when it loads state, it
might also require allowing the client to have a way to prevent
restoring context on the next submission. I think it would be good to
add this to the API even if HW doesn't require it.
Either way, I think this gets messy if we allow sharing contexts amongst
clients. I hope nobody has a good use case for sharing contexts :-).
>
> Cheers, Daniel
>
Ben
next prev parent reply other threads:[~2010-12-30 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-25 22:53 [RFC] drm/i915: context support unit test Ben Widawsky
2010-12-28 22:36 ` Daniel Vetter
2010-12-29 4:03 ` Ben Widawsky
2010-12-30 10:07 ` Daniel Vetter
2010-12-30 11:13 ` Chris Wilson
2010-12-30 12:48 ` Daniel Vetter
2010-12-30 20:21 ` Ben Widawsky [this message]
2010-12-31 0:48 ` Ben Widawsky
2010-12-31 9:31 ` Chris Wilson
2011-01-04 20:10 ` Daniel Vetter
2011-01-04 20:21 ` Ben Widawsky
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=20101230202118.GA4813@snipes.kumite \
--to=widawsky@gmail.com \
--cc=benjamin.widawsky@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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