Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp493102rwb; Wed, 5 Oct 2022 23:31:44 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4IaJfmJFSEAYgC6p6qENRahuxOwc+xcGNzGLqz74RUrMynt0hTwJvjzrR03MzCsdk9gVrD X-Received: by 2002:a05:6a00:2446:b0:52b:e9a8:cb14 with SMTP id d6-20020a056a00244600b0052be9a8cb14mr3287718pfj.32.1665037903894; Wed, 05 Oct 2022 23:31:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665037903; cv=none; d=google.com; s=arc-20160816; b=JhIz/ob5i/davmN3ZFj5huItRUDjTgwq2r35KQaxvX8Men6QaLHVZIL/er5teGiRSO z17tIltJSb6uKJiKN+FuaYIKMl5Rm5TKHsCGSPzANbMEdewPtSTf5KGXrOhjod/uvKBg 3/KP6hi5p0L4l4Fz3pQUyCPkVfGlkiN82JXIQ/46r8IzFbjerKhCASS+WJXDVlQt+yJN QeZrauwL/h8UGGoV8+LU8Lo9CEtQPrSMklloYlUg6LaSeTeYOeZ3I9PN2T22+dlLmLQ9 fAOk5QCuNl8kfD6XNjbH5gRyhkOF0/9qTYnYoR5SkJugDVPB9GBaYcnteZQx4atChtjy WLfQ== 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=2XrgiIqxfYqeYgpiX2f0Tk/oR7IHm7sRfeEC295sJaA=; b=QowuYJRWsvEErrv0aeHNDJW9V+4Y+TAj90GmToEeLxyd6VBYFdEApuGPOAnXSfdZtI aRr/qSfZvONMmMkxpEe+X7Etv+E/dIFXsi5qUXXaJKv9dGWi6LKKmc3GDvjmGiAD+bzG vuVa0CfXGU3RJPQmtrEZn5QGXbar7GjG5JXwMfXhr0h1PN3fTLPlDj0BzCAiBM93KUJT i14/E9yjOceTyJC0wHhRgh7oizcWdNp4p+FR3nKlaAJVVEb0TKmLBhAiFB0//sA9QYQr bC/QsGXv8aktDDqUA87T3WntxAQVc9tZixyjx3IXr1is08/g2NkNRilt0bmWYvNhQGg6 yicA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=mSp6cxf6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d1-20020a170903230100b0016c4fc2de44si19166353plh.456.2022.10.05.23.31.27; Wed, 05 Oct 2022 23:31:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=mSp6cxf6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230209AbiJFGCE (ORCPT + 99 others); Thu, 6 Oct 2022 02:02:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49432 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229555AbiJFGCC (ORCPT ); Thu, 6 Oct 2022 02:02:02 -0400 Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 41F9762911 for ; Wed, 5 Oct 2022 23:02:01 -0700 (PDT) Received: by mail-pf1-x42e.google.com with SMTP id i3so1125736pfk.9 for ; Wed, 05 Oct 2022 23:02:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=2XrgiIqxfYqeYgpiX2f0Tk/oR7IHm7sRfeEC295sJaA=; b=mSp6cxf6NE0+p5rZyZdvKHmAxBMiREVppMlFoZL89AyaB8ynlQrw6/S5Gw0RDmksR+ ww/LJh7kbYjyYNTu8eIpaZ1VPoncaP5x0gFXTFJKWM4Zsj+xGE9P22KvOrtceZiEtdBG hvFB6VXjCKB4DOxfiqgL41mBeyagCEqqz5IpRjhw97CH6bRE+8Za0UhCNXcUkEQMPkcV GWkyLTqGH+Gjik8aPHxxBfUjCbICLaErV4mpkpp447XJ4P5JrQoCWuCf5Dta+1SZ4+HA 83WKmsQL8LS5cmviGopTTi6I/PGgDbyjWhFLDMM/0F0VTTh4Ei4MUncGXU41rdzgRha1 IIAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=2XrgiIqxfYqeYgpiX2f0Tk/oR7IHm7sRfeEC295sJaA=; b=Oc2+kC9g7EqtXZOkivNZoESlKZ4Wx4TvTuHKdNK1rnmLwMb8DIeaIDRT2kfV6wUXbW XIq6dAZujoV5TRnWyDhRVeoC4itYVINnJUctU8xSjVlEdPklUH9TbAxfOZQeb6plzywA Nygpdqk2u0QX/iAVi8zXgcKX6T/IzCUHaFN9X3H2PmoDFXgPXrQJVV+gvC7tPzXzNPgU MeINt/dlAZXcqNEf2LNLkxEW7egrYzuNDcZT1tNH+gy6MUfcgDjGBPibqRkC5buHVsDP fbflFnfDF1SCnTizfwTI4kk54zkeYMrOilN5ekKZazKfIrlEG7+QjPPOAveVMypABgEl 5NSA== X-Gm-Message-State: ACrzQf2x5FyjfoYxG3HIdFgC3+KWSdfMOaAa1OZKS4UQrY1Van9+mwHo ru3VYAinJMlrJEAEVqTDOdizBxjaZMqOozIh X-Received: by 2002:a63:86c2:0:b0:45a:2045:471 with SMTP id x185-20020a6386c2000000b0045a20450471mr2990557pgd.447.1665036120636; Wed, 05 Oct 2022 23:02:00 -0700 (PDT) Received: from leoy-yangtze.lan (45.78.17.119.16clouds.com. [45.78.17.119]) by smtp.gmail.com with ESMTPSA id w2-20020a623002000000b00538056de6ecsm11938015pfw.52.2022.10.05.23.01.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 05 Oct 2022 23:01:59 -0700 (PDT) Date: Thu, 6 Oct 2022 14:01:54 +0800 From: Leo Yan To: Namhyung Kim Cc: Arnaldo Carvalho de Melo , Jiri Olsa , Ingo Molnar , Peter Zijlstra , LKML , Ian Rogers , Adrian Hunter , linux-perf-users@vger.kernel.org, Kan Liang , Ravi Bangoria Subject: Re: [PATCH] perf mem: Fix -C option behavior for perf mem record Message-ID: References: <20221004200211.1444521-1-namhyung@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221004200211.1444521-1-namhyung@kernel.org> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 04, 2022 at 01:02:11PM -0700, Namhyung Kim wrote: > The -C/--cpu option was maily for report but it also affected record as > it ate the option. So users needed to use "--" after perf mem record to > pass the info to the perf record properly. > > Check if this option is set for record, and pass it to the actual perf > record. > > Before) > $ sudo perf --debug perf-event-open mem record -C 0 2>&1 | grep -a sys_perf_event_open > ... > sys_perf_event_open: pid -1 cpu 0 group_fd -1 flags 0x8 = 4 > sys_perf_event_open: pid -1 cpu 1 group_fd -1 flags 0x8 = 5 > sys_perf_event_open: pid -1 cpu 2 group_fd -1 flags 0x8 = 6 > sys_perf_event_open: pid -1 cpu 3 group_fd -1 flags 0x8 = 7 > sys_perf_event_open: pid -1 cpu 0 group_fd -1 flags 0x8 = 8 > sys_perf_event_open: pid -1 cpu 1 group_fd -1 flags 0x8 = 9 > sys_perf_event_open: pid -1 cpu 2 group_fd -1 flags 0x8 = 10 > sys_perf_event_open: pid -1 cpu 3 group_fd -1 flags 0x8 = 11 > ... > > After) > $ sudo perf --debug perf-event-open mem record -C 0 2>&1 | grep -a sys_perf_event_open > ... > sys_perf_event_open: pid -1 cpu 0 group_fd -1 flags 0x8 = 4 > sys_perf_event_open: pid -1 cpu 0 group_fd -1 flags 0x8 = 5 > sys_perf_event_open: pid -1 cpu 0 group_fd -1 flags 0x8 = 6 > sys_perf_event_open: pid -1 cpu 0 group_fd -1 flags 0x8 = 7 > > Cc: Leo Yan > Reported-by: Ravi Bangoria > Signed-off-by: Namhyung Kim The change LGTM: Reviewed-by: Leo Yan Tested-by: Leo Yan