From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B00F3C433F5 for ; Sun, 12 Sep 2021 20:44:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9A1CA60F43 for ; Sun, 12 Sep 2021 20:44:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236315AbhILUpd (ORCPT ); Sun, 12 Sep 2021 16:45:33 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:35040 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236172AbhILUpc (ORCPT ); Sun, 12 Sep 2021 16:45:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1631479457; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Puu8xsr4TXMGSJ8xUTdr7j+2vdNDkflNeu5gWeczPAc=; b=dUCja9hHlHRdlMCS2SkRZQ55BHvK8Mxqu6Cuo2+OXphwYinSk7LkpZO/WvQ1RjrtpxCKAL tQPi/C2hqRNGOELo2vurdOmbroEgit7PBO2nDjbNI3Gxdqz5c6+3gsZMF5okHrxpvqrhBT 4CESODZSMEhgwnIU4eBMGGmhA2Fzh9k= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-3-u-Ur3lt8PJCbWBtaOsBDuw-1; Sun, 12 Sep 2021 16:44:15 -0400 X-MC-Unique: u-Ur3lt8PJCbWBtaOsBDuw-1 Received: by mail-ed1-f72.google.com with SMTP id w18-20020aa7cb52000000b003c95870200fso3845805edt.16 for ; Sun, 12 Sep 2021 13:44:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Puu8xsr4TXMGSJ8xUTdr7j+2vdNDkflNeu5gWeczPAc=; b=NOgyc0w6jhUo254SUjKzNecvmj+DtGx3D5ETPrw3NnoUYvLH94/ABk5brSgaHQiYoy cGOGZQIEKifz0g27hchQ6QfjDf9pWJpgfZQVgUIqGcl3auoMBzEpw8s34dg8fFhzSN7q PXdGE+tcKOUTn0YZ801Qs+pbUycb6NcwHRi9Da9p8qydEFtYDthX6rfVQFzsWdAx8lRZ l2usCceNt63WjbeN05+RDMGW83YjZsCSiYTvyp9KEo+b4FIgTu80BoB+acq+5TZ6aZEm 0W968LoqFTwEGy42R/F79JG/afUbGYYviGIUx4bigRvswd5PkseKnTgVpxUgq0iHTsuz EyNA== X-Gm-Message-State: AOAM533wLtfPuZfzaIqyS0HODDWZBytAGWqBpZ2LvAntU+rKRJ0/2eLP g3YK4GrHtsNrL36L/AbUAwvQfE14T29BeQTkL9U0eK3/gmDUSc+asVw6YNzbiZcTM6BkNDFWOmm zK/UY+ZdCi5+V6/XYXV1vUgsz X-Received: by 2002:a05:6402:274d:: with SMTP id z13mr9638987edd.214.1631479454747; Sun, 12 Sep 2021 13:44:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyJkBjzmqIS4dVLu7mh48t4h9naVVffW0yNn5iIcdMmHGGybVTLYvHctHJjd1tFQg5rgvKy5Q== X-Received: by 2002:a05:6402:274d:: with SMTP id z13mr9638974edd.214.1631479454609; Sun, 12 Sep 2021 13:44:14 -0700 (PDT) Received: from krava ([83.240.60.52]) by smtp.gmail.com with ESMTPSA id ay3sm2475616ejb.0.2021.09.12.13.44.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 12 Sep 2021 13:44:14 -0700 (PDT) Date: Sun, 12 Sep 2021 22:44:12 +0200 From: Jiri Olsa To: Alexey Bayduraev Cc: Arnaldo Carvalho de Melo , Namhyung Kim , Alexander Shishkin , Peter Zijlstra , Ingo Molnar , linux-kernel , Andi Kleen , Adrian Hunter , Alexander Antonov , Alexei Budankov , Riccardo Mancini Subject: Re: [PATCH v11 00/24] Introduce threaded trace streaming for basic perf record operation Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 17, 2021 at 11:23:03AM +0300, Alexey Bayduraev wrote: SNIP > > Alexey Bayduraev (24): > perf record: Introduce thread affinity and mmap masks > tools lib: Introduce fdarray duplicate function > perf record: Introduce thread specific data array > perf record: Introduce function to propagate control commands > perf record: Introduce thread local variable > perf record: Stop threads in the end of trace streaming > perf record: Start threads in the beginning of trace streaming > perf record: Introduce data file at mmap buffer object > perf record: Introduce bytes written stats to support --max-size > option > perf record: Introduce data transferred and compressed stats > perf record: Init data file at mmap buffer object > perf record: Introduce --threads command line option > perf record: Extend --threads command line option > perf record: Implement compatibility checks > perf report: Output non-zero offset for decompressed records > perf report: Output data file name in raw trace dump following patches: > perf session: Move reader structure to the top > perf session: Introduce reader_state in reader object > perf session: Introduce reader objects in session object > perf session: Introduce decompressor into trace reader object > perf session: Move init into reader__init function > perf session: Move map/unmap into reader__mmap function > perf session: Load single file for analysis up to here are changing the core of processing perf.data files, I think they should be submitted in separate patchset first and some tests for that would be great jirka