linux-kernel - Re: [PATCH v2 2/6] perf evsel: Introduce an observed performance device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAM9d7cikD68d0iAiFQ2A6J5tDqM-jphqQUjLAV0vQZqH7Mi37A@mail.gmail.com>
Date:   Wed, 6 Jan 2021 17:44:21 +0900
From:   Namhyung Kim <namhyung@...nel.org>
To:     Alexander Antonov <alexander.antonov@...ux.intel.com>
Cc:     Arnaldo Carvalho de Melo <acme@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Jiri Olsa <jolsa@...hat.com>, Andi Kleen <ak@...ux.intel.com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Mark Rutland <mark.rutland@....com>,
        Ian Rogers <irogers@...gle.com>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v2 2/6] perf evsel: Introduce an observed performance device

Hi,

On Wed, Dec 23, 2020 at 10:03 PM Alexander Antonov
<alexander.antonov@...ux.intel.com> wrote:
>
> Adding evsel::perf_device void pointer.
>
> For performance monitoring purposes, an evsel can have a related device.
> These changes allow to attribute, for example, I/O performance metrics
> to IIO stack.
>
> Signed-off-by: Alexander Antonov <alexander.antonov@...ux.intel.com>
> ---
>  tools/perf/util/evsel.h | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/util/evsel.h b/tools/perf/util/evsel.h
> index 79a860d8e3ee..c346920f477a 100644
> --- a/tools/perf/util/evsel.h
> +++ b/tools/perf/util/evsel.h
> @@ -127,6 +127,7 @@ struct evsel {
>          * See also evsel__has_callchain().
>          */
>         __u64                   synth_sample_type;
> +       void                    *perf_device;

Maybe we can use the existing 'priv' field.

Thanks,
Namhyung


>  };
>
>  struct perf_missing_features {
> --
> 2.19.1
>