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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6BA8AC6FD18 for ; Tue, 25 Apr 2023 10:29:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233448AbjDYK3C (ORCPT ); Tue, 25 Apr 2023 06:29:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35838 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233329AbjDYK3A (ORCPT ); Tue, 25 Apr 2023 06:29:00 -0400 Received: from mout-p-102.mailbox.org (mout-p-102.mailbox.org [80.241.56.152]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E5F8F12CA7 for ; Tue, 25 Apr 2023 03:28:28 -0700 (PDT) Received: from smtp202.mailbox.org (smtp202.mailbox.org [10.196.197.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4Q5J966X28z9sjC; Tue, 25 Apr 2023 12:27:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1682418458; 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=AzoOwKMdJiLKK3BSiCIwb6001/mIm7hyJsaLnt4CuOY=; b=gcckeR9ypTnpx8tyY5QCL0wq+wig31N845d0UcpgHbiaBysK4rFUe7QTKjgoOtzw1yVQ9q olCCPx4pt5kj2OjdDr++5kP2lbKTA+FYGmlnG2iKIMxCqG35wvvyZpq5phrD6Cxl4yocRY LmCfwgcbto4PAo+Y+Le1GYzh8f/3BiYcoljJjTFHOIw/d5tZ6vpsMPwwSdi1gEJa/Ib3On CPHZY0jOb8D5GDUaneWnMb1ZBU8kDWZ6mMsjAEKHYV6EmaCNAdtDJ4qXGIo0GkrKn0qiiW mdhcfwqZbywi1z+Q6+4ZrmVSsXBerBKQ4d6jj+FwVX+LmTuyvY/gfLCH8tpCbw== Message-ID: <784561bb-0937-befc-3774-892d6f6a4318@mailbox.org> Date: Tue, 25 Apr 2023 12:27:37 +0200 MIME-Version: 1.0 Subject: Re: [PATCH] drm/amdgpu: Mark contexts guilty for any reset type Content-Language: de-CH-frami, en-CA To: =?UTF-8?B?TWFyZWsgT2zFocOhaw==?= , =?UTF-8?Q?Christian_K=c3=b6nig?= Cc: Pierre-Eric Pelloux-Prayer , =?UTF-8?Q?Andr=c3=a9_Almeida?= , Linux Kernel Mailing List , amd-gfx mailing list , "Tuikov, Luben" , dri-devel , kernel-dev@igalia.com, "Deucher, Alexander" References: <20230424014324.218531-1-andrealmeid@igalia.com> From: =?UTF-8?Q?Michel_D=c3=a4nzer?= In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MBO-RS-ID: e4acb3074d567e8fc3c X-MBO-RS-META: qakb7pkk8zexswyiqwxbcthy4cfcgjgp Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/24/23 18:45, Marek Olšák wrote: > Soft resets are fatal just as hard resets, but no reset is "always fatal". There are cases when apps keep working depending on which features are being used. It's still unsafe. Agreed, in theory. In practice, from a user PoV, right now there's pretty much 0 chance of the user session surviving if the GPU context in certain critical processes (e.g. the Wayland compositor or Xwayland) hits a fatal reset. There's a > 0 chance of it surviving after a soft reset. There's ongoing work towards making user-space components more robust against fatal resets, but it's taking time. Meanwhile, I suspect most users would take the > 0 chance. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and Xwayland developer