From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
Dan Carpenter <error27@gmail.com>
Cc: David Airlie <airlied@linux.ie>, Eric Anholt <eric@anholt.net>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
nanhai.zou@intel.com, Benny Halevy <bhalevy@panasas.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Jin, Gordon" <gordon.jin@intel.com>
Subject: Re: [patch] i915: take struct_mutex in i915_dma_cleanup()
Date: Sun, 25 Jul 2010 16:05:45 +0100 [thread overview]
Message-ID: <89kc63$hi6qh3@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <20100623084718.2dfe6e7f@virtuousgeek.org>
On Wed, 23 Jun 2010 08:47:18 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> Reminds me, Gordon can you add module unload testing to your set of
> basic daily tests? To unload you need to unbind the fbcon interface
> first, my script is like this:
>
> echo 0 > /sys/class/vtconsole/vtcon1/bind
> rmmod i915
> rmmod drm_kms_helper
> rmmod drm
> modprobe i915
> echo 1 > /sys/class/vtconsole/vtcon1/bind
To which we could even add a kmemleak check.
After rmmod drm and before reloading i915:
echo scan > /sys/kernel/debug/kmemleak
cat /sys/kernel/debug/kmemleak > `hostname`-leaks.txt
If the output is not empty, file a bug. [Of course this means having to
compile kmemleak into the kernel. The DEBUG_KMEMLEAK option is found under
Kernel Hacking.] And since each generation has slightly different
initialization stanzas, we need to repeat the test on all platforms.
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-07-25 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 11:19 [patch] i915: take struct_mutex in i915_dma_cleanup() Dan Carpenter
2010-06-23 15:47 ` Jesse Barnes
2010-07-25 15:05 ` Chris Wilson [this message]
2010-07-01 22:39 ` Eric Anholt
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='89kc63$hi6qh3@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=bhalevy@panasas.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=error27@gmail.com \
--cc=gordon.jin@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=zhenyuw@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