This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: kernel BUG at arch/x86/xen/mmu.c:1872

To: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>
Subject: [Xen-devel] Re: kernel BUG at arch/x86/xen/mmu.c:1872
From: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
Date: Mon, 11 Apr 2011 20:16:53 +0800
Cc: jeremy@xxxxxxxx, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, keir@xxxxxxx, ian.campbell@xxxxxxxxxx, konrad.wilk@xxxxxxxxxx, dave@xxxxxxxxxx
Delivery-date: Mon, 11 Apr 2011 05:17:30 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2ke2o8o3kqcfaaleUqHqfzk7/eCO1+FFgwilnWcF1gs=; b=Nrm87hiEHMHizRtQhkal2GENmOzSHKxQvZhxOv38CJf4qRvIKGcKrMtLGKG97XGnxd 4hrb3h1P9p2PkBfmT9ADQB+RFb0BXoO8QjgEAUJMIkQxZ+fkIpDofsaWz6D5bUDg8Z6L rxFg5pbKDQJ4QtBt3aG8oqQc8vHKRNICSIp2I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wBEY3CgsigEPne9h/sjDPvcs+W4peZq5Bs0PCDZBD/obiX/c1lVxVtHQmjFOwHGgPh AKMM35mhbPJofKQWbcBwyzca1QQCGEzznYWlP8CENKahusAdfUVq5N9Z41lQyTTFNjzT GoJlcEtmrzBX6aIall10zYpf7yE2dDMssHZgk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTimgh_iip27zkDPNV9r7miwbxHmdVg@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <COL0-MC1-F14hmBzxHs00230882@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <BLU157-w488E5FEBD5E2DBC0666EF1DAA70@xxxxxxx> <BLU157-w5025BFBB4B1CDFA7AA0966DAA90@xxxxxxx> <BLU157-w540B39FBA137B4D96278D2DAA90@xxxxxxx> <BANLkTimgh_iip27zkDPNV9r7miwbxHmdVg@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Hi,
> Sorry, since this mmu related BUG has been troubled me for very
> long... I really want to "kill" this BUG but my knowledge in kernel
> hacking and/or xen is very limited.
> While waiting for Jeremy or Konrad or others ...
> Many thanks for spending time to track down this mmu related BUG.  I
> have backported the commit from
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=64141da587241301ce8638cc945f8b67853156ec
> to PVOPS kernel and patch attached.  I won't know whether
> did I backport it correctly nor does it affects anything.  I am
> currently testing the PVOPS kernel with this patch applied
> and also unset CONFIG_DEBUG_PAGEALLOC.  Currently running testcrash.sh
> loop 1000 as I am unable to reproduce this mmu BUG 1872 in
> testcrash.sh loop 100.  Please note that when CONFIG_DEBUG_PAGEALLOC
> is unset, I can reproduce this mmu BUG 1872 easily within <50
> testcrash.sh loop cycle with PVOPS version to
> kernel.  Now test with this backport patch to see whether I can
> reproduce this mmu BUG... ...
> Kindest regards,
> Giam Teck Choon

I have tested with my backport patch and it is working fine as I am
unable to reproduce the mmu.c 1872 or 1860 bug with
CONFIG_DEBUG_PAGEALLOC not set.  I tested with testcrash.sh loop 100
and 1000.  Now doing testcrash.sh loop 10000.

Xiaoyun, is it possible for you to test my patch and see whether can
you reproduce the mmu.c 1872/1860 bug?

Can anyone of you review my patch?

I will post a format patch according to
Documentation/SubmittingPatches in my next reply and hopefully can be


Kindest regards,
Giam Teck Choon

Xen-devel mailing list