From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
Subject: RE: 3.1.x and 3.2.x releases
Date: Wed, 26 Dec 2007 12:53:21 -0700
Message-ID: <20071226125321671.00000002676@djm-pc>
References: <C38FF3C4.1A122%Keir.Fraser@cl.cam.ac.uk>
Reply-To: "dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C38FF3C4.1A122%Keir.Fraser@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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-testin=
g simply by adding a (e.g.) "timer_mode=3D3" line in the config file?  If s=
o, is there another way I can verify that?

Thanks,
Dan

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com]On Behalf Of Keir Fraser
> Sent: Thursday, December 20, 2007 3:26 AM
> To: dan.magenheimer@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.magenheimer@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.
> >
> > Thanks,
> > Dan
> >
> >> -----Original Message-----
> >> From: xen-devel-bounces@lists.xensource.com
> >> [mailto:xen-devel-bounces@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
> >>
> >>
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> >>
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> =

> =

> =

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>