From: Daniel Stone <daniel@fooishbar.org>
To: "Marek Olšák" <maraeo@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v3] drm/fourcc: document modifier uniqueness requirements
Date: Thu, 4 Jun 2020 10:14:24 +0100 [thread overview]
Message-ID: <CAPj87rNw7w3itcWiA0A1GGWRW4jhuHBzCkWYPJoRxhU4xoTcXw@mail.gmail.com> (raw)
In-Reply-To: <CAAxE2A4wE0Q4NCQHmQhCa3nQn8VHWngtmuhg2DBtQYsCncTSFw@mail.gmail.com>
On Wed, 3 Jun 2020 at 19:53, Marek Olšák <maraeo@gmail.com> wrote:
> TMZ is more complicated. If there is a TMZ buffer used by a command buffer, then all other used buffers must also be TMZ or read only. If no TMZ buffers are used by a command buffer, then TMZ is disabled. If a context is not secure, TMZ is also disabled. A context can switch between secure and non-secure based on the buffers being used.
>
> So mixing secure and non-secure memory writes in one command buffer won't work. This is not fixable in the driver - apps must be aware of this.
Sure, that makes sense. It probably points to TMZ being its own
special thing, independent of modifiers, since it touches so much
global state, and doesn't mesh cleanly any of the models we have for
advertising and negotiating buffer allocation and import.
Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-06-04 9:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 14:38 [PATCH v3] drm/fourcc: document modifier uniqueness requirements Simon Ser
2020-05-28 15:49 ` Marek Olšák
2020-05-29 8:59 ` Simon Ser
2020-05-29 13:28 ` Alex Deucher
2020-05-29 13:43 ` Daniel Vetter
2020-05-29 13:56 ` Daniel Stone
2020-05-29 14:29 ` Alex Deucher
2020-05-29 14:30 ` Daniel Stone
2020-05-29 14:36 ` Alex Deucher
2020-05-29 15:01 ` Daniel Stone
2020-05-29 15:31 ` Alex Deucher
2020-05-30 13:08 ` Michel Dänzer
2020-06-01 14:25 ` Alex Deucher
2020-06-03 9:48 ` Daniel Stone
2020-06-03 18:53 ` Marek Olšák
2020-06-04 9:14 ` Daniel Stone [this message]
2020-06-01 13:43 ` Neil Armstrong
2020-06-01 11:01 ` Brian Starkey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPj87rNw7w3itcWiA0A1GGWRW4jhuHBzCkWYPJoRxhU4xoTcXw@mail.gmail.com \
--to=daniel@fooishbar.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=maraeo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.