From: Ingo Molnar <mingo@elte.hu>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/xen] x86: use flush_tlb_others to implement flush_tlb_all, fix
Date: Mon, 11 May 2009 17:40:34 +0200 [thread overview]
Message-ID: <20090511154034.GA30361@elte.hu> (raw)
In-Reply-To: <20090511151151.GA3267@elte.hu>
sigh:
BUG: using smp_processor_id() in preemptible [00000000] code: S99local/1903
caller is flush_tlb_others_ipi+0x1b/0xc0
Pid: 1903, comm: S99local Not tainted
2.6.30-rc5-tip-01485-g1304846-dirty #40905
Call Trace:
[<40a9e184>] ? printk+0x1d/0x1f
[<4066d2e6>] debug_smp_processor_id+0xc6/0xd0
[<40422dab>] flush_tlb_others_ipi+0x1b/0xc0
[<40422e5d>] native_flush_tlb_others+0xd/0x10
[<40422ea9>] flush_tlb_all+0x19/0x60
[<4041e972>] zap_low_mappings+0x52/0x60
[<40a9b080>] native_cpu_up+0x156/0x220
[<40a9ca42>] _cpu_up+0xb0/0x151
[<40a9cb66>] cpu_up+0x83/0x8d
[<40a68b90>] store_online+0x60/0xa0
[<40a68b30>] ? store_online+0x0/0xa0
[<4072ed8a>] sysdev_store+0x2a/0x40
[<40522511>] sysfs_write_file+0xa1/0xf0
[<404d9d44>] vfs_write+0xa4/0x130
[<4065fcec>] ? trace_hardirqs_on_thunk+0xc/0x10
[<40522470>] ? sysfs_write_file+0x0/0xf0
[<404d9ea2>] sys_write+0x42/0x70
[<40403bc8>] sysenter_do_call+0x12/0x3c
CPU0 attaching NULL sched-domain.
Ingo
next prev parent reply other threads:[~2009-05-11 15:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 20:24 [GIT PULL] Xen core updates Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 1/8] xen/x86-64: fix breakpoints and hardware watchpoints Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 2/8] xen/x86-64: clean up warnings about IST-using traps Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 3/8] xen: cache cr0 value to avoid trap'n'emulate for read_cr0 Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 4/8] xen: deal with NMI's use of IST too Jeremy Fitzhardinge
2009-05-07 20:24 ` [PATCH 5/8] xen/i386: make sure initial VGA/ISA mappings are not overridden Jeremy Fitzhardinge
2009-05-08 10:57 ` Ingo Molnar
2009-05-08 15:08 ` Jeremy Fitzhardinge
2009-05-07 20:25 ` [PATCH 6/8] x86: use flush_tlb_others to implement flush_tlb_all Jeremy Fitzhardinge
2009-05-08 15:24 ` Ian Campbell
2009-05-08 15:49 ` Jeremy Fitzhardinge
2009-05-08 15:52 ` Ian Campbell
2009-05-11 13:09 ` [tip:x86/xen] x86: use flush_tlb_others to implement flush_tlb_all, fix tip-bot for Ian Campbell
2009-05-11 13:12 ` Ingo Molnar
2009-05-11 15:00 ` Ian Campbell
2009-05-11 15:11 ` Ingo Molnar
2009-05-11 15:39 ` Ian Campbell
2009-05-11 15:42 ` Ingo Molnar
2009-05-11 15:59 ` Ian Campbell
2009-05-11 15:40 ` Ingo Molnar [this message]
2009-05-11 15:06 ` tip-bot for Ian Campbell
2009-05-07 20:25 ` [PATCH 7/8] xen/i386: reserve Xen pagetables Jeremy Fitzhardinge
2009-05-07 20:25 ` [PATCH 8/8] xen: reserve Xen start_info rather than e820 reserving Jeremy Fitzhardinge
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=20090511154034.GA30361@elte.hu \
--to=mingo@elte.hu \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox