From: Rob Clark <robdclark@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Linaro MM SIG Mailman List <linaro-mm-sig@lists.linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Tomasz Stanislawski <stanislawski.tomasz@googlemail.com>,
Robin Murphy <robin.murphy@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [RFCv3 2/2] dma-buf: add helpers for sharing attacher constraints with dma-parms
Date: Mon, 2 Feb 2015 17:36:10 -0500 [thread overview]
Message-ID: <CAF6AEGvE78a9u9=C6HbuuYs_zwGf6opdXUNfxb51kixFa7zLwA@mail.gmail.com> (raw)
In-Reply-To: <20150202214616.GI8656@n2100.arm.linux.org.uk>
On Mon, Feb 2, 2015 at 4:46 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Feb 02, 2015 at 03:30:21PM -0500, Rob Clark wrote:
>> On Mon, Feb 2, 2015 at 11:54 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> >> My initial thought is for dma-buf to not try to prevent something than
>> >> an exporter can actually do.. I think the scenario you describe could
>> >> be handled by two sg-lists, if the exporter was clever enough.
>> >
>> > That's already needed, each attachment has it's own sg-list. After all
>> > there's no array of dma_addr_t in the sg tables, so you can't use one sg
>> > for more than one mapping. And due to different iommu different devices
>> > can easily end up with different addresses.
>>
>>
>> Well, to be fair it may not be explicitly stated, but currently one
>> should assume the dma_addr_t's in the dmabuf sglist are bogus. With
>> gpu's that implement per-process/context page tables, I'm not really
>> sure that there is a sane way to actually do anything else..
>
> That's incorrect - and goes dead against the design of scatterlists.
yeah, a bit of an abuse, although I'm not sure I see a much better way
when a device vaddr depends on user context..
> Not only that, but it is entirely possible that you may get handed
> memory via dmabufs for which there are no struct page's associated
> with that memory - think about display systems which have their own
> video memory which is accessible to the GPU, but it isn't system
> memory.
well, I guess anyways when it comes to sharing buffers, it won't be
the vram placement of the bo that gets shared ;-)
BR,
-R
> In those circumstances, you have to use the dma_addr_t's and not the
> pages.
>
> --
> FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
> according to speedtest.net.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-02-02 22:36 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 8:25 [RFCv3 1/2] device: add dma_params->max_segment_count Sumit Semwal
2015-01-27 8:25 ` [RFCv3 2/2] dma-buf: add helpers for sharing attacher constraints with dma-parms Sumit Semwal
2015-01-29 14:16 ` Maarten Lankhorst
2015-01-29 14:39 ` Russell King - ARM Linux
2015-01-29 15:30 ` Sumit Semwal
2015-01-29 15:47 ` Russell King - ARM Linux
2015-01-29 16:55 ` Sumit Semwal
2015-01-29 18:52 ` Rob Clark
2015-01-29 19:26 ` Russell King - ARM Linux
2015-01-29 22:18 ` Rob Clark
2015-01-29 22:31 ` Russell King - ARM Linux
2015-01-29 23:19 ` Rob Clark
2015-02-02 16:54 ` Daniel Vetter
2015-02-02 20:30 ` Rob Clark
2015-02-02 21:46 ` Russell King - ARM Linux
2015-02-02 22:36 ` Rob Clark [this message]
2015-02-03 7:50 ` Daniel Vetter
2015-02-03 7:46 ` Daniel Vetter
2015-02-03 7:48 ` Daniel Vetter
2015-02-03 12:28 ` Russell King - ARM Linux
2015-02-03 13:00 ` Daniel Vetter
2015-02-03 13:28 ` Christian Gmeiner
2015-02-03 14:32 ` Russell King - ARM Linux
2015-02-03 14:25 ` Rob Clark
2015-02-03 14:04 ` Rob Clark
2015-02-03 14:17 ` Arnd Bergmann
2015-02-03 14:41 ` Russell King - ARM Linux
2015-02-03 14:52 ` Arnd Bergmann
2015-02-03 15:22 ` Russell King - ARM Linux
2015-02-03 15:31 ` [Linaro-mm-sig] " Arnd Bergmann
2015-02-03 15:54 ` Russell King - ARM Linux
2015-02-03 16:12 ` Arnd Bergmann
2015-02-03 16:22 ` Rob Clark
2015-02-03 16:36 ` Arnd Bergmann
2015-02-03 20:04 ` Daniel Vetter
2015-02-03 21:42 ` Arnd Bergmann
2015-02-03 22:07 ` Daniel Vetter
2015-02-04 0:14 ` Russell King - ARM Linux
2015-02-03 17:01 ` Russell King - ARM Linux
2015-02-03 16:58 ` Russell King - ARM Linux
2015-02-03 17:35 ` Rob Clark
2015-02-03 20:08 ` Daniel Vetter
2015-02-03 21:44 ` Arnd Bergmann
2015-02-03 15:25 ` Rob Clark
2015-02-03 15:19 ` Rob Clark
2015-02-03 14:37 ` Russell King - ARM Linux
2015-02-03 14:44 ` Rob Clark
2015-02-03 14:58 ` Russell King - ARM Linux
2015-02-02 5:53 ` Sumit Semwal
2015-02-11 8:28 ` Marek Szyprowski
2015-02-11 11:12 ` Russell King - ARM Linux
2015-02-11 11:23 ` Rob Clark
2015-02-11 12:56 ` Daniel Vetter
2015-02-11 13:30 ` Rob Clark
2015-02-11 12:20 ` Marek Szyprowski
2015-02-11 16:23 ` Russell King - ARM Linux
2015-05-05 14:41 ` Sumit Semwal
2015-06-03 6:39 ` [Linaro-mm-sig] " Hans Verkuil
2015-06-03 8:41 ` Russell King - ARM Linux
2015-06-03 9:37 ` Hans Verkuil
2015-06-04 5:24 ` Sumit Semwal
2015-01-28 14:09 ` [RFCv3 1/2] device: add dma_params->max_segment_count Marek Szyprowski
2015-06-03 6:13 ` [Linaro-mm-sig] " Hans Verkuil
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='CAF6AEGvE78a9u9=C6HbuuYs_zwGf6opdXUNfxb51kixFa7zLwA@mail.gmail.com' \
--to=robdclark@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=stanislawski.tomasz@googlemail.com \
--cc=sumit.semwal@linaro.org \
/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).