[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v1 1/1] target/riscv: Print CPU and privledge in disas

From: Alistair Francis
Subject: Re: [PATCH v1 1/1] target/riscv: Print CPU and privledge in disas
Date: Fri, 27 Sep 2019 14:29:01 -0700

On Fri, Sep 27, 2019 at 10:53 AM Richard Henderson
<address@hidden> 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.


> r~

reply via email to

[Prev in Thread] Current Thread [Next in Thread]