From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: A clocksource question Date: Tue, 9 Mar 2010 10:42:20 -0500 Message-ID: <20100309154220.GB22018@phenom.dumpdata.com> References: <4B9628F3.5060101@invisiblethingslab.com> <4B962BD1.3060307@invisiblethingslab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4B962BD1.3060307@invisiblethingslab.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Joanna Rutkowska Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Tue, Mar 09, 2010 at 12:06:57PM +0100, Joanna Rutkowska wrote: > On 03/09/2010 11:54 AM, Joanna Rutkowska wrote: > > On 03/09/2010 11:50 AM, Keir Fraser wrote: > >> On 09/03/2010 10:47, "Joanna Rutkowska" > >> wrote: > >> > >>> Interestingly the above problem didn't seem to affect the Dom0 kernel > >>> based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to > >>> run this kernel when using Xen 3.4.2. > >> > >> You could run the 3.4.3 release candidates? > >> > > Let's just say that after my recent experience with a 4.0.0 release > > candidate, I decided to use a stable version (or at least for the > > hypervisor) for now :) I really want to use on a production system. > > > > Perhaps you would say that in that case I should not be using a pvops0 > > kernel at all? But what would be a good alternative with all reasonable > > hardware support then? > > > ...plus the xen/stable-2.6/.32 doesn't have the pciback, which I happen > to need in Dom0... You will be happy to know that I just finished that. git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git pv/pciback-2.6.32 or a copy of jeremy/xen/net with the pciback merged in: pv/merge.xen.next Or refer to the e-mail I have sent to Xen-Devel with details.