Re: [Mesa-dev] Perfetto CPU/GPU tracing

2021-02-18 Thread Tamminen, Eero T
Hi, (This isn't anymore that related to Mesa, but maybe it's still of interest.) On Thu, 2021-02-18 at 16:40 +0100, Primiano Tucci wrote: > On 18/02/2021 14:35, Tamminen, Eero T wrote: [...] > > It doesn't require executable code to be writable from user-space, > > library code

Re: [Mesa-dev] Perfetto CPU/GPU tracing

2021-02-18 Thread Tamminen, Eero T
Hi, On Thu, 2021-02-18 at 12:17 +0100, Primiano Tucci wrote: [discussion about Perfetto itself] ... > eero.t.tamminen@ > from in common Linux distro repos. > > That's right. I am aware of the problem. The plan is to address it > with > bit.ly/perfetto-debian as a starter. Glad to hear

Re: [Mesa-dev] Perfetto CPU/GPU tracing

2021-02-15 Thread Tamminen, Eero T
Hi, On Fri, 2021-02-12 at 18:20 -0800, Rob Clark wrote: > On Fri, Feb 12, 2021 at 5:56 PM Lionel Landwerlin > wrote: ... > > In our implementation that precision (in particular when a drawcall > > ends) comes at a stalling cost unfortunately. > > yeah, stalling on our end too for per-draw

Re: [Mesa-dev] Perfetto CPU/GPU tracing

2021-02-12 Thread Tamminen, Eero T
Hi, On Thu, 2021-02-11 at 17:39 -0800, John Bates wrote: > I recently opened issue 4262 > to begin the > discussion on integrating perfetto into mesa. > > *Background* > > System-wide tracing is an invaluable tool for developers to find

Re: [Mesa-dev] Rust drivers in Mesa

2020-10-15 Thread Tamminen, Eero T
Hi, On Wed, 2020-10-14 at 15:40 -0700, Eric Anholt wrote: > On Wed, Oct 14, 2020 at 3:26 PM Alyssa Rosenzweig > wrote: > > I didn't think to enforce a lint during CI. Part of me wonders if > > we > > should be doing that for C too, but we can shave that yak sometime > > else. > > I don't think

Re: [Mesa-dev] RFC: Memory allocation on Mesa

2020-05-12 Thread Tamminen, Eero T
Hi, On Tue, 2020-05-12 at 14:36 +, Jose Fonseca wrote: > From: mesa-dev on behalf of > Tamminen, Eero T > I've done a lot of resource usage analysis at former job[1], but I've > never had needed anything like that. malloc etc all reside in a > separate shared library from

Re: [Mesa-dev] RFC: Memory allocation on Mesa

2020-05-12 Thread Tamminen, Eero T
Hi, On Tue, 2020-05-12 at 10:36 +0200, Timur Kristóf wrote: > On Mon, 2020-05-11 at 20:19 +0000, Tamminen, Eero T wrote: > > I've done a lot of resource usage analysis at former job[1], but > > I've > > never had needed anything like that. malloc etc all reside in a > &

Re: [Mesa-dev] RFC: Memory allocation on Mesa

2020-05-11 Thread Tamminen, Eero T
Hi, On Mon, 2020-05-11 at 16:13 +, Jose Fonseca wrote: > Some might retort: why not just play some tricks with the linker, and > intercept all malloc/free calls, without actually having to modify > any source code? > > Yes, that's indeed technically feasible. And is precisely the sort > of