From: Jeremy Fitzhardinge <jeremy@goop.org>
To: MaoXiaoyun <tinnycloud@hotmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>,
giamteckchoon@gmail.com, konrad.wilk@oracle.com
Subject: Re: Kernel BUG at arch/x86/mm/tlb.c:61
Date: Fri, 15 Apr 2011 14:22:29 -0700 [thread overview]
Message-ID: <4DA8B715.9080508@goop.org> (raw)
In-Reply-To: <BLU157-w42DAD248C94153635E9749DAAC0@phx.gbl>
On 04/15/2011 05:23 AM, MaoXiaoyun wrote:
> Hi:
>
> Could the crash related to this patch ?
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=45bfd7bfc6cf32f8e60bb91b32349f0b5090eea3
>
> Since now TLB state change to TLBSTATE_OK(mmu_context.h:40) is before
> cpumask_clear_cpu(line 49).
> Could it possible that right after execute line 40 of mmu_context.h,
> CPU revice IPI from other CPU to
> flush the mm, and when in interrupt, find the TLB state happened to be
> TLBSTATE_OK. Which conflicts.
Does reverting it help?
J
>
> Thanks.
>
> arch/x86/include/asm/mmu_context.h
>
> 33 static inline void switch_mm(struct mm_struct *prev, struct
> mm_struct *next,
> 34 <+++<+++<+++ struct task_struct *tsk)
> 35 {
> 36 <+++unsigned cpu = smp_processor_id();
> 37
> 38 <+++if (likely(prev != next)) {
> 39 #ifdef CONFIG_SMP
> 40 <+++<+++percpu_write(cpu_tlbstate.state, TLBSTATE_OK);
> 41 <+++<+++percpu_write(cpu_tlbstate.active_mm, next);
> 42 #endif
> 43 <+++<+++cpumask_set_cpu(cpu, mm_cpumask(next));
> 44
> 45 <+++<+++/* Re-load page tables */
> 46 <+++<+++load_cr3(next->pgd);
> 47
> 48 <+++<+++/* stop flush ipis for the previous mm */
> 49 <+++<+++cpumask_clear_cpu(cpu, mm_cpumask(prev));
>
>
next prev parent reply other threads:[~2011-04-15 21:22 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <COL0-MC1-F14hmBzxHs00230882@col0-mc1-f14.Col0.hotmail.com>
2011-04-08 11:24 ` kernel BUG at arch/x86/xen/mmu.c:1860! MaoXiaoyun
2011-04-08 11:46 ` MaoXiaoyun
2011-04-10 3:57 ` kernel BUG at arch/x86/xen/mmu.c:1872 MaoXiaoyun
2011-04-10 4:29 ` MaoXiaoyun
2011-04-10 13:57 ` MaoXiaoyun
2011-04-10 20:14 ` Teck Choon Giam
2011-04-11 12:16 ` Teck Choon Giam
2011-04-11 12:22 ` Teck Choon Giam
2011-04-11 12:31 ` MaoXiaoyun
2011-04-11 15:25 ` Teck Choon Giam
2011-04-12 3:30 ` MaoXiaoyun
2011-04-12 16:08 ` Teck Choon Giam
2011-04-11 18:08 ` Jeremy Fitzhardinge
2011-04-12 3:35 ` MaoXiaoyun
2011-04-12 6:48 ` Grant Table Error on 2.6.32.36 + Xen 4.0.1 MaoXiaoyun
2011-04-12 8:46 ` Konrad Rzeszutek Wilk
2011-04-12 9:02 ` MaoXiaoyun
2011-04-12 9:11 ` Kernel BUG at arch/x86/mm/tlb.c:61 MaoXiaoyun
2011-04-12 10:00 ` Konrad Rzeszutek Wilk
2011-04-12 10:10 ` MaoXiaoyun
2011-04-14 6:16 ` MaoXiaoyun
2011-04-14 7:26 ` Teck Choon Giam
2011-04-14 7:56 ` MaoXiaoyun
2011-04-14 11:16 ` MaoXiaoyun
2011-04-15 12:23 ` MaoXiaoyun
2011-04-15 21:22 ` Jeremy Fitzhardinge [this message]
2011-04-18 15:20 ` MaoXiaoyun
2011-04-25 3:15 ` MaoXiaoyun
2011-04-26 5:52 ` Tian, Kevin
2011-04-26 7:04 ` MaoXiaoyun
2011-04-26 8:31 ` Tian, Kevin
2011-04-28 23:29 ` Jeremy Fitzhardinge
2011-04-29 0:19 ` Tian, Kevin
2011-04-29 1:50 ` MaoXiaoyun
2011-04-29 1:57 ` Tian, Kevin
2011-04-25 4:42 ` MaoXiaoyun
2011-04-25 12:54 ` MaoXiaoyun
2011-04-25 13:11 ` MaoXiaoyun
2011-04-25 15:05 ` MaoXiaoyun
2011-04-26 5:55 ` Tian, Kevin
2011-04-12 16:32 ` kernel BUG at arch/x86/xen/mmu.c:1872 Teck Choon Giam
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=4DA8B715.9080508@goop.org \
--to=jeremy@goop.org \
--cc=giamteckchoon@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=tinnycloud@hotmail.com \
--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 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.