From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: no cycles for certain xentrace entries
Date: Thu, 30 Sep 2010 16:18:45 +0200 [thread overview]
Message-ID: <20100930141845.GA1772@aepfle.de> (raw)
In-Reply-To: <AANLkTim1t+aCV+c5mfNpCMEzmvwVSENz1yHbBjzLwtw1@mail.gmail.com>
On Thu, Sep 30, George Dunlap wrote:
> Have you tried using xenalyze to analyze your trace?
>
> http://xenbits.xensource.com/ext/xenalyze.hg
I will try it, thanks.
To build it, these changes are needed:
xenalyze.c:8038: error: ignoring return value of 'pipe', declared with attribute warn_unused_result
xenalyze.c:7731: error: 'toplevel' may be used uninitialized in this function
xenalyze.c:6168: error: 'e.pte' may be used uninitialized in this function
xenalyze.c:6168: error: 'e.addr' may be used uninitialized in this function
xenalyze.c:6168: error: 'e.eip' may be used uninitialized in this function
xenalyze.c:7360: error: 'first_tsc' may be used uninitialized in this function
xenalyze.c:6611: error: 'sevt.new_runstate' may be used uninitialized in this function
xenalyze.c:6611: error: 'sevt.old_runstate' may be used uninitialized in this function
xenalyze.c:6591: error: 'type' may be used uninitialized in this function
---
xenalyze.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--- xenalyze.hg/xenalyze.c
+++ xenalyze.hg/xenalyze.c
@@ -6167,6 +6167,7 @@ void pv_ptwr_emulation_process(struct re
unsigned long long pte, addr, eip;
} e;
+ memset(&e, 0x5a, sizeof(e));
switch ( pevt.minor ) {
case PV_PTWR_EMULATION_PAE:
if ( pevt.x64 )
@@ -6622,6 +6623,7 @@ void sched_runstate_process(struct pcpu_
sevt.old_runstate = _sevt.old_runstate;
break;
case 2:
+ default:
type = CONTINUE;
sevt.new_runstate = sevt.old_runstate = RUNSTATE_RUNNING;
break;
@@ -7366,8 +7368,7 @@ void process_lost_records(struct pcpu_in
ri->extra_words);
dump_unexpected_and_exit(ri);
}
- else
- first_tsc = r->first_tsc;
+ first_tsc = r->first_tsc;
if(opt.dump_cooked || opt.dump_all)
{
@@ -7728,7 +7729,7 @@ void create_dump_header(struct record_in
int find_toplevel_event(struct record_info *ri)
{
- int toplevel, i, count;
+ int toplevel = 0, i, count;
for(i=0, count=0; i<TOPLEVEL_MAX; i++)
if(ri->evt.main & (1UL<<i))
@@ -8035,7 +8036,8 @@ void progress_child_exec(void) {
void progress_init(void) {
int pid;
- pipe(G.progress.pipe);
+ if (pipe(G.progress.pipe) < 0)
+ perror("pipe");
if(!(pid = fork())) {
progress_child_exec();
next prev parent reply other threads:[~2010-09-30 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 18:44 no cycles for certain xentrace entries Olaf Hering
2010-09-29 8:09 ` Olaf Hering
2010-09-30 9:56 ` George Dunlap
2010-09-30 14:18 ` Olaf Hering [this message]
2010-09-30 14:21 ` George Dunlap
2010-09-30 14:47 ` Olaf Hering
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=20100930141845.GA1772@aepfle.de \
--to=olaf@aepfle.de \
--cc=George.Dunlap@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).