From: Pekka Paalanen <pq@iki.fi>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/4] Documentation: update mmiotrace.txt
Date: Sat, 19 Dec 2009 12:39:36 +0200 [thread overview]
Message-ID: <20091219123936.1aa3fd1b@daedalus.pq.iki.fi> (raw)
In-Reply-To: <4B2C0D68.6080401@oracle.com>
On Fri, 18 Dec 2009 15:16:56 -0800
Randy Dunlap <randy.dunlap@oracle.com> wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix typos, spellos, hyphenation, line lengths.
>
> BTW: are there some userspace tools? There is a reference to
> some at the wiki page, but there are no tools listed there.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Pekka Paalanen <pq@iki.fi>
> ---
> Documentation/trace/mmiotrace.txt | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
Acked-by: Pekka Paalanen <pq@iki.fi>
Yes, there are some shady user space tools. I moved the
references to the mmiotrace developer page:
http://nouveau.freedesktop.org/wiki/MmioTraceDeveloper
People recording traces do not need the tools, so I
removed them from the MmioTrace page to clarify it.
Here "developer" includes people analyzing the traces.
I added a note to the MmioTrace wiki page.
I'm not actively developing nor even maintaining those
tools anymore. I guess hardcore developers do not even need
them, they prefer reading hex. But, the tools should still be
in a working order. The documentation may be a bit scattered.
The tools are in http://cgit.freedesktop.org/~pq/mmio-trace/
and the Rules-ng parts are in
http://nouveau.cvs.sourceforge.net/nouveau/rules-ng/
More information is in the wiki.
Thanks.
--
Pekka Paalanen
http://www.iki.fi/pq/
next prev parent reply other threads:[~2009-12-19 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 23:16 Randy Dunlap
2009-12-19 10:39 ` Pekka Paalanen [this message]
2009-12-20 5:21 ` [tip:tracing/urgent] Documentation: Update mmiotrace.txt tip-bot for Randy Dunlap
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=20091219123936.1aa3fd1b@daedalus.pq.iki.fi \
--to=pq@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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
all inboxes | Powered by JetHome®