qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nazerke Turtayeva <nturtayeva@ucsb.edu>
To: qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: What riscv tracing tools do you recommend and how are they accurate for measurements?
Date: Wed, 28 Feb 2024 20:27:23 -0800	[thread overview]
Message-ID: <CAHY78Bq6AdcZPuFRbdShDPvgmgcoB+PKLWqPuOoX3vdJ-NsZ+A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Hi everyone,

Recently, I was planning to measure the performance of my application of
interest for potential RISC-V hardware. Hence, I started my simulations
from Spike to analyze dynamic instruction traces and instruction count,
nevertheless given it does not support multithreading, I started using Qemu
to test my app too. However, it seems like I cannot rely on timing results
of Qemu for comparing different implementations. Accordingly, given I am
brand new to the Qemu ecosystem, I was wondering whether I am missing some
important mainstream instrumentation and tracing tools that I can use for
performance evaluation of my target app in other ways. Particularly, I want
to understand implications of adding custom ISA instructions to the
performance of my application.

In this regard, do you have any recommendations on where I can look?

Thanks,
Best wishes

-- 
Nazerke Turtayeva
Graduate Student
Electrical and Computer Engineering, Computer Science
Email: nturtayeva@ucsb.edu
*UC Santa Barbara*

[-- Attachment #2: Type: text/html, Size: 2523 bytes --]

             reply	other threads:[~2024-02-29 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  4:27 Nazerke Turtayeva [this message]
2024-03-06  4:44 ` What riscv tracing tools do you recommend and how are they accurate for measurements? Alistair Francis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHY78Bq6AdcZPuFRbdShDPvgmgcoB+PKLWqPuOoX3vdJ-NsZ+A@mail.gmail.com \
    --to=nturtayeva@ucsb.edu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).