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

[Xen-devel] [PATCH] xentrace: Disable tracing, then read records one more time.

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: George Dunlap <dunlapg@xxxxxxxxx>
  • Date: Mon, 1 Feb 2010 11:05:54 -0800
  • Delivery-date: Mon, 01 Feb 2010 11:06:12 -0800
  • 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=krIvZhKf5e8ZvlpgReQbk+67yoW6KVNlaXeL4jEBqpPxhzQyIemrPCivYKsGFSfAac Or2deGpAIDVSLVbLMF6BqTWh4JxQm5rZElfFiTV5D8ccBGZpk2YfobRayfgPpZ7iMa5P qGL4MgIBScrnqvSTEXwTYhPB+DOoRmi34e88s=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

When interrupted, first disable tracing, then read through the records
one last time.

Without this patch, it's possible to get traces which interact (such as runstate
changes) on processors with higher numbers, while missing the corresponding
traces generated on lower-numbered processors.

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

Attachment: 20100107-unstable-xentrace-read-after-disable.diff
Description: Text Data

Xen-devel mailing list



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