linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [2/2] vmallocinfo: Add caller information
Date: Fri, 21 Mar 2008 12:16:00 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803211212520.19558@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080321184526.GB6571@elte.hu>

On Fri, 21 Mar 2008, Ingo Molnar wrote:

> the best i found for lockdep was to include a fair number of them, and 
> to skip the top 3. struct vm_area that vmalloc uses isnt space-critical, 
> so 4-8 entries with a 3 skip would be quite ok. (but can be more than 
> that as well)

STACKTRACE depends on STACKTRACE_SUPPORT which is not available on 
all arches? alpha blackfin ia64 etc are missing it?

I thought there were also issues on x86 with optimizations leading to 
weird stacktraces?


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-03-21 19:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 22:27 [0/2] vmalloc: Add /proc/vmallocinfo to display mappings Christoph Lameter
2008-03-18 22:27 ` [1/2] vmalloc: Show vmalloced areas via /proc/vmallocinfo Christoph Lameter
2008-03-20  4:04   ` Arjan van de Ven
2008-03-20 19:22     ` Christoph Lameter
2008-03-21 22:19       ` Andrew Morton
2008-03-21 22:09         ` Alan Cox
2008-03-18 22:27 ` [2/2] vmallocinfo: Add caller information Christoph Lameter
2008-03-19 21:42   ` Ingo Molnar
2008-03-20  0:03     ` Christoph Lameter
2008-03-21 11:00       ` Ingo Molnar
2008-03-21 17:35         ` Christoph Lameter
2008-03-21 18:45           ` Ingo Molnar
2008-03-21 19:16             ` Christoph Lameter [this message]
2008-03-21 20:55               ` Ingo Molnar
2008-03-22  2:40                 ` Mike Frysinger
2008-04-29  8:48   ` Ingo Molnar
2008-04-29 17:08     ` Christoph Lameter
2008-04-28 19:48       ` Arjan van de Ven
2008-04-29 18:49         ` Christoph Lameter
2008-04-28 21:00           ` Arjan van de Ven
2008-04-29 19:09             ` Christoph Lameter
2008-04-29 19:23               ` Pekka Enberg
2008-04-29 19:29                 ` Pekka Enberg
2008-04-29 19:29               ` Ingo Molnar
2008-03-19  2:23 ` [0/2] vmalloc: Add /proc/vmallocinfo to display mappings KOSAKI Motohiro
2008-03-19 22:07   ` Andrew Morton
2008-03-19 23:33     ` Christoph Lameter
2008-03-20  7:43     ` KOSAKI Motohiro

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=Pine.LNX.4.64.0803211212520.19558@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).