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 8E530EA4FD7 for ; Tue, 24 Feb 2026 09:28:53 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 2AEC210E531; Tue, 24 Feb 2026 09:28:51 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="MmJsU4Fa"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) by gabe.freedesktop.org (Postfix) with ESMTPS id DB08010E52E; Tue, 24 Feb 2026 09:28:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1771925330; x=1803461330; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version:content-transfer-encoding; bh=UUB7Qzg/Lk4zTAYo7yVNhF4APyQVocV/hsKW/ia8dBw=; b=MmJsU4Fai1cGLEepAShzx+TdUTApEbszP1Sifxf1lxAwErh8FsxqgvCc 3ttO8Fqpw4T0gTwxsWKg2PzylEm2nZlC0+TIpgQ/ms34iiiPCcqO+jYC0 +ruNdJMkn+PxP8EoT7bmb2wV5MDVlTFaDb5brLUy7Lnu4uwRApwVe0MVg sMHDUX+PKjYO0UBAhn9y6TB8BM4uH5K4NUCzn4GMsaKmax3nYGR1lBx1U gl7K6/dQnIiSRG//VXVdANe1FiFZNDRXZ1u1sXOYAL4/oEC4aXD4kByN+ 1ymhTBbv17jVmpS/FExSLLTBMinFUEVCAl7C3fKbeo47OEEcn0+RbQ0H3 w==; X-CSE-ConnectionGUID: nf23E/BpTMyEYibK6RZ4PQ== X-CSE-MsgGUID: t1c4dJc6QS2KNBqyQdNBiw== X-IronPort-AV: E=McAfee;i="6800,10657,11710"; a="84391348" X-IronPort-AV: E=Sophos;i="6.21,308,1763452800"; d="scan'208";a="84391348" Received: from fmviesa002.fm.intel.com ([10.60.135.142]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Feb 2026 01:28:49 -0800 X-CSE-ConnectionGUID: LRgP5gwQQuOy8p13mQRoWQ== X-CSE-MsgGUID: kubyX7yWTB2yU0qwDo9F9w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,308,1763452800"; d="scan'208";a="238826435" Received: from ettammin-mobl2.ger.corp.intel.com (HELO localhost) ([10.245.246.20]) by fmviesa002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Feb 2026 01:28:44 -0800 From: Jani Nikula To: Ville =?utf-8?B?U3lyasOkbMOk?= , "Murthy, Arun R" Cc: Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Rodrigo Vivi , Joonas Lahtinen , Tvrtko Ursulin , xaver.hugl@kde.org, harry.wentland@amd.com, uma.shankar@intel.com, louis.chauvet@bootlin.com, naveen1.kumar@intel.com, ramya.krishna.yella@intel.com, dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org, Suraj Kandpal Subject: Re: [PATCH v10 0/7] User readable error codes on atomic_ioctl failure In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs Bertel Jungin Aukio 5, 02600 Espoo, Finland References: <20260223-atomic-v10-0-f59c8def2e70@intel.com> <1a4462b8-def9-4474-8382-6e99b7c8276d@intel.com> <5f04b5f1-744e-449e-9a45-00fd477256fc@intel.com> Date: Tue, 24 Feb 2026 11:28:41 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 Tue, 24 Feb 2026, Ville Syrj=C3=A4l=C3=A4 wrote: > Although I kinda doubt its actual usefulness to drive useful > fallback logic because often the restrictions might be a combination > of many things, and the kernel can only realistically report one of > those things. Yeah, this is my main concern as well. The drivers will have to bail out on the first issue they hit, whatever it is. The drivers may choose to do the checks in different orders, resulting in different failure modes for different drivers. And finally, accidentally making the order of the checks part of the ABI contract is a scary prospect. Imagine user space depending on certain checks happening first in order for the fallback logic to work properly. Is it a kernel regression to change the order of the checks then? BR, Jani. --=20 Jani Nikula, Intel