Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1457694pxb; Mon, 11 Oct 2021 06:29:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw0w9GWLsY2cf0sZCCwgkYtrL7WT/7UTeh6nFUGAe2PhFC6ndoSvmDCq6x+G1A3g0kHR7C2 X-Received: by 2002:aa7:dbcf:: with SMTP id v15mr41591179edt.243.1633958997820; Mon, 11 Oct 2021 06:29:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633958997; cv=none; d=google.com; s=arc-20160816; b=HTbBoD1L8HCYktf91Bem89VVMi1a8T4qfKHJx4ErJld1OtVfW9u3qqFtFoZfQ5rS/a bMQqhX2vsGq4oR3BgHPXCtEkaXsOO6DGS1q38wyp/2hfbYs+jJqcLU4bvz3tki6IDLT9 P1Yb6j4mNcnbUeieKpIkdAAMAbajiVAplU4z0TrGc2zfp+7sY4u0YlKfU4k900NpKSjz drh0wBMJnxyMagp5SfeVc4Hx40IDoEZ4fLyp4ey0G88G8OFo6pkqmOlwvdAzZ050Lcjm VnCOpwlLpYBzrsjn7DLgbGYJJjvH+iD8MjEW7SdcEb2xJPz3u4uchfM/3CVHJitlXjXy mIHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :references:cc:to:from:subject; bh=IOPHFGeRrV6eSZ5u6Blum0tQ1F8+J8J7VilwU8pCToU=; b=ozqBCLmsNeqfW+rnWqZwC0BMcj9I1FXI6geTMa5fLoWXtMNZAG+IfwatW2HHCMeMqY X4PE73v/qUD5/oDxps9yM1QKYeO9SzR+lU7CjiMeOT8uCkqV9BvriTAMTvzLqSO5HQW7 QsLRIMcfLEIxLZXh5zAL1kSBg9ZbsRj9vR59WYjCeht3HfKftxVNRt50oG16ci9z67xL y/quOfPfowrYRYvcI0vTRd7NhRunyozt6TjkTx2wNKJw+X0x/kApxFe4uCW8Gw84pppB B3d3x1w09dUQHQQSX9nHXzdDiakk8Q6DADQrFHCu4QB7ZeT3v1Y4xbKasB6cIR1wFpNp 21Zg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v8si15204800ede.567.2021.10.11.06.29.32; Mon, 11 Oct 2021 06:29:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235623AbhJKJzg (ORCPT + 99 others); Mon, 11 Oct 2021 05:55:36 -0400 Received: from mga14.intel.com ([192.55.52.115]:11562 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235522AbhJKJzf (ORCPT ); Mon, 11 Oct 2021 05:55:35 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10133"; a="227127722" X-IronPort-AV: E=Sophos;i="5.85,364,1624345200"; d="scan'208";a="227127722" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Oct 2021 02:53:35 -0700 X-IronPort-AV: E=Sophos;i="5.85,364,1624345200"; d="scan'208";a="490404734" Received: from abaydur-mobl1.ccr.corp.intel.com (HELO [10.249.229.105]) ([10.249.229.105]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Oct 2021 02:53:32 -0700 Subject: Re: [PATCH v3 6/8] perf session: Move event read code to separate function From: "Bayduraev, Alexey V" To: Jiri Olsa 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 References: <6ab47325fa261deca4ca55ecacf1ca2437abcd78.1633596227.git.alexey.v.bayduraev@linux.intel.com> <5e5ecfcd-57f1-1a06-4ed6-6a1e6983d1f8@linux.intel.com> Organization: Intel Corporation Message-ID: Date: Mon, 11 Oct 2021 12:53:30 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <5e5ecfcd-57f1-1a06-4ed6-6a1e6983d1f8@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11.10.2021 12:08, Bayduraev, Alexey V wrote: > > On 08.10.2021 17:38, Jiri Olsa wrote: >> On Fri, Oct 08, 2021 at 11:42:18AM +0300, Bayduraev, Alexey V wrote: >>> >>> >>> On 08.10.2021 10:33, Jiri Olsa wrote: >>>> On Thu, Oct 07, 2021 at 01:25:41PM +0300, Alexey Bayduraev wrote: >>>> >>>> SNIP >>>> >>>>> static int >>>>> -reader__process_events(struct reader *rd, struct perf_session *session, >>>>> - struct ui_progress *prog) >>>>> +reader__read_event(struct reader *rd, struct perf_session *session, >>>>> + struct ui_progress *prog) > > SNIP > >>>> >>>> active_decomp should be set/unset within reader__process_events, >>>> not just for single event read, right? >>> >>> No, it should be set before perf_session__process_event/process_decomp_events >>> and unset after these calls. So active_decomp setting/unsetting is moved in >>> this patch to the reader__read_event function. This is necessary for multiple >>> trace reader because it could call reader__read_event in round-robin manner. >> >> hum, is that code already in? I can't see this happening in current code > > Probably I don't understand the question. In [PATCH v3 2/8] I introduced > active_decomp pointer in perf_session. It is initialized by a pointer to the > decompressor object in perf_session. In reader__process_events it is set to > the reader decompressor object. And it is reset to the session decompressor > object at exit. In this case we do not need to reset it after each > perf_session__process_event because this code reads events in loop with > constant reader object. Maybe setting of active_decomp should be at the > entrance to the reader__process_events, not before reader__process_events, > in [PATCH v3 2/8]. All this code is new. We set active_decomp for perf_session__process_event (rd->process() in our case) and for __perf_session__process_decomp_events, active_decomp is not necessary for other parts of reader__process_events. Regards, Alexey > > In this patch I separates single event reading and moves setting/resetting > of active_decomp before/after perf_session__process_event because this is > necessary for multiple trace reader. > > Regards, > Alexey > >> >> jirka >> >>> >>> Regards, >>> Alexey >>> >>>> >>>> jirka >>>> >>>>> return err; >>>>> } >>>>> >>>>> -- >>>>> 2.19.0 >>>>> >>>> >>> >>