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 1D04CC32771 for ; Wed, 28 Sep 2022 18:18:08 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 9581210E59A; Wed, 28 Sep 2022 18:18:03 +0000 (UTC) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTPS id C718610E59C; Wed, 28 Sep 2022 18:17:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1664389075; x=1695925075; h=date:message-id:from:to:cc:subject:in-reply-to: references:mime-version; bh=71AVxOFtuM2MDuE7E7WSjdy5d68O66vHSqiEauBT62g=; b=e05WSPCcBOUFLD1wNap9a5JXJ5LlQTVRfm2btBb3MXTpKfvMWWKyPGbl hGX69KWI02pn2TsltSc9cJOZxJFPuANJcMZpEJoL5PfwXk8T7D67zX58q P+4XDFxO9jtZcpoup8+irjksiZSaKUXAlykc7k/3BP5FcfMzlB7E0UnId jx0mc+jXhh6TKaSvMc3Q8HbZzolKJrTkzhTiWcR6lV6uKOSKjPReuHqJs /VKF2tJDbAMk/Z+mOCu+K57JxEHlA/FdpFNGAjsDiaxL3iKZoNpmo0D1j nIv8y2kTKwMsnsVUjglVF6YAnFzGGUc2qX+t1MYJGvPW5reSWt3mvu/Hl Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10484"; a="288839674" X-IronPort-AV: E=Sophos;i="5.93,352,1654585200"; d="scan'208";a="288839674" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2022 11:17:55 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10484"; a="573145031" X-IronPort-AV: E=Sophos;i="5.93,352,1654585200"; d="scan'208";a="573145031" Received: from adixit-mobl.amr.corp.intel.com (HELO adixit-arch.intel.com) ([10.212.246.34]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2022 11:17:54 -0700 Date: Wed, 28 Sep 2022 11:17:06 -0700 Message-ID: <87v8p75pp9.wl-ashutosh.dixit@intel.com> From: "Dixit, Ashutosh" To: Jani Nikula In-Reply-To: <871qrvzq2h.fsf@intel.com> References: <20220919162401.2077713-1-ashutosh.dixit@intel.com> <871qrvzq2h.fsf@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/28.1 (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 Subject: Re: [Intel-gfx] [PATCH] drm/i915: Perf_limit_reasons are only available for Gen11+ X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, Rodrigo Vivi Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Wed, 28 Sep 2022 04:38:46 -0700, Jani Nikula wrote: > > On Mon, 19 Sep 2022, Ashutosh Dixit wrote: > > Register GT0_PERF_LIMIT_REASONS (0x1381a8) is available only for > > Gen11+. Therefore ensure perf_limit_reasons sysfs/debugfs files are created > > only for Gen11+. Otherwise on Gen < 5 accessing these files results in the > > following oops: > > > > <1> [88.829420] BUG: unable to handle page fault for address: ffffc90000bb81a8 > > <1> [88.829438] #PF: supervisor read access in kernel mode > > <1> [88.829447] #PF: error_code(0x0000) - not-present page > > > > Bspec: 20008 > > Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/6863 > > Fixes: fe5979665f64 ("drm/i915/debugfs: Add perf_limit_reasons in debugfs") > > Fixes: fa68bff7cf27 ("drm/i915/gt: Add sysfs throttle frequency interfaces") > > Signed-off-by: Ashutosh Dixit > Hi Jani, > Ashutosh, can you provide a backport of this i.e. commit 0d2d201095e9 > ("drm/i915: Perf_limit_reasons are only available for Gen11+") that > applies cleanly on drm-intel-fixes, please? I've sent the patch: https://patchwork.freedesktop.org/series/109196/ Not sure though if it is worth applying on drm-intel-fixes because of one conflict with drm-tip which will need to be resolved manually. On drm-intel-fixes the crash mentioned above will be seen only on Gen < 5 if someone manually cat's the sysfs. We had to fix on drm-tip because there was a CI failure with Gen3 debugfs but that code is not in drm-intel-fixes. Thanks. -- Ashutosh