Re: [RFC][PATCH 2/2] tracing: Do not return EINVAL in snapshot when not allocated

2013-03-06 Thread Hiraku Toyooka
(03/06/2013 10:49 PM), Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > To use the tracing snapshot feature, writing a '1' into the snapshot > file causes the snapshot buffer to be allocated if it has not already > been allocated and dose a 'swap' with the main buffer, so that the >

[RFC][PATCH 2/2] tracing: Do not return EINVAL in snapshot when not allocated

2013-03-06 Thread Steven Rostedt
From: "Steven Rostedt (Red Hat)" To use the tracing snapshot feature, writing a '1' into the snapshot file causes the snapshot buffer to be allocated if it has not already been allocated and dose a 'swap' with the main buffer, so that the snapshot now contains what was in the main buffer, and

[RFC][PATCH 2/2] tracing: Do not return EINVAL in snapshot when not allocated

2013-03-06 Thread Steven Rostedt
From: Steven Rostedt (Red Hat) srost...@redhat.com To use the tracing snapshot feature, writing a '1' into the snapshot file causes the snapshot buffer to be allocated if it has not already been allocated and dose a 'swap' with the main buffer, so that the snapshot now contains what was in the

Re: [RFC][PATCH 2/2] tracing: Do not return EINVAL in snapshot when not allocated

2013-03-06 Thread Hiraku Toyooka
(03/06/2013 10:49 PM), Steven Rostedt wrote: From: Steven Rostedt (Red Hat)srost...@redhat.com To use the tracing snapshot feature, writing a '1' into the snapshot file causes the snapshot buffer to be allocated if it has not already been allocated and dose a 'swap' with the main buffer, so