From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Cc: Dave Winchell <dwinchell@virtualiron.com>
Subject: RE: [PATCH] [RFC] Building guests on monotonic Xen system time
Date: Tue, 3 Jun 2008 13:47:13 -0600 [thread overview]
Message-ID: <20080603134713906.00000002776@djm-pc> (raw)
In-Reply-To: <C45D8389.18FE0%keir.fraser@eu.citrix.com>
> I have a pretty clear vision of what I want now, so I will make the
> necessary adjustments to the patch. Then we can go from there
I noticed you fixed a related bug (cset 17760), but haven't
seen anything that changes timer_mode==0 back to non-monotonic.
Is that still on your list, or do you want me to submit a
patch for that?
Related, I'm wondering if we should change the defaults for
timer_mode and hpet now. I'll start a new thread on that
to avoid topic drift.
Dan
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: Saturday, May 24, 2008 1:34 AM
> To: dan.magenheimer@oracle.com; Xen-Devel (E-mail)
> Cc: Dave Winchell
> Subject: Re: [Xen-devel] [PATCH] [RFC] Building guests on
> monotonic Xen
> system time
>
>
> On 23/5/08 23:44, "Dan Magenheimer"
> <dan.magenheimer@oracle.com> wrote:
>
> > Here's another option: I think delay_for_missed_ticks is
> > the only mode where time must be set backwards. All of the
> > other modes track wallclock. It looks possible that we
> > could enforce monotonicity for the other three modes and
> > not enforce it for delay_for_missed_ticks (which is,
> > unfortunately, the default).
> >
> > If this is acceptable to you (and you don't disagree with
> > my "only mode...set backwards" conjecture), I'll try to
> > code a patch for this.
>
> I agree with your analysis. I couldn't remember if any modes
> other than 0
> would require non-monotonic time across VCPUs, but it does
> appear that this
> property is exclusive to mode 0.
>
> > P.S. I think the answer is no, but is there any way to specify
> > gang-scheduling for a domain? If so, we could say if your
> > OS is non-resilient to preemption and your application requires
> > time monotonicity, you must specify gang scheduling.
>
> There isn't currently a way to request gang scheduling. I
> think that is a
> second step anyway. It sounds like you could simply turn off your
> monotonicity checks for timer mode 0 and I'll be happy.
>
> I have a pretty clear vision of what I want now, so I will make the
> necessary adjustments to the patch. Then we can go from there
> if you think
> further modifications are required.
>
> -- Keir
>
>
>
next prev parent reply other threads:[~2008-06-03 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 17:31 [PATCH] [RFC] Building guests on monotonic Xen system time Dan Magenheimer
2008-05-19 18:27 ` Dan Magenheimer
2008-05-20 0:56 ` Dan Magenheimer
2008-05-20 7:36 ` Keir Fraser
2008-05-21 19:01 ` Dan Magenheimer
2008-05-22 8:46 ` Keir Fraser
2008-05-22 16:05 ` Dan Magenheimer
2008-05-22 16:11 ` Keir Fraser
2008-05-23 22:44 ` Dan Magenheimer
2008-05-24 7:34 ` Keir Fraser
2008-06-03 19:47 ` Dan Magenheimer [this message]
2008-06-03 21:10 ` Keir Fraser
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=20080603134713906.00000002776@djm-pc \
--to=dan.magenheimer@oracle.com \
--cc=dwinchell@virtualiron.com \
--cc=keir.fraser@eu.citrix.com \
--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.