[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110831085718.GB13884@glandium.org>
Date: Wed, 31 Aug 2011 10:57:18 +0200
From: Mike Hommey <mh@...ndium.org>
To: linux-kernel@...r.kernel.org
Subject: Problem with perf hardware counters grouping
Hi,
I'm having two different problems with perf hardware counters with a
group leader:
- perf_event_open()ing more than 3 makes all of them always return a
value of 0;
- perf_event_open()ing more than 4 fails with ENOSPC.
This doesn't happen with software counters.
The source at the end of this message exhibits the problem:
$ gcc -o test test.c
$ strace -eperf_event_open ./test
perf_event_open(0x7fff7aeb3e00, 0, 0xffffffff, 0xffffffff, 0) = 3
perf_event_open(0x7fff7aeb3e00, 0, 0xffffffff, 0x3, 0) = 4
perf_event_open(0x7fff7aeb3e00, 0, 0xffffffff, 0x3, 0) = 5
Count: 10857
$ gcc -o test test.c -DN=4
$ strace -eperf_event_open ./test
perf_event_open(0x7fff13a16bd0, 0, 0xffffffff, 0xffffffff, 0) = 3
perf_event_open(0x7fff13a16bd0, 0, 0xffffffff, 0x3, 0) = 4
perf_event_open(0x7fff13a16bd0, 0, 0xffffffff, 0x3, 0) = 5
perf_event_open(0x7fff13a16bd0, 0, 0xffffffff, 0x3, 0) = 6
Count: 0
$ gcc -o test test.c -DN=5
$ strace -eperf_event_open ./test
perf_event_open(0x7fff64700c60, 0, 0xffffffff, 0xffffffff, 0) = 3
perf_event_open(0x7fff64700c60, 0, 0xffffffff, 0x3, 0) = 4
perf_event_open(0x7fff64700c60, 0, 0xffffffff, 0x3, 0) = 5
perf_event_open(0x7fff64700c60, 0, 0xffffffff, 0x3, 0) = 6
perf_event_open(0x7fff64700c60, 0, 0xffffffff, 0x3, 0) = -1 ENOSPC (No
space left on device)
Count: 0
I think the latter is due to the hard limit of 4 for the number of slots
for hardware breakpoints. No idea about the former.
Mike
----------------8<-------------------
#define _GNU_SOURCE 1
#include <stdint.h>
#include <stdio.h>
#include <string.h>
#include <unistd.h>
#include <sys/ioctl.h>
#include <sys/syscall.h>
#include <linux/perf_event.h>
int perf_event_open(struct perf_event_attr *hw_event_uptr,
pid_t pid, int cpu, int group_fd, unsigned long flags) {
return syscall(__NR_perf_event_open, hw_event_uptr, pid, cpu, group_fd,flags);
}
int group_leader = -1;
int _perf_event_open(uint64_t config) {
struct perf_event_attr pe;
int fd;
memset(&pe,0,sizeof(struct perf_event_attr));
pe.type = PERF_TYPE_HARDWARE;
pe.size = sizeof(struct perf_event_attr);
pe.config = config;
if (group_leader == -1)
pe.disabled = 1;
pe.mmap = 1;
pe.comm = 1;
fd = perf_event_open(&pe, 0, -1, group_leader, 0);
if (fd >= 0 && group_leader == -1)
group_leader = fd;
return fd;
}
int main(int argc, char** argv) {
uint64_t c;
int fd = _perf_event_open(PERF_COUNT_HW_CPU_CYCLES);
_perf_event_open(PERF_COUNT_HW_INSTRUCTIONS);
_perf_event_open(PERF_COUNT_HW_CACHE_REFERENCES);
#if N > 3
_perf_event_open(PERF_COUNT_HW_CACHE_MISSES);
#endif
#if N > 4
_perf_event_open(PERF_COUNT_HW_BRANCH_INSTRUCTIONS);
#endif
ioctl(fd, PERF_EVENT_IOC_ENABLE, 0);
ioctl(fd, PERF_EVENT_IOC_DISABLE,0);
read(fd, &c, sizeof(c));
printf("Count: %ld\n",c);
return 0;
}
--
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