[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fUWbe-owCHsjQfOuTyt8kEzM_M_4GqS_rqKwL9VY3tJOQ@mail.gmail.com>
Date: Fri, 2 Feb 2024 18:49:05 -0800
From: Ian Rogers <irogers@...gle.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>, Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>, Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
linux-perf-users@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>, Stephane Eranian <eranian@...gle.com>,
Masami Hiramatsu <mhiramat@...nel.org>, linux-toolchains@...r.kernel.org,
linux-trace-devel@...r.kernel.org
Subject: Re: [PATCH 07/14] perf annotate-data: Add update_insn_state()
On Fri, Feb 2, 2024 at 2:05 PM Namhyung Kim <namhyung@...nel.org> wrote:
>
> The update_insn_state() function is to update the type state table after
> processing each instruction. For now, it handles MOV (on x86) insn
> to transfer type info from the source location to the target.
>
> The location can be a register or a stack slot. Check carefully when
> memory reference happens and fetch the type correctly. It basically
> ignores write to a memory since it doesn't change the type info. One
> exception is writes to (new) stack slots for register spilling.
Just an aside, it seems a shame objdump can't do this tracking for us.
objdump already augments its output with symbol and relocation data.
Thanks,
Ian
Powered by blists - more mailing lists