Hi Pawel,
On 09/12/2014 07:48 AM, Pawel Moll wrote:
> This patch adds a PERF_COUNT_SW_MARKER event type, which
> can be requested by user and a PERF_EVENT_IOC_MARKER
> ioctl command which will inject an event of said type into
> the perf buffer. The ioctl can take a zero-terminated
> string argument, similar to tracing_marker in ftrace,
> which will be kept in the "raw" field of the sample.
>
> The main use case for this is synchronisation of
> performance data generated in user space with the perf
> stream coming from the kernel. For example, the marker
> can be inserted by a JIT engine after it generated
> portion of the code, but before the code is executed
> for the first time, allowing the post-processor to
> pick the correct debugging information. Other example
> is a system profiling tool taking data from other
> sources than just perf, which generates a marker
> at the beginning at at the end of the session
> (also possibly periodically during the session) to
> synchronise kernel timestamps with clock values
> obtained in userspace (gtod or raw_monotonic).
> @@ -5960,6 +5965,44 @@ static struct pmu perf_swevent = {
> .event_idx = perf_swevent_event_idx,
> };
>
> +static int perf_sw_event_marker(struct perf_event *event, char __user *arg)
> +{
> + struct perf_sample_data data;
> + struct pt_regs *regs = current_pt_regs();
> + struct perf_raw_record raw = { 0, };
> +
> + if (!static_key_false(&perf_swevent_enabled[PERF_COUNT_SW_MARKER]))
> + return 0;
> +
> + perf_sample_data_init(&data, 0, 0);
> +
> + if (arg) {
> + long len = strnlen_user(arg, PAGE_SIZE);
Just to ask the dumb questions in case the answers I've come up with are
wrong: What is PAGE_SIZE on an arm64 kernel? How does userspace know?
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
