Here is a patch that will track live engines and expose them via debugfs.
This will show if there are stale engines and their refcounts, also to
determine if there are any engine slab leaks.
This is just for debug purposes. Needs tweaking if this needs to be
part of the core patch (ifdefs, etc).
Hi -
On Thu, Jan 29, 2009 at 04:34:46PM +0100, Frédéric Weisbecker wrote:
> 2009/1/29 Ingo Molnar :
> [...]
> >> > sure - how do the minimal bits/callbacks look like which enable syscall
> >> > tracing?
> I know you are talking about the only necessary bits from utrace to
> have the syscalls trac
2009/1/29 Ingo Molnar :
>
> * Frédéric Weisbecker wrote:
>
>> 2009/1/29 Ingo Molnar :
>> >>
>> >> Several people talked me about utrace and gave some examples about it in
>> >> this discussion. The Api is very convenient to fetch syscall numbers,
>> >> arguments and return values. And the hooks ar
2009/1/29 Ingo Molnar :
>
> * Frédéric Weisbecker wrote:
>
>> 2009/1/29 Ingo Molnar :
>> >>
>> >> Several people talked me about utrace and gave some examples about it in
>> >> this discussion. The Api is very convenient to fetch syscall numbers,
>> >> arguments and return values. And the hooks ar
2009/1/29 Ingo Molnar :
>>
>> Several people talked me about utrace and gave some examples about it in
>> this discussion. The Api is very convenient to fetch syscall numbers,
>> arguments and return values. And the hooks are done in the generic core
>> code, so it is arch independent.
>>
>> The on
* Frédéric Weisbecker wrote:
> 2009/1/29 Ingo Molnar :
> >>
> >> Several people talked me about utrace and gave some examples about it in
> >> this discussion. The Api is very convenient to fetch syscall numbers,
> >> arguments and return values. And the hooks are done in the generic core
> >> c
2009/1/29 Frédéric Weisbecker :
> 2009/1/29 Ingo Molnar :
>>>
>>> Several people talked me about utrace and gave some examples about it in
>>> this discussion. The Api is very convenient to fetch syscall numbers,
>>> arguments and return values. And the hooks are done in the generic core
>>> code,
* Frédéric Weisbecker wrote:
> 2009/1/29 Ingo Molnar :
> >
> > * Frederic Weisbecker wrote:
> >
> >> On Tue, Jan 27, 2009 at 11:43:03PM +0100, Frederic Weisbecker wrote:
> >> > On Tue, Jan 27, 2009 at 12:08:04PM -0800, Kok, Auke wrote:
> >> > >
> >> > > This tracer monitors regular file open()
2009/1/29 Ingo Molnar :
>
> * Frederic Weisbecker wrote:
>
>> On Tue, Jan 27, 2009 at 11:43:03PM +0100, Frederic Weisbecker wrote:
>> > On Tue, Jan 27, 2009 at 12:08:04PM -0800, Kok, Auke wrote:
>> > >
>> > > This tracer monitors regular file open() syscalls. This is a fast
>> > > and low-overhead
