All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: realtime-preempt-2.6.12-final-V0.7.51-11 glitches [no more]
Date: Mon, 11 Jul 2005 17:55:03 +0200	[thread overview]
Message-ID: <20050711155503.GA21762@elte.hu> (raw)
In-Reply-To: <63108.195.245.190.94.1121094757.squirrel@www.rncbc.org>


* Rui Nuno Capela <rncbc@rncbc.org> wrote:

> After several trials, with CONFIG_PROFILING=y and profile=1 
> nmi_watchdog=2 as boot parameters, I'm almost convinced I'm doing 
> something wrong :)
> 
> - `readprofile` always just outputs one line:
> 
>      0 total                                    0.0000
> 
> - `readprofile -a` gives the whole kernel symbol list, all with zero times.
> 
> Is there anything else I can check around here?

it means that the NMI watchdog was not activated - i.e. the 'NMI' counts 
in /proc/interrupts do not increase. Do you have LOCAL_APIC enabled in 
the .config? If yes and if nmi_watchdog=1 does not work either then it's 
probably not possible to activate the NMI watchdog on your box. In that 
case try nmi_watchdog=0, that should activate normal profiling. (unless 
i've broken it via the profile-via-NMI changes ...)

	Ingo

  reply	other threads:[~2005-07-11 15:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1119299227.20873.113.camel@cmn37.stanford.edu>
     [not found] ` <20050621105954.GA18765@elte.hu>
     [not found]   ` <1119370868.26957.9.camel@cmn37.stanford.edu>
     [not found]     ` <20050621164622.GA30225@elte.hu>
     [not found]       ` <1119375988.28018.44.camel@cmn37.stanford.edu>
     [not found]         ` <1120256404.22902.46.camel@cmn37.stanford.edu>
     [not found]           ` <20050703133738.GB14260@elte.hu>
     [not found]             ` <1120428465.21398.2.camel@cmn37.stanford.edu>
2005-07-07 18:46               ` realtime-preempt-2.6.12-final-V0.7.51-11 glitches Rui Nuno Capela
2005-07-07 18:53                 ` realtime-preempt-2.6.12-final-V0.7.51-11 glitches [2] Rui Nuno Capela
2005-07-07 19:49                 ` realtime-preempt-2.6.12-final-V0.7.51-11 glitches Ingo Molnar
2005-07-07 19:59                   ` Ingo Molnar
2005-07-07 23:19                   ` Rui Nuno Capela
2005-07-08  8:46                     ` realtime-preempt-2.6.12-final-V0.7.51-11 glitches [no more] Rui Nuno Capela
2005-07-08  8:52                       ` Ingo Molnar
2005-07-08  9:40                         ` Rui Nuno Capela
2005-07-08  9:56                           ` Ingo Molnar
2005-07-08 10:53                             ` Rui Nuno Capela
2005-07-11 15:12                             ` Rui Nuno Capela
2005-07-11 15:55                               ` Ingo Molnar [this message]
2005-07-11 22:00                                 ` Rui Nuno Capela
2005-07-11 22:09                                   ` Rui Nuno Capela

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=20050711155503.GA21762@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rncbc@rncbc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.