linux-kernel - Re: [PATCH V3 0/6] event synthesization multithreading for perf record

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: <20171023142533.GB21936@kernel.org>
Date:   Mon, 23 Oct 2017 11:25:33 -0300
From:   "acme@...nel.org" <acme@...nel.org>
To:     "Liang, Kan" <kan.liang@...el.com>
Cc:     Ingo Molnar <mingo@...nel.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "peterz@...radead.org" <peterz@...radead.org>,
        "jolsa@...nel.org" <jolsa@...nel.org>,
        "wangnan0@...wei.com" <wangnan0@...wei.com>,
        "hekuang@...wei.com" <hekuang@...wei.com>,
        "namhyung@...nel.org" <namhyung@...nel.org>,
        "alexander.shishkin@...ux.intel.com" 
        <alexander.shishkin@...ux.intel.com>,
        "Hunter, Adrian" <adrian.hunter@...el.com>,
        "ak@...ux.intel.com" <ak@...ux.intel.com>
Subject: Re: [PATCH V3 0/6] event synthesization multithreading for perf
 record

Em Mon, Oct 23, 2017 at 01:43:39PM +0000, Liang, Kan escreveu:
> The plan is to do the multithreading step by step from the simplest case.
> Synthesizing stage is just a start.
 
> Only for synthesizing stage, I think the patch series should already cover all the
> 'synthesizing' steps which can do multithreading. For the rest 'synthesizing' steps,
> it only need to be done by single thread.
 
> Since there is only multithreading for 'synthesizing' step, the threads creation related
> code is event.c for now. It's better to move it to a dedicate file and make it generic for
> recording threads. I think we can do it later separately. 

Yes, and I'm happy that you plan to continue working in this area,
right? :-)

- Arnaldo