From: labbott at redhat.com (Laura Abbott)
Subject: [RFC PATCH 0/2] Ion unit test with VGEM
Date: Thu, 15 Feb 2018 17:24:43 -0800 [thread overview]
Message-ID: <20180216012445.17264-1-labbott@redhat.com> (raw)
Hi,
Ion hasn't had much in the way of unit tests and fixing that is
something that needs to happen before it can move out of staging. The
difficult part of testing parts of Ion is that it relies on having a
kernel driver to actually make some of the dma_buf calls. The vgem
DRM driver exists mostly for testing and works great for this case. I
went back and forth about trying to put this in the existing graphics
test suite but I think having something in the self-tests directory is
easier.
I'm mostly interested in feedback about the use of the DRM APIs but I
appreciate any and all comments.
Thanks,
Laura
Laura Abbott (2):
selftests: ion: Remove some prints
selftests: ion: Add simple test with the vgem driver
tools/testing/selftests/android/ion/Makefile | 3 +-
tools/testing/selftests/android/ion/config | 1 +
tools/testing/selftests/android/ion/ionmap_test.c | 136 ++++++++++++++++++++++
tools/testing/selftests/android/ion/ionutils.c | 6 -
4 files changed, 139 insertions(+), 7 deletions(-)
create mode 100644 tools/testing/selftests/android/ion/ionmap_test.c
--
2.14.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: labbott@redhat.com (Laura Abbott)
Subject: [RFC PATCH 0/2] Ion unit test with VGEM
Date: Thu, 15 Feb 2018 17:24:43 -0800 [thread overview]
Message-ID: <20180216012445.17264-1-labbott@redhat.com> (raw)
Message-ID: <20180216012443.CbUrui3_LfSuvCDI4e6v4OPu2fUnnOtICC58Slp-Z74@z> (raw)
Hi,
Ion hasn't had much in the way of unit tests and fixing that is
something that needs to happen before it can move out of staging. The
difficult part of testing parts of Ion is that it relies on having a
kernel driver to actually make some of the dma_buf calls. The vgem
DRM driver exists mostly for testing and works great for this case. I
went back and forth about trying to put this in the existing graphics
test suite but I think having something in the self-tests directory is
easier.
I'm mostly interested in feedback about the use of the DRM APIs but I
appreciate any and all comments.
Thanks,
Laura
Laura Abbott (2):
selftests: ion: Remove some prints
selftests: ion: Add simple test with the vgem driver
tools/testing/selftests/android/ion/Makefile | 3 +-
tools/testing/selftests/android/ion/config | 1 +
tools/testing/selftests/android/ion/ionmap_test.c | 136 ++++++++++++++++++++++
tools/testing/selftests/android/ion/ionutils.c | 6 -
4 files changed, 139 insertions(+), 7 deletions(-)
create mode 100644 tools/testing/selftests/android/ion/ionmap_test.c
--
2.14.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Laura Abbott <labbott@redhat.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: devel@driverdev.osuosl.org, Todd Kjos <tkjos@android.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: [RFC PATCH 0/2] Ion unit test with VGEM
Date: Thu, 15 Feb 2018 17:24:43 -0800 [thread overview]
Message-ID: <20180216012445.17264-1-labbott@redhat.com> (raw)
Hi,
Ion hasn't had much in the way of unit tests and fixing that is
something that needs to happen before it can move out of staging. The
difficult part of testing parts of Ion is that it relies on having a
kernel driver to actually make some of the dma_buf calls. The vgem
DRM driver exists mostly for testing and works great for this case. I
went back and forth about trying to put this in the existing graphics
test suite but I think having something in the self-tests directory is
easier.
I'm mostly interested in feedback about the use of the DRM APIs but I
appreciate any and all comments.
Thanks,
Laura
Laura Abbott (2):
selftests: ion: Remove some prints
selftests: ion: Add simple test with the vgem driver
tools/testing/selftests/android/ion/Makefile | 3 +-
tools/testing/selftests/android/ion/config | 1 +
tools/testing/selftests/android/ion/ionmap_test.c | 136 ++++++++++++++++++++++
tools/testing/selftests/android/ion/ionutils.c | 6 -
4 files changed, 139 insertions(+), 7 deletions(-)
create mode 100644 tools/testing/selftests/android/ion/ionmap_test.c
--
2.14.3
WARNING: multiple messages have this Message-ID (diff)
From: Laura Abbott <labbott@redhat.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Laura Abbott <labbott@redhat.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Todd Kjos <tkjos@android.com>,
dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
Liam Mark <lmark@codeaurora.org>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: [RFC PATCH 0/2] Ion unit test with VGEM
Date: Thu, 15 Feb 2018 17:24:43 -0800 [thread overview]
Message-ID: <20180216012445.17264-1-labbott@redhat.com> (raw)
Hi,
Ion hasn't had much in the way of unit tests and fixing that is
something that needs to happen before it can move out of staging. The
difficult part of testing parts of Ion is that it relies on having a
kernel driver to actually make some of the dma_buf calls. The vgem
DRM driver exists mostly for testing and works great for this case. I
went back and forth about trying to put this in the existing graphics
test suite but I think having something in the self-tests directory is
easier.
I'm mostly interested in feedback about the use of the DRM APIs but I
appreciate any and all comments.
Thanks,
Laura
Laura Abbott (2):
selftests: ion: Remove some prints
selftests: ion: Add simple test with the vgem driver
tools/testing/selftests/android/ion/Makefile | 3 +-
tools/testing/selftests/android/ion/config | 1 +
tools/testing/selftests/android/ion/ionmap_test.c | 136 ++++++++++++++++++++++
tools/testing/selftests/android/ion/ionutils.c | 6 -
4 files changed, 139 insertions(+), 7 deletions(-)
create mode 100644 tools/testing/selftests/android/ion/ionmap_test.c
--
2.14.3
next reply other threads:[~2018-02-16 1:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 1:24 labbott [this message]
2018-02-16 1:24 ` [RFC PATCH 0/2] Ion unit test with VGEM Laura Abbott
2018-02-16 1:24 ` Laura Abbott
2018-02-16 1:24 ` Laura Abbott
2018-02-16 1:24 ` [PATCH 1/2] selftests: ion: Remove some prints labbott
2018-02-16 1:24 ` Laura Abbott
2018-02-16 1:24 ` Laura Abbott
2018-02-16 1:24 ` Laura Abbott
2018-02-26 16:54 ` shuah
2018-02-26 16:54 ` Shuah Khan
2018-02-26 16:54 ` Shuah Khan
2018-02-16 1:24 ` [PATCH 2/2] selftests: ion: Add simple test with the vgem driver labbott
2018-02-16 1:24 ` Laura Abbott
2018-02-16 1:24 ` Laura Abbott
2018-02-16 1:24 ` Laura Abbott
2018-02-19 15:31 ` daniel
2018-02-19 15:31 ` Daniel Vetter
2018-02-19 15:31 ` Daniel Vetter
2018-02-19 15:31 ` Daniel Vetter
2018-02-19 18:18 ` labbott
2018-02-19 18:18 ` Laura Abbott
2018-02-19 18:18 ` Laura Abbott
2018-02-19 18:18 ` Laura Abbott
2018-02-19 18:33 ` daniel
2018-02-19 18:33 ` Daniel Vetter
2018-02-19 18:33 ` Daniel Vetter
2018-02-19 18:33 ` Daniel Vetter
2018-02-26 17:07 ` shuah
2018-02-26 17:07 ` Shuah Khan
2018-02-26 17:07 ` Shuah Khan
2018-02-26 17:07 ` Shuah Khan
2018-02-27 1:48 ` labbott
2018-02-27 1:48 ` Laura Abbott
2018-02-27 1:48 ` Laura Abbott
2018-02-27 1:48 ` Laura Abbott
2018-02-27 15:06 ` shuahkh
2018-02-27 15:06 ` Shuah Khan
2018-02-27 15:06 ` Shuah Khan
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=20180216012445.17264-1-labbott@redhat.com \
--to=unknown@example.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 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.