From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jed Smith Subject: Re: Re: [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update Date: Fri, 21 Aug 2009 12:30:40 -0400 Message-ID: <4A8ECBB0.2050007@linode.com> References: <4A89F539.2070801@theshore.net> <4A8A2E74.9010202@goop.org> <4A8AB7B8.4070905@theshore.net> <4A8B0BD2.2060304@goop.org> <4A8D9FC7.7070101@linode.com> <4A8DDCEF.9020303@goop.org> <4A8DE6B7.7060001@linode.com> <4A8DEC9C.50207@goop.org> <4A8EB5CD.6070706@linode.com> <4A8EC964.3020605@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A8EC964.3020605@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: xen devel , Keir Fraser List-Id: xen-devel@lists.xenproject.org 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. Jed > > J >