All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: RE: 3.1.x and 3.2.x releases
Date: Wed, 26 Dec 2007 12:53:21 -0700	[thread overview]
Message-ID: <20071226125321671.00000002676@djm-pc> (raw)
In-Reply-To: <C38FF3C4.1A122%Keir.Fraser@cl.cam.ac.uk>

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?

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
>

  reply	other threads:[~2007-12-26 19:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 16:00 3.1.x and 3.2.x releases Keir Fraser
2007-12-19 17:22 ` Dan Magenheimer
2007-12-20 10:26   ` Keir Fraser
2007-12-26 19:53     ` Dan Magenheimer [this message]
2007-12-26 23:08       ` Keir Fraser
2007-12-28 22:52         ` Dan Magenheimer
2007-12-29  9:18           ` Keir Fraser
2007-12-29  9:21             ` Keir Fraser
2008-01-03 17:24               ` Dan Magenheimer
2007-12-19 18:34 ` John Levon
2007-12-20  3:58 ` You, Yongkang
2007-12-20  5:02   ` John Levon
2007-12-27 23:37 ` S.Çağlar Onur
2007-12-28  8:38   ` Keir Fraser
2007-12-28 10:17     ` S.Çağlar Onur
2007-12-28 13:16       ` Keir Fraser
2007-12-28 14:55         ` John Levon
2007-12-28 15:19           ` Keir Fraser
2007-12-29  1:18           ` Ryan Scott
2007-12-28 15:47         ` Daniel P. Berrange
2007-12-28 16:00           ` Keir Fraser
2008-01-01 16:31             ` S.Çağlar Onur
2008-01-06 22:50               ` Keir Fraser
2007-12-28 23:04           ` S.Çağlar Onur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071226125321671.00000002676@djm-pc \
    --to=dan.magenheimer@oracle.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.