All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
	Dave Winchell <dwinchell@virtualiron.com>,
	Ben Guthro <bguthro@virtualiron.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: RE: Re: Isolation and time
Date: Sat, 14 Jun 2008 09:16:53 -0600	[thread overview]
Message-ID: <20080614091653406.00000002884@djm-pc> (raw)
In-Reply-To: <C47946E8.19E0A%keir.fraser@eu.citrix.com>

That's what I thought.  Sorry to belabour, but
that leads to one more question:

If one were to put an appropriately random CPU-only load
on every processor on domain0 (assuming domain0 runs
on all physical processors), then this would presumably
be sufficient to exercise a domain-under-test's time
synchronization, correct?

Thanks,
Dan

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com]On Behalf Of Keir Fraser
> Sent: Saturday, June 14, 2008 2:59 AM
> To: dan.magenheimer@oracle.com; Dave Winchell; Ben Guthro; xen-devel
> Subject: [Xen-devel] Re: Isolation and time
> 
> 
> On 14/6/08 03:20, "Dan Magenheimer" 
> <dan.magenheimer@oracle.com> wrote:
> 
> > But is there anything else?
> >
> > Suppose the credit scheduler were modified to
> > optionally schedule random "spurts" when the
> > sum of caps was less than the total available
> > CPU.  Would you then expect the results to be
> > essentially the same?
> 
> I wouldn't expect another domain's workload to affect the 
> test domain's time
> synchronisation except so far as the workload affects the domain's CPU
> demand over time. I imagine you could therefore simulate that 
> CPU demand
> process inside the scheduler. How hard that is presumably depends how
> accurate you want the simulation to be.
> 
>  -- Keir
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2008-06-14 15:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B99564216C25704085A82B41C46DD3427B060A@exchange.katana.local>
2008-06-13 17:53 ` Isolation and time Dan Magenheimer
2008-06-13 18:49   ` Kernel printk timestamps and walltime drift Roger Cruz
2008-06-13 19:47     ` Keir Fraser
2008-06-13 20:10       ` Roger Cruz
2008-06-13 20:31         ` Keir Fraser
2008-06-13 20:06     ` Dan Magenheimer
2008-06-13 21:05       ` Roger Cruz
2008-06-13 21:21         ` Dan Magenheimer
2008-06-13 21:36           ` Keir Fraser
2008-06-13 22:02             ` Roger Cruz
2008-06-13 22:09               ` Keir Fraser
2008-06-13 19:38   ` Isolation and time Keir Fraser
2008-06-14  2:20     ` Dan Magenheimer
2008-06-14  8:59       ` Keir Fraser
2008-06-14 15:16         ` Dan Magenheimer [this message]
2008-06-14 15:25           ` Keir Fraser
2008-07-01  0:22             ` Dan Magenheimer

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=20080614091653406.00000002884@djm-pc \
    --to=dan.magenheimer@oracle.com \
    --cc=bguthro@virtualiron.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.