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 EB926C433EF for ; Thu, 14 Jul 2022 14:24:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240323AbiGNOX7 (ORCPT ); Thu, 14 Jul 2022 10:23:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239521AbiGNOXr (ORCPT ); Thu, 14 Jul 2022 10:23:47 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 19EB46587 for ; Thu, 14 Jul 2022 07:23:41 -0700 (PDT) Received: from [192.168.2.145] (109-252-119-232.nat.spd-mgts.ru [109.252.119.232]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: dmitry.osipenko) by madras.collabora.co.uk (Postfix) with ESMTPSA id A6AD76601A3F; Thu, 14 Jul 2022 15:23:38 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1657808619; bh=C9VLKUurDe58HrZqhM0aPD6VGh/A29qN7rcwvWQV/HU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Qzg0i2ttNNypfFQcymKJHqgoKRP7AA52ZfEr3r/2Uxi6gRBYgOC94+5D/JbchEAWD OihyZBxtPbFByuNM5544hyt4W6ESA124yVAwY0rX5MbSYxhNul4Y4Uh1NfiElxM/oi Lr9K40trURiThyT0TG5R7V7xMu5rSJFkNuK/3mPNf9+Us9HKi19kZO+34BnCSvykpm GwFp83kuhOVFb5LcICCDb0L++Tq2Oppo6VZ+774bJ97fJ7m7B9ZtdY+736vn6UPVV8 xYIMGh8oBtzTlJfqN5e6r3hFC71StHtPTs5PLahOjHtiaB2G9vAtRYaKlp/wyzx/zc yUFTLEu2PFI+Q== Message-ID: <73fde0e0-11d2-a627-0bf9-84ee7d3b5fcc@collabora.com> Date: Thu, 14 Jul 2022 17:23:35 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH v1] drm/scheduler: Don't kill jobs in interrupt context Content-Language: en-US To: Andrey Grodzovsky , Alex Deucher , Thomas Zimmermann , Maarten Lankhorst Cc: Erico Nunes , Steven Price , Tomeu Vizoso , David Airlie , linux-kernel , dri-devel , Alyssa Rosenzweig , Dmitry Osipenko References: <20220411221536.283312-1-dmitry.osipenko@collabora.com> <573fae0d-c9ab-98b0-c6f1-5b0d4e52dd01@amd.com> <107fe968-8311-0511-cc31-22feb994a6d7@collabora.com> <3e07a8d0-2cbc-8f3e-8f9f-5b73fb82028b@amd.com> <6e0c7590-6ffb-162b-a98d-0a39333453f6@collabora.com> <4ca27cee-eda0-0a65-f972-c69cc3b3e53e@amd.com> From: Dmitry Osipenko In-Reply-To: <4ca27cee-eda0-0a65-f972-c69cc3b3e53e@amd.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/14/22 17:14, Andrey Grodzovsky wrote: > > On 2022-07-14 05:57, Dmitry Osipenko wrote: >> On 7/12/22 11:56, Dmitry Osipenko wrote: >>> On 7/6/22 18:46, Alex Deucher wrote: >>>> On Wed, Jul 6, 2022 at 9:49 AM Andrey Grodzovsky >>>> wrote: >>>>> On 2022-07-06 03:07, Dmitry Osipenko wrote: >>>>> >>>>>> Hello Andrey, >>>>>> >>>>>> On 5/17/22 17:48, Dmitry Osipenko wrote: >>>>>>> On 5/17/22 17:13, Andrey Grodzovsky wrote: >>>>>>>> Done. >>>>>>>> >>>>>>>> Andrey >>>>>>> Awesome, thank you! >>>>>>> >>>>>> Given that this drm-scheduler issue needs to be fixed in the >>>>>> 5.19-RC and >>>>>> earlier, shouldn't it be in the drm-fixes and not in drm-next? >>>>> >>>>> I pushed it into drm-misc from where it got into drm-next. I don't >>>>> have >>>>> permission for drm-fixes. >>>> The -fixes branch of drm-misc. >>> Now I don't see the scheduler bugfix neither in the -fixes branch nor in >>> the -next and today Dave sent out 5.19-rc7 pull request without the >>> scheduler fix. Could anyone please check what is going on with the DRM >>> patches? Thanks! >>> >>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffreedesktop%2Fdrm-misc%2Fcommits%2Fdrm-misc-fixes&data=05%7C01%7Candrey.grodzovsky%40amd.com%7C68b627b8482a4fd28a5608da657f4375%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933894551324163%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CDdLG%2F7SqCudEnjhBSsXqq15mfhlHlS3xAdAfB%2Bh%2F1s%3D&reserved=0 >>> >>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcgit.freedesktop.org%2Fdrm%2Fdrm-misc%2Flog%2F%3Fh%3Ddrm-misc-fixes&data=05%7C01%7Candrey.grodzovsky%40amd.com%7C68b627b8482a4fd28a5608da657f4375%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637933894551324163%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4Vz40j6F%2FzHYckXEyPEunj9DRSoTXikhNxZDXeocTss%3D&reserved=0 >>> >> The patch is in the drm-misc-next-fixes, so it wasn't moved to the >> drm-misc-fixes. >> >> Andrey, don't you have access to drm-misc-fixes? Or you meant >> drm-fixes=drm-misc-fixes? > > > I have only accesses to drm-misc-next to which I pushed this patch. Thank you for the clarification. IIUC, the drm-misc-next-fixes should become drm-misc-fixes, but perhaps it was late for the 5.19-rc6 for this patch. -- Best regards, Dmitry