Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2811002pxb; Sat, 30 Jan 2021 15:53:24 -0800 (PST) X-Google-Smtp-Source: ABdhPJxqVLoHetiQCD6+y0mfTHuo/RS0/gXs6qA3UgZt2kUOnWerxOSg8RUpQ12cWVP2Q2WKIuH8 X-Received: by 2002:a17:906:94ce:: with SMTP id d14mr10914139ejy.121.1612050804325; Sat, 30 Jan 2021 15:53:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612050804; cv=none; d=google.com; s=arc-20160816; b=k3Spc7l4yTl9Uh3LDnxmVh0LY0CDaIrcJm9BDcMXoabxyZop4XoB8Dkdoc1LglmS3Q YxzT/7PAA5uiMjyCWdFvptjC87D/7ll+w1YI2d0Vkwu5PSwaSUDPHdunXByv2YPE8bzi rsuOgqS+F18C9GWmYbjYz1uA16GKDSOxQM+0SbLtxTGUKX1wMNTYEqH4prgS6j6cCad6 OhgZ2+c1f3SJFSSRnBJgFtii+0je4GbVU7UA27BjNBZ00ZnzfzvICoCVEdvt5bbfpT6d yCTnlkhIw8jU1xNcZ7XRMFElo6QqngmrcOGCx6AZDRsqocoZFKMCNy93buzRWgNlIOEc MEAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=ijIpGADLAI4AO9q+CAPENjtE1ahUGoI6ZHwZAGCAXJE=; b=tozOJ29s1FjU05IpIBWd74FXLEKUnfbNLr5cHyClMemN+mFxaOK1kdRE/9oHH+r38i PQzjhHMRYBJJuFAxGVC/jPIpCmrcNUv4d8VltHbnH8dVVanF/sOApmdjOlqbZScIUVIA oKY2eZm3rXB7q2wavxuyTX9qAZMDgvQSr6m7O8Fz67xrTit+v13hvQwnzKbnoEeoeMUa 7I9U0w9f/P+tfXTEk5em3BlEY/M3ZFslyO6ClPOTZ/kRQOFWWK0RU+gdxLEpJFoPfYL9 +zkCYgmQC8DSEQICNuP3bl030m+izcYmcM8LWfnxN3rO6/oLv67schowi5kJ+TGBsvkP OYqw== 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d5si7634965edq.173.2021.01.30.15.52.59; Sat, 30 Jan 2021 15:53:24 -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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232617AbhA3XvX convert rfc822-to-8bit (ORCPT + 99 others); Sat, 30 Jan 2021 18:51:23 -0500 Received: from us-smtp-delivery-44.mimecast.com ([205.139.111.44]:43881 "EHLO us-smtp-delivery-44.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232531AbhA3XuW (ORCPT ); Sat, 30 Jan 2021 18:50:22 -0500 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-232-vxHeuP0xM1Ox5VFFZlxQiA-1; Sat, 30 Jan 2021 18:49:03 -0500 X-MC-Unique: vxHeuP0xM1Ox5VFFZlxQiA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E054F10054FF; Sat, 30 Jan 2021 23:49:00 +0000 (UTC) Received: from krava.redhat.com (unknown [10.40.192.30]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2855760DA0; Sat, 30 Jan 2021 23:48:56 +0000 (UTC) From: Jiri Olsa To: Arnaldo Carvalho de Melo Cc: lkml , Peter Zijlstra , Ingo Molnar , Mark Rutland , Namhyung Kim , Alexander Shishkin , Michael Petlan , Ian Rogers , Stephane Eranian , Alexei Budankov Subject: [PATCHv3 00/24] perf tools: Add daemon command Date: Sun, 31 Jan 2021 00:48:32 +0100 Message-Id: <20210130234856.271282-1-jolsa@kernel.org> In-Reply-To: <20210129134855.195810-1-jolsa@redhat.com> References: <20210129134855.195810-1-jolsa@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=jolsa@kernel.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: kernel.org Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset=WINDOWS-1252 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org hi, we were asked for possibility to be able run record sessions on background. This patchset adds support to configure and run record sessions on background via new 'perf daemon' command. Please check below the example on usage. Available also here: git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git perf/daemon v3 changes: - several patches merged - add comments to daemon locking [Namhyung] - split patch 1 to multiple patches [Namhyung] - add missing allocation checks [Namhyung] - add comments for session state transitions [Namhyung] - add base directory check [Namhyung] - use ',' as default for -x option [Namhyung] - remove extra close before dup2 [Namhyung] - add new reconfig test for empty config - add --base option v2 changes: - switch options to sub-commands [Namhyung] - use signalfd to track on sessions [Alexei] - use stop command to stop sessions [Alexei] - couple minor fixes [Alexei] - more detailed changelogs [Arnaldo] - added tests thanks, jirka --- Jiri Olsa (24): perf daemon: Add daemon command perf daemon: Add config option perf daemon: Add base option perf daemon: Add server socket support perf daemon: Add client socket support perf daemon: Add config file support perf daemon: Add config file change check perf daemon: Add background support perf daemon: Add signalfd support perf daemon: Add list command perf daemon: Add signal command perf daemon: Add stop command perf daemon: Allow only one daemon over base directory perf daemon: Set control fifo for session perf daemon: Add ping command perf daemon: Use control to stop session perf daemon: Add up time for daemon/session list perf daemon: Add man page for perf-daemon perf tests: Add daemon list command test perf tests: Add daemon reconfig test perf tests: Add daemon stop command test perf tests: Add daemon signal command test perf tests: Add daemon ping command test perf tests: Add daemon lock test tools/perf/Build | 1 + tools/perf/Documentation/perf-config.txt | 14 ++ tools/perf/Documentation/perf-daemon.txt | 187 +++++++++++++++++++++ tools/perf/builtin-daemon.c | 1448 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ tools/perf/builtin.h | 1 + tools/perf/command-list.txt | 1 + tools/perf/perf.c | 1 + tools/perf/tests/shell/daemon.sh | 475 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 8 files changed, 2128 insertions(+) create mode 100644 tools/perf/Documentation/perf-daemon.txt create mode 100644 tools/perf/builtin-daemon.c create mode 100755 tools/perf/tests/shell/daemon.sh --- Example with 2 record sessions: # cat ~/.perfconfig [daemon] base=/opt/perfdata [session-cycles] run = -m 10M -e cycles --overwrite --switch-output -a [session-sched] run = -m 20M -e sched:* --overwrite --switch-output -a Starting the daemon: # perf daemon start Check sessions: # perf daemon [603349:daemon] base: /opt/perfdata [603350:cycles] perf record -m 10M -e cycles --overwrite --switch-output -a [603351:sched] perf record -m 20M -e sched:* --overwrite --switch-output -a First line is daemon process info with configured daemon base. Check sessions with more info: # perf daemon -v [603349:daemon] base: /opt/perfdata output: /opt/perfdata/output lock: /opt/perfdata/lock up: 1 minutes [603350:cycles] perf record -m 10M -e cycles --overwrite --switch-output -a base: /opt/perfdata/session-cycles output: /opt/perfdata/session-cycles/output control: /opt/perfdata/session-cycles/control ack: /opt/perfdata/session-cycles/ack up: 1 minutes [603351:sched] perf record -m 20M -e sched:* --overwrite --switch-output -a base: /opt/perfdata/session-sched output: /opt/perfdata/session-sched/output control: /opt/perfdata/session-sched/control ack: /opt/perfdata/session-sched/ack up: 1 minutes The 'base' path is daemon/session base. The 'lock' file is daemon's lock file guarding that no other daemon is running on top of the base. The 'output' file is perf record output for specific session. The 'control' and 'ack' files are perf control files. The 'up' number shows minutes daemon/session is running. Make sure control session is online: # perf daemon ping OK cycles OK sched Send USR2 signal to session 'cycles' to generate perf.data file: # perf daemon signal --session cycles signal 12 sent to session 'cycles [603452]' # tail -2 /opt/perfdata/session-cycles/output [ perf record: dump data: Woken up 1 times ] [ perf record: Dump perf.data.2020123017013149 ] Send USR2 signal to all sessions: # perf daemon signal signal 12 sent to session 'cycles [603452]' signal 12 sent to session 'sched [603453]' # tail -2 /opt/perfdata/session-cycles/output [ perf record: dump data: Woken up 1 times ] [ perf record: Dump perf.data.2020123017024689 ] # tail -2 /opt/perfdata/session-sched/output [ perf record: dump data: Woken up 1 times ] [ perf record: Dump perf.data.2020123017024713 ] Stop daemon: # perf daemon stop