On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
Yes. Please see:
On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
Yes. Please see:
On 2016/3/30 10:38, Wangnan (F) wrote:
On 2016/3/30 10:28, Wangnan (F) wrote:
On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new
On 2016/3/30 10:38, Wangnan (F) wrote:
On 2016/3/30 10:28, Wangnan (F) wrote:
On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new
On 2016/3/30 10:28, Wangnan (F) wrote:
On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
int perf_output_begin(struct
On 2016/3/30 10:28, Wangnan (F) wrote:
On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
int perf_output_begin(struct
On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
int perf_output_begin(struct perf_output_handle *handle,
On 2016/3/29 22:04, Peter Zijlstra wrote:
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
int perf_output_begin(struct perf_output_handle *handle,
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
> int perf_output_begin(struct perf_output_handle *handle,
> struct perf_event *event, unsigned int
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
Could you maybe write a perf/tests thingy for this so that _some_
userspace exists that exercises this new code?
> int perf_output_begin(struct perf_output_handle *handle,
> struct perf_event *event, unsigned int
On 2016/3/29 12:59, Alexei Starovoitov wrote:
On Tue, Mar 29, 2016 at 10:01:24AM +0800, Wangnan (F) wrote:
On 2016/3/28 14:41, Wang Nan wrote:
[SNIP]
To prevent this problem, we need to find a way to ensure the ring buffer
is stable during reading. ioctl(PERF_EVENT_IOC_PAUSE_OUTPUT) is
On 2016/3/29 12:59, Alexei Starovoitov wrote:
On Tue, Mar 29, 2016 at 10:01:24AM +0800, Wangnan (F) wrote:
On 2016/3/28 14:41, Wang Nan wrote:
[SNIP]
To prevent this problem, we need to find a way to ensure the ring buffer
is stable during reading. ioctl(PERF_EVENT_IOC_PAUSE_OUTPUT) is
On Tue, Mar 29, 2016 at 10:01:24AM +0800, Wangnan (F) wrote:
>
>
> On 2016/3/28 14:41, Wang Nan wrote:
>
> [SNIP]
>
> >
> >To prevent this problem, we need to find a way to ensure the ring buffer
> >is stable during reading. ioctl(PERF_EVENT_IOC_PAUSE_OUTPUT) is
> >suggested because its
On Tue, Mar 29, 2016 at 10:01:24AM +0800, Wangnan (F) wrote:
>
>
> On 2016/3/28 14:41, Wang Nan wrote:
>
> [SNIP]
>
> >
> >To prevent this problem, we need to find a way to ensure the ring buffer
> >is stable during reading. ioctl(PERF_EVENT_IOC_PAUSE_OUTPUT) is
> >suggested because its
On 2016/3/28 14:41, Wang Nan wrote:
[SNIP]
To prevent this problem, we need to find a way to ensure the ring buffer
is stable during reading. ioctl(PERF_EVENT_IOC_PAUSE_OUTPUT) is
suggested because its overhead is lower than
ioctl(PERF_EVENT_IOC_ENABLE).
Add comment:
By carefully
On 2016/3/28 14:41, Wang Nan wrote:
[SNIP]
To prevent this problem, we need to find a way to ensure the ring buffer
is stable during reading. ioctl(PERF_EVENT_IOC_PAUSE_OUTPUT) is
suggested because its overhead is lower than
ioctl(PERF_EVENT_IOC_ENABLE).
Add comment:
By carefully
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
> This patch introduces 'write_backward' bit to perf_event_attr, which
> controls the direction of a ring buffer. After set, the corresponding
> ring buffer is written from end to beginning. This feature is design to
> support reading from
On Mon, Mar 28, 2016 at 06:41:32AM +, Wang Nan wrote:
> This patch introduces 'write_backward' bit to perf_event_attr, which
> controls the direction of a ring buffer. After set, the corresponding
> ring buffer is written from end to beginning. This feature is design to
> support reading from
This patch introduces 'write_backward' bit to perf_event_attr, which
controls the direction of a ring buffer. After set, the corresponding
ring buffer is written from end to beginning. This feature is design to
support reading from overwritable ring buffer.
Ring buffer can be created by mapping a
This patch introduces 'write_backward' bit to perf_event_attr, which
controls the direction of a ring buffer. After set, the corresponding
ring buffer is written from end to beginning. This feature is design to
support reading from overwritable ring buffer.
Ring buffer can be created by mapping a
20 matches
Mail list logo
