24 messages in com.xensource.lists.xen-develRe: [Xen-devel] 3.1.x and 3.2.x releases
FromSent OnAttachments
Keir Fraser19 Dec 2007 08:00 
Dan Magenheimer19 Dec 2007 09:22 
John Levon19 Dec 2007 10:34 
You, Yongkang19 Dec 2007 19:58 
John Levon19 Dec 2007 21:02 
Keir Fraser20 Dec 2007 02:25 
Dan Magenheimer26 Dec 2007 11:52 
Keir Fraser26 Dec 2007 15:07 
S.Çağlar Onur27 Dec 2007 15:37 
Keir Fraser28 Dec 2007 00:38 
S.Çağlar Onur28 Dec 2007 02:16 
Keir Fraser28 Dec 2007 05:16 
John Levon28 Dec 2007 06:55 
Keir Fraser28 Dec 2007 07:18 
Daniel P. Berrange28 Dec 2007 07:46 
Keir Fraser28 Dec 2007 08:00 
Dan Magenheimer28 Dec 2007 14:51 
S.Çağlar Onur28 Dec 2007 15:04 
Ryan Scott28 Dec 2007 17:17 
Keir Fraser29 Dec 2007 01:18 
Keir Fraser29 Dec 2007 01:21 
S.Çağlar Onur01 Jan 2008 08:31 
Dan Magenheimer03 Jan 2008 09:23 
Keir Fraser06 Jan 2008 14:50 
Subject:Re: [Xen-devel] 3.1.x and 3.2.x releases
From:Keir Fraser (Keir@cl.cam.ac.uk)
Date:12/26/2007 03:07:44 PM
List:com.xensource.lists.xen-devel

I only did a straightforward port of the xend parts, without much testing. You could add tracing to the hvm_param hypercall in xen/arch/x86/hvm/hvm.c, and see whether the timer mode is being set for your HVM guest that way.

-- Keir

On 26/12/07 19:53, "Dan Magenheimer" <dan.@oracle.com> wrote:

Thanks Keir... but in trying to test this, I find that timer_mode seems to be displayed in sxp debug output in xend.log for xen-unstable, but I don't see sxp output for timer_mode in xend.log for xen-3.1-testing (cset 15564). Does timer_mode get properly set and passed down to xen in xen-3.1-testing simply by adding a (e.g.) "timer_mode=3" line in the config file? If so, is there another way I can verify that?

-----Original Message----- From: xen-@lists.xensource.com [mailto:xen-@lists.xensource.com]On Behalf Of Keir Fraser Sent: Thursday, December 20, 2007 3:26 AM To: dan.@oracle.com; xen-devel Subject: Re: [Xen-devel] 3.1.x and 3.2.x releases

Done.

K.

On 19/12/07 17:22, "Dan Magenheimer" <dan.@oracle.com> wrote:

Any chance the sequence of timer/tick fixes that you, Dave Winchell, Ben Guthro, Haitao Shan, and Eddie Dong were discussing/developing over the last two months could get into 3.1.3? Clocks that gain time can cause some pretty nasty difficult-to-diagnose real customer problems.

-----Original Message----- From: xen-@lists.xensource.com [mailto:xen-@lists.xensource.com]On Behalf Of Keir Fraser Sent: Wednesday, December 19, 2007 9:01 AM To: xen-devel Subject: [Xen-devel] 3.1.x and 3.2.x releases

Folks,

A new release candidate for 3.2.0 has just been checked into the xen-unstable tree. It's available from staging and will be in the main tree when it has passed internal regression tests.

Meanwhile, in preparation for 3.1.3, please let me know if there are any further patches from xen-unstable that should be backported into the 3.1 branch. You can pull the xen-3.1-testing.hg repository to see what has already been backported.

Thanks, Keir