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 X-Spam-Level: X-Spam-Status: No, score=-14.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,HK_RANDOM_FROM,INCLUDES_PATCH, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9DDA4C433B4 for ; Thu, 13 May 2021 16:41:05 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 3CCCA61438 for ; Thu, 13 May 2021 16:41:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3CCCA61438 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 4245A6ED6B; Thu, 13 May 2021 16:41:02 +0000 (UTC) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by gabe.freedesktop.org (Postfix) with ESMTPS id 486626E0AA; Thu, 13 May 2021 16:41:01 +0000 (UTC) IronPort-SDR: qqQgFYGuxfJV3qUVBuktYk5mgb7Wmq+44RUJ6g+T7Jgzq8Ir1qcxfuNgf8ZAUMZxdcSnj0E5p+ PvH/4CkmwkJQ== X-IronPort-AV: E=McAfee;i="6200,9189,9983"; a="179582978" X-IronPort-AV: E=Sophos;i="5.82,296,1613462400"; d="scan'208";a="179582978" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2021 09:40:56 -0700 IronPort-SDR: zvpeWm9M9E54Zx0UAYT2cNnoDN6hVFBdMwaa+uLa7oDM2bP4B6zJSZ9sx46WEtDvdOyYh++dzK hsW6Ggpbj2gw== X-IronPort-AV: E=Sophos;i="5.82,296,1613462400"; d="scan'208";a="626297750" Received: from hcadcock-mobl1.ger.corp.intel.com (HELO [10.213.209.166]) ([10.213.209.166]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2021 09:40:55 -0700 Subject: Re: [PATCH 0/7] Per client engine busyness To: Alex Deucher References: <20210513110002.3641705-1-tvrtko.ursulin@linux.intel.com> From: Tvrtko Ursulin Organization: Intel Corporation UK Plc Message-ID: Date: Thu, 13 May 2021 17:40:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Intel Graphics Development , Maling list - DRI developers Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hi, On 13/05/2021 16:48, Alex Deucher wrote: > On Thu, May 13, 2021 at 7:00 AM Tvrtko Ursulin > wrote: >> >> From: Tvrtko Ursulin >> >> Resurrect of the previosuly merged per client engine busyness patches. In a >> nutshell it enables intel_gpu_top to be more top(1) like useful and show not >> only physical GPU engine usage but per process view as well. >> >> Example screen capture: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> intel-gpu-top - 906/ 955 MHz; 0% RC6; 5.30 Watts; 933 irqs/s >> >> IMC reads: 4414 MiB/s >> IMC writes: 3805 MiB/s >> >> ENGINE BUSY MI_SEMA MI_WAIT >> Render/3D/0 93.46% |████████████████████████████████▋ | 0% 0% >> Blitter/0 0.00% | | 0% 0% >> Video/0 0.00% | | 0% 0% >> VideoEnhance/0 0.00% | | 0% 0% >> >> PID NAME Render/3D Blitter Video VideoEnhance >> 2733 neverball |██████▌ || || || | >> 2047 Xorg |███▊ || || || | >> 2737 glxgears |█▍ || || || | >> 2128 xfwm4 | || || || | >> 2047 Xorg | || || || | >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> Internally we track time spent on engines for each struct intel_context, both >> for current and past contexts belonging to each open DRM file. >> >> This can serve as a building block for several features from the wanted list: >> smarter scheduler decisions, getrusage(2)-like per-GEM-context functionality >> wanted by some customers, setrlimit(2) like controls, cgroups controller, >> dynamic SSEU tuning, ... >> >> To enable userspace access to the tracked data, we expose time spent on GPU per >> client and per engine class in sysfs with a hierarchy like the below: >> >> # cd /sys/class/drm/card0/clients/ >> # tree >> . >> ├── 7 >> │ ├── busy >> │ │ ├── 0 >> │ │ ├── 1 >> │ │ ├── 2 >> │ │ └── 3 >> │ ├── name >> │ └── pid >> ├── 8 >> │ ├── busy >> │ │ ├── 0 >> │ │ ├── 1 >> │ │ ├── 2 >> │ │ └── 3 >> │ ├── name >> │ └── pid >> └── 9 >> ├── busy >> │ ├── 0 >> │ ├── 1 >> │ ├── 2 >> │ └── 3 >> ├── name >> └── pid >> >> Files in 'busy' directories are numbered using the engine class ABI values and >> they contain accumulated nanoseconds each client spent on engines of a >> respective class. > > We did something similar in amdgpu using the gpu scheduler. We then > expose the data via fdinfo. See > https://cgit.freedesktop.org/drm/drm-misc/commit/?id=1774baa64f9395fa884ea9ed494bcb043f3b83f5 > https://cgit.freedesktop.org/drm/drm-misc/commit/?id=874442541133f78c78b6880b8cc495bab5c61704 Interesting! Is yours wall time or actual GPU time taking preemption and such into account? Do you have some userspace tools parsing this data and how to do you client discovery? Presumably there has to be a better way that going through all open file descriptors? Our implementation was merged in January but Daniel took it out recently because he wanted to have discussion about a common vendor framework for this whole story on dri-devel. I think. +Daniel to comment. I couldn't find the patch you pasted on the mailing list to see if there was any such discussion around your version. Regards, Tvrtko > > Alex > > >> >> Tvrtko Ursulin (7): >> drm/i915: Expose list of clients in sysfs >> drm/i915: Update client name on context create >> drm/i915: Make GEM contexts track DRM clients >> drm/i915: Track runtime spent in closed and unreachable GEM contexts >> drm/i915: Track all user contexts per client >> drm/i915: Track context current active time >> drm/i915: Expose per-engine client busyness >> >> drivers/gpu/drm/i915/Makefile | 5 +- >> drivers/gpu/drm/i915/gem/i915_gem_context.c | 61 ++- >> .../gpu/drm/i915/gem/i915_gem_context_types.h | 16 +- >> drivers/gpu/drm/i915/gt/intel_context.c | 27 +- >> drivers/gpu/drm/i915/gt/intel_context.h | 15 +- >> drivers/gpu/drm/i915/gt/intel_context_types.h | 24 +- >> .../drm/i915/gt/intel_execlists_submission.c | 23 +- >> .../gpu/drm/i915/gt/intel_gt_clock_utils.c | 4 + >> drivers/gpu/drm/i915/gt/intel_lrc.c | 27 +- >> drivers/gpu/drm/i915/gt/intel_lrc.h | 24 ++ >> drivers/gpu/drm/i915/gt/selftest_lrc.c | 10 +- >> drivers/gpu/drm/i915/i915_drm_client.c | 365 ++++++++++++++++++ >> drivers/gpu/drm/i915/i915_drm_client.h | 123 ++++++ >> drivers/gpu/drm/i915/i915_drv.c | 6 + >> drivers/gpu/drm/i915/i915_drv.h | 5 + >> drivers/gpu/drm/i915/i915_gem.c | 21 +- >> drivers/gpu/drm/i915/i915_gpu_error.c | 31 +- >> drivers/gpu/drm/i915/i915_gpu_error.h | 2 +- >> drivers/gpu/drm/i915/i915_sysfs.c | 8 + >> 19 files changed, 716 insertions(+), 81 deletions(-) >> create mode 100644 drivers/gpu/drm/i915/i915_drm_client.c >> create mode 100644 drivers/gpu/drm/i915/i915_drm_client.h >> >> -- >> 2.30.2 >>