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 C6910E77184 for ; Thu, 19 Dec 2024 16:05:27 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 9346210E34D; Thu, 19 Dec 2024 16:05:27 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="N9Hwm1u2"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.14]) by gabe.freedesktop.org (Postfix) with ESMTPS id 13E5510E34D for ; Thu, 19 Dec 2024 16:05:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1734624327; x=1766160327; h=date:message-id:from:to:cc:subject:in-reply-to: references:mime-version:content-transfer-encoding; bh=IJtmVImsrqrPUKuYV0xR9HITO9gsnqA3US85K+mDewc=; b=N9Hwm1u2uKGbtoV1HGVQfpPvDaxy4cs6MAMtCUkrrxPxw7PN0AKcgCpG ixjIEPfg5dXdSOoi1HOB6QsJIyXGejXwWGsNuf7yBKBIoaMPG24kmRACu bh9cDklazZ6OdqmcusKwe2YmAf5fJsFOPSN42avSsTfI3S7Z9XKRcPif7 DeXY7ME5xxUb5x1XDtvkUiK/l+bCS8JH2fwcc1ljYiDh6vE9ew48QGuEG UVO7o5piIa/TDC8ZPqu3kgwMQo+K3DkZgvS5edTRWqJbmwW40GHmm9us+ O44i0pH3vGWcXsTpI47z3UPcIlLkXFqrVMpkbxo+eaB4zYxQdxWEnPVdx Q==; X-CSE-ConnectionGUID: nnZJl3t6SlCILT0pdO3RbQ== X-CSE-MsgGUID: Rf/VFIbDR+O1hm+qa719BA== X-IronPort-AV: E=McAfee;i="6700,10204,11290"; a="38922110" X-IronPort-AV: E=Sophos;i="6.12,248,1728975600"; d="scan'208";a="38922110" Received: from orviesa004.jf.intel.com ([10.64.159.144]) by orvoesa106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Dec 2024 08:05:27 -0800 X-CSE-ConnectionGUID: RW2ptGBaSFml1IrWc70dlA== X-CSE-MsgGUID: pFZdTHPdRFunvppUKN4YuQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,248,1728975600"; d="scan'208";a="103218122" Received: from orsosgc001.jf.intel.com (HELO orsosgc001.intel.com) ([10.165.21.142]) by orviesa004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Dec 2024 08:05:27 -0800 Date: Thu, 19 Dec 2024 08:05:26 -0800 Message-ID: <85v7vf1wvt.wl-ashutosh.dixit@intel.com> From: "Dixit, Ashutosh" To: "Souza, Jose" Cc: "De Marchi, Lucas" , "thomas.hellstrom@linux.intel.com" , "intel-xe@lists.freedesktop.org" , "Brost,\ Matthew" , "Nerlige Ramappa, Umesh" Subject: Re: [PATCH] drm/xe: Force write completion of MI_STORE_DATA_IMM In-Reply-To: References: <20241217160732.46280-1-jose.souza@intel.com> <3ebdd73cecef119cbfb7fc902909c8c2adc5b0fc.camel@intel.com> <85wmfw1l7b.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/28.2 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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, 19 Dec 2024 05:58:59 -0800, Souza, Jose wrote: > > On Wed, 2024-12-18 at 18:05 -0800, Dixit, Ashutosh wrote: > > On Wed, 18 Dec 2024 09:27:36 -0800, Matthew Brost wrote: > > > > > > > Folks, > > > > > On Wed, Dec 18, 2024 at 08:38:49AM -0700, Souza, Jose wrote: > > > > On Tue, 2024-12-17 at 15:39 -0800, Matthew Brost wrote: > > > > > On Tue, Dec 17, 2024 at 08:07:32AM -0800, Jos=E9 Roberto de Souza= wrote: > > > > > > With Force write completion unset there is no guarantees of whe= n the > > > > > > write will be globally visible what is not the behavior wanted. > > > > > > > > > > > > > > > > Do we want this backported? If so, maybe add a fixes? > > > > > > > > Not sure, I don't have an actual issue that is fixed by this but I > > > > think would be good to have it backported. But what do you > > > > suggest? Add a fixes tag to the patch removing force probe from > > > > LNL? > > > > > > > > > > Yea fixing LNL force probe removal sounds reasonable to me. > > > > Hmm the plan was add Fixes to this patch and also Cc: stable. Yet it was > > merged without these: > > > > 1460bb1fef9c ("drm/xe: Force write completion of MI_STORE_DATA_IMM") > > > > Lucas/Thomas, > > > > Would it be possible to send it to -fixes with a Cc:stable. We have pat= ches > > depending on this one which we want to send to stable. > > Please correct me if I'm wrong but that is enough for it to be picked to > stable, it will happen in the next Xe stable pull request. Ah, ok, sorry I missed that there is a Fixes: in the merged patch, so maybe that is sufficient for it to be picked to stable.