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 16:31:59 -0700
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 20 Aug 2009 16:32:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A8D9FC7.7070101@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>
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 12:11, Jed Smith wrote:
> Jeremy Fitzhardinge wrote:
>>>> Is it new with
> Perhaps earlier, and we're just now running into it.  I am able to
> reproduce on the v2.6.30 release.  My initial bisect leads me here (from
> bad=v2.6.30 and good=v2.6.29 in linux-2.6.git):
> commit 9049a11de73d3ecc623f1903100d099f82ede56c
> Merge: c47c1b1 e4d0407
> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
> Date:   Wed Feb 11 11:52:22 2009 -0800
>     Merge commit 'remotes/tip/x86/paravirt' into x86/untangle2
> I note astutely, however, that's a pretty large merge commit.

Yeah.  If it shows up in that merge, then obviously it must be one of
the constituent changes which is provoking the problem, unless there's
something about the merge itself.

Just to double check, can to test the two parents,
c47c1b1f3a9d6973108020df1dcab7604f7774dd and
e4d0407185cdbdcfd99fc23bde2e5454bbc46329, to see if one or both exhibits
the problem?

I see your bisect tested c47c1b1f3a9 as OK, so try e4d0407185.


Xen-devel mailing list

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