All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, george.dunlap@citrix.com,
	david.vrabel@citrix.com
Subject: Re: [PATCH] updates to the format file for xentrace (v1).
Date: Tue, 12 Mar 2013 18:59:36 +0000	[thread overview]
Message-ID: <513F7B18.1000507@citrix.com> (raw)
In-Reply-To: <1363113251-21670-1-git-send-email-konrad.wilk@oracle.com>

On 12/03/13 18:34, Konrad Rzeszutek Wilk wrote:
> While trying to troubleshoot an guest and hypervisor freeze I noticed
> that there were a couple of various 'unknown' in the trace file.

Do these event show up correctly with xenalyze?

David

> This fixes the majority of them.
> 
>  tools/xentrace/formats | 13 +++++++++++--
>  1 file changed, 11 insertions(+), 2 deletions(-)
> 
> 
> Konrad Rzeszutek Wilk (2):
>       trace: Use correct trace class for power management changes.
>       trace: Add trace events for IRQ activities.
> 
> Please review and if OK apply to the tree.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2013-03-12 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 18:34 [PATCH] updates to the format file for xentrace (v1) Konrad Rzeszutek Wilk
2013-03-12 18:34 ` [PATCH 1/2] trace: Use correct trace class for power management changes Konrad Rzeszutek Wilk
2013-03-13 10:37   ` George Dunlap
2013-03-12 18:34 ` [PATCH 2/2] trace: Add trace events for IRQ activities Konrad Rzeszutek Wilk
2013-03-13 10:38   ` George Dunlap
2013-03-12 18:59 ` David Vrabel [this message]
2013-03-12 20:14   ` [PATCH] updates to the format file for xentrace (v1) Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=513F7B18.1000507@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.