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


Re: [Xen-devel] Re: [pv_ops domU] - unable to handle kernel pag

To: Jed Smith <jsmith@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [pv_ops domU] - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 20 Aug 2009 17:38:52 -0700
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 20 Aug 2009 17:39:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A8DE6B7.7060001@xxxxxxxxxx>
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: <4A89F539.2070801@xxxxxxxxxxxx> <4A8A2E74.9010202@xxxxxxxx> <4A8AB7B8.4070905@xxxxxxxxxxxx> <4A8B0BD2.2060304@xxxxxxxx> <4A8D9FC7.7070101@xxxxxxxxxx> <4A8DDCEF.9020303@xxxxxxxx> <4A8DE6B7.7060001@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 08/20/09 17:13, Jed Smith wrote:
> Jeremy Fitzhardinge wrote:
>> I see your bisect tested c47c1b1f3a9 as OK, so try e4d0407185.
> jsmith@lindev7:~/linux-2.6$ git reset --hard e4d0407185
> HEAD is now at e4d0407 xen: use direct ops on 64-bit
> http://lateralus.jedsmith.org/Jeremy1/
> Fails as before there.  I bisected using that commit as the right side
> before, but most of the kernels I built failed to boot before the first
> printk(); I wasn't sure if there was something environmental going on.

Yes, there's a lot of stuff on that line which will not bisect well;
there were substantial changes to percpu data handling, and a change to
some of the core pvops calling conventions.  It will take care to choose
good bisection points to narrow things down.

But it also sounds like it could be on the Xen side.  Would it be
possible to try and narrow down where Xen stops breaking?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>