public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Ingo Molnar" <mingo@elte.hu>, "Andrew Morton" <akpm@osdl.org>,
	<linux-kernel@vger.kernel.org>,
	"Randy Dunlap" <rdunlap@xenotime.net>,
	tilman@imap.cc
Subject: Re: [2.6.18-rc7-mm1] slow boot
Date: 29 Sep 2006 18:12:56 +0200	[thread overview]
Message-ID: <p73lko2ircn.fsf@verdi.suse.de> (raw)
In-Reply-To: <451CE2F0.76E4.0078.0@novell.com>

"Jan Beulich" <jbeulich@novell.com> writes:

> There's nothing stack trace/unwind related among the functions listed at all afaics.
> I don't know much about how profiling works, is it perhaps just missing something?

Perhaps lockdep calls them with interrupts off?
The old profiler doesn't support profiling with interrupts off.
oprofile does, but it cannot be used at early boot.

-Andi

  reply	other threads:[~2006-09-29 16:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 16:59 [2.6.18-rc7-mm1] slow boot Tilman Schmidt
2006-09-24 19:22 ` Valdis.Kletnieks
2006-09-24 22:02   ` Tilman Schmidt
2006-09-24 21:53 ` Andrew Morton
2006-09-24 22:15   ` Tilman Schmidt
2006-09-24 22:36   ` Alan Cox
2006-09-24 22:41     ` Andrew Morton
2006-09-26 23:48   ` Tilman Schmidt
2006-09-27  0:21     ` Andrew Morton
2006-09-28 17:00   ` Tilman Schmidt
2006-09-28 17:12     ` Andi Kleen
2006-09-28 23:20       ` Tilman Schmidt
2006-09-28 23:30         ` Randy Dunlap
2006-09-29  0:15           ` Tilman Schmidt
2006-09-29  7:10             ` Jan Beulich
2006-09-29 16:12               ` Andi Kleen [this message]
2006-09-29 18:39                 ` Ingo Molnar
2006-10-04  7:05                   ` Jan Beulich
2006-09-29  8:49         ` Andi Kleen
2006-09-24 21:58 ` [2.6.18-mm1] slow boot (was: [2.6.18-rc7-mm1] slow boot) Tilman Schmidt
2006-09-25 12:09 ` [2.6.18-rc7-mm1] slow boot Alexander Gran
2006-10-25 18:14 ` Tilman Schmidt

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=p73lko2ircn.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    --cc=tilman@imap.cc \
    /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