[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221118103302.7ea12016@gandalf.local.home>
Date: Fri, 18 Nov 2022 10:33:02 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ian Rogers <irogers@...gle.com>,
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>,
Masami Hiramatsu <mhiramat@...nel.org>,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
Steven Rostedt <rostedt@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Linux Trace Devel <linux-trace-devel@...r.kernel.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH v1 1/2] perf build: Require libtraceevent from the
system
On Fri, 18 Nov 2022 12:02:38 -0300
Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
> yeah, this probably should work like with other libraries, don't stop
> the build, just don't build features that depend on libtraceevent,
> warning the user that features foo, bar and baz won't be available.
>
> For people working with just hardware, software, cache events, no
> problem.
How are software events parsed?
-- Steve
Powered by blists - more mailing lists