From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: What is MMU_TRACE for?
Date: Wed, 18 Aug 2004 08:13:32 +0000 [thread overview]
Message-ID: <16675.4012.367668.929781@napali.hpl.hp.com> (raw)
In-Reply-To: <20040818042558.GC1170@cse.unsw.EDU.AU>
>>>>> 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
next prev parent reply other threads:[~2004-08-18 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 4:25 What is MMU_TRACE for? Ian Wienand
2004-08-18 8:13 ` David Mosberger [this message]
2004-08-19 4:55 ` Ian Wienand
2004-08-19 7:41 ` David Mosberger
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=16675.4012.367668.929781@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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