All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>
Subject: Re: mm snapshot broken-out-2007-03-18-02-44.tar.gz uploaded
Date: Tue, 20 Mar 2007 19:22:33 +0100	[thread overview]
Message-ID: <20070320182233.GC4286@bingen.suse.de> (raw)
In-Reply-To: <20070320083627.27d90a91.akpm@linux-foundation.org>

On Tue, Mar 20, 2007 at 08:36:27AM -0800, Andrew Morton wrote:
> > caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
> >  [<c0105256>] show_trace_log_lvl+0x1a/0x2f
> >  [<c010597b>] show_trace+0x12/0x14
> >  [<c0105a3d>] dump_stack+0x16/0x18
> >  [<c0213313>] debug_smp_processor_id+0xb3/0xc8
> >  [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
> >  [<fdc819b9>] nmi_create_files+0x2a/0x10e [oprofile]
> >  [<fdc80f52>] oprofile_create_files+0xe6/0xec [oprofile]
> >  [<fdc81157>] oprofilefs_fill_super+0x78/0x7e [oprofile]
> >  [<c0182d2e>] get_sb_single+0x59/0x9f
> >  [<fdc8108f>] oprofilefs_get_sb+0x1c/0x1e [oprofile]
> >  [<c0182792>] vfs_kern_mount+0x81/0xf1
> >  [<c0182852>] do_kern_mount+0x38/0xde
> >  [<c0196671>] do_mount+0x605/0x693
> >  [<c019677f>] sys_mount+0x80/0xb5
> >  [<c0104270>] syscall_call+0x7/0xb
> >  =======================
> 
> Odd.  It looks like oprofile has been doing this for some time.  Andi,
> there are a few changes in the NMI area - can you think of one whihc would
> have triggered this?

Looks like it was always broken. avail_to_resrv_perfctr_nmi_bit() must 
always do all this for all possible CPUs, not just the current one.
I can cook up a patch.

-Andi



      reply	other threads:[~2007-03-20 17:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18  9:44 mm snapshot broken-out-2007-03-18-02-44.tar.gz uploaded akpm
2007-03-18 18:35 ` Michal Piotrowski
     [not found]   ` <6bffcb0e0703190845s6bdc1a65p71937d1dffbf6d9e@mail.gmail.com>
2007-03-19 15:54     ` Pekka J Enberg
2007-03-19 16:29       ` Michal Piotrowski
2007-03-19 16:34         ` Michal Piotrowski
2007-03-19 16:39           ` Pekka J Enberg
2007-03-19 16:38         ` Pekka J Enberg
2007-03-19 16:45           ` Michal Piotrowski
     [not found]             ` <6bffcb0e0703191024w527638f8yacc3a8fea9fd451d@mail.gmail.com>
2007-03-19 18:02               ` Michal Piotrowski
2007-03-19 18:10                 ` Pekka J Enberg
2007-03-19 19:27                   ` Michal Piotrowski
2007-03-19 23:25   ` Andrew Morton
2007-03-20 11:43     ` Sam Ravnborg
2007-03-19 19:23 ` Michal Piotrowski
2007-03-19 21:08   ` Andrew Morton
     [not found]     ` <6bffcb0e0703191437i2ee706d4xaec3bc11ca7c3234@mail.gmail.com>
2007-03-20  1:58       ` Andrew Morton
2007-03-20  2:02         ` Andrew Morton
2007-03-20  2:47           ` Nick Piggin
2007-03-20  4:56             ` Andrew Morton
2007-03-20  5:17               ` Nick Piggin
2007-03-20  5:18                 ` Nick Piggin
2007-03-20  9:07                 ` Michal Piotrowski
2007-03-19 19:56 ` Michal Piotrowski
2007-03-20  7:17 ` Michal Piotrowski
2007-03-20 16:36   ` Andrew Morton
2007-03-20 18:22     ` Andi Kleen [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=20070320182233.GC4286@bingen.suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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.