From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Chris Wilson <chris@chris-wilson.co.uk>, David Airlie <airlied@linux.ie>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: DRM range manager selftest run time
Date: Thu, 9 Feb 2017 10:58:38 +0100 [thread overview]
Message-ID: <CAMuHMdU9JXh34tGrpuUgQsMfGRNsZtEFvJ=9KtWT1MWosumW+w@mail.gmail.com> (raw)
Hi Chris, Dave,
Recently, I started seeing ca. 2 minute delays during boot-up on Renesas
R-Car Gen2 boards.
It turned out the DRM range manager selftests started taking quite some time.
With debug output, I get:
[ 2.310472] drm_mm: Testing DRM range manger (struct drm_mm), with
random_seed=0x637f8ba8 max_iterations=8192 max_prime=128
[ 2.321625] drm_mm: drm: Running sanitycheck
[ 2.325905] drm_mm: igt_sanitycheck - ok!
[ 2.329915] drm_mm: drm: Running init
[ 2.333590] drm_mm: drm: Running debug
[ 2.337341] drm_mm: drm: Running reserve
[ 2.862878] drm_mm: drm: Running insert
[ 49.205174] drm_mm: drm: Running replace
[ 95.570840] drm_mm: drm: Running insert_range
[ 98.971590] drm_mm: drm: Running align
[ 98.975614] drm_mm: drm: Running align32
[ 98.979601] drm_mm: drm: Running align64
[ 98.983652] drm_mm: drm: Running evict
[ 100.321925] drm_mm: drm: Running evict_range
[ 101.226411] drm_mm: drm: Running bottomup
[ 101.316911] drm_mm: drm: Running topdown
[ 101.404385] drm_mm: drm: Running color
[ 103.889639] drm_mm: drm: Running color_evict
[ 107.318608] drm_mm: drm: Running color_evict_range
[ 110.485926] drm_mm: run_selftests: Completed
Perhaps some tests can be simplified, to reduce run time?
Alternatviely, the pr_debug() calls in drivers/gpu/drm/selftests/drm_selftest.c
could be turned into pr_info() calls (cfr. the output above), to give a cue?
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
next reply other threads:[~2017-02-09 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 9:58 Geert Uytterhoeven [this message]
2017-02-09 10:05 ` DRM range manager selftest run time 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='CAMuHMdU9JXh34tGrpuUgQsMfGRNsZtEFvJ=9KtWT1MWosumW+w@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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).