Re: What is MMU_TRACE for?

From: David Mosberger <davidm_at_napali.hpl.hp.com>
Date: 2004-08-18 18:13:32
>>>>> On Wed, 18 Aug 2004 14:25:58 +1000, Ian Wienand <ianw@gelato.unsw.edu.au> said:

  Ian> Hi, The change @ http://tinyurl.com/4g5dz introduced MMU_TRACE,
  Ian> but left the structure to keep the traces in as extern with no
  Ian> corresponding definition.  Is maybe some of the patch missing?
  Ian> What was its original intention?

It's just left-over debugging code.  We should remove it.  What I used
to do is store the traces in kernel-memory and then I'd use Ski to
look at the traces.

  Ian> I actaully wanted to use something like this, so just exported
  Ian> it out to a proc entry (attached just for the archives).

Looks like a fine patch.  Such debug code is normally maintained as
separate patches, though, and not part of the main-line source tree.

	--david
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Wed Aug 18 04:13:56 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:29 EST