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: Tue, 4 Jan 2011 12:21:52 -0800 [thread overview]
Message-ID: <20110104202152.GA3838@snipes.kumite> (raw)
In-Reply-To: <20110104201004.GA3519@viiv.ffwll.ch>
On Tue, Jan 04, 2011 at 09:10:04PM +0100, Daniel Vetter wrote:
> On Fri, Dec 31, 2010 at 09:31:23AM +0000, Chris Wilson wrote:
> > I'm still leaning towards explicit associate/disassociate ioctls as I
> > think that will lead to a simpler userspace API (or at least integrate
> > conveniently with the existing libdrm).
>
> I don't like a separate ioctl to associate/disassociate a buffer from a
> context: Conceptually there's no way to change that association without an
> execbuf call. Doing the book-keeping as a separate, non-atomic ioctl calls
> calls for trouble imho.
>
I think there is a distinct possibility that we'll need a way to
associate buffers with either the GGTT or the ppGTT. I'm currently
trying to figure out if this is actually the case but I haven't yet been
able to find exactly which memory objects, if any, must be accessed
through the GGTT.
Just curious Daniel, if this is the case, does it change your feeling
on the IOCTL, or do you still prefer execbuf?
Ben
prev parent reply other threads:[~2011-01-04 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
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 [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=20110104202152.GA3838@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