From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>
Subject: perf code using smp_processor_id() in preemptible [00000000] code
Date: Thu, 14 Nov 2013 22:29:07 -0500 [thread overview]
Message-ID: <20131115032907.GA25243@redhat.com> (raw)
BUG: using smp_processor_id() in preemptible [00000000] code: trinity-main/890
caller is p4_pmu_schedule_events+0x25/0x4c0
CPU: 0 PID: 890 Comm: trinity-main Not tainted 3.12.0+ #3
Hardware name: Dell Inc. Precision WorkStation 470 /0P7996, BIOS A05 05/18/2005
ffff88001e675668 ffff880025e79d00 ffffffff8171f332 0000000000000000
ffff880025e79d18 ffffffff8133132a 0000000000000002 ffff880025e79dc0
ffffffff81018e55 ffff88001e675668 00000000000080d0 ffff88001e675668
Call Trace:
[<ffffffff8171f332>] dump_stack+0x4e/0x7a
[<ffffffff8133132a>] debug_smp_processor_id+0xca/0xe0
[<ffffffff81018e55>] p4_pmu_schedule_events+0x25/0x4c0
[<ffffffff811a5c9f>] ? kmem_cache_alloc_trace+0x12f/0x2d0
[<ffffffff810160ff>] ? allocate_fake_cpuc+0x2f/0x90
[<ffffffff81016443>] x86_pmu_event_init+0x193/0x440
[<ffffffff81146850>] perf_init_event+0x250/0x330
[<ffffffff81146600>] ? perf_pmu_unregister+0x160/0x160
[<ffffffff81146ca8>] perf_event_alloc+0x378/0x420
[<ffffffff81147335>] SYSC_perf_event_open+0x5e5/0xa80
[<ffffffff81147b89>] SyS_perf_event_open+0x9/0x10
[<ffffffff81731ee4>] tracesys+0xdd/0xe2
next reply other threads:[~2013-11-15 3:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 3:29 Dave Jones [this message]
2013-11-15 10:02 ` perf code using smp_processor_id() in preemptible [00000000] code Peter Zijlstra
2013-11-15 10:19 ` Cyrill Gorcunov
2013-11-15 11:30 ` Cyrill Gorcunov
2013-11-15 11:51 ` Peter Zijlstra
2013-11-15 12:10 ` Cyrill Gorcunov
2013-11-15 12:33 ` Peter Zijlstra
2013-11-15 12:42 ` Cyrill Gorcunov
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=20131115032907.GA25243@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 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).