linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>
Subject: Re: dma-buf: Add selftests for dma-fence
Date: Tue, 27 Aug 2019 14:30:04 +0200	[thread overview]
Message-ID: <CAMuHMdUk9G22rDfUrX3CZ=st3_bSehyaW_URtCk0ZfJqFTmLuQ@mail.gmail.com> (raw)

Hi Chris,

When running the new dmabuf-selftests on two different systems, I get:

    dma-buf: Running sanitycheck
    dma-buf: Running dma_fence
    sizeof(dma_fence)=48
    dma-buf: Running dma_fence/sanitycheck
    dma-buf: Running dma_fence/test_signaling
    dma-buf: Running dma_fence/test_add_callback
    dma-buf: Running dma_fence/test_late_add_callback
    dma-buf: Running dma_fence/test_rm_callback
    dma-buf: Running dma_fence/test_late_rm_callback
    dma-buf: Running dma_fence/test_status
    dma-buf: Running dma_fence/test_error
    dma-buf: Running dma_fence/test_wait
    dma-buf: Running dma_fence/test_wait_timeout
    dma-buf: Running dma_fence/test_stub
    dma-buf: Running dma_fence/race_signal_callback
    thread_signal_callback[0] completed 28855 passes, 3929 misses
    thread_signal_callback[1] completed 28846 passes, 3918 misses
    thread_signal_callback[0] completed 37179 passes, 37179 misses
    thread_signal_callback[1] completed 37184 passes, 37183 misses

and

    dma-buf: Running sanitycheck
    dma-buf: Running dma_fence
    sizeof(dma_fence)=64
    dma-buf: Running dma_fence/sanitycheck
    dma-buf: Running dma_fence/test_signaling
    dma-buf: Running dma_fence/test_add_callback
    dma-buf: Running dma_fence/test_late_add_callback
    dma-buf: Running dma_fence/test_rm_callback
    dma-buf: Running dma_fence/test_late_rm_callback
    dma-buf: Running dma_fence/test_status
    dma-buf: Running dma_fence/test_error
    dma-buf: Running dma_fence/test_wait
    dma-buf: Running dma_fence/test_wait_timeout
    dma-buf: Running dma_fence/test_stub
    dma-buf: Running dma_fence/race_signal_callback
    thread_signal_callback[0] completed 3423 passes, 2148 misses
    thread_signal_callback[1] completed 2360 passes, 9 misses
    thread_signal_callback[0] completed 4028 passes, 4028 misses
    thread_signal_callback[1] completed 8080 passes, 8079 misses

Unfortunately it is not clear to me if this is good or bad?
Perhaps the test output can be improved, e.g. with a clear PASS/FAIL output?

Thanks!

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

             reply	other threads:[~2019-08-27 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 12:30 Geert Uytterhoeven [this message]
2019-08-27 12:36 ` dma-buf: Add selftests for dma-fence Chris Wilson

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='CAMuHMdUk9G22rDfUrX3CZ=st3_bSehyaW_URtCk0ZfJqFTmLuQ@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.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).