Re: [PATCH v2 1/1] ftrace: do not update max buffer with no users

[Steven Rostedt]

On Thu, 13 Nov 2008, Steven Rostedt wrote:

> Right now I'm thinking my other suggestion is the best. Just allocate the 
> max_tr.buffer and get rid of the CONFIG. This solution is very small, and 
> covers all corner cases.

And for 29, we can change the code so that the max_tr buffer is only 
allocated by request of a tracer at plugin time. In which we can do tests 
if the max_tr.buffer exists in the use cases, and warn if it does not (a 
plugin needs to request a max_tr buffer before using update_max_tr).

-- Steve

--
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/