Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp712044pxu; Mon, 23 Nov 2020 02:04:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJzuiTJKD2fnky7nlAIdfplEGNIPBR4ioH4MubT8F0DQD8a7NnurYsnRwmLjZSqZljk/hREv X-Received: by 2002:a05:6402:1c0a:: with SMTP id ck10mr7484238edb.266.1606125885584; Mon, 23 Nov 2020 02:04:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606125885; cv=none; d=google.com; s=arc-20160816; b=Ib9rKIvF/T7/kdtN/kUhFfk9Ylwh+QXwNuWamm3zvSNf09GlRCKZRasG029/pvw6Gh n3KY9hmlQK1yB44pfwUUL5++UagVz75cUNTvAP9XilRNCcxL7V5ywUM2YfBwPuMKcdgN nfJAoLuM/wlphukC5C9V4tOshRN9VPCvnTccDENxK5fo7oILZPjcOirpq74tkxr4k8mW GnyFUPED+jBvMC+NYgw1lMkI5w7DJESIIi6bavHAESwoigDeDIqgfH/jKnAMaBkoVHZT /VfgtIKnhV5nprkFHPX4t7bBU7s6rTDx7QJfP8B+aVgoL50sNh4spMIM/aqnanySUn9A CMGQ== 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:from:references :cc:to:subject; bh=91Hlv4mBHI12Wf1yw5eqtErpDKv/p5DKMm7ubTRKwTc=; b=aaGltgkkuTNJCOzjFXY25uZ0+LsY82f4kh5L6DQEKIkYBuhkK1Me43PpfI2nUV6CJ+ ioUcGQJDGnaQ6mgZyrHk78TTLz6wuOV7qEv7WxzIlLxKzQGlImJkjmcqYVIB7XFAFfXt PQXvj7xzo9ueWiHsTWqxip+h3YakP69VVE7RL1Ix0OI9e51sXT7iMRWABS8UPMk2DEv0 jW8tejFyXHt1ZbepbSw0G6RtbR6yFTkit+2A6ZrE/vIZCs1rSuWsVekqJkRlkkuek38w Aswg7TMkC+w+TFTDac2yfRcEJqzr85A3G/VyLxx09tN7mTq7xai21RO/zTszu3x6oaqJ bJDQ== 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=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u22si7293841eda.496.2020.11.23.02.04.21; Mon, 23 Nov 2020 02:04:45 -0800 (PST) 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=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727692AbgKWKBo (ORCPT + 99 others); Mon, 23 Nov 2020 05:01:44 -0500 Received: from foss.arm.com ([217.140.110.172]:39600 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725843AbgKWKBo (ORCPT ); Mon, 23 Nov 2020 05:01:44 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 221CF101E; Mon, 23 Nov 2020 02:01:43 -0800 (PST) Received: from [10.57.53.209] (unknown [10.57.53.209]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9F3D83F70D; Mon, 23 Nov 2020 02:01:39 -0800 (PST) Subject: Re: [RFC 09/11] coresight: etm-perf: Disable the path before capturing the trace data To: Anshuman Khandual , linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org Cc: linux-kernel@vger.kernel.org, mathieu.poirier@linaro.org, mike.leach@linaro.org References: <1605012309-24812-1-git-send-email-anshuman.khandual@arm.com> <1605012309-24812-10-git-send-email-anshuman.khandual@arm.com> <1ad992f4-5981-6ff1-470b-875e30d3c229@arm.com> From: Suzuki K Poulose Message-ID: <9973ce74-fca5-6d68-5a0f-c53677a113d6@arm.com> Date: Mon, 23 Nov 2020 10:01:32 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/23/20 6:08 AM, Anshuman Khandual wrote: > > > On 11/12/20 2:57 PM, Suzuki K Poulose wrote: >> On 11/10/20 12:45 PM, Anshuman Khandual wrote: >>> perf handle structure needs to be shared with the TRBE IRQ handler for >>> capturing trace data and restarting the handle. There is a probability >>> of an undefined reference based crash when etm event is being stopped >>> while a TRBE IRQ also getting processed. This happens due the release >>> of perf handle via perf_aux_output_end(). This stops the sinks via the >>> link before releasing the handle, which will ensure that a simultaneous >>> TRBE IRQ could not happen. >>> >>> Signed-off-by: Anshuman Khandual >>> --- >>> This might cause problem with traditional sink devices which can be >>> operated in both sysfs and perf mode. This needs to be addressed >>> correctly. One option would be to move the update_buffer callback >>> into the respective sink devices. e.g, disable(). >>> >>>   drivers/hwtracing/coresight/coresight-etm-perf.c | 2 ++ >>>   1 file changed, 2 insertions(+) >>> >>> diff --git a/drivers/hwtracing/coresight/coresight-etm-perf.c b/drivers/hwtracing/coresight/coresight-etm-perf.c >>> index 534e205..1a37991 100644 >>> --- a/drivers/hwtracing/coresight/coresight-etm-perf.c >>> +++ b/drivers/hwtracing/coresight/coresight-etm-perf.c >>> @@ -429,7 +429,9 @@ static void etm_event_stop(struct perf_event *event, int mode) >>>             size = sink_ops(sink)->update_buffer(sink, handle, >>>                             event_data->snk_config); >>> +        coresight_disable_path(path); >>>           perf_aux_output_end(handle, size); >>> +        return; >>>       } >> >> As you mentioned, this is not ideal where another session could be triggered on >> the sink from a different ETM (not for per-CPU sink) in a different mode before >> you collect the buffer. I believe the best option is to leave the >> update_buffer() to disable_hw. This would need to pass on the "handle" to the >> disable_path. > > Passing 'handle' into coresight_ops_sink->disable() would enable pushing > updated trace data into perf aux buffer. But do you propose to drop the > update_buffer() call back completely or just move it into disable() call > back (along with PERF_EF_UPDATE mode check) for all individual sinks for > now. May be, later it can be dropped off completely. Yes, once we update the buffer from within the sink_ops->disable(), we don't need the update buffer anymore. It is pointless to have a function that is provided to the external user. > >> >> That way the races can be handled inside the sinks. Also, this aligns the >> perf mode of the sinks with that of the sysfs mode. > > Did not get that, could you please elaborate ? > In sysfs mode, we already do an action similar to "update buffer" for all the sinks. (e.g, see tmc_etr_sync_sysfs_buf() ). i.e, update the buffer before the sink is disabled. That is the same we propose above. Suzuki