Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp162663pxa; Wed, 26 Aug 2020 07:27:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwfdUdppUVNbIw1SdZTs09rLuubS/+KTVnqRckpgDPmIBMGtAs4q6fcbheR05GtukFFt2bE X-Received: by 2002:a05:6402:b9c:: with SMTP id cf28mr5001755edb.274.1598452076721; Wed, 26 Aug 2020 07:27:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598452076; cv=none; d=google.com; s=arc-20160816; b=DUH/pym67JxpyP/Ir9RCRCZsu2cOAAqg/afTpJJZ69nkjfEdQ9DBuN5IISriP2G993 tBoeeDnXMoQCA5wuh4v14sQIgkgz3EgCr8kik72P80l7PtGfBiJPEht0tX2o6W/ueRUK +BHdNLsfmqwgEi3SCEdtA4L0sNnub0Fu5LW5AIuL3toLw13cZMPgQJrj/Cz9m7bDgopZ +Wqxfkr6Or4L8yuUZn+hGF9i5JjW5Nezv8ceQO/f9xQcmj62Y6iszT/dYz0IbyQwPGH7 ay4RTz4qrKRihVkWJE6EenBqkyjj1bASifkI1ZNEvM/xaL2agGeT0gdJVBDrSrA8GEQ0 hrjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=FskuWt/52uAVEc7YfEFHlRkngN4vr7P72425Jpneec0=; b=v+elCFV1XAHEyp2kRFg4jTfVNcsnnkKdq9RDtlyB+2OzmQVdtBRRFwPFCbBoQ0WsR8 qbRxqQOeA22C4Ghjv+2OcxrPaw/RQCwDqU7F8QEddbWRGnrx+jlU9skLrSHJmUL+qMYZ Cr7cFpsR9b4PkwB58cl7tJDdDaRzh+7OJeGnn1L7s1dWu6dAuKVT1LYtxHrvGW869QNj kHElMgR9HYYnHsGbHiGQCL5KoHYGgDucerpmU/MselSYbBeC0RwENhHwiTnW/hqPs6lg SKcNoCtOF9Dd4VI+A/YloDPlC/sF0c1Dx9K38JSpXHWFGDKPWvE9ixgS90defsvZa/O9 1wrA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dr22si2096693ejc.35.2020.08.26.07.27.33; Wed, 26 Aug 2020 07:27:56 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729012AbgHZLju (ORCPT + 99 others); Wed, 26 Aug 2020 07:39:50 -0400 Received: from foss.arm.com ([217.140.110.172]:44570 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729034AbgHZLed (ORCPT ); Wed, 26 Aug 2020 07:34:33 -0400 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 8205A1FB; Wed, 26 Aug 2020 04:24:48 -0700 (PDT) Received: from C02TD0UTHF1T.local (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 678023F71F; Wed, 26 Aug 2020 04:24:46 -0700 (PDT) Date: Wed, 26 Aug 2020 12:24:35 +0100 From: Mark Rutland To: Al Grant Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, ak@linux.intel.com, acme@redhat.com, Peter Zijlstra , Ingo Molnar , Alexander Shishkin , Jiri Olsa , Namhyung Kim Subject: Re: [PATCH] perf: correct SNOOPX field offset Message-ID: <20200826112435.GA43491@C02TD0UTHF1T.local> References: <9974f2d0-bf7f-518e-d9f7-4520e5ff1bb0@foss.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9974f2d0-bf7f-518e-d9f7-4520e5ff1bb0@foss.arm.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, [ adding the kernel-side perf maintainers ] Please note that scripts/get_maintainer.pl can help to find relevant maintainers. On Mon, Aug 24, 2020 at 10:28:34AM +0100, Al Grant wrote: > perf_event.h has macros that define the field offsets in the > data_src bitmask in perf records. The SNOOPX and REMOTE offsets > were both 37. These are distinct fields, and the bitfield layout > in perf_mem_data_src confirms that SNOOPX should be at offset 38. > > From: Al Grant This needs a Signed-off-by line from you. See: https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin The patch itself looks right to me, so provided you add an S-o-B line: Acked-by: Mark Rutland Mark > > include/uapi/linux/perf_event.h | 2 +- > tools/include/uapi/linux/perf_event.h | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/include/uapi/linux/perf_event.h > b/include/uapi/linux/perf_event.h > index 077e7ee69e3d..3e5dcdd48a49 100644 > --- a/include/uapi/linux/perf_event.h > +++ b/include/uapi/linux/perf_event.h > @@ -1196,7 +1196,7 @@ union perf_mem_data_src { > > #define PERF_MEM_SNOOPX_FWD 0x01 /* forward */ > /* 1 free */ > -#define PERF_MEM_SNOOPX_SHIFT 37 > +#define PERF_MEM_SNOOPX_SHIFT 38 > > /* locked instruction */ > #define PERF_MEM_LOCK_NA 0x01 /* not available */ > diff --git a/tools/include/uapi/linux/perf_event.h > b/tools/include/uapi/linux/perf_event.h > index 077e7ee69e3d..3e5dcdd48a49 100644 > --- a/tools/include/uapi/linux/perf_event.h > +++ b/tools/include/uapi/linux/perf_event.h > @@ -1196,7 +1196,7 @@ union perf_mem_data_src { > > #define PERF_MEM_SNOOPX_FWD 0x01 /* forward */ > /* 1 free */ > -#define PERF_MEM_SNOOPX_SHIFT 37 > +#define PERF_MEM_SNOOPX_SHIFT 38 > > /* locked instruction */ > #define PERF_MEM_LOCK_NA 0x01 /* not available */