linux-kernel - Re: DRM range manager selftest run time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 9 Feb 2017 10:05:55 +0000
From:   Chris Wilson <chris@...is-wilson.co.uk>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     David Airlie <airlied@...ux.ie>,
        DRI Development <dri-devel@...ts.freedesktop.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: DRM range manager selftest run time

On Thu, Feb 09, 2017 at 10:58:38AM +0100, Geert Uytterhoeven wrote:
> 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?

Don't build test-drm_mm as a builtin? Or set a limit to the number of
tests to run, e.g. test-drm_mm.max_iterations=16 test-drm_mm.max_primes=16.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre