From: Ben Widawsky <ben@bwidawsk.net>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/5] lib: Add a drm_open_any_render() that will try to use render nodes
Date: Thu, 24 Oct 2013 15:17:14 -0700 [thread overview]
Message-ID: <20131024221714.GD28973@bwidawsk.net> (raw)
In-Reply-To: <20131024210543.GB2935@strange.amr.corp.intel.com>
On Thu, Oct 24, 2013 at 10:05:43PM +0100, Damien Lespiau wrote:
> On Thu, Oct 24, 2013 at 10:01:21PM +0100, Damien Lespiau wrote:
> > On Thu, Oct 24, 2013 at 01:43:22PM -0700, Ben Widawsky wrote:
> > > On Thu, Oct 24, 2013 at 03:40:54PM +0100, Damien Lespiau wrote:
> > > > I was fedup with having to run my tests as root and not being able to
> > > > use my usual setup for tests that only exercise the GT part of the GPU.
> > > >
> > > > Render nodes to the rescue!
> > >
> > > I think usually this is a bad idea except for pretty isolated proof of
> > > concept kind of things. Mostly intel-gpu-tools is testing our kernel
> > > driver, and therefore running without a reboot anyway is sort of
> > > unusual.
> >
> > Hum? I fail to see the link. It should be strickly equivalent, with the
> > added bonus that you can write and execute a test as a normal user.
>
> By "normal user" I mean with a DRM master running and without having to
> do the authentification dance.
>
> --
> Damien
You're right, this was a half baked thought. What I was thinking is,
condoning running tests on a live system is a bad idea - but forcing
rendernodes doesn't effect that.
Also, I agree with Daniel. Getting some simultaneous tests would be
nice.
Practically, requiring root won't go away I think, since certain things
like our forcewake debugfs require root. Anyway, carry on.
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-10-24 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 14:40 Using render nodes in i-g-t Damien Lespiau
2013-10-24 14:40 ` [PATCH 1/5] lib: Remove stale comment Damien Lespiau
2013-10-24 14:40 ` [PATCH 2/5] lib: Close non intel fds in drm_get_card() Damien Lespiau
2013-10-24 14:40 ` [PATCH 3/5] lib: Add a drm_open_any_render() that will try to use render nodes Damien Lespiau
2013-10-24 20:43 ` Ben Widawsky
2013-10-24 21:01 ` Damien Lespiau
2013-10-24 21:05 ` Damien Lespiau
2013-10-24 22:17 ` Ben Widawsky [this message]
2013-10-24 14:40 ` [PATCH 4/5] tests/gem_render_copy: Use " Damien Lespiau
2013-10-24 14:40 ` [PATCH 5/5] tests: Convert the ctx test to use render nodes when possible Damien Lespiau
2013-10-28 11:04 ` Using render nodes in i-g-t Damien Lespiau
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=20131024221714.GD28973@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=damien.lespiau@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