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 B0D77C54764 for ; Mon, 19 Feb 2024 10:32:04 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 3631210E2B2; Mon, 19 Feb 2024 10:32:04 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="LYCD5r/s"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.20]) by gabe.freedesktop.org (Postfix) with ESMTPS id C4C6410E2A4; Mon, 19 Feb 2024 10:32:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1708338723; x=1739874723; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=EMBRqBRFw8T7hhFbe2NlzLlqJGZE8btg4vYfiNAbfnk=; b=LYCD5r/siOJ/0Ym4nvgeuL5fTizzafofQ+Rq+KePvtyoykSX1+u/oYCE jde319A29XoYNBO21Imy7NrJ2KY8NfmkuqliGYaV4QMssvMFITFRCX7ys 1imKXTAhHCvTKzPBOeH/TtFqq30jvLrjKw2e7KrYg1SjVRh3Ke2BohO42 bdJzxiQYhW/zjByUtBGu5ocAShQ9fkQZ3Tbh3aIM7/4ihT08/SpmBJmNR 7iLzS+Nbb+b0CzR2j54bKTiiLb2QbaKLtPZaBk3NIAAM77PE3gg3oI4M0 mzSwHmxchlWvTuPX3WhTU2GbNjVbu86NcNjxy5RcoIaH61ZnlGsQU+JTN w==; X-IronPort-AV: E=McAfee;i="6600,9927,10988"; a="2273791" X-IronPort-AV: E=Sophos;i="6.06,170,1705392000"; d="scan'208";a="2273791" Received: from fmviesa006.fm.intel.com ([10.60.135.146]) by orvoesa112.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Feb 2024 02:32:03 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.06,170,1705392000"; d="scan'208";a="4709503" Received: from samathah-mobl1.ger.corp.intel.com (HELO intel.com) ([10.246.48.149]) by fmviesa006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Feb 2024 02:32:00 -0800 Date: Mon, 19 Feb 2024 11:31:57 +0100 From: Andi Shyti To: Andi Shyti Cc: Matt Roper , intel-gfx , dri-devel , Chris Wilson , Joonas Lahtinen , stable@vger.kernel.org, Andi Shyti Subject: Re: [PATCH 1/2] drm/i915/gt: Disable HW load balancing for CCS Message-ID: References: <20240215135924.51705-1-andi.shyti@linux.intel.com> <20240215135924.51705-2-andi.shyti@linux.intel.com> <20240215165541.GJ718896@mdroper-desk1.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Mon, Feb 19, 2024 at 11:17:33AM +0100, Andi Shyti wrote: > On Thu, Feb 15, 2024 at 08:55:41AM -0800, Matt Roper wrote: > > On Thu, Feb 15, 2024 at 02:59:23PM +0100, Andi Shyti wrote: > > > The hardware should not dynamically balance the load between CCS > > > engines. Wa_16016805146 recommends disabling it across all > > > > Is this the right workaround number? When I check the database, this > > workaround was rejected on both DG2-G10 and DG2-G11, and doesn't even > > have an entry for DG2-G12. > > > > There are other workarounds that sound somewhat related to load > > balancing (e.g., part 3 of Wa_14019159160), but what's asked there is > > more involved than just setting one register bit and conflicts a bit > > with the second patch of this series. > > thanks for checking it. Indeed the WA I mentioned is limited to > a specific platform. This recommendation comes in different WA, > e.g. this one: Wa_14019186972 (3rd point). Will start using that > as a reference. actually you are right, I checked with Joonas and I will use Wa_14019159160. Thanks, Andi