From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751562AbdJWOZh (ORCPT ); Mon, 23 Oct 2017 10:25:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:33964 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751198AbdJWOZg (ORCPT ); Mon, 23 Oct 2017 10:25:36 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 18A11218AC Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=acme@kernel.org Date: Mon, 23 Oct 2017 11:25:33 -0300 From: "acme@kernel.org" To: "Liang, Kan" Cc: Ingo Molnar , "mingo@redhat.com" , "linux-kernel@vger.kernel.org" , "peterz@infradead.org" , "jolsa@kernel.org" , "wangnan0@huawei.com" , "hekuang@huawei.com" , "namhyung@kernel.org" , "alexander.shishkin@linux.intel.com" , "Hunter, Adrian" , "ak@linux.intel.com" Subject: Re: [PATCH V3 0/6] event synthesization multithreading for perf record Message-ID: <20171023142533.GB21936@kernel.org> References: <1508529934-369393-1-git-send-email-kan.liang@intel.com> <20171023114822.ijbixdkhysinlwqv@gmail.com> <37D7C6CF3E00A74B8858931C1DB2F077537D874E@SHSMSX103.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F077537D874E@SHSMSX103.ccr.corp.intel.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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