From mboxrd@z Thu Jan 1 00:00:00 1970 From: Emmanuel Ackaouy Subject: Re: [Q] about Credit Scheduler Dom0 Scheduling policy. Date: Tue, 24 Oct 2006 10:49:52 +0100 Message-ID: <20061024094952.GA29248@cockermouth.uk.xensource.com> References: <200610181150.k9IBoP8W031962@fjmscan502.ms.jp.fujitsu.com> <20061018131115.GA5327@cockermouth.uk.xensource.com> <20061018132410.GA5372@cockermouth.uk.xensource.com> <200610230414.k9N4EKGJ011580@fjmscan501.ms.jp.fujitsu.com> <20061023143210.GA26848@cockermouth.uk.xensource.com> <200610240647.k9O6lYQR004608@fjmscan503.ms.jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200610240647.k9O6lYQR004608@fjmscan503.ms.jp.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Atsushi SAKAI Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Oct 24, 2006 at 03:46:59PM +0900, Atsushi SAKAI wrote: > Currently, I am testing on IA64. > CPU=1595MHz > itc=1595MHz In the chunk of the trace file you sent, the scheduler is behaving quite well. The domU being woken up at various times on a clock boundary (10ms) must be due to some timers. There is one case where dom0 wakes up and doesn't preempt the CPU (the first dom0 wake in the trace file) though. I would like to see a bigger chunk of your trace file and scan it to see if there are other examples of this. If it's too big for the list, can you send it to me privately or put it up on some publicly accessible server somewhere? Thanks.