Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp1607664pxb; Sat, 23 Apr 2022 11:23:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxeDH1DEkjQ2LOQkAGu6Eu2/SPPoiMJjYCYUZQwGFYl4G/F8UnYtiK21cYSkLG63It0a4yf X-Received: by 2002:a17:906:a05a:b0:6ef:a44d:2f46 with SMTP id bg26-20020a170906a05a00b006efa44d2f46mr9485410ejb.192.1650738206735; Sat, 23 Apr 2022 11:23:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650738206; cv=none; d=google.com; s=arc-20160816; b=xX4Fuc922eTtOtrV1jF5Y3yZlv10P4TcfszDTqkctKL3GvlMK3fnXzQTLI9dPhzO4T sSf8zSLvX0qHPbuopND0tj2wbSHSBKnrdtiG+ne9sT4cV8/VQdDhvXspSHQO/tIUFRZf 5U/cVr6Kd3WM7NrUADcfyj42GcUPe6xPsNlZJ4OwyVUrr9N+3/K+sdQrIMK+N1PYuM4a uWe3DtGkd52/9gUo1ZoWzaucMYYAlxYp3wjmbgOI3TvOxT+Tq1a2blGwhc29vxHpUZJy NbrVQx11qsUzI13MNOaVHtaSItxXhoi9yOFYTYgFMwiMq84OplGTucR8glaRdNJxq0+q uQlw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=cEmVTFwEAjm6PtJgvD3jDbZomQIitbx7/0qufvUA3iY=; b=HNndt8ciFq+HpAVdWaZKQ7iL60Sucw+Va3Wx4B9UIwq58kSut2J1rNmzCXcfgkZthR 81ZZrbOGQqN+SiVCvdjnp4WVpxHXmrvIUxWCjsR6/ituGPUX/9+SO2cuIQNNZ1zLQkWZ sSz8WGYnTyhuxxwWin9iyCvHY3Fsh/t9BZlJB+U7JsyOjf9JokaqigHSWeroCDWak7hl XoT0U3/IEuAMgy90PrE8AKfMr2V3k9FbkHnyECC8ci90K3QPty0oDv76jHsZKSYcYRMX E1ag9QJ0tzb+nEwU31QiWvTMuzVoFW6JpXiye9HVxMc7RzHtZ5S3ddFB83AStcBZMAKh X7uw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=l7GWD2fn; 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=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bu22-20020a170906a15600b006df76385dbbsi9644272ejb.603.2022.04.23.11.23.02; Sat, 23 Apr 2022 11:23:26 -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=@intel.com header.s=Intel header.b=l7GWD2fn; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234862AbiDWM4f (ORCPT + 99 others); Sat, 23 Apr 2022 08:56:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35020 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231196AbiDWM4c (ORCPT ); Sat, 23 Apr 2022 08:56:32 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 90E6B261; Sat, 23 Apr 2022 05:53:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650718415; x=1682254415; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=OBOX3LfVl7XRiJUyCXwa9+7Ll3XU3H92WTMvH//IWQI=; b=l7GWD2fnnI50zocnpRhEfFmFafQ/ut9XNgxakJkLaH0ArIUl9JXcYxys VRoVKwSNSrL3LWkxIOsj9BL8pzfsZaueuOIg/wit1C9cRE/PbCwc6dnaj VJZpd06k06CimVcsYAPFXYPCsznZ1LTHZDd5wWjmv27j/frxGxiv58cx5 sGMqZEW+aXbsz0bIpW6e0VUIfMXHKlL8OrhvGljwrgl8O3LSWcIxvQk4D suy5h7qLz8uzKS40UKbohcGN1vD6M0lXGZlSYlh6VTXeF2X4Ts+GSWWDt 9SbPtBIv7cHH9i3qVTwPpBQQZKj1mWEICBSj1JzHxVFnP238lgMtY0pAM Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10324"; a="244818048" X-IronPort-AV: E=Sophos;i="5.90,284,1643702400"; d="scan'208";a="244818048" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Apr 2022 05:53:35 -0700 X-IronPort-AV: E=Sophos;i="5.90,284,1643702400"; d="scan'208";a="556858428" Received: from vietqle-mobl1.amr.corp.intel.com (HELO [10.212.229.58]) ([10.212.229.58]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Apr 2022 05:53:33 -0700 Message-ID: <8e09af67-a416-4ead-b406-6c8b998de344@linux.intel.com> Date: Sat, 23 Apr 2022 05:53:28 -0700 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: Leo Yan , Ali Saidi Cc: kan.liang@linux.intel.com, 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, 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 References: <20220422212249.22463-1-alisaidi@amazon.com> <20220423063805.GA559531@leoy-ThinkPad-X240s> From: Andi Kleen In-Reply-To: <20220423063805.GA559531@leoy-ThinkPad-X240s> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_NONE,URIBL_BLOCKED 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 > Except SNOOPX_FWD means a no modified cache snooping, it also means it's > a cache conherency from *remote* socket. This is quite different from we > define SNOOPX_PEER, which only snoop from peer CPU or clusters. > > If no objection, I prefer we could keep the new snoop type SNOOPX_PEER, > this would be easier for us to distinguish the semantics and support the > statistics for SNOOPX_FWD and SNOOPX_PEER separately. > > I overlooked the flag SNOOPX_FWD, thanks a lot for Kan's reminding. Yes seems better to keep using a separate flag if they don't exactly match. It's not that we're short on flags anyways. -Andi