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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0477CC433EF for ; Wed, 20 Oct 2021 02:34:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DF5A061167 for ; Wed, 20 Oct 2021 02:34:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229750AbhJTChL (ORCPT ); Tue, 19 Oct 2021 22:37:11 -0400 Received: from mail.kernel.org ([198.145.29.99]:40950 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229555AbhJTChK (ORCPT ); Tue, 19 Oct 2021 22:37:10 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 023B961004; Wed, 20 Oct 2021 02:34:55 +0000 (UTC) Date: Tue, 19 Oct 2021 22:34:54 -0400 From: Steven Rostedt To: Masami Hiramatsu Cc: Li Zhijian , , , , , Philip Li , kernel test robot Subject: Re: [PATCH] kselftests: ftrace: limit the executing time by reading from cached trace Message-ID: <20211019223454.5da09d74@gandalf.local.home> In-Reply-To: <20211020112027.b01762f2adcfac99e71dcf99@kernel.org> References: <20211018132616.2234853-1-lizhijian@cn.fujitsu.com> <20211018221636.47157e52@gandalf.local.home> <20211020112027.b01762f2adcfac99e71dcf99@kernel.org> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 20 Oct 2021 11:20:27 +0900 Masami Hiramatsu wrote: > Hmm, by the way, shouldn't we set this feature by default? > There are many "cat trace | grep ..." style test code in ftracetest just for > checking whether the event is recorded. At least for the ftracetest, it should > be set unless the testcase is explicitly disable it. For testing, sure. I was criticized by the BPF folks about tracing stopping when the trace file was being read. So for normal operations, it doesn't pause, because that "confuses" people (so I am told). -- Steve