[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1410530335.16936.60.camel@hornet>
Date: Fri, 12 Sep 2014 14:58:55 +0100
From: Pawel Moll <pawel.moll@....com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Christopher Covington <cov@...eaurora.org>,
Richard Cochran <richardcochran@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Paul Mackerras <paulus@...ba.org>,
John Stultz <john.stultz@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>
Subject: Re: [RFC 2/2] perf: Marker software event and ioctl
On Fri, 2014-09-12 at 14:49 +0100, Arnaldo Carvalho de Melo wrote:
> Perhaps both? I.e. an u64 followed from a string, if the u64 is zero,
> then there is a string right after it?
How would this look like in userspace? Something like this?
8<----
struct perf_event_marker {
uint64_t value;
char *string;
} arg;
arg.value = 0x1234;
/* or */
arg.value = 0;
arg.string = "abcd";
ioctl(fd, PERF_EVENT_IOC_MARKER, &arg)
8<----
If so, maybe it would simpler just to go for classic size/data
structure?
8<-----
struct perf_event_marker {
uint32_t size;
void *data;
}
8<-----
This would directly map into struct perf_raw_record...
Paweł
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists