From: Julien Cristau <jcristau@debian.org>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 01/10] intel: shared header for shader debugging
Date: Wed, 27 Jul 2011 17:16:31 +0200 [thread overview]
Message-ID: <20110727151630.GA30414@coloquinte.cristau.org> (raw)
In-Reply-To: <20110727150807.GA2006@cloud01>
On Wed, Jul 27, 2011 at 15:08:08 +0000, Ben Widawsky wrote:
> On Thu, Jul 21, 2011 at 11:22:12PM +0200, Julien Cristau wrote:
> > On Thu, Jul 21, 2011 at 13:54:41 +0000, Ben Widawsky wrote:
> >
> > > On Tue, Jul 19, 2011 at 11:06:17PM +0200, Julien Cristau wrote:
> > > > On Wed, Jul 13, 2011 at 13:51:43 -0700, Ben Widawsky wrote:
> > > >
> > > > > +#define SHADER_DEBUG_SOCKET "/tmp/gen_debug"
> > > >
> > > > Not sure what this is used for, but does it really need to be in /tmp?
> > >
> > > It is the shared socket between a debug client (ie. Mesa) and the
> > > debugger. I don't care where it goes, do you have any recommendations?
> > >
> > Somewhere under $HOME is probably better than a predictable file name in
> > /tmp.
>
> $HOME is not great because it requires a little hackery to accomplish.
> The debugger will be running as root, and so if we put it in root's
> $HOME, mesa may not be able to reach it.
>
Ah, I didn't realise this would run as root. Would /run (or /var/run)
be ok then? Alternately, use an abstract domain socket to not have to
care about the underlying filesystem.
Cheers,
Julien
next prev parent reply other threads:[~2011-07-27 15:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 20:51 [PATCH 0/10] fs shader debugging Ben Widawsky
2011-07-13 20:51 ` [PATCH 01/10] intel: shared header for " Ben Widawsky
2011-07-13 20:56 ` Chris Wilson
2011-07-19 21:06 ` [Intel-gfx] " Julien Cristau
2011-07-21 13:54 ` Ben Widawsky
2011-07-21 21:22 ` [Intel-gfx] " Julien Cristau
2011-07-27 15:08 ` Ben Widawsky
2011-07-27 15:16 ` Julien Cristau [this message]
2011-07-27 15:28 ` Alan Cox
2011-07-27 15:40 ` Ben Widawsky
2011-07-13 20:51 ` [PATCH 02/10] i965: copy in system routine, reserve extra scratch Ben Widawsky
2011-07-18 18:13 ` Eric Anholt
2011-07-13 20:51 ` [PATCH 03/10] i965: Reserve scratch space for debugger communication Ben Widawsky
2011-07-13 20:51 ` [PATCH 04/10] i965: setup system routine Ben Widawsky
2011-07-13 21:04 ` [Mesa-dev] " Chris Wilson
2011-07-13 20:51 ` [PATCH 05/10] i965: emit breakpoints Ben Widawsky
2011-07-13 20:51 ` [PATCH 06/10] i965: attach to a listening debugger Ben Widawsky
2011-07-13 20:51 ` [PATCH 07/10] intel-gpu-tools: register range handling for forcewake hooks Ben Widawsky
2011-07-13 21:15 ` Chris Wilson
2011-07-13 20:51 ` [PATCH 08/10] intel-gpu-tools/forcewaked: simple forcewake app Ben Widawsky
2011-07-13 21:18 ` Chris Wilson
2011-07-13 20:51 ` [PATCH 09/10] debugging: add important debug regs Ben Widawsky
2011-07-13 21:20 ` Chris Wilson
2011-07-13 20:51 ` [PATCH 10/10] debugging: shader debugging Ben Widawsky
2011-07-13 22:06 ` [PATCH 0/10] fs " 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=20110727151630.GA30414@coloquinte.cristau.org \
--to=jcristau@debian.org \
--cc=ben@bwidawsk.net \
--cc=dri-devel@lists.freedesktop.org \
--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 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.