From: David Howells <dhowells@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] kill odd mm context pinning hack in frv
Date: Thu, 11 Aug 2005 18:57:43 +0100 [thread overview]
Message-ID: <6466.1123783063@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20050811172312.GA10202@lst.de>
Christoph Hellwig <hch@lst.de> wrote:
> David, is that more than a debugging aid? I'm trying to get rid of
> tasklist_lock users and this one looks really suspicios..
Yes. The FR451 CPU (the only one with an MMU at the moment) has accounting and
profiling aids that are enabled by the context number set in the CXNR
register. This context number also selectively enables TLB entries on a per-mm
context basis.
So to profile a process you pin a context number to that process, and then the
profiling h/w is only active for that process.
David
prev parent reply other threads:[~2005-08-11 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 17:23 [PATCH, RFC] kill odd mm context pinning hack in frv Christoph Hellwig
2005-08-11 17:57 ` David Howells [this message]
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=6466.1123783063@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=hch@lst.de \
--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