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 X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id ADA30C43462 for ; Wed, 19 May 2021 10:57:16 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 6EAAE6135B for ; Wed, 19 May 2021 10:57:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6EAAE6135B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=amd-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 6C94F6ED0B; Wed, 19 May 2021 10:57:15 +0000 (UTC) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) by gabe.freedesktop.org (Postfix) with ESMTPS id 97A726ED0B; Wed, 19 May 2021 10:57:14 +0000 (UTC) Received: by mail-ej1-x634.google.com with SMTP id n2so19311268ejy.7; Wed, 19 May 2021 03:57:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=eIfk0EYHcUWSLcvMPAirbEiPk6baNKVTiRgoiVmFRVQ=; b=sEREbwW6YA7K89gV4VdyhKBYItBL1dOXIUIpz6vkHYFaX579lrecFp4BlVvi4bLDV2 7mmDvwGebhf89186JpwcGkqyXiAJ2M211zM5uwf0YaTBnLC/+Z/MOfODzLC+wwE8zC/N Bh7jLqfIMWLuYvonHfsRPYtJby1hoc3APTq6BrjlcEMikEaueNp8RW+xHAleSETAJTSV o2PRo/svgwJZzHBC9/TCiBk/GON7VcGpAPMlpf7YvHb9OsD2R9HIqiXuZh6jMa5JcYe2 ZESHC6zwqPHrU1JqqaIzvM5gXN7rt7ActRQ82pfTrEcgwmk/QsAtBlcai9GPXZB8MC3H HY8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=eIfk0EYHcUWSLcvMPAirbEiPk6baNKVTiRgoiVmFRVQ=; b=Z5cmJWLMR6CK0qW2sQeBhzIz3TtEqu+e7DKMzOE7hE5en4wY/Sq4CoDntSiOGm7zwA 0GbT1gDhrWxmY7u1IntXxYFwAzVNO2GHqQWT5T+Wxrne75CftlF+c8G2l7s7PCePqh7s thMpL0tFzzG7OLESWC+6UVbNmxMoD6C1wfY5oZ8lY24/iDP6QSJIVGL9EHRMBJUN0HF7 Fnp3kwIQ7LYDzD+pr5sCrSp6/N11TpZpfAwTNTjjUoNIrVXD5pUBNVn8e/CbHi3gdiab cY7+vpK/9ZaTM8Hism1DeB0o0cTOFumXLZWBEck0eW5jBOTlUUrRMDzZJcxLr0seN0mt MwSA== X-Gm-Message-State: AOAM532XLj49e8HPoe3cynvrljO6SsnGgKPNcCiFMKsICpSN7palAI25 cPy6S0yItnJS9441laEFzdE= X-Google-Smtp-Source: ABdhPJz4gO4nMeqvJ32qure4n+cnMraucNdsIEccSVII0cCqiNIIAIHE/k+gVZhf+Wfa/zWhifB1JA== X-Received: by 2002:a17:906:f84:: with SMTP id q4mr12165250ejj.442.1621421833266; Wed, 19 May 2021 03:57:13 -0700 (PDT) Received: from ?IPv6:2a02:908:1252:fb60:8e28:1d3:41f3:e15a? ([2a02:908:1252:fb60:8e28:1d3:41f3:e15a]) by smtp.gmail.com with ESMTPSA id g4sm5902727edm.83.2021.05.19.03.57.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 May 2021 03:57:12 -0700 (PDT) Subject: Re: [PATCH v7 13/16] drm/scheduler: Fix hang when sched_entity released To: Andrey Grodzovsky , =?UTF-8?Q?Christian_K=c3=b6nig?= , dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org, linux-pci@vger.kernel.org, daniel.vetter@ffwll.ch, Harry.Wentland@amd.com References: <20210512142648.666476-1-andrey.grodzovsky@amd.com> <20210512142648.666476-14-andrey.grodzovsky@amd.com> <9e1270bf-ab62-5d76-b1de-e6cd49dc4841@amd.com> <34d4e4a8-c577-dfe6-3190-28a5c63a2d23@amd.com> <8228ea6b-4faf-bb7e-aaf4-8949932e869a@amd.com> <53f281cc-e4c0-ea5d-9415-4413c85a6a16@amd.com> <0b49fc7b-ca0b-58c4-3f76-c4a5fab97bdc@amd.com> <31febf08-e9c9-77fa-932d-a50505866ec4@amd.com> From: =?UTF-8?Q?Christian_K=c3=b6nig?= Message-ID: <77efa177-f313-5f1e-e273-6672ed46a90a@gmail.com> Date: Wed, 19 May 2021 12:57:11 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-BeenThere: amd-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion list for AMD gfx List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Alexander.Deucher@amd.com, gregkh@linuxfoundation.org, ppaalanen@gmail.com, helgaas@kernel.org, Felix.Kuehling@amd.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: amd-gfx-bounces@lists.freedesktop.org Sender: "amd-gfx" Am 18.05.21 um 20:48 schrieb Andrey Grodzovsky: > [SNIP] >>> >>> Would this be the right way to do it ? >> >> Yes, it is at least a start. Question is if we can wait blocking here >> or not. >> >> We install a callback a bit lower to avoid blocking, so I'm pretty >> sure that won't work as expected. >> >> Christian. > > I can't see why this would create problems, as long as the dependencies > complete or force competed if they are from same device (extracted) but > on a different ring then looks to me it should work. I will give it > a try. Ok, but please also test the case for a killed process. Christian. > > Andrey _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx