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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (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 9FBD4C27C6E for ; Fri, 14 Jun 2024 15:53:40 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 42CD410E107; Fri, 14 Jun 2024 15:53:40 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="EXHBsfwJ"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) by gabe.freedesktop.org (Postfix) with ESMTPS id DE7F110EDC2 for ; Fri, 14 Jun 2024 15:53:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1718380418; x=1749916418; h=date:message-id:from:to:cc:subject:in-reply-to: references:mime-version; bh=V5sMHLZTmAR21ClCLuZWtboDp/BjZGIOQxlY7rI6uIE=; b=EXHBsfwJ3ZswGPw9z8zkEg9taf6f9LVBNa9vJ7lKi34yzszTgxFpU4DZ HS5JX0cDJ5j+2SU0yVbaDhgN8031Q+s6MBDMyO/xRPxEIowm9Hd4X2OHR dLqhX9JIXADu/i2X2/DOQTuRbp/RIZkvUEHKod1S55L7iQavN6GTQMfKY KoqpDweAZCPoCTxqLim4jjMRhB7rDaLhSyzXKYueblt9CrReMVhNZvwMs yudAUdXXlc3aSYcqf7Hlha78FgNopczUdUUGmNdT8eSRdKABbL5v8WmYb 2ioF9HqiSFAkzIyqYHA57I9jQljuaoRzamqzPPDyOoDbupfzDHKu9+TiF Q==; X-CSE-ConnectionGUID: TEW4hBvtQfGHianzN/ZIMQ== X-CSE-MsgGUID: mXgM+mLMRu+6wgoo1+bYuw== X-IronPort-AV: E=McAfee;i="6700,10204,11103"; a="26690585" X-IronPort-AV: E=Sophos;i="6.08,238,1712646000"; d="scan'208";a="26690585" Received: from orviesa008.jf.intel.com ([10.64.159.148]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jun 2024 08:53:37 -0700 X-CSE-ConnectionGUID: odsEQtHjQGWLmH1ymatTEQ== X-CSE-MsgGUID: 7H07t/n0Rb2VgNvUZ6n3fg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.08,238,1712646000"; d="scan'208";a="41216536" Received: from mridulya-mobl.amr.corp.intel.com (HELO adixit-arch.intel.com) ([10.125.147.12]) by orviesa008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jun 2024 08:53:37 -0700 Date: Fri, 14 Jun 2024 08:34:30 -0700 Message-ID: <875xubtu61.wl-ashutosh.dixit@intel.com> From: "Dixit, Ashutosh" To: Riana Tauro Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com, aravind.iddamsetty@linux.intel.com, rodrigo.vivi@intel.com, umesh.nerlige.ramappa@intel.com, krishnaiah.bommu@intel.com Subject: Re: [PATCH v9 0/2] drm/xe/pmu: Enable PMU interface In-Reply-To: References: <20240613100411.1579218-1-riana.tauro@intel.com> <878qz8u1on.wl-ashutosh.dixit@intel.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/29.3 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: intel-xe@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Xe graphics driver List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-xe-bounces@lists.freedesktop.org Sender: "Intel-xe" On Thu, 13 Jun 2024 22:50:39 -0700, Riana Tauro wrote: > > Hi Ashutosh > > On 6/14/2024 12:09 AM, Dixit, Ashutosh wrote: > > On Thu, 13 Jun 2024 03:04:09 -0700, Riana Tauro wrote: > >> > > > > Hi Riana, > > > >> There are a set of engine group busyness counters provided by HW which are > >> perfect fit to be exposed via PMU perf events. > >> > >> BSPEC: 46559, 46560, 46722, 46729, 52071, 71028 > >> > >> events can be listed using: > >> perf list > >> xe_0000_03_00.0/any-engine-group-busy-gt0/ [Kernel PMU event] > >> xe_0000_03_00.0/copy-group-busy-gt0/ [Kernel PMU event] > >> xe_0000_03_00.0/media-group-busy-gt0/ [Kernel PMU event] > >> xe_0000_03_00.0/render-group-busy-gt0/ [Kernel PMU event] > > > > PMU patches merged previously were dropped in 90a8b23f9b85 ("drm/xe/pmu: > > Remove PMU from Xe till uapi is finalized") because PMU uapi was expected > > to change. Why are we re-posting these old patches again now, without > > including the planned uapi changes? > > The uapi changes were dropped and there are no other upcoming changes for > Group busyness. So re-posted the old series. What happened to VF busyness (which is why I thought the uapi was going to change)? > > Thanks, > Riana > > > > Thanks. > > -- > > Ashutosh