Re: [PATCH] tracing: Fix the outmost stupidity of tracing_off()

[Thomas Gleixner]

Steven,

On Fri, 15 Jun 2012, Thomas Gleixner wrote:
>  void tracing_off(void)
>  {
>  	if (global_trace.buffer)
> -		ring_buffer_record_on(global_trace.buffer);
> +		ring_buffer_record_off(global_trace.buffer);

this is the gazillionst time that I wasted valuable time relying on
the not so extraordinary expectation that the kernel tracer stays
functional at least in the most basic ways.

I'm really tired of wasting hours and days just because you are unable
to keep your stuff straight and functional.

I avoided to make public fuzz about that so far, but my patience is
exhausted now.

You know yourself how many times I ranted to you on IRC or in private
conversations, but you just keep on to bask in your egocentric
mastering the uber complexity treat.

Your self description (https://lwn.net/Articles/500388/):

 Complexity is my Sun, and I am the planet that orbits around it.

is pretty accurate.

You can orbit around whatever you want and as long as you want, just
please do that on your own playground and not on the expense of
others.

I always held up to ftrace, but the repeating experience of
disfunctionality caused by your refusal to put your priorites straight
is just too annoying.

It's not the first time, that tracing_off() or other stuff I'm
depending on has been broken and caused me exhaustive loss of time.

I know that I'm not the average user of tracing, but that's not an
excuse for pushing out crap over and over again.

I'm tired of it and to be honest, I'm going to spend some quality time
on evaluating LLTNG. If it can do what I need then I switch over and
see whether it can hold up to the basic expectations of a primary
user. AFAICT from previous experience it can do that, and if Matthieu
is willing and able to cooperate on integrating with perf, then I
happily kick you off into your self chosen complexity orbit forever.

Sadly,

	Thomas

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/