Re: refcount btrace

2022-06-27 Thread Alexander Bluhm
On Fri, Apr 22, 2022 at 12:07:44AM +0200, Alexander Bluhm wrote: > I still think it is worth to have refcount debugging in generic > kernel dt(4). Having tools is easier than first adding printf to > hunt a bug. I see no downside. I have talked with mpi@. We both think it is useful to have refc

Re: refcount btrace

2022-04-21 Thread Alexander Bluhm
I still think it is worth to have refcount debugging in generic kernel dt(4). Having tools is easier than first adding printf to hunt a bug. I see no downside. ok? bluhm Index: dev/dt/dt_prov_static.c === RCS file: /data/mirror/op

Re: refcount btrace

2022-04-12 Thread Alexander Bluhm
On Mon, Apr 11, 2022 at 07:19:00PM +0200, Martin Pieuchot wrote: > On 08/04/22(Fri) 12:16, Alexander Bluhm wrote: > > On Fri, Apr 08, 2022 at 02:39:34AM +, Visa Hankala wrote: > > > On Thu, Apr 07, 2022 at 07:55:11PM +0200, Alexander Bluhm wrote: > > > > On Wed, Mar 23, 2022 at 06:13:27PM +0100

Re: refcount btrace

2022-04-11 Thread Martin Pieuchot
On 08/04/22(Fri) 12:16, Alexander Bluhm wrote: > On Fri, Apr 08, 2022 at 02:39:34AM +, Visa Hankala wrote: > > On Thu, Apr 07, 2022 at 07:55:11PM +0200, Alexander Bluhm wrote: > > > On Wed, Mar 23, 2022 at 06:13:27PM +0100, Alexander Bluhm wrote: > > > > In my opinion tracepoints give insight a

Re: refcount btrace

2022-04-08 Thread Alexander Bluhm
On Fri, Apr 08, 2022 at 02:39:34AM +, Visa Hankala wrote: > On Thu, Apr 07, 2022 at 07:55:11PM +0200, Alexander Bluhm wrote: > > On Wed, Mar 23, 2022 at 06:13:27PM +0100, Alexander Bluhm wrote: > > > In my opinion tracepoints give insight at minimal cost. It is worth > > > it to have it in GEN

Re: refcount btrace

2022-04-07 Thread Visa Hankala
On Thu, Apr 07, 2022 at 07:55:11PM +0200, Alexander Bluhm wrote: > On Wed, Mar 23, 2022 at 06:13:27PM +0100, Alexander Bluhm wrote: > > In my opinion tracepoints give insight at minimal cost. It is worth > > it to have it in GENERIC to make it easy to use. > > After release I want to revive the b

Re: refcount btrace

2022-04-07 Thread Alexander Bluhm
On Wed, Mar 23, 2022 at 06:13:27PM +0100, Alexander Bluhm wrote: > In my opinion tracepoints give insight at minimal cost. It is worth > it to have it in GENERIC to make it easy to use. After release I want to revive the btrace of refcounts discussion. As mpi@ mentioned the idea of dt(4) is to h

Re: refcount btrace

2022-03-23 Thread Alexander Bluhm
On Mon, Mar 21, 2022 at 01:22:22PM +0100, Martin Pieuchot wrote: > On 20/03/22(Sun) 05:39, Visa Hankala wrote: > > On Sat, Mar 19, 2022 at 12:10:11AM +0100, Alexander Bluhm wrote: > > > On Thu, Mar 17, 2022 at 07:25:27AM +, Visa Hankala wrote: > > > > On Thu, Mar 17, 2022 at 12:42:13AM +0100, A

Re: refcount btrace

2022-03-21 Thread Martin Pieuchot
On 20/03/22(Sun) 05:39, Visa Hankala wrote: > On Sat, Mar 19, 2022 at 12:10:11AM +0100, Alexander Bluhm wrote: > > On Thu, Mar 17, 2022 at 07:25:27AM +, Visa Hankala wrote: > > > On Thu, Mar 17, 2022 at 12:42:13AM +0100, Alexander Bluhm wrote: > > > > I would like to use btrace to debug refernc

Re: refcount btrace

2022-03-19 Thread Visa Hankala
On Sat, Mar 19, 2022 at 12:10:11AM +0100, Alexander Bluhm wrote: > On Thu, Mar 17, 2022 at 07:25:27AM +, Visa Hankala wrote: > > On Thu, Mar 17, 2022 at 12:42:13AM +0100, Alexander Bluhm wrote: > > > I would like to use btrace to debug refernce counting. The idea > > > is to a a tracepoint for

Re: refcount btrace

2022-03-18 Thread Alexander Bluhm
On Thu, Mar 17, 2022 at 07:25:27AM +, Visa Hankala wrote: > On Thu, Mar 17, 2022 at 12:42:13AM +0100, Alexander Bluhm wrote: > > I would like to use btrace to debug refernce counting. The idea > > is to a a tracepoint for every type of refcnt we have. When it > > changes, print the actual obj

Re: refcount btrace

2022-03-18 Thread Visa Hankala
On Thu, Mar 17, 2022 at 06:16:51PM +0100, Alexander Bluhm wrote: > On Thu, Mar 17, 2022 at 07:25:27AM +, Visa Hankala wrote: > > On Thu, Mar 17, 2022 at 12:42:13AM +0100, Alexander Bluhm wrote: > > > I would like to use btrace to debug refernce counting. The idea > > > is to a a tracepoint for

Re: refcount btrace

2022-03-17 Thread Alexander Bluhm
On Thu, Mar 17, 2022 at 07:25:27AM +, Visa Hankala wrote: > On Thu, Mar 17, 2022 at 12:42:13AM +0100, Alexander Bluhm wrote: > > I would like to use btrace to debug refernce counting. The idea > > is to a a tracepoint for every type of refcnt we have. When it > > changes, print the actual obj

Re: refcount btrace

2022-03-17 Thread Visa Hankala
On Thu, Mar 17, 2022 at 12:42:13AM +0100, Alexander Bluhm wrote: > I would like to use btrace to debug refernce counting. The idea > is to a a tracepoint for every type of refcnt we have. When it > changes, print the actual object, the current counter and the change > value. > Do we want that fe

refcount btrace

2022-03-16 Thread Alexander Bluhm
Hi, I would like to use btrace to debug refernce counting. The idea is to a a tracepoint for every type of refcnt we have. When it changes, print the actual object, the current counter and the change value. #!/usr/sbin/btrace tracepoint:refcnt:inpcb{ printf("%s %x %u %+d\n", probe, arg0