From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout-p-102.mailbox.org (mout-p-102.mailbox.org [80.241.56.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 92C401EDA2B for ; Mon, 16 Feb 2026 09:28:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=80.241.56.152 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771234105; cv=none; b=VXDG3NafD7QVr+taKhkhFjyYTj0QeH11aJNSHGIuqh+lhAk9hGbMPP/mmdhR5DLhyZ3VfItQyMtvNPgLlIVznqeYhxTU2Y+uzCAQBt+L2vL0FodbbNfjTkMZnXylI1oSUhDWSNE5CikFoKN7bpJTvJQUHSiHxaTaE+Kj/bZuCoQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771234105; c=relaxed/simple; bh=std8LGp8fRx1rjN5OvnQQ7Hi0kxDP2xP5zKo9Vwu4i4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=MKIuAZZuiyMoF823buYQY0BYrZiEkpLaYd7JnjA3oUJwnEVbc3PooDAtEOxRspdnoLs2tmh5xmirprOQxSKzv8PO+3gF9SUgN6wke9UghKgMtxESHgBY2N6TL0OQIlWhCgCBYfOwf4UsVMc0vEIJeEESVAmXLDftUYHwNBTfpLs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org; spf=pass smtp.mailfrom=mailbox.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b=CPCKfPDi; arc=none smtp.client-ip=80.241.56.152 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mailbox.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b="CPCKfPDi" Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4fDyBC406lz9vDx; Mon, 16 Feb 2026 10:28:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1771234099; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xrnqCAaSli5/FQRdIXyZ88I9oAN4JNz7CSF+8kqQWjQ=; b=CPCKfPDimpPMuukfGC4X2vFdpvcL1kWE7p+GE/LP0H5HiRSqGsUEE10h/3BrQE8ymULMmN gkvJtCHHRK9PX8ZpFFdkpXlSc0G5MHH8SnK9HFKd5Ty2EkKGyYf2B+XnAkdglnzDzjyakJ y9df8f2F5/BqLzlUwxDn1yU1vC321BMooeZtJ8JBx7Lqsgi9fvk5Q4fozbGDF9JJPPN+7H h9EC5EAZYj+hAzFejLedWTk0g5e25+xtobpKoAOFhcInH7z5hZK8VQTg1DPv8GceZpseDW XluQ3W0E/M58oEGMs7lfbmqDP48KaON2pLudpOqKS80G85iNmab6tcPi+kH+Jw== Message-ID: <7f4a86ad-d642-444c-a576-17ff9caaa934@mailbox.org> Date: Mon, 16 Feb 2026 10:28:13 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v3 1/2] drm: introduce KMS recovery mechanism To: Hamza Mahfooz Cc: Mario Limonciello , dri-devel@lists.freedesktop.org, Harry Wentland , Leo Li , Rodrigo Siqueira , Alex Deucher , =?UTF-8?Q?Christian_K=C3=B6nig?= , David Airlie , Simona Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Alex Hung , Wayne Lin , Aurabindo Pillai , Ivan Lipski , =?UTF-8?Q?Timur_Krist=C3=B3f?= , Dominik Kaszewski , amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org References: <20260212230905.688006-1-someguy@effective-light.com> <2e359cd9-0192-44d0-886f-7f93a8b0a4fa@amd.com> <85319290-4027-4eb8-95d1-9009d23f2294@mailbox.org> From: =?UTF-8?Q?Michel_D=C3=A4nzer?= Content-Language: de-CH-frami, en-CA In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MBO-RS-ID: 62359b98baf74e21a94 X-MBO-RS-META: ji19nbhxmym4obz7fekxib6m8podn94n On 2/14/26 23:16, Hamza Mahfooz wrote: > On Sat, Feb 14, 2026 at 03:02:49PM +0100, Michel Dänzer wrote: >> Why couldn't a full modeset? > > As far as I see it the only reasons why we should be timing out is > either an interrupt went missing (perhaps due to a race condition in > driver code) or hung hardware. In either case, the interrupt associated > with the page flip for the current commit is long gone. That's a matter of bookkeeping, the interrupt isn't required to keep track of the commit and complete it. >> In principle it's possible to do (the equivalent of) a modeset with the current state for all CRTCs, no need to do it separately per CRTC. > > AFAIK that is what the uevent is already doing (unless I'm mistaken). This is about just doing a full modeset, which isn't something user space can do in response to a wedged event. -- Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer https://redhat.com \ Libre software enthusiast