Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3457689pxu; Tue, 15 Dec 2020 07:29:22 -0800 (PST) X-Google-Smtp-Source: ABdhPJwDLqILtpx6pMn7UfykAMkGsvBbopjI6tMhSE6PZ4TOPw7lIu9kLcGZn8KMjatKAbyuARaI X-Received: by 2002:a17:906:3c11:: with SMTP id h17mr26743072ejg.20.1608046161896; Tue, 15 Dec 2020 07:29:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608046161; cv=none; d=google.com; s=arc-20160816; b=a9kaZc+khF+0r27Zqz9S+zWol2GVfyiDuOArzTc6gxrVlQY6W8LKK38dSE6QcqUn4/ b6bYu4ARpygd8U2dUwToVmTd8/JiQcNKrJrr1n4qWWi2Hp6g4NdB5DlV+qjxvcL64RXH Gk3GaRioCfJLN0W5EQdy3CAt/zotXRwITKUKcyDTnvC4qTjRlV3qyj6F1Bp9c7LRaDGc BgTRvVqP8hLVuoUUgWKI43kg2sbyPivFzY7Hgt2w8ie5KKwCdkS/VmRT3/01yPndl/T8 ZwtaWJ+uSLifi+Zg1a32GB9NKrxCmHsB9ZreoJAfPpRXrEGXWUFC8HLtXYCz7l9WSVG2 I1kg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=9favKO92bZy+hUVuBjcpdkLduaBsVNLOb6uBu9wK6Jk=; b=0DoVReCLCkuw+4pJbjQ7/Hs0MSL8aDGVIjKcwBlGv6khm4CXIagSKYbizc6xLyc3tz LiKgXupWbih5zmoVyaOg/d7g8QOWCdQ3O3CY5DlM+SaNjEuTnR4gqaMY6A0cdBLoDTMJ GL+kSDy+mEtUgWc3eg1KbdWN3VPbW0kl4fuXuTZ+W30rlXxkVb91iZHo9csB1+dxJKYV hO0HG8FggTk890Hvb8XRxMFl91Ynjip3i2oPFEcw//a0efsdKhnhqlAZ/J68F4h09TEn N32igj1Jzcf2O5vKW7HmZi6r68BNyg3DdMDmx26n16Gx8Gn3kIoPwZJbWLyO40UcdyNM T/Ug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="TrN1T/6I"; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c24si1024848edj.459.2020.12.15.07.28.56; Tue, 15 Dec 2020 07:29:21 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="TrN1T/6I"; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729584AbgLOPZz (ORCPT + 99 others); Tue, 15 Dec 2020 10:25:55 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:52432 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726844AbgLOPZz (ORCPT ); Tue, 15 Dec 2020 10:25:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1608045868; 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=9favKO92bZy+hUVuBjcpdkLduaBsVNLOb6uBu9wK6Jk=; b=TrN1T/6IOGpVceBXrU4chcxL3UppLJLR19Uk9K5nji8t5XseTso4zy9v0bhj8aRdKXv8UH AFkCmoft28lFLa+5WdW4CrM6uD8RBMmG0j6QrS/3uXUYD6GvyPpbttPbaYU13ZADyx8ejS u7oooqgfbE243v4twr+SQLqp12OTQpA= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-28-RgEdB_V4NG6BENukGEQ2vA-1; Tue, 15 Dec 2020 10:24:26 -0500 X-MC-Unique: RgEdB_V4NG6BENukGEQ2vA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BCAA315720; Tue, 15 Dec 2020 15:24:24 +0000 (UTC) Received: from krava (ovpn-113-169.ams2.redhat.com [10.36.113.169]) by smtp.corp.redhat.com (Postfix) with SMTP id 9D7041E5; Tue, 15 Dec 2020 15:24:21 +0000 (UTC) Date: Tue, 15 Dec 2020 16:24:20 +0100 From: Jiri Olsa To: Arnaldo Carvalho de Melo Cc: Jiri Olsa , Namhyung Kim , lkml , Peter Zijlstra , Ingo Molnar , Mark Rutland , Alexander Shishkin , Michael Petlan , Ian Rogers , Stephane Eranian , Alexei Budankov Subject: Re: [PATCH 2/3] perf tools: Allow to enable/disable events via control file Message-ID: <20201215152420.GC658008@krava> References: <20201210204330.233864-1-jolsa@kernel.org> <20201210204330.233864-3-jolsa@kernel.org> <20201215151413.GE252952@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201215151413.GE252952@kernel.org> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 15, 2020 at 12:14:13PM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Dec 10, 2020 at 09:43:29PM +0100, Jiri Olsa escreveu: > > Adding new control events to enable/disable specific event. > > The interface string for control file are: > > > > 'enable-' > > 'disable-' > > Wwy do we have "enable-" as the "tag" for this? the whole 'enable-' is prefix for command that enables specific event following '-' starts the event name > > Also is it possible to use "enable sched:*" and have that match what is > in the evlist and enable (or disable, if using "disable sched:*") what > matches? yep, that should be possible to add > > This second suggestion can be done on top of this, i.e. as an > enhancement, but mixing up the command (enable, disable) with its > arguments looks strange. the '-' determines that there's event name following, pure 'enable' switches on everything jirka