[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173039472904.1704862.15241557863386801558.b4-ty@kernel.org>
Date: Thu, 31 Oct 2024 10:12:09 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
"Liang, Kan" <kan.liang@...ux.intel.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, linux-riscv@...ts.infradead.org,
Björn Töpel <bjorn@...nel.org>
Cc: Björn Töpel <bjorn@...osinc.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
Anup Patel <anup@...infault.org>, Atish Patra <atishp@...osinc.com>
Subject: Re: [PATCH] perf, riscv: Wire up perf trace support for RISC-V
On Thu, 24 Oct 2024 12:03:51 -0700, Björn Töpel wrote:
> RISC-V does not currently support perf trace, since the system call
> table is not generated.
>
> Perform the copy/paste exercise, wiring up RISC-V system call table
> generation.
>
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists