From: Alistair Francis <alistair23@gmail.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
Palmer Dabbelt <palmer@sifive.com>,
Alistair Francis <alistair.francis@wdc.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v1 1/1] target/riscv: Print CPU and privledge in disas
Date: Fri, 27 Sep 2019 14:29:01 -0700 [thread overview]
Message-ID: <CAKmqyKP86E9aJBKjrGzG7=A7dLDsfhFBdnDjc6pZjtECpticAg@mail.gmail.com> (raw)
In-Reply-To: <8248daee-d5d0-0576-ee89-bd1400ddf947@linaro.org>
On Fri, Sep 27, 2019 at 10:53 AM Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> On 9/27/19 10:23 AM, Alistair Francis wrote:
> >> I'm curious about the motivation here.
> >>
> >> In particular, what difference does it make what cpu the TB is generated for?
> >> It would seem like the more relevant place to look for this is with -d cpu or
> >> -d exec where the TB is actually executed, which could well be multiple cpus.
> >
> > The main reason is that the sifive_u machine now has two RISC-V
> > clusters so it's useful to see what is happening on each CPU. -d cpu
> > and -d exec are much more difficult to comprehend so aren't always as
> > useful.
>
> Hmm. I wonder if it might be time to find a way to be able to optionally split
> the qemu_log output on a per-cpu basis. It wouldn't necessarily always be
> helpful, because we'd still have the case of a given TB being translated by one
> cpu and executed on another, but it could make some things easier to follow.
A per cpu-cluster basis would be useful.
Until then though this patch helps.
Alistair
>
>
> r~
prev parent reply other threads:[~2019-09-27 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 0:45 [PATCH v1 1/1] target/riscv: Print CPU and privledge in disas Alistair Francis
2019-09-27 3:07 ` Bin Meng
2019-09-27 9:09 ` Philippe Mathieu-Daudé
2019-09-27 17:03 ` Alistair Francis
2019-09-27 17:17 ` Richard Henderson
2019-09-27 17:23 ` Alistair Francis
2019-09-27 17:53 ` Richard Henderson
2019-09-27 21:29 ` Alistair Francis [this message]
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='CAKmqyKP86E9aJBKjrGzG7=A7dLDsfhFBdnDjc6pZjtECpticAg@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.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).