Messages in this thread | | | Date | Fri, 12 Nov 2010 11:39:20 +0100 | Subject | Re: [PATCH 2/3] perf: Add support for extra parameters for raw events | From | Stephane Eranian <> |
| |
On Thu, Nov 11, 2010 at 8:59 PM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote: > On Thu, 2010-11-11 at 20:49 +0100, Andi Kleen wrote: >> > I think it would have parsed OK, but it is a confusing syntax to >> > look at. I should point out that there are also the u,k,h modifiers >> > which can be specified, even on raw events, so the full syntax looks >> > something like: >> > >> > -e rXXXX[+YYYY][:u|:k|:h] >> >> Ok I can fix the help text for that. > > If we're frobbing it in the existing config qword, do we still need > special syntax? > I don't think you need special syntax. You can simply come up with the 64-bit raw hex value. corey recently added a small utility to do this via libpfm4: perf stat -e `evt2raw unhalted_core_cycles:u` ....
With libpfm4, I'll expose the event as a normal one. Therefore you would do:
perf stat -e OFFCORE_RESPONSE_0:PF_DATA_RD:REMOTE_DRAM ...
This will encode to: attr.config = 0x01b7ULL | ((1ULL << 4) | (1ULL << 13)) << 32
> Also, I think we can use the same mechanism to program the > PEBS-load-latency MSR, right? > Yes, we could hardcode the latency the same way. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |