From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: no cycles for certain xentrace entries
Date: Thu, 30 Sep 2010 16:47:07 +0200 [thread overview]
Message-ID: <20100930144706.GA1948@aepfle.de> (raw)
In-Reply-To: <4CA49CFA.9080408@eu.citrix.com>
On Thu, Sep 30, George Dunlap wrote:
> Thanks for the patch; I'll take a look and apply what I can. What
> version of gcc / what flags are you using?
gcc 4.3.4 from SLES11 SP1.
gcc -O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables
-fasynchronous-unwind-tables -g -fno-strict-aliasing -std=gnu99 -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs
-Werror -o xenalyze xenalyze.c
Olaf
prev parent reply other threads:[~2010-09-30 14:47 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
2010-09-30 14:21 ` George Dunlap
2010-09-30 14:47 ` Olaf Hering [this message]
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=20100930144706.GA1948@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).