From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Add module param to test the load detect code
Date: Wed, 04 Mar 2015 08:09:57 -0800 [thread overview]
Message-ID: <54F72E55.2040609@virtuousgeek.org> (raw)
In-Reply-To: <20150304085645.GC26004@nuc-i3427.alporthouse.com>
On 03/04/2015 12:56 AM, Chris Wilson wrote:
> On Tue, Mar 03, 2015 at 04:27:47PM -0800, Jesse Barnes wrote:
>> My "rant du jour" still is. mlock() is a good solution for some things,
>> but for the simple task of testing kernel swap out code, just running
>> that code is the most straightforward thing to do, rather than trying to
>> contort into it from userspace.
>
> Once upon a time, there was a minor request for MADV_POPULATE and
> MADV_INVALIDATE (basically wrappers around get_pages() and put_pages())
> which would give you the fuzzy feeling of testing those paths without
> actually testing the shrinker. But no use cases.
Yeah, that sounds cool, but otoh adding stable ABI just for debug is a
little scary...
Jesse
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-04 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:03 [PATCH] drm/i915: Add module param to test the load detect code Daniel Vetter
2015-03-03 19:23 ` Jesse Barnes
2015-03-03 21:15 ` Chris Wilson
2015-03-04 0:06 ` Daniel Vetter
2015-03-04 0:27 ` Jesse Barnes
2015-03-04 8:56 ` Chris Wilson
2015-03-04 16:09 ` Jesse Barnes [this message]
2015-03-04 16:09 ` Daniel Vetter
2015-03-04 14:29 ` shuang.he
2015-03-27 9:57 ` Ander Conselvan De Oliveira
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=54F72E55.2040609@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.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 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.