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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 70246C433F5 for ; Fri, 22 Apr 2022 21:09:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To:Subject: MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=HwJls2zioczoh1cwvij+JCwCpfmQvatox5RyTTcYPhU=; b=DkLGnSZqVzTugL I+oLQzPuaJBr2rl4iGago2N8MhF2c9uf3bkraCOwD9gmjw5pqqqxbdylWa6+fHFRUYL+RABx70y3C d5W5CTxDlbCSL7xwBcTs9x9uwzBZxOgA+d688Yqhlepx8Ia+FO5Zxn51q4A2PNaXIhZ60mm5EZgNy eWobvqcxDxi7FaAOp5RKI0OqWidDAz1iiZsm516Gql82cIKlvlzdHKQoQwbKCryOwMGD3v7fOUHNn +rcBI55GYs0cTn7CNaD6iFBluRKgDDHgCXa9VS0FwXfGbq0Gt0rJxl7iO2AIWo1iYN1/YnnxMhQEa PXdwNETltobjM7FP9zng==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ni0WE-002LO1-9x; Fri, 22 Apr 2022 21:08:46 +0000 Received: from mga12.intel.com ([192.55.52.136]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ni0WA-002LMc-C6 for linux-arm-kernel@lists.infradead.org; Fri, 22 Apr 2022 21:08:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650661722; x=1682197722; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=mnJlzMRuA2xcyrsUtKJwoToHi8lzCbaFKElkF30JqEg=; b=F5Rd0H56aSOvSzAMkNZjhAGZ4+LUYPumKEJunyCRuAY4VKDKzeSetzFM ABXfpAdSFWJJkm2Iz95le1lxgupkzCw2Q64UfmA9Tc4TKS+CZFoL1Oa3B C52lU72sTT8YuM930eDeEWWQxenId2x9MX9lYUR5o5NUoO+6t9ueb0CCO tMfkFDKUvTKavmFaN8bb0RPLC3Tv0CIkzZwT7tZF20Zl/TFqrVfppu099 ZAoJkP7th78i3NRQedWHA20arrBlYshbN6NlUqKgGNUC683ivzTSzEDd7 1HH5L0Pa0mEilFpXZQ7DKgj1Y4POfkSA3NvzpHHeV4Lz3WePXqs2y6ll2 A==; X-IronPort-AV: E=McAfee;i="6400,9594,10324"; a="244711562" X-IronPort-AV: E=Sophos;i="5.90,282,1643702400"; d="scan'208";a="244711562" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Apr 2022 14:08:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,282,1643702400"; d="scan'208";a="703707316" Received: from linux.intel.com ([10.54.29.200]) by fmsmga001.fm.intel.com with ESMTP; 22 Apr 2022 14:08:38 -0700 Received: from [10.212.135.29] (kliang2-MOBL.ccr.corp.intel.com [10.212.135.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id C9B2C580A85; Fri, 22 Apr 2022 14:08:35 -0700 (PDT) Message-ID: Date: Fri, 22 Apr 2022 17:08:34 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH v5 2/5] perf: Add SNOOP_PEER flag to perf mem data struct Content-Language: en-US To: Ali Saidi Cc: Nick.Forrington@arm.com, acme@kernel.org, alexander.shishkin@linux.intel.com, andrew.kilroy@arm.com, benh@kernel.crashing.org, german.gomez@arm.com, james.clark@arm.com, john.garry@huawei.com, jolsa@kernel.org, kjain@linux.ibm.com, leo.yan@linaro.org, lihuafei1@huawei.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, mark.rutland@arm.com, mathieu.poirier@linaro.org, mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org, will@kernel.org, Andi Kleen References: <20220422184934.29270-1-alisaidi@amazon.com> From: "Liang, Kan" In-Reply-To: <20220422184934.29270-1-alisaidi@amazon.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220422_140842_500940_6829F3A9 X-CRM114-Status: GOOD ( 14.08 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 4/22/2022 2:49 PM, Ali Saidi wrote: > On Wed, 20 Apr 2022 18:43:28, Kan Liang wrote: >> On 4/8/2022 3:53 PM, Ali Saidi wrote: >>> Add a flag to the perf mem data struct to signal that a request caused a >>> cache-to-cache transfer of a line from a peer of the requestor and >>> wasn't sourced from a lower cache level. >> >> It sounds similar to the Forward state. Why can't the >> PERF_MEM_SNOOPX_FWD be reused? > > Is there a definition of SNOOPX_FWD i can refer to? Happy to use this instead if > the semantics align between architectures. > + Andi As my understanding, the SNOOPX_FWD means the Forward state, which is a non-modified (clean) cache-to-cache copy. https://en.wikipedia.org/wiki/MESIF_protocol Thanks, Kan _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9A74BC433EF for ; Fri, 22 Apr 2022 22:17:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232631AbiDVWTw (ORCPT ); Fri, 22 Apr 2022 18:19:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52946 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231816AbiDVWRB (ORCPT ); Fri, 22 Apr 2022 18:17:01 -0400 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 394DA325835; Fri, 22 Apr 2022 14:08:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650661719; x=1682197719; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=mnJlzMRuA2xcyrsUtKJwoToHi8lzCbaFKElkF30JqEg=; b=H/Z0pzoPofmOjKpkUa8959IiuKO2bZjLxIzXQk9iyviy9e5N8EszG9QV PQNBezj7tGLczxCn0spoW4s/QmdqhafSqJLi/0EjHydksgM1tD3e44UDK vQPj3ZI9ZtZ/GW0zrY4ySw9Fk0eUdB6QmpuX+If4vU/Jc4vX/VAEREbfo PIahefXkLVChPJReIitEzLz/EH5yRSYkIDBKj+cNuQyDfg4EjoglDTswK /Vo6ns7Ow2h31eNLQAFLH9DrMpBkJlmYkTYWe15k6sUYfU8S+DvVVNpVc PE5eCsVmKYcxwGTVQqguIu0S6oyGWKNDKcRLMBfeXGlFtarg3+k5wFy6G Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10324"; a="351236493" X-IronPort-AV: E=Sophos;i="5.90,282,1643702400"; d="scan'208";a="351236493" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Apr 2022 14:08:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,282,1643702400"; d="scan'208";a="703707316" Received: from linux.intel.com ([10.54.29.200]) by fmsmga001.fm.intel.com with ESMTP; 22 Apr 2022 14:08:38 -0700 Received: from [10.212.135.29] (kliang2-MOBL.ccr.corp.intel.com [10.212.135.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id C9B2C580A85; Fri, 22 Apr 2022 14:08:35 -0700 (PDT) Message-ID: Date: Fri, 22 Apr 2022 17:08:34 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH v5 2/5] perf: Add SNOOP_PEER flag to perf mem data struct Content-Language: en-US To: Ali Saidi Cc: Nick.Forrington@arm.com, acme@kernel.org, alexander.shishkin@linux.intel.com, andrew.kilroy@arm.com, benh@kernel.crashing.org, german.gomez@arm.com, james.clark@arm.com, john.garry@huawei.com, jolsa@kernel.org, kjain@linux.ibm.com, leo.yan@linaro.org, lihuafei1@huawei.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, mark.rutland@arm.com, mathieu.poirier@linaro.org, mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org, will@kernel.org, Andi Kleen References: <20220422184934.29270-1-alisaidi@amazon.com> From: "Liang, Kan" In-Reply-To: <20220422184934.29270-1-alisaidi@amazon.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/22/2022 2:49 PM, Ali Saidi wrote: > On Wed, 20 Apr 2022 18:43:28, Kan Liang wrote: >> On 4/8/2022 3:53 PM, Ali Saidi wrote: >>> Add a flag to the perf mem data struct to signal that a request caused a >>> cache-to-cache transfer of a line from a peer of the requestor and >>> wasn't sourced from a lower cache level. >> >> It sounds similar to the Forward state. Why can't the >> PERF_MEM_SNOOPX_FWD be reused? > > Is there a definition of SNOOPX_FWD i can refer to? Happy to use this instead if > the semantics align between architectures. > + Andi As my understanding, the SNOOPX_FWD means the Forward state, which is a non-modified (clean) cache-to-cache copy. https://en.wikipedia.org/wiki/MESIF_protocol Thanks, Kan