public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@infradead.org>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch]  Add a simple backtrace test module
Date: Thu, 10 Jan 2008 10:04:29 +0100	[thread overview]
Message-ID: <20080110090429.GA23878@elte.hu> (raw)
In-Reply-To: <20080110083934.GC10745@infradead.org>


* Christoph Hellwig <hch@infradead.org> wrote:

> On Wed, Jan 09, 2008 at 10:42:08PM -0800, Arjan van de Ven wrote:
> > 
> > Subject: Add a simple backtrace test module
> > From: Arjan van de Ven <arjan@linux.intel.com>
> > 
> > During the work on the x86 32 and 64 bit backtrace code I found it 
> > useful to have a simple test module to test a process and irq 
> > context backtrace. Since the existing backtrace code was buggy, I 
> > figure it might be useful to have such a test module in the kernel 
> > so that maybe we can even detect such bugs earlier..
> 
> Care to add new testcases to a new tests/ subdirectory so we can have 
> them in one place?

yeah, agreed, we'll clean this all up, and move the other testcode there 
too, ok? There's rcutorture, lock-selftests, rt-tester, 
kprobes-smoke-test and now backtracetest.

Arjan might as well want to use the opportunity and break new kernel 
namespace ground by creating the tests/ directory for the first time in 
Linux history and introduce tests/backtracetest.c :-)

	Ingo

  reply	other threads:[~2008-01-10  9:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10  6:42 [patch] Add a simple backtrace test module Arjan van de Ven
2008-01-10  8:39 ` Christoph Hellwig
2008-01-10  9:04   ` Ingo Molnar [this message]
2008-01-10  9:06     ` Christoph Hellwig
2008-01-10  9:13 ` Ingo Molnar

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=20080110090429.GA23878@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=hch@infradead.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