From: Steven Rostedt <rostedt@goodmis.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>
Subject: Re: perf trace errors
Date: Thu, 29 Oct 2009 17:24:49 -0400 [thread overview]
Message-ID: <1256851489.26028.3247.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <c62985530910251643k6b3e59c0l6069b08741469b47@mail.gmail.com>
On Mon, 2009-10-26 at 00:43 +0100, Frederic Weisbecker wrote:
> 2009/10/25 Christoph Hellwig <hch@lst.de>:
> > On Fri, Oct 16, 2009 at 10:32:42AM +0200, Ingo Molnar wrote:
> >> FYI, these bugs are fixed in latest -tip, your testcase works for me:
> >
> >> Mind checking whether it works for you?
> >
> > Yes, it works on -tip, but not yet on mainline. What still doesn't
> > work yet on -tip either is printing of dynamic strings in some events,
> > e.g.:
> >
> > kjournald-1105 [000] 643.002702: block_rq_complete: 253,0 W () 2283224
>
>
> Ah, interesting, it means we support __string() but not well other
> dynamic arrays.
> I'll have a look at it.
Frederic,
Have you found anything with this yet? If not, I can take a look too.
-- Steve
next prev parent reply other threads:[~2009-10-29 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 2:54 Christoph Hellwig
2009-10-11 12:19 ` Frederic Weisbecker
2009-10-11 12:40 ` Christoph Hellwig
2009-10-11 20:23 ` Frederic Weisbecker
2009-10-16 8:32 ` Ingo Molnar
2009-10-25 7:17 ` Christoph Hellwig
2009-10-25 23:43 ` Frederic Weisbecker
2009-10-29 21:24 ` Steven Rostedt [this message]
2009-11-02 1:24 ` Frederic Weisbecker
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=1256851489.26028.3247.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/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
all inboxes | Powered by JetHome®