WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] xentrace: fix lost records resume
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:received:message-id:subject:from:to :content-type; bh=S2rIap/1ckxMm8D1NYmFLWcdbjIIIXZQpeVMDDvT53s=; b=Xwf2rqaz5swfnfAkUTMo34uaxCtJAvjOjB1QlE7FIqVo3NQv06a9dQazoU/vlAiS5s a43mNsS4F3zAkHKhG2HX/10/29MnpsOP9y4JpjMah4gZ2F+NnKC8GNlN36DfK6Zs1rbp YKYxcjCbMECaHXXAdQLUDZu7fGW7qvHDuoDhM=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] xentrace: fix lost records resume, George Dunlap <=