From: "Andrew F. Davis" <afd@ti.com> To: John Stultz <john.stultz@linaro.org> Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>, lkml <linux-kernel@vger.kernel.org>, Laura Abbott <labbott@redhat.com>, Greg KH <gregkh@linuxfoundation.org>, Sumit Semwal <sumit.semwal@linaro.org>, Liam Mark <lmark@codeaurora.org>, Brian Starkey <Brian.Starkey@arm.com>, Chenbo Feng <fengc@google.com>, Alistair Strachan <astrachan@google.com>, ML dri-devel <dri-devel@lists.freedesktop.org> Subject: Re: [RFC][PATCH 5/5 v2] kselftests: Add dma-heap test Date: Wed, 6 Mar 2019 12:32:53 -0600 [thread overview] Message-ID: <5fbeb711-62f9-1619-cc50-15594713551f@ti.com> (raw) In-Reply-To: <CALAqxLU9aq6Qj1qJKQK=a5AbnLc1Hwxvb0nX9JemoW=29gDVoA@mail.gmail.com> On 3/6/19 12:19 PM, John Stultz wrote: > On Wed, Mar 6, 2019 at 10:15 AM Andrew F. Davis <afd@ti.com> wrote: >> >> On 3/6/19 10:14 AM, Benjamin Gaignard wrote: >>> Le mar. 5 mars 2019 à 21:54, John Stultz <john.stultz@linaro.org> a écrit : >>>> >>>> Add very trivial allocation test for dma-heaps. >>>> >>>> TODO: Need to actually do some validation on >>>> the returned dma-buf. >>>> >>>> Cc: Laura Abbott <labbott@redhat.com> >>>> Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org> >>>> Cc: Greg KH <gregkh@linuxfoundation.org> >>>> Cc: Sumit Semwal <sumit.semwal@linaro.org> >>>> Cc: Liam Mark <lmark@codeaurora.org> >>>> Cc: Brian Starkey <Brian.Starkey@arm.com> >>>> Cc: Andrew F. Davis <afd@ti.com> >>>> Cc: Chenbo Feng <fengc@google.com> >>>> Cc: Alistair Strachan <astrachan@google.com> >>>> Cc: dri-devel@lists.freedesktop.org >>>> Signed-off-by: John Stultz <john.stultz@linaro.org> >>>> --- >>>> v2: Switched to use reworked dma-heap apis >>>> --- >>>> tools/testing/selftests/dmabuf-heaps/Makefile | 11 +++ >>>> tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c | 96 ++++++++++++++++++++++ >>>> 2 files changed, 107 insertions(+) >>>> create mode 100644 tools/testing/selftests/dmabuf-heaps/Makefile >>>> create mode 100644 tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c >>>> >>>> diff --git a/tools/testing/selftests/dmabuf-heaps/Makefile b/tools/testing/selftests/dmabuf-heaps/Makefile >>>> new file mode 100644 >>>> index 0000000..c414ad3 >>>> --- /dev/null >>>> +++ b/tools/testing/selftests/dmabuf-heaps/Makefile >>>> @@ -0,0 +1,11 @@ >>>> +# SPDX-License-Identifier: GPL-2.0 >>>> +CFLAGS += -static -O3 -Wl,-no-as-needed -Wall >>>> +#LDLIBS += -lrt -lpthread -lm >>>> + >>>> +# these are all "safe" tests that don't modify >>>> +# system time or require escalated privileges >>>> +TEST_GEN_PROGS = dmabuf-heap >>>> + >>>> + >>>> +include ../lib.mk >>>> + >>>> diff --git a/tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c b/tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c >>>> new file mode 100644 >>>> index 0000000..06837a4 >>>> --- /dev/null >>>> +++ b/tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c >>>> @@ -0,0 +1,96 @@ >>>> +// SPDX-License-Identifier: GPL-2.0 >>>> + >>>> +#include <dirent.h> >>>> +#include <errno.h> >>>> +#include <fcntl.h> >>>> +#include <stdio.h> >>>> +#include <string.h> >>>> +#include <unistd.h> >>>> +#include <sys/ioctl.h> >>>> +#include <sys/mman.h> >>>> +#include <sys/types.h> >>>> + >>>> +#include "../../../../include/uapi/linux/dma-heap.h" >>>> + >>>> +#define DEVPATH "/dev/dma_heap" >>>> + >>>> +int dmabuf_heap_open(char *name) >>>> +{ >>>> + int ret, fd; >>>> + char buf[256]; >>>> + >>>> + ret = sprintf(buf, "%s/%s", DEVPATH, name); >>>> + if (ret < 0) { >>>> + printf("sprintf failed!\n"); >>>> + return ret; >>>> + } >>>> + >>>> + fd = open(buf, O_RDWR); >>>> + if (fd < 0) >>>> + printf("open %s failed!\n", buf); >>>> + return fd; >>>> +} >>>> + >>>> +int dmabuf_heap_alloc(int fd, size_t len, unsigned int flags, int *dmabuf_fd) >>>> +{ >>>> + struct dma_heap_allocation_data data = { >>>> + .len = len, >>>> + .flags = flags, >>>> + }; >>>> + int ret; >>>> + >>>> + if (dmabuf_fd == NULL) >>>> + return -EINVAL; >>>> + >>>> + ret = ioctl(fd, DMA_HEAP_IOC_ALLOC, &data); >>>> + if (ret < 0) >>>> + return ret; >>>> + *dmabuf_fd = (int)data.fd; >>>> + return ret; >>>> +} >>>> + >>>> +#define ONE_MEG (1024*1024) >>>> + >>>> +void do_test(char *heap_name) >>>> +{ >>>> + int heap_fd = -1, dmabuf_fd = -1; >>>> + int ret; >>>> + >>>> + printf("Testing heap: %s\n", heap_name); >>>> + >>>> + heap_fd = dmabuf_heap_open(heap_name); >>>> + if (heap_fd < 0) >>>> + return; >>>> + >>>> + printf("Allocating 1 MEG\n"); >>>> + ret = dmabuf_heap_alloc(heap_fd, ONE_MEG, 0, &dmabuf_fd); >>>> + if (ret) >>>> + goto out; >>>> + >>>> + /* DO SOMETHING WITH THE DMABUF HERE? */ >>> >>> You can do a call to mmap and write a pattern in the buffer. >>> >> >> mmap is optional for DMA-BUFs, only attach/map are required. To test >> those we would need a dummy device, so a test kernel module may be >> needed to really exercise this. >> >> I have one I use for ION buffer testing, it consumes a DMA-BUF passed >> from userspace, attach/maps it to a dummy device then return the >> physical address of the first page of the buffer for validation. Might >> be a good test, but dummy devices don't always have the proper dma >> attributes set like a real device does, so it may also fail for some >> otherwise valid buffers. > > Cool! Do you mind sharing that? I might try to rework and integrate it > into this patchset? > Sure, top two patches here: > https://git.ti.com/ti-analog-linux-kernel/afd-analog/commits/dma-buf-to-phys Andrew > thanks > -john >
WARNING: multiple messages have this Message-ID (diff)
From: "Andrew F. Davis" <afd@ti.com> To: John Stultz <john.stultz@linaro.org> Cc: Alistair Strachan <astrachan@google.com>, Greg KH <gregkh@linuxfoundation.org>, Chenbo Feng <fengc@google.com>, lkml <linux-kernel@vger.kernel.org>, Liam Mark <lmark@codeaurora.org>, ML dri-devel <dri-devel@lists.freedesktop.org> Subject: Re: [RFC][PATCH 5/5 v2] kselftests: Add dma-heap test Date: Wed, 6 Mar 2019 12:32:53 -0600 [thread overview] Message-ID: <5fbeb711-62f9-1619-cc50-15594713551f@ti.com> (raw) In-Reply-To: <CALAqxLU9aq6Qj1qJKQK=a5AbnLc1Hwxvb0nX9JemoW=29gDVoA@mail.gmail.com> On 3/6/19 12:19 PM, John Stultz wrote: > On Wed, Mar 6, 2019 at 10:15 AM Andrew F. Davis <afd@ti.com> wrote: >> >> On 3/6/19 10:14 AM, Benjamin Gaignard wrote: >>> Le mar. 5 mars 2019 à 21:54, John Stultz <john.stultz@linaro.org> a écrit : >>>> >>>> Add very trivial allocation test for dma-heaps. >>>> >>>> TODO: Need to actually do some validation on >>>> the returned dma-buf. >>>> >>>> Cc: Laura Abbott <labbott@redhat.com> >>>> Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org> >>>> Cc: Greg KH <gregkh@linuxfoundation.org> >>>> Cc: Sumit Semwal <sumit.semwal@linaro.org> >>>> Cc: Liam Mark <lmark@codeaurora.org> >>>> Cc: Brian Starkey <Brian.Starkey@arm.com> >>>> Cc: Andrew F. Davis <afd@ti.com> >>>> Cc: Chenbo Feng <fengc@google.com> >>>> Cc: Alistair Strachan <astrachan@google.com> >>>> Cc: dri-devel@lists.freedesktop.org >>>> Signed-off-by: John Stultz <john.stultz@linaro.org> >>>> --- >>>> v2: Switched to use reworked dma-heap apis >>>> --- >>>> tools/testing/selftests/dmabuf-heaps/Makefile | 11 +++ >>>> tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c | 96 ++++++++++++++++++++++ >>>> 2 files changed, 107 insertions(+) >>>> create mode 100644 tools/testing/selftests/dmabuf-heaps/Makefile >>>> create mode 100644 tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c >>>> >>>> diff --git a/tools/testing/selftests/dmabuf-heaps/Makefile b/tools/testing/selftests/dmabuf-heaps/Makefile >>>> new file mode 100644 >>>> index 0000000..c414ad3 >>>> --- /dev/null >>>> +++ b/tools/testing/selftests/dmabuf-heaps/Makefile >>>> @@ -0,0 +1,11 @@ >>>> +# SPDX-License-Identifier: GPL-2.0 >>>> +CFLAGS += -static -O3 -Wl,-no-as-needed -Wall >>>> +#LDLIBS += -lrt -lpthread -lm >>>> + >>>> +# these are all "safe" tests that don't modify >>>> +# system time or require escalated privileges >>>> +TEST_GEN_PROGS = dmabuf-heap >>>> + >>>> + >>>> +include ../lib.mk >>>> + >>>> diff --git a/tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c b/tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c >>>> new file mode 100644 >>>> index 0000000..06837a4 >>>> --- /dev/null >>>> +++ b/tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c >>>> @@ -0,0 +1,96 @@ >>>> +// SPDX-License-Identifier: GPL-2.0 >>>> + >>>> +#include <dirent.h> >>>> +#include <errno.h> >>>> +#include <fcntl.h> >>>> +#include <stdio.h> >>>> +#include <string.h> >>>> +#include <unistd.h> >>>> +#include <sys/ioctl.h> >>>> +#include <sys/mman.h> >>>> +#include <sys/types.h> >>>> + >>>> +#include "../../../../include/uapi/linux/dma-heap.h" >>>> + >>>> +#define DEVPATH "/dev/dma_heap" >>>> + >>>> +int dmabuf_heap_open(char *name) >>>> +{ >>>> + int ret, fd; >>>> + char buf[256]; >>>> + >>>> + ret = sprintf(buf, "%s/%s", DEVPATH, name); >>>> + if (ret < 0) { >>>> + printf("sprintf failed!\n"); >>>> + return ret; >>>> + } >>>> + >>>> + fd = open(buf, O_RDWR); >>>> + if (fd < 0) >>>> + printf("open %s failed!\n", buf); >>>> + return fd; >>>> +} >>>> + >>>> +int dmabuf_heap_alloc(int fd, size_t len, unsigned int flags, int *dmabuf_fd) >>>> +{ >>>> + struct dma_heap_allocation_data data = { >>>> + .len = len, >>>> + .flags = flags, >>>> + }; >>>> + int ret; >>>> + >>>> + if (dmabuf_fd == NULL) >>>> + return -EINVAL; >>>> + >>>> + ret = ioctl(fd, DMA_HEAP_IOC_ALLOC, &data); >>>> + if (ret < 0) >>>> + return ret; >>>> + *dmabuf_fd = (int)data.fd; >>>> + return ret; >>>> +} >>>> + >>>> +#define ONE_MEG (1024*1024) >>>> + >>>> +void do_test(char *heap_name) >>>> +{ >>>> + int heap_fd = -1, dmabuf_fd = -1; >>>> + int ret; >>>> + >>>> + printf("Testing heap: %s\n", heap_name); >>>> + >>>> + heap_fd = dmabuf_heap_open(heap_name); >>>> + if (heap_fd < 0) >>>> + return; >>>> + >>>> + printf("Allocating 1 MEG\n"); >>>> + ret = dmabuf_heap_alloc(heap_fd, ONE_MEG, 0, &dmabuf_fd); >>>> + if (ret) >>>> + goto out; >>>> + >>>> + /* DO SOMETHING WITH THE DMABUF HERE? */ >>> >>> You can do a call to mmap and write a pattern in the buffer. >>> >> >> mmap is optional for DMA-BUFs, only attach/map are required. To test >> those we would need a dummy device, so a test kernel module may be >> needed to really exercise this. >> >> I have one I use for ION buffer testing, it consumes a DMA-BUF passed >> from userspace, attach/maps it to a dummy device then return the >> physical address of the first page of the buffer for validation. Might >> be a good test, but dummy devices don't always have the proper dma >> attributes set like a real device does, so it may also fail for some >> otherwise valid buffers. > > Cool! Do you mind sharing that? I might try to rework and integrate it > into this patchset? > Sure, top two patches here: > https://git.ti.com/ti-analog-linux-kernel/afd-analog/commits/dma-buf-to-phys Andrew > thanks > -john > _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-06 18:33 UTC|newest] Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-05 20:54 [RFC][PATCH 0/5 v2] DMA-BUF Heaps (destaging ION) John Stultz 2019-03-05 20:54 ` John Stultz 2019-03-05 20:54 ` [RFC][PATCH 1/5 v2] dma-buf: Add dma-buf heaps framework John Stultz 2019-03-05 20:54 ` John Stultz 2019-03-06 16:12 ` Benjamin Gaignard 2019-03-06 16:57 ` John Stultz 2019-03-15 8:55 ` Christoph Hellwig 2019-03-06 16:27 ` Andrew F. Davis 2019-03-06 16:27 ` Andrew F. Davis 2019-03-06 19:03 ` John Stultz 2019-03-06 21:45 ` Andrew F. Davis 2019-03-06 21:45 ` Andrew F. Davis 2019-03-15 8:54 ` Christoph Hellwig 2019-03-15 20:24 ` Andrew F. Davis 2019-03-15 20:24 ` Andrew F. Davis 2019-03-15 20:18 ` Laura Abbott 2019-03-15 20:49 ` Andrew F. Davis 2019-03-15 20:49 ` Andrew F. Davis 2019-03-15 21:29 ` John Stultz 2019-03-15 22:44 ` Laura Abbott 2019-03-18 4:38 ` Sumit Semwal 2019-03-18 4:41 ` Sumit Semwal 2019-03-18 4:41 ` Sumit Semwal 2019-03-19 12:08 ` Brian Starkey 2019-03-19 15:24 ` Andrew F. Davis 2019-03-19 15:24 ` Andrew F. Davis 2019-03-21 21:16 ` John Stultz 2019-03-21 21:16 ` John Stultz 2019-03-27 14:53 ` Greg KH 2019-03-27 14:53 ` Greg KH 2019-03-28 6:09 ` John Stultz 2019-03-05 20:54 ` [RFC][PATCH 2/5 v2] dma-buf: heaps: Add heap helpers John Stultz 2019-03-05 20:54 ` John Stultz 2019-03-13 20:18 ` Liam Mark 2019-03-13 20:18 ` Liam Mark 2019-03-13 21:48 ` Andrew F. Davis 2019-03-13 21:48 ` Andrew F. Davis 2019-03-13 22:57 ` Liam Mark 2019-03-13 23:42 ` Andrew F. Davis 2019-03-13 23:42 ` Andrew F. Davis 2019-03-15 9:06 ` Christoph Hellwig 2019-03-19 15:03 ` Andrew F. Davis 2019-03-19 15:03 ` Andrew F. Davis 2019-03-21 20:01 ` John Stultz 2019-03-19 14:26 ` Brian Starkey 2019-03-21 20:11 ` John Stultz 2019-03-21 20:11 ` John Stultz 2019-03-21 20:35 ` Andrew F. Davis 2019-03-21 20:43 ` Andrew F. Davis 2019-03-21 20:43 ` Andrew F. Davis 2019-03-05 20:54 ` [RFC][PATCH 3/5 v2] dma-buf: heaps: Add system heap to dmabuf heaps John Stultz 2019-03-06 16:01 ` Benjamin Gaignard 2019-03-11 5:48 ` John Stultz 2019-03-11 5:48 ` John Stultz 2019-03-13 20:20 ` Liam Mark 2019-03-13 22:49 ` John Stultz 2019-03-15 9:06 ` Christoph Hellwig 2019-03-05 20:54 ` [RFC][PATCH 4/5 v2] dma-buf: heaps: Add CMA heap to dmabuf heapss John Stultz 2019-03-06 16:05 ` Benjamin Gaignard 2019-03-21 20:15 ` John Stultz 2019-03-15 9:06 ` Christoph Hellwig 2019-03-15 20:08 ` John Stultz 2019-03-15 20:08 ` John Stultz 2019-03-19 14:53 ` Brian Starkey 2019-03-05 20:54 ` [RFC][PATCH 5/5 v2] kselftests: Add dma-heap test John Stultz 2019-03-05 20:54 ` John Stultz 2019-03-06 16:14 ` Benjamin Gaignard 2019-03-06 16:35 ` Andrew F. Davis 2019-03-06 16:35 ` Andrew F. Davis 2019-03-06 18:19 ` John Stultz 2019-03-06 18:19 ` John Stultz 2019-03-06 18:32 ` Andrew F. Davis [this message] 2019-03-06 18:32 ` Andrew F. Davis 2019-03-06 17:01 ` John Stultz 2019-03-06 17:01 ` John Stultz 2019-03-15 20:07 ` Laura Abbott 2019-03-15 20:13 ` John Stultz 2019-03-15 20:49 ` Laura Abbott 2019-03-15 20:49 ` Laura Abbott 2019-03-13 20:23 ` Liam Mark 2019-03-13 20:11 ` [RFC][PATCH 0/5 v2] DMA-BUF Heaps (destaging ION) Liam Mark 2019-03-13 22:30 ` John Stultz 2019-03-13 22:30 ` John Stultz 2019-03-13 23:29 ` Liam Mark 2019-03-19 16:54 ` Benjamin Gaignard 2019-03-19 16:59 ` Andrew F. Davis 2019-03-19 16:59 ` Andrew F. Davis 2019-03-19 21:58 ` Rob Clark 2019-03-19 21:58 ` Rob Clark 2019-03-19 22:36 ` John Stultz 2019-03-20 9:16 ` Benjamin Gaignard 2019-03-20 14:44 ` Andrew F. Davis 2019-03-20 15:59 ` Benjamin Gaignard 2019-03-20 16:11 ` John Stultz 2019-03-15 20:34 ` Laura Abbott 2019-03-15 23:15 ` Jerome Glisse 2019-03-16 0:16 ` John Stultz 2019-03-16 0:16 ` John Stultz
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=5fbeb711-62f9-1619-cc50-15594713551f@ti.com \ --to=afd@ti.com \ --cc=Brian.Starkey@arm.com \ --cc=astrachan@google.com \ --cc=benjamin.gaignard@linaro.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=fengc@google.com \ --cc=gregkh@linuxfoundation.org \ --cc=john.stultz@linaro.org \ --cc=labbott@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lmark@codeaurora.org \ --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: linkBe 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.