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: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [pv_ops domU] - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update
From: Jed Smith <jsmith@xxxxxxxxxx>
Date: Fri, 21 Aug 2009 12:30:40 -0400
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Fri, 21 Aug 2009 09:31:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A8EC964.3020605@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>
Organization: Linode, LLC
References: <4A89F539.2070801@xxxxxxxxxxxx> <4A8A2E74.9010202@xxxxxxxx> <4A8AB7B8.4070905@xxxxxxxxxxxx> <4A8B0BD2.2060304@xxxxxxxx> <4A8D9FC7.7070101@xxxxxxxxxx> <4A8DDCEF.9020303@xxxxxxxx> <4A8DE6B7.7060001@xxxxxxxxxx> <4A8DEC9C.50207@xxxxxxxx> <4A8EB5CD.6070706@xxxxxxxxxx> <4A8EC964.3020605@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Macintosh/20090605)
Jeremy Fitzhardinge wrote:
> Well, to be honest, I can't say I can get very excited about tracking
> down where a bug *disappeared*.  Do you have a strong need to support
> current kernels on old versions of Xen, or would it be simpler to update
> Xen?

We understand!  You have a lot on your plate.  We had reached that
conclusion already, and we just wondered if there was an easy fix.
Soaking dev time into a bug that has disappeared is never appealing.
We'll queue upgrades for our affected machines.

> (Though I suspect that PARAVIRT_SPINLOCKS may be the explanation in this
> case, assuming you have them enabled.)

Don't have *PARAVIRT_SPINLOCK* in .config for my kernels...hm.  Just
stuff for debugging spinlocks and the usual PARAVIRT options.


>     J

Xen-devel mailing list

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