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

[Xen-devel] Scheduler stats and some doubts


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
  • Date: Sat, 12 Sep 2009 17:39:17 +0200
  • Delivery-date: Sat, 12 Sep 2009 08:40:03 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=EyoIti6JS6E7nPwG5KmGDRHMiS2sL2VXOHw0sMvKmNffDggfE8llD/b2Z8GfLNgnM5 g0U+jYn3Ea+kJ8cWEhrO3k9/Qoz/+2X+DDUuxZiJVOofFuijKY9iXpXfUpqfmbTvfphq 8dqcdu1k6l8UCuVCU4hWIn6DaEp2vVHPg5bFU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,
someone can tell me how to enable scheduler statistics and how to display them?

I found this comment:

---------------------------------------
/*
 * CSCHED_STATS
 *
 * Manage very basic per-vCPU counters and stats.
 *
 * Useful for debugging live systems. The stats are displayed
 * with runq dumps ('r' on the Xen console).
 */
#ifdef PERF_COUNTERS
#define CSCHED_STATS
#endif
---------------------------------------

I've just enabled this in Rules.mk:
---------------------------------------
verbose       ?= y
perfc         ?= y
perfc_arrays  ?= y
---------------------------------------

now xenperf works but I don't know how to access the "Xen console".

Also, not related to this issue, I'm interested in accounting how many
ticks the net backend driver spends in rx/tx.
Can it make sense using the getrusage() function at start/end of
net_rx_action()/net_tx_action() or it can lead to unconsistent
accounting?

Is there a better way?

Any suggestions are welcome.

Thanks in advance.
Marco

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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