From: Ben Widawsky <ben@bwidawsk.net>
To: Eric Anholt <eric@anholt.net>
Cc: Ian Romanick <ian.d.romanick@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] intel: Add accessor to get HW context ID from a drm_intel_context
Date: Tue, 12 Nov 2013 23:08:17 -0800 [thread overview]
Message-ID: <20131113070816.GA26107@bwidawsk.net> (raw)
In-Reply-To: <87txfig16k.fsf@eliezer.anholt.net>
On Mon, Nov 11, 2013 at 11:58:59AM -0800, Eric Anholt wrote:
> Ian Romanick <idr@freedesktop.org> writes:
>
> > From: Ian Romanick <ian.d.romanick@intel.com>
> >
> > The drm_intel_context structure is, wisely, opaque. However, libdrm
> > users may want to know the hardware context ID associated with the
> > structure.
>
> We've had a bunch of our other structures be partially transparent. The
> context id to be passed to the kernel could easily be public just like
> the gem handle in a BO is public. I would lean slightly toward that.
>
> But I don't feel strongly either way, so these two are:
>
> Reviewed-by: Eric Anholt <eric@anholt.net>
I think my preference would be to add a "context" argument to a libdrm
get_hangstats function, but if you feel this way is better, it is fine
with me.
My only [slight, unjustified] concern is that once you make the id
transparent, we can't play any games. Since the DDX doesn't use libdrm
however, I think it is fairly moot.
Acked-by: Ben Widawsky <ben@bwidawsk.net>
--
Ben Widawsky, Intel Open Source Technology Center
prev parent reply other threads:[~2013-11-13 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:48 [PATCH 1/2] intel: Add accessor to get HW context ID from a drm_intel_context Ian Romanick
2013-11-11 17:48 ` [PATCH 2/2] intel: Silence warning in non-Valgrind build Ian Romanick
2013-11-11 19:58 ` [PATCH 1/2] intel: Add accessor to get HW context ID from a drm_intel_context Eric Anholt
2013-11-13 7:08 ` 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=20131113070816.GA26107@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=ian.d.romanick@intel.com \
--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