From: Philipp Zabel <p.zabel@pengutronix.de>
To: "Guido Günther" <agx@sigxcpu.org>,
"Lucas Stach" <l.stach@pengutronix.de>
Cc: etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
patchwork-lst@pengutronix.de, kernel@pengutronix.de,
Russell King <linux+etnaviv@armlinux.org.uk>
Subject: Re: [PATCH v2 2/8] drm/etnaviv: split out cmdbuf mapping into address space
Date: Fri, 02 Aug 2019 16:21:53 +0200 [thread overview]
Message-ID: <1564755713.3090.3.camel@pengutronix.de> (raw)
In-Reply-To: <20190802133900.GA3251@bogon.m.sigxcpu.org>
Hi Guido,
On Fri, 2019-08-02 at 15:39 +0200, Guido Günther wrote:
> Hi Lucas,
> On Fri, Jul 05, 2019 at 07:17:21PM +0200, Lucas Stach wrote:
> > This allows to decouple the cmdbuf suballocator create and mapping
> > the region into the GPU address space. Allowing multiple AS to share
> > a single cmdbuf suballoc.
>
> Can you tell me where this would apply? I tried 5.2 and next-20190726
> with and without
>
> [PATCH 1/2] drm/etnaviv: fix etnaviv_cmdbuf_suballoc_new return value
I have stacked
drm/etnaviv: drop use of drmP.h
drm/etnaviv: Use
devm_platform_ioremap_resource()
drm/etnaviv: clean up includes
drm/etnaviv: fix
etnaviv_cmdbuf_suballoc_new return value
drm/etnaviv: remove unused function etnaviv_gem_mapping_reference
drm/etnaviv: dump only failing submit
drm/etnaviv: simplify unbind checks
on top of v5.3-r1 and this patch applied with a bit of fuzz.
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-02 14:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 17:17 [PATCH v2 1/8] drm/etnaviv: simplify unbind checks Lucas Stach
2019-07-05 17:17 ` [PATCH v2 2/8] drm/etnaviv: split out cmdbuf mapping into address space Lucas Stach
2019-07-24 13:51 ` Philipp Zabel
2019-08-02 13:39 ` Guido Günther
2019-08-02 14:21 ` Philipp Zabel [this message]
2019-08-02 18:23 ` Guido Günther
2019-08-02 18:40 ` Guido Günther
2019-08-08 10:26 ` Guido Günther
2019-08-09 9:17 ` Lucas Stach
2019-08-09 9:28 ` Guido Günther
2019-07-05 17:17 ` [PATCH v2 3/8] drm/etnaviv: share a single cmdbuf suballoc region across all GPUs Lucas Stach
2019-07-24 15:37 ` Philipp Zabel
2019-07-05 17:17 ` [PATCH v2 4/8] drm/etnaviv: replace MMU flush marker with flush sequence Lucas Stach
2019-07-24 15:45 ` Philipp Zabel
2019-08-13 15:27 ` Guido Günther
2019-07-05 17:17 ` [PATCH v2 5/8] drm/etnaviv: rework MMU handling Lucas Stach
2019-07-29 15:35 ` Philipp Zabel
2019-07-05 17:17 ` [PATCH v2 6/8] drm/etnaviv: split out starting of FE idle loop Lucas Stach
2019-07-29 15:36 ` Philipp Zabel
2019-07-05 17:17 ` [PATCH v2 7/8] drm/etnaviv: provide MMU context to etnaviv_gem_mapping_get Lucas Stach
2019-07-29 15:38 ` Philipp Zabel
2019-07-05 17:17 ` [PATCH v2 8/8] drm/etnaviv: implement per-process address spaces on MMUv2 Lucas Stach
2019-07-30 9:44 ` Philipp Zabel
2019-07-24 12:11 ` [PATCH v2 1/8] drm/etnaviv: simplify unbind checks Philipp Zabel
2019-08-02 8:14 ` Guido Günther
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=1564755713.3090.3.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=agx@sigxcpu.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=patchwork-lst@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).