From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: Steven Price <steven.price@arm.com>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
Robin Murphy <robin.murphy@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: Re: [PATCH 4/5] drm/panfrost: Add support for GPU heap allocations
Date: Mon, 22 Jul 2019 07:12:56 -0700 [thread overview]
Message-ID: <20190722141256.GE2156@rosenzweig.io> (raw)
In-Reply-To: <604cb426-6034-1e92-f653-9ee5a3d4c180@arm.com>
> A fair bit of the complexity of kbase comes from trying to avoid the
> possibility of one process DoSing another by submitting malicious jobs.
...and yet it was still doable so easily (by accident, with buggy jobs
instead of malicious jobs).... sigh...
Still is on the mainline kernel (e.g. running dEQP in a window in
Weston, some faults triggered in dEQP end up messing up Weston's
rendering outside the deqp window). What's our threat model here?
Is "banning WebGL on Panfrost" allowed? :)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-22 14:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 18:33 [PATCH 1/5] drm/panfrost: Restructure the GEM object creation Rob Herring
2019-07-17 18:33 ` [PATCH 2/5] drm/panfrost: Split panfrost_mmu_map SG list mapping to its own function Rob Herring
2019-07-18 15:03 ` Steven Price
2019-07-17 18:33 ` [PATCH 3/5] drm/panfrost: Add a no execute flag for BO allocations Rob Herring
[not found] ` <ecde43d2-45cc-d00a-9635-cb56a67263d4@arm.com>
2019-07-18 17:03 ` Rob Herring
2019-07-19 10:39 ` Steven Price
2019-07-19 22:07 ` Rob Herring
2019-07-22 9:45 ` Steven Price
2019-07-22 9:50 ` Robin Murphy
2019-07-22 10:07 ` Steven Price
2019-07-22 12:09 ` Robin Murphy
2019-07-22 12:19 ` Steven Price
2019-07-22 13:25 ` Robin Murphy
2019-07-22 16:18 ` Rob Herring
2019-07-22 14:08 ` Alyssa Rosenzweig
2019-07-17 18:33 ` [PATCH 4/5] drm/panfrost: Add support for GPU heap allocations Rob Herring
2019-07-18 15:03 ` Steven Price
2019-07-19 14:27 ` Rob Herring
2019-07-19 14:45 ` Steven Price
2019-07-22 14:12 ` Alyssa Rosenzweig [this message]
2019-07-23 9:27 ` Tomeu Vizoso
2019-07-22 14:10 ` Alyssa Rosenzweig
[not found] ` <20190722141536.GF2156@rosenzweig.io>
2019-07-22 16:33 ` Rob Herring
2019-07-17 18:33 ` [PATCH 5/5] drm/panfrost: Bump driver version to 1.1 Rob Herring
[not found] ` <9a01262c-eb29-5e48-cf94-4e9597ea414c@arm.com>
2019-07-19 22:22 ` [PATCH 1/5] drm/panfrost: Restructure the GEM object creation Rob Herring
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=20190722141256.GE2156@rosenzweig.io \
--to=alyssa@rosenzweig.io \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox