From: Alyssa Rosenzweig <alyssa@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: Jason Ekstrand <jason@jlekstrand.net>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v3 5/7] drm/panfrost: Add a new ioctl to submit batches
Date: Tue, 6 Jul 2021 08:48:44 -0400 [thread overview]
Message-ID: <YORRLPYgX1nbetLG@maud> (raw)
In-Reply-To: <b2002c8c-ebce-0d6b-03d1-d29775db3cc5@arm.com>
> My concern is if we ever find a security bug which requires new
> information/behaviour in the submit ABI to properly fix. In this case it
> would be appropriate to backport a 'feature' (bug fix) which provides a
> new ABI but it would need to be a small change. A flags field where we
> can set a "PANFROST_ACTUALLY_BE_SECURE" bit would be useful then - but
> we wouldn't want to start bumping version numbers in the backport.
>
> But at least for now we could just assume we'll expand the ioctl struct
> if we ever hit that situation, so no need for an explicit flags field.
I'm curious if kbase ever hit something like this? It wouldn't have
occurred to me as a possibility.
next prev parent reply other threads:[~2021-07-06 12:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 14:32 [PATCH v3 0/7] drm/panfrost: drm/panfrost: Add a new submit ioctl Boris Brezillon
2021-07-02 14:32 ` [PATCH v3 1/7] drm/panfrost: Pass a job to panfrost_{acquire, attach}_object_fences() Boris Brezillon
2021-07-02 14:32 ` [PATCH v3 2/7] drm/panfrost: Move the mappings collection out of panfrost_lookup_bos() Boris Brezillon
2021-07-02 14:32 ` [PATCH v3 3/7] drm/panfrost: Add BO access flags to relax dependencies between jobs Boris Brezillon
2021-07-02 14:32 ` [PATCH v3 4/7] drm/panfrost: Add the ability to create submit queues Boris Brezillon
2021-07-02 15:05 ` Steven Price
2021-07-02 15:49 ` Boris Brezillon
2021-07-02 16:01 ` Boris Brezillon
2021-07-02 14:32 ` [PATCH v3 5/7] drm/panfrost: Add a new ioctl to submit batches Boris Brezillon
2021-07-02 15:13 ` Alyssa Rosenzweig
2021-07-02 15:38 ` Boris Brezillon
2021-07-02 16:49 ` Alyssa Rosenzweig
2021-07-02 17:54 ` Boris Brezillon
2021-07-02 18:11 ` Boris Brezillon
2021-07-05 8:22 ` Steven Price
2021-07-05 8:43 ` Boris Brezillon
2021-07-05 8:51 ` Steven Price
2021-07-06 12:48 ` Alyssa Rosenzweig [this message]
2021-07-07 9:09 ` Steven Price
2021-07-02 15:31 ` Steven Price
2021-07-02 15:34 ` Alyssa Rosenzweig
2021-07-02 14:32 ` [PATCH v3 6/7] drm/panfrost: Advertise the SYNCOBJ_TIMELINE feature Boris Brezillon
2021-07-02 14:32 ` [PATCH v3 7/7] drm/panfrost: Bump minor version to reflect the feature additions Boris Brezillon
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=YORRLPYgX1nbetLG@maud \
--to=alyssa@collabora.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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.