Xen project Mailing List

[Xen-users] Re: Why CPU intensive domain gets 60ms time slice?

From: Thawan Kooburat <kthawan@xxxxxxxxx>

Date: Thu, 3 Mar 2011 20:26:12 -0600

Delivery-date: Thu, 03 Mar 2011 18:27:31 -0800

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=pjq83QglHcS/Nij62GEeILZMDpiMK1Q41wp6KibG5gMo1e0CI89Radxpve2Z5Nxb57 nMYB9He0hHAc8/gFUuByHf76yVP7ROJYCwq+05Ad8xcHyphHnejXq9ud3p1tSpXBtle5 5xmSRKkgnpB7HYhZXgaK1zavObazRuhUY1HPI=

List-id: Xen user discussion <xen-users.lists.xensource.com>

Found the reason, I added TRC_SCHED_CONTINUE_RUNNING into the formats used to print the log. Now, it made more sense. CPU2 1663536439522 (+149622930) switch_infprev [ old_domid = 0x00007fff, runtime = 60006279 ] CPU2 1663536440024 (+ 502) switch_infnext [ new_domid = 0x00000001, time = 1100, r_time = 30000000 ] CPU2 1663536440557 (+ 533) __enter_scheduler [ prev<domid:edomid> = 0x00007fff : 0x00000002, next<domid:edomid> = 0x00000001 : 0x00000000 ] CPU2 1663536441067 (+ 510) running_to_runnable [ dom:vcpu = 0x7fff0002 ] CPU2 1663536441809 (+ 742) runnable_to_running [ dom:vcpu = 0x00010000 ] CPU2 0 (+ 0) cpu_change 0x00000002 CPU2 1663611251009 (+74809200) continue_running [ vcpu:dom = 0x00010000 ] CPU2 1663685986987 (+74735978) continue_running [ vcpu:dom = 0x00010000 ] CPU2 1663685997997 (+ 11010) switch_infprev [ old_domid = 0x00000001, runtime = 60007641 ] CPU2 1663685998590 (+ 593) switch_infnext [ new_domid = 0x00007fff, time = 60007641, r_time = 4294967295 ] -- Thawan Kooburat Graduate Student Department of Computer Science UW-Madison _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.