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

[Xen-devel] [PATCH] xentrace: fix lost records resume


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
  • Date: Mon, 12 Apr 2010 18:01:54 +0100
  • Delivery-date: Mon, 12 Apr 2010 10:02:53 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=vjrlhmzkGGeNXIV7+cS+uk+0E8wONDG/P34JpUhe0BJ0n5zhYdHTEtXfQBBD5EoEeR SF5O9QgWeLXNAdSi8lWK3AG8Lf5bKcsqPK8ba9Ad5Xn1CfcN59VTOXpts72iJXyFB9xc lNLx3C9O+jaCwCRMgbt1Nh0a0EGR9JkE0kOe8=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Reorder the SCHED_SWITCH trace before the runstate change trace to fix
a problem with the lost records "resume" code.

Namely: The "lost records" trace includes the currently running
process.  But during SCHED_SWITCH, it reads the wrong value, confusing
xenalyze.  Making sure there are no trace records between runstate
change trace and the actual context switch fixes it.

Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>

Attachment: trace-reorder-sched-trace.diff
Description: Text Data

_______________________________________________
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®.