How can I get dynamic instruction count? about riscv-isa-sim HOT 11 CLOSED

The proxy kernel can do this for you with its -s flag (try spike pk -s
hello)

On Mon, Mar 23, 2015 at 1:23 AM, Channoh Kim [email protected]
wrote:

Hi,

I want to get dynamic instruction count via Spike, but the disassembly
codes from -d option (i.e., spike -d pk hello and :r) is weird.

—
Reply to this email directly or view it on GitHub
#14.

from riscv-isa-sim.

Good. Thanks!

from riscv-isa-sim.

Is there an updated and current way to get dynamic instruction count? This no longer works.

from riscv-isa-sim.

Is there a way to get a more detailed breakdown of types of instructions executed?
And if not, would there be an interest in me implementing this feature and upstreaming it?

from riscv-isa-sim.

Hi,
We are working on a Python tool which takes as input the log file generated from spike using the -l option and outputs different statistics based on the log file.

You can check out the implemented features and ongoing features at - https://bitbucket.org/anmol07/spikepost

from riscv-isa-sim.

Can that one differentiate between instructions in the user program vs instructions from pk?
My other concern is that for most benchmarks the log files quickly become huge (>30GB)

from riscv-isa-sim.

Currently we are processing log files using pure Python. These suffice for the common riscv benchmarks. I am looking at a numpy/spark backend for faster analytics.

As to the other part of your question, I am not sure if I understand correctly. Could you please elaborate a bit about what you mean instructions generated by pk?

from riscv-isa-sim.

What I mean is when you execute a program with spike pk <prog>, you aren't just running your program, you are also running pk. So not every instruction that is a part of the log is a part of the program.
But as I type this out I realized pk is only necessary for me because of the printf statements.

from riscv-isa-sim.

from riscv-isa-sim.

We already have a feature of selecting an address range where you want the profiling to happen. It can be extended to incorporate address blocks that have to be skipped. Will add that as an enhancement in the repo.

from riscv-isa-sim.

I think the problem with using a full log file is that for complicated programs, it becomes really huge. for the program I was trying to benchmark, it produced a 300GB log file and then crashed because it run out of HDD space. I could move it onto a larger system but at that point, parsing will also be ridiculous. It's possible I did something wrong.
I'm working on an instruction count modification on my fork and will submit a PR if I can get anything reasonable.

from riscv-isa-sim.