WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] upgrade to 2.6.18.8 ?

To: "Eduardo Habkost" <ehabkost@xxxxxxxxxx>
Subject: Re: [Xen-devel] upgrade to 2.6.18.8 ?
From: "Teck Choon Giam" <giamteckchoon@xxxxxxxxx>
Date: Wed, 3 Oct 2007 23:43:14 +0800
Cc: Keir Fraser <keir@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Stefan Berger <stefanb@xxxxxxxxxx>
Delivery-date: Wed, 03 Oct 2007 08:43:54 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=TQqVvfGFYtRDMZz6+CUJd6ktEXsziwbFA0RhxYQcfjo=; b=aSlLf85AxshcrqivTf0UcdEzAfUFj2rUCzwEWX3IAQBmc01QBIVpVR7kWkuxREHcb0J3lRLsvwTzhjUArzTwxLm+9PgNtjaf7fr7mGlHA5SwVq604/FgqAhkcCyO5Cx02xi+J6aGHxHb6D0dw9EySA5ITvTZ5u4Me3ursqGt2IE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OYNukCmSgqgBIe6MmOhgTziFHSbwqm9s18wuP0UgPDHRjQstlDul1NwqVkSoAnjvwfnFteOJaPw5JjZ2rha997lck9bCfSeeDe9OYE/CLZp9q97nvFY4SPzC3dkTofYgFLy/HL43Lmg6GhPamG3uV5H4B6HvaHH9dQrzXbnpqL4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071003125129.GE6232@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <OF2D584034.C46200DE-ON85257368.007160AB-85257368.0071C9C0@xxxxxxxxxx> <9b5c9bb30710030441mae3f1ebw2fa74551e34d3ef2@xxxxxxxxxxxxxx> <20071003125129.GE6232@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 10/3/07, Eduardo Habkost <ehabkost@xxxxxxxxxx> wrote:
> Do you have CONFIG_HIGHPTE enabled? CONFIG_HIGHPTE have caused problems
> on 2.6.20 and 2.6.21 rebases of Xen 3.1 on Fedora, on pgd_pin() and
> other page table updating hypercalls, because the kernel somehow was
> trying to map page table entries as writeable.

# grep CONFIG_HIGHPTE /boot/config-2.6.18.8-xen0
CONFIG_HIGHPTE=y

So yes it is enabled.

> 'xm dmesg' should give more information on the cause of this Oops.

Unfortunately I don't look at the xm dmesg during the Oops closely and
now the system has been running on xen-3.1.1-rc2.  I guess I will try
to reproduce and post related xm dmesg and oops message when it happen
when I have the time to test on my other test system after getting my
new RAM (waiting for 6 x 1GB RAM).

> I haven't reproduced my CONFIG_HIGHPTE problems on 2.6.18-xen-3.1.0,
> also. I don't know if it was a problem of our Xen rebase or the problem
> is present on the 2.6.18 xenbits tree.
>
> Enabling CONFIG_HIGHPTE under Xen is not recommended, anyway. Even if
> it was working, performance will probably suffer.

Ok, noted and will try on disabling CONFIG_HIGHPTE and try whether can
I reproduce the oops :)

Thanks ;)

Kindest regards,
Giam Teck Choon

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel