From: Dmitry Osipenko <digetx@gmail.com>
To: Mikko Perttunen <cyndis@kapsi.fi>,
Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
sumit.semwal@linaro.org, gustavo@padovan.org
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
talho@nvidia.com, bhuntsman@nvidia.com,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RFC] Host1x/TegraDRM UAPI
Date: Wed, 24 Jun 2020 23:55:25 +0300 [thread overview]
Message-ID: <867dea06-8741-82e8-3e26-9a017ad9057a@gmail.com> (raw)
In-Reply-To: <9b06b7ec-f952-2561-7afb-5653514cd5d3@kapsi.fi>
23.06.2020 15:09, Mikko Perttunen пишет:
...
> * Previously present GEM IOCTLs (GEM_CREATE, GEM_MMAP) are not present.
> Not sure if they are still needed.
Hello Mikko!
A quick comment for the starter. Switching away from the Tegra-specific
GEM IOCTLs to the dma-buf heaps is a such radical change! But I like it!
Previously I was curious about whether we could have multiple CMA
regions (one shared/reusable and other private, for example) for the
Tegra DRM driver and at a quick glance the dma-buf heaps could be a nice
solution that avoids re-inventing a driver-specific things for that.
I'm instantly foreseeing these types of heaps:
1. Large reusable CMA heap.
2. Smaller non-reusable common CMA that could be used when allocation
from a reusable CMA fails. Or vice versa, when we want to reduce the
chance to block for a long time on allocation, for example.
3. Sparse (system) memory heap.
It's the first time I'm looking at the dma-buf heaps and it sounds like
a very nice idea to utilize them!
The https://lkml.org/lkml/2019/11/18/787 says that the system-contiguous
and carveout heaps we not added because they were not needed, but they
will be needed for the Tegra20 drivers and for the case where IOMMU is
disabled. It shouldn't be difficult to add these types of heaps.
I'll continue to examine the dma-buf heaps in a more details.
_______________________________________________
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-25 7:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 12:09 [RFC] Host1x/TegraDRM UAPI Mikko Perttunen
2020-06-24 20:55 ` Dmitry Osipenko [this message]
2020-06-25 9:17 ` Mikko Perttunen
2020-06-24 22:33 ` Dmitry Osipenko
2020-06-25 9:27 ` Mikko Perttunen
2020-06-25 22:50 ` [RFC] Host1x/TegraDRM UAPI (drm_tegra_submit_relocation) Dmitry Osipenko
2020-06-26 9:01 ` Mikko Perttunen
2020-06-24 23:11 ` [RFC] Host1x/TegraDRM UAPI Dmitry Osipenko
2020-06-25 9:16 ` Mikko Perttunen
2020-06-25 23:24 ` Dmitry Osipenko
2020-06-26 9:05 ` Mikko Perttunen
2020-06-24 23:18 ` Dmitry Osipenko
2020-06-25 0:59 ` Dmitry Osipenko
2020-06-24 23:23 ` Dmitry Osipenko
2020-06-25 9:19 ` Mikko Perttunen
2020-06-25 0:47 ` Dmitry Osipenko
2020-06-25 9:23 ` Mikko Perttunen
2020-06-25 22:47 ` [RFC] Host1x/TegraDRM UAPI (drm_tegra_channel_map) Dmitry Osipenko
2020-06-26 7:34 ` Thierry Reding
2020-06-26 16:35 ` Dmitry Osipenko
2020-06-28 11:16 ` Mikko Perttunen
2020-06-28 22:59 ` Dmitry Osipenko
2020-06-30 10:55 ` Mikko Perttunen
2020-06-30 19:48 ` Dmitry Osipenko
2020-06-26 11:06 ` [RFC] Host1x/TegraDRM UAPI Karol Herbst
2020-06-26 11:13 ` Mikko Perttunen
2020-06-26 11:16 ` Karol Herbst
2020-06-26 11:40 ` Thierry Reding
2020-06-26 13:38 ` Daniel Vetter
2020-06-26 13:59 ` Dmitry Osipenko
2020-06-30 9:09 ` Daniel Vetter
2020-06-27 21:47 ` [RFC] Host1x/TegraDRM UAPI (drm_tegra_submit_syncpt_incr) Dmitry Osipenko
2020-06-28 11:10 ` Mikko Perttunen
2020-06-27 22:32 ` [RFC] Host1x/TegraDRM UAPI (drm_tegra_submit_command) Dmitry Osipenko
2020-06-28 10:28 ` Mikko Perttunen
2020-06-29 0:00 ` Dmitry Osipenko
2020-06-30 10:40 ` Mikko Perttunen
2020-06-27 23:27 ` [RFC] Host1x/TegraDRM UAPI (sync points) Dmitry Osipenko
2020-06-28 9:44 ` Mikko Perttunen
2020-06-29 2:36 ` Dmitry Osipenko
2020-06-29 10:27 ` Mikko Perttunen
2020-06-29 19:28 ` Dmitry Osipenko
2020-06-29 19:33 ` Dmitry Osipenko
2020-06-29 19:42 ` Dmitry Osipenko
2020-06-30 10:26 ` Mikko Perttunen
2020-07-01 0:22 ` Dmitry Osipenko
2020-07-02 12:10 ` Mikko Perttunen
2020-07-07 11:06 ` Dmitry Osipenko
2020-07-08 10:06 ` Mikko Perttunen
2020-07-09 9:28 ` Dmitry Osipenko
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=867dea06-8741-82e8-3e26-9a017ad9057a@gmail.com \
--to=digetx@gmail.com \
--cc=airlied@linux.ie \
--cc=bhuntsman@nvidia.com \
--cc=cyndis@kapsi.fi \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=talho@nvidia.com \
--cc=thierry.reding@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 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).