llvm dev - Dec 2019 - [llvm-exegesis] Uops mode isnćt working

Hello,
I've been testing llvm-exegesis on X86. Latency and inverse_throughput modes
work fine but when I run uops I get an error:

event not found - cannot create event uops_dispatched_port:port_0
LLVM ERROR: invalid perf event 'uops_dispatched_port:port_0'

I'm running this on a i7-4790K. Am I missing something on my computer or is
this not yet fully implemented?

This also affects the llvm-exegesis lit tests and they all get skipped becuse
the configuration script determines that uops doens't work. This could be
changed so that the tests still run the modes that work (latency and
inverse_throughput in my case).

Regards
Miloš
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191217/72f10661/attachment.html>

That means the pfm counters are not specified correctly for that CPU.
You'll need to patch X86PfmCounter.td
Please do submit that patch to https://reviews.llvm.org/ afterwards!

Roman

On Tue, Dec 17, 2019 at 5:39 PM Milos Stojanovic via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> Hello,
> I've been testing llvm-exegesis on X86. Latency and inverse_throughput
modes work fine but when I run uops I get an error:
>
> event not found - cannot create event uops_dispatched_port:port_0
> LLVM ERROR: invalid perf event 'uops_dispatched_port:port_0'
>
> I'm running this on a i7-4790K. Am I missing something on my computer
or is this not yet fully implemented?
>
> This also affects the llvm-exegesis lit tests and they all get skipped
becuse the configuration script determines that uops doens't work. This
could be changed so that the tests still run the modes that work (latency and
inverse_throughput in my case).
>
> Regards
> Miloš _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Thanks Roman,

To elaborate a bit, you can tell which host CPU llvm detected by looking at
the `cpu_name` field in llvm-exegesis output for latency, something like:

cpu_name:        haswell

And check that this one has a PfmCountersBinding in X86PfmCounter.td, and
that it's correct.


On Tue, Dec 17, 2019 at 3:42 PM Roman Lebedev <lebedev.ri at gmail.com>
wrote:
> That means the pfm counters are not specified correctly for that CPU.
> You'll need to patch X86PfmCounter.td
> Please do submit that patch to https://reviews.llvm.org/ afterwards!
>
> Roman
>
> On Tue, Dec 17, 2019 at 5:39 PM Milos Stojanovic via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> >
> > Hello,
> > I've been testing llvm-exegesis on X86. Latency and
inverse_throughput
> modes work fine but when I run uops I get an error:
> >
> > event not found - cannot create event uops_dispatched_port:port_0
> > LLVM ERROR: invalid perf event 'uops_dispatched_port:port_0'
> >
> > I'm running this on a i7-4790K. Am I missing something on my
computer or
> is this not yet fully implemented?
> >
> > This also affects the llvm-exegesis lit tests and they all get skipped
> becuse the configuration script determines that uops doens't work. This
> could be changed so that the tests still run the modes that work (latency
> and inverse_throughput in my case).
> >
> > Regards
> > Miloš _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191217/b748c78e/attachment.html>