From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: "Pekka Paalanen" <pq@iki.fi>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Steven Rostedt" <rostedt@goodmis.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mmiotrace: fix buffer overrun detection
Date: Mon, 24 Nov 2008 21:30:24 +0100 [thread overview]
Message-ID: <c62985530811241230x601a27e1w504b0564b9513a13@mail.gmail.com> (raw)
In-Reply-To: <20081124221849.33c91bcf@daedalus.pq.iki.fi>
2008/11/24 Pekka Paalanen <pq@iki.fi>:
> On Sun, 23 Nov 2008 20:34:13 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
>
>> Sure - applied them to tip/tracing/urgent:
>>
>> fb91ee6: tracing, doc: update mmiotrace documentation
>> 7ee1768: x86, mmiotrace: fix buffer overrun detection
>>
>> Does this make mmiotrace fully functional in .28 ?
>
> Oh right, the busylooping bug when echoing into trace_marker,
> I already forgot about that, since I couldn't reproduce it.
> I guess there's nothing to do, until someone finds a way to
> reproduce it.
Hi Pekka.
Are you talking about this old bug that broke the pipe?
If so, you fixed it yourself partially with a patch that corrected
tracing_read_pipe.
Another origin was the none tracer that set tracer_enabled to 0.
But i has been fixed with the nop tracer.
Perhaps you are talking of something else?
next prev parent reply other threads:[~2008-11-24 20:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 13:41 Mmiotrace regression in 2.6.28-rc6 Pekka Paalanen
2008-11-23 14:03 ` Ingo Molnar
2008-11-23 16:35 ` Steven Rostedt
2008-11-23 19:24 ` [PATCH 1/2] mmiotrace: fix buffer overrun detection Pekka Paalanen
2008-11-23 19:34 ` Ingo Molnar
2008-11-23 19:59 ` Pekka Paalanen
2008-11-24 20:18 ` Pekka Paalanen
2008-11-24 20:30 ` Frédéric Weisbecker [this message]
2008-11-24 21:27 ` Pekka Paalanen
2008-11-25 11:55 ` Frédéric Weisbecker
2008-11-25 11:59 ` Frédéric Weisbecker
2008-11-25 17:13 ` Pekka Paalanen
2008-11-23 19:24 ` [PATCH 2/2] doc: update mmiotrace documentation Pekka Paalanen
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=c62985530811241230x601a27e1w504b0564b9513a13@mail.gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.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®