public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	joonas.lahtinen@linux.intel.com
Subject: Re: [PATCH v2 08/40] drm: Add a simple prime number generator
Date: Fri, 16 Dec 2016 11:08:10 +0100	[thread overview]
Message-ID: <20161216100810.GB11910@wunner.de> (raw)
In-Reply-To: <20161216094354.GO29871@nuc-i3427.alporthouse.com>

On Fri, Dec 16, 2016 at 09:43:54AM +0000, Chris Wilson wrote:
> On Fri, Dec 16, 2016 at 10:31:17AM +0100, Lukas Wunner wrote:
> > On Fri, Dec 16, 2016 at 07:46:46AM +0000, Chris Wilson wrote:
> > > Prime numbers are interesting for testing components that use multiplies
> > > and divides, such as testing struct drm_mm alignment computations.
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > ---
> > >  drivers/gpu/drm/Kconfig                 |   4 +
> > >  drivers/gpu/drm/Makefile                |   1 +
> > >  drivers/gpu/drm/lib/drm_prime_numbers.c | 175 ++++++++++++++++++++++++++++++++
> > >  drivers/gpu/drm/lib/drm_prime_numbers.h |  10 ++
> > >  4 files changed, 190 insertions(+)
> > >  create mode 100644 drivers/gpu/drm/lib/drm_prime_numbers.c
> > >  create mode 100644 drivers/gpu/drm/lib/drm_prime_numbers.h
> > 
> > Hm, why not put this in lib/ ?  Don't see anything DRM-specific here
> > at first glance and this might be useful to others.  Or others might
> > come up with improvements and they'll be more likely to discover it
> > outside of DRM.
> 
> Because that is a 3+ month cycle before I can then apply the testcases,
> and without the testscases do you want the bugfixes?

Do patches for lib/ have to go through a different tree?
Don't think so, I've seen e.g. changes to lib/ucs2_string.c
go through the EFI tree.  It seems to me lib/ is sort of
free for all.


> If I put in in drm/lib then lift it, I can use it immediately and drop
> the local copy once merged.

That is also workable of course.  Anyway, it was just a suggestion.

Thanks,

Lukas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-12-16 10:08 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16  7:46 drm_mm range manager fixes, take 2 Chris Wilson
2016-12-16  7:46 ` [PATCH v2 01/40] drm/i915: Use the MRU stack search after evicting Chris Wilson
2016-12-16  9:03   ` Joonas Lahtinen
2016-12-16  7:46 ` [PATCH v2 02/40] drm/i915: Simplify i915_gtt_color_adjust() Chris Wilson
2016-12-16  7:46 ` [PATCH v2 03/40] drm: Add drm_mm_for_each_node_safe() Chris Wilson
2016-12-16  9:06   ` Joonas Lahtinen
2016-12-16 13:32     ` Daniel Vetter
2016-12-16  7:46 ` [PATCH v2 04/40] drm: Constify the drm_mm API Chris Wilson
2016-12-16 13:45   ` Daniel Vetter
2016-12-16  7:46 ` [PATCH v2 05/40] drm: Compile time enabling for asserts in drm_mm Chris Wilson
2016-12-16  7:46 ` [PATCH v2 06/40] drm: Add some kselftests for the DRM range manager (struct drm_mm) Chris Wilson
2016-12-16  7:46 ` [PATCH v2 07/40] drm: Add a simple generator of random permutations Chris Wilson
2016-12-16  9:38   ` Joonas Lahtinen
2016-12-16  7:46 ` [PATCH v2 08/40] drm: Add a simple prime number generator Chris Wilson
2016-12-16  9:31   ` Lukas Wunner
2016-12-16  9:43     ` Chris Wilson
2016-12-16 10:08       ` Lukas Wunner [this message]
2016-12-16 10:25         ` Chris Wilson
2016-12-16 13:23   ` [PATCH] lib: " Chris Wilson
2016-12-16 13:53     ` Chris Wilson
2016-12-16 14:02     ` [PATCH v3] " Chris Wilson
2016-12-16 18:47       ` kbuild test robot
2016-12-16  7:46 ` [PATCH v2 09/40] drm: kselftest for drm_mm_init() Chris Wilson
2016-12-16  9:41   ` Joonas Lahtinen
2016-12-16  7:46 ` [PATCH v2 10/40] drm: kselftest for drm_mm_debug() Chris Wilson
2016-12-16  9:44   ` Joonas Lahtinen
2016-12-16 10:01     ` Chris Wilson
2016-12-16  7:46 ` [PATCH v2 11/40] drm: kselftest for drm_mm_reserve_node() Chris Wilson
2016-12-16  7:46 ` [PATCH v2 12/40] drm: kselftest for drm_mm_insert_node() Chris Wilson
2016-12-16 14:02   ` Joonas Lahtinen
2016-12-16 14:59     ` Chris Wilson
2016-12-16  7:46 ` [PATCH v2 13/40] drm: kselftest for drm_mm_replace_node() Chris Wilson
2016-12-16  7:46 ` [PATCH v2 14/40] drm: kselftest for drm_mm_insert_node_in_range() Chris Wilson
2016-12-16 14:08   ` Joonas Lahtinen
2016-12-16  7:46 ` [PATCH v2 15/40] drm: kselftest for drm_mm and alignment Chris Wilson
2016-12-16  7:46 ` [PATCH v2 16/40] drm: kselftest for drm_mm and eviction Chris Wilson
2016-12-16  7:46 ` [PATCH v2 17/40] drm: kselftest for drm_mm and range restricted eviction Chris Wilson
2016-12-16  7:46 ` [PATCH v2 18/40] drm: kselftest for drm_mm and top-down allocation Chris Wilson
2016-12-16  7:46 ` [PATCH v2 19/40] drm: kselftest for drm_mm and color adjustment Chris Wilson
2016-12-16  7:46 ` [PATCH v2 20/40] drm: kselftest for drm_mm and color eviction Chris Wilson
2016-12-16 14:38   ` Joonas Lahtinen
2016-12-16 14:48     ` Chris Wilson
2016-12-16  7:46 ` [PATCH v2 21/40] drm: kselftest for drm_mm and restricted " Chris Wilson
2016-12-16 14:41   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 22/40] drm/i915: Build DRM range manager selftests for CI Chris Wilson
2016-12-16  7:47 ` [PATCH v2 23/40] drm: Promote drm_mm alignment to u64 Chris Wilson
2016-12-16  7:47 ` [PATCH v2 24/40] drm: Fix kerneldoc for drm_mm_scan_remove_block() Chris Wilson
2016-12-16 10:09   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 25/40] drm: Detect overflow in drm_mm_reserve_node() Chris Wilson
2016-12-16 10:11   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 26/40] drm: Simplify drm_mm_clean() Chris Wilson
2016-12-16  7:47 ` [PATCH v2 27/40] drm: Add asserts to catch overflow in drm_mm_init() and drm_mm_init_scan() Chris Wilson
2016-12-16 13:10   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 28/40] drm: Extract struct drm_mm_scan from struct drm_mm Chris Wilson
2016-12-16  7:47 ` [PATCH v2 29/40] drm: Rename prev_node to hole in drm_mm_scan_add_block() Chris Wilson
2016-12-16 14:41   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 30/40] drm: Unconditionally do the range check " Chris Wilson
2016-12-16  7:47 ` [PATCH v2 31/40] drm: Fix application of color vs range restriction when scanning drm_mm Chris Wilson
2016-12-16  7:47 ` [PATCH v2 32/40] drm: Compute tight evictions for drm_mm_scan Chris Wilson
2016-12-16  7:47 ` [PATCH v2 33/40] drm: Optimise power-of-two alignments in drm_mm_scan_add_block() Chris Wilson
2016-12-16  7:47 ` [PATCH v2 34/40] drm: Simplify drm_mm scan-list manipulation Chris Wilson
2016-12-16 13:06   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 35/40] drm: Apply tight eviction scanning to color_adjust Chris Wilson
2016-12-16 14:14   ` Joonas Lahtinen
2016-12-16 14:24     ` Chris Wilson
2016-12-16  7:47 ` [PATCH v2 36/40] drm: Wrap drm_mm_node.hole_follows Chris Wilson
2016-12-16 13:04   ` Joonas Lahtinen
2016-12-16 13:31     ` Chris Wilson
2016-12-16 13:41       ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 37/40] drm: Apply range restriction after color adjustment when allocation Chris Wilson
2016-12-16 12:57   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 38/40] drm: Use drm_mm_insert_node_in_range_generic() for everyone Chris Wilson
2016-12-16 13:01   ` Joonas Lahtinen
2016-12-16  7:47 ` [PATCH v2 39/40] drm: Improve drm_mm search (and fix topdown allocation) with rbtrees Chris Wilson
2016-12-16 13:46   ` Joonas Lahtinen
2016-12-16 13:56     ` Chris Wilson
2016-12-16  7:47 ` [PATCH v2 40/40] drm: kselftest for drm_mm and bottom-up allocation Chris Wilson
2016-12-16  9:15 ` ✓ Fi.CI.BAT: success for series starting with [v2,01/40] drm/i915: Use the MRU stack search after evicting Patchwork
2016-12-16 16:31 ` ✗ Fi.CI.BAT: failure for series starting with [v2,01/40] drm/i915: Use the MRU stack search after evicting (rev3) Patchwork

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=20161216100810.GB11910@wunner.de \
    --to=lukas@wunner.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox