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.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 DC143C47083 for ; Wed, 2 Jun 2021 09:39:29 +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 9C26160FF2 for ; Wed, 2 Jun 2021 09:39:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9C26160FF2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 170F56E5BB; Wed, 2 Jun 2021 09:39:29 +0000 (UTC) Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) by gabe.freedesktop.org (Postfix) with ESMTPS id 65F516E5BB; Wed, 2 Jun 2021 09:39:27 +0000 (UTC) Received: by mail-pf1-x429.google.com with SMTP id t28so1712910pfg.10; Wed, 02 Jun 2021 02:39:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UoqfQasLN0pZ00mRIInlwQ56qBNCyjrvVbN90p7EI58=; b=kdXFzSq+Og4JjpWrwbfWDW+BJgr5KKzHJZcpprrqzrd3iepnUEPQsBoqEeoyGYoI3E 2z5ZVZWUWxVChlcqfuKuFuovtyJLAL+0dbzRsl8cRAP8lVagFIWoXEtHxGV4t0cQ5a7Y 6v4iC1Fwv7KPl4zT9e5eqUvw5ICfpQkUv7G+tznQGkj3v45F5DkEuR7l7wHklYICDV0/ 5U1nANEcGG+lz/S2boote+bEUDl7XyhBbHbyLy/KDDbkWcYfmjiIjb+u+/Sv4jpvTIPg JLx0bglSzIuL1dHdYwNWlaMffUivTT+T16GcwEKkDjmSxaX4Q8nnuM+6qZOdn4hArBZY UOYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UoqfQasLN0pZ00mRIInlwQ56qBNCyjrvVbN90p7EI58=; b=H+sOEJ+dBtHTiNgClYNYgY98flSPWgSQy66eMozt+PIxE0g1gXJFJk8ybEaVG4SZhl KbZ4tygVo5Q2N9pyJvg/cr484P68PfQDpZL20NM0w+vYogsDNBWT3/HzVbfh5wsmGEsV uP7b+42i2vxGxOF7fbq23AHCr9+yzZ8+0seRZo43V9gMN/3Dx5JJnArsbjBWb1xAvU/R 1bX3AuQQXuFDFsXyo2Cl+HNpE+gSNS2eGxlJW/e43DhRzyw7M1np/5zmYFB9eWmrb6eh QJ7/D2969PqMYbItXouHN+CA3pnQd+GRP00Je9Ks5IbxiWbKC31csny5ymFyIoRabMOB kGaQ== X-Gm-Message-State: AOAM531X2z1u0iV8MmuGDLVUGIrrn3xJMVvdi83UbKbBK6uXkKnHHbET 4nZzKKow0J2wJW7fEMIGhKyoV8ThKvfKmi0yrlM= X-Google-Smtp-Source: ABdhPJzcq3eoBhDZ2b5+lw46fl0RPclCovg50g49UBs5csgPlYIiJ8kjVdePKg32AJBpb1t+cUsAuBCS4wokwTDWp6U= X-Received: by 2002:a63:4e4f:: with SMTP id o15mr33045814pgl.208.1622626767063; Wed, 02 Jun 2021 02:39:27 -0700 (PDT) MIME-Version: 1.0 References: <327e4008-b29f-f5b7-bb30-532fa52c797f@gmail.com> <7f19e3c7-b6b2-5200-95eb-3fed8d22a6b3@daenzer.net> In-Reply-To: From: =?UTF-8?B?TWFyZWsgT2zFocOhaw==?= Date: Wed, 2 Jun 2021 05:38:51 -0400 Message-ID: Subject: Re: [Mesa-dev] Linux Graphics Next: Userspace submission update To: Daniel Stone Content-Type: multipart/alternative; boundary="0000000000000dcfbf05c3c53ca4" X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: =?UTF-8?Q?Christian_K=C3=B6nig?= , =?UTF-8?Q?Michel_D=C3=A4nzer?= , dri-devel , Jason Ekstrand , ML Mesa-dev Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" --0000000000000dcfbf05c3c53ca4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 2, 2021 at 5:34 AM Marek Ol=C5=A1=C3=A1k wro= te: > Yes, we can't break anything because we don't want to complicate things > for us. It's pretty much all NAK'd already. We are trying to gather more > knowledge and then make better decisions. > > The idea we are considering is that we'll expose memory-based sync object= s > to userspace for read only, and the kernel or hw will strictly control th= e > memory writes to those sync objects. The hole in that idea is that > userspace can decide not to signal a job, so even if userspace can't > overwrite memory-based sync object states arbitrarily, it can still decid= e > not to signal them, and then a future fence is born. > This would actually be treated as a GPU hang caused by that context, so it should be fine. Marek --0000000000000dcfbf05c3c53ca4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, Jun 2, 2021 at 5:34 AM Marek Ol=C5=A1=C3=A1k <maraeo@gmail.com> wrote:
Yes, we = can't break anything because we don't want to complicate things for= us. It's pretty much all NAK'd already. We are trying to gather mo= re knowledge and then make better decisions.

The i= dea we are considering is that we'll expose memory-based sync objects t= o userspace for read only, and the kernel or hw will strictly control the m= emory writes to those sync objects. The hole in that idea is that userspace= can decide not to signal a job, so even if userspace can't overwrite m= emory-based sync object states arbitrarily, it can still decide not to sign= al them, and then a future fence is born.

=
This would actually be treated as a GPU hang caused by that cont= ext, so it should be fine.

Marek
--0000000000000dcfbf05c3c53ca4--