[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Re: Isolation and time

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?


> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Keir Fraser
> Sent: Saturday, June 14, 2008 2:59 AM
> To: dan.magenheimer@xxxxxxxxxx; Dave Winchell; Ben Guthro; xen-devel
> Subject: [Xen-devel] Re: Isolation and time
> On 14/6/08 03:20, "Dan Magenheimer" 
> <dan.magenheimer@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.