[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220517125404.GD153558@leoy-ThinkPad-X240s>
Date: Tue, 17 May 2022 20:54:04 +0800
From: Leo Yan <leo.yan@...aro.org>
To: James Clark <james.clark@....com>
Cc: linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
broonie@...nel.org, acme@...nel.org, german.gomez@....com,
mathieu.poirier@...aro.org, john.garry@...wei.com,
Will Deacon <will@...nel.org>,
Mike Leach <mike.leach@...aro.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 3/4] perf tools: arm64: Decouple Libunwind register
names from Perf
On Tue, May 17, 2022 at 11:20:04AM +0100, James Clark wrote:
> Dwarf register numbers and real register numbers on aarch64 are
> equivalent. Remove the references to the register names from
> Libunwind so that new registers are supported without having to
> add build time feature checks for each new register.
>
> The unwinder won't ask for a register that it doesn't know about
> and Perf will already report an error for an unknown or unrecorded
> register in the perf_reg_value() function so extra validation
> isn't needed.
>
> After this change the new VG register can be read by libunwind.
>
> Signed-off-by: James Clark <james.clark@....com>
Looks good to me:
Reviewed-by: Leo Yan <leo.yan@...aro.org>
Powered by blists - more mailing lists