mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Banks <gnb@melbourne.sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: OProfile List <oprofile-list@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/11] oprofile: add check_user_page_readable()
Date: Tue, 09 Nov 2004 22:52:45 +1100	[thread overview]
Message-ID: <1100001164.1985.855.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <20041109032658.5d67d5e3.akpm@osdl.org>

On Tue, 2004-11-09 at 22:26, Andrew Morton wrote:
> > The i386 callgraph code attempts to follow user stacks, from
> > an interrupt (perfmon, NMI, or timer)
> 
> Yikes.

There are a number of problems with this, for example modern libcs
built with -fomit-frame-pointer limit it's usefulness.  But when it
does get meaningful traces it's really quite useful.

> > >   And why is that usage
> > > pattern not racy in the presence of paging activity?
> > 
> > The i386 backtracer takes the &current->mm->page_table_lock,
> 
> But that cannot be taken from interrupt context.  A trylock would be OK I
> guess.

The code reads:

#ifdef CONFIG_SMP
        if (!spin_trylock(&current->mm->page_table_lock))
                return;
#endif

i.e. it tries to get the lock and abandons the trace if it can't.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.



      reply	other threads:[~2004-11-09 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 10:37 Greg Banks
2004-11-09 11:04 ` Andrew Morton
2004-11-09 11:20   ` Greg Banks
2004-11-09 11:26     ` Andrew Morton
2004-11-09 11:52       ` Greg Banks [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=1100001164.1985.855.camel@hole.melbourne.sgi.com \
    --to=gnb@melbourne.sgi.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    /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®