From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Widawsky Subject: Re: [Intel-gfx] [PATCH 01/10] intel: shared header for shader debugging Date: Wed, 27 Jul 2011 15:40:35 +0000 Message-ID: <20110727154035.GC2006@cloud01> References: <1310590312-21669-1-git-send-email-ben@bwidawsk.net> <1310590312-21669-2-git-send-email-ben@bwidawsk.net> <20110719210617.GA32052@radis.liafa.jussieu.fr> <20110721135441.GA19752@cloud01> <20110721212212.GD32052@radis.liafa.jussieu.fr> <20110727150807.GA2006@cloud01> <20110727151630.GA30414@coloquinte.cristau.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20110727151630.GA30414@coloquinte.cristau.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Julien Cristau Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Wed, Jul 27, 2011 at 05:16:31PM +0200, Julien Cristau wrote: > 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. I wasn't even aware of abstract domain sockets. Seems like fun, let me try that one first. Ben