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] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle ker

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Thu, 2 Dec 2010 11:34:49 -0800
Cc: Boris Derzhavets <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 02 Dec 2010 11:35:42 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4XgwI1jvOWodlpNH6AY2AAt3Y0FvY/B00SJigd+LLqs=; b=Yo3Y4+tIdFiEGyDdKqcvs5iMPcMrlTzvghC5nBy6jMM3no5QoSRPmzkO3HDrYdTxp+ TEFKNHt7Y1qOlr1YZmiVLX3I+c7Alh44j663tBjqJ12NVMVDpZ158ciA0DBTpoF3Lqdb FJSUAsDiFsguvGyNdoUhe6pHpPF+zYm1vZL7g=
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=stXNhW4i4e6NAOP8PuYwRM67S1GTDAv2CaRqRblMMna6QlT2AP6D0CqTeIn0BmI63O 7dfpMlJ4SKUUofIzHQVMLaX/5azxLkM/acR86QQd7bqp/fucg6V3rZvyqYzEjmJHagp7 OR0WVAIi6pUjP1eTbFzN3vUOfGLSb3Z5aN4CE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CF7EA77.8030302@xxxxxxxx>
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: <AANLkTim6OyguwUPVryBjw2RJYoiiW_cE10yw1T2pzpEJ@xxxxxxxxxxxxxx> <697216.62238.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <AANLkTi=_gdYqY5xTE73_oR56wVNa00DrJz3iG8b=KDO8@xxxxxxxxxxxxxx> <4CF73DCF.4010200@xxxxxxxx> <AANLkTi=KTY_0JxzTrYVw8Gcpgwhrsw7tUHmk2yxr2dBX@xxxxxxxxxxxxxx> <AANLkTimErriqP+G7DiVzZp9WJpHYEseX-Wo+aA4vuKg9@xxxxxxxxxxxxxx> <4CF7E558.3010206@xxxxxxxx> <AANLkTi=FRrEK7-bOwjAc1ymPKj8fMPgJ6_F0xkj29W-h@xxxxxxxxxxxxxx> <4CF7EA77.8030302@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Dec 2, 2010 at 10:50 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> On 12/02/2010 10:38 AM, Bruce Edge wrote:
>>> OK, these look like exactly the sort of symptoms which should be fixed
>>> by that patch, so assuming you're actually running the right kernel
>>> (worth checking!  I get bitten by this occasionally), there's something
>>> else going on here.
>> You're right, my branch was a day out of date. I didn't have the last
>> changes to:
>>
>>  arch/x86/xen/grant-table.c |   28 +++++---
>>  arch/x86/xen/mmu.c         |  124 ++++++++++--------------------
>>  include/linux/mm.h         |    6 ++
>>  include/linux/vmalloc.h    |    2 -
>>  mm/memory.c                |   56 ++++++++++----
>>  mm/vmalloc.c               |  182 
>> ++++++++++++++------------------------------
>
> Those are the ones.
>
>> rebuilding with great expectations now :-)
>
> I'm doing a kernel build over NFS at the moment.  (Well, still copying
> sources.)

Fixed!  Nice work.

This unblocks a large chunk of my work. Thank you.

This thread can happily die now.

-Bruce

>
>    J
>

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