From: Pekka Paalanen <pq@iki.fi>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
fweisbec@gmail.com
Subject: Re: [PATCH 1/2] mmiotrace: fix buffer overrun detection
Date: Sun, 23 Nov 2008 21:59:53 +0200 [thread overview]
Message-ID: <20081123215953.52da4dca@daedalus.pq.iki.fi> (raw)
In-Reply-To: <20081123193413.GB2794@elte.hu>
On Sun, 23 Nov 2008 20:34:13 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Pekka Paalanen <pq@iki.fi> wrote:
>
> > Ingo, could these two patches still make it into .28?
>
> 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 ?
Yes, as fully as it was originally meant to be. Again.
I don't know of any more urgent bugs.
It passes the testmmiotrace.ko test, and also notices overruns if they
happen. Still untested with the nvidia proprietary driver, though, or
with SMP, but it should work.
btw. the testmmiotrace.ko testing cannot be automated, since it
involves writing to "somewhere" in the PCI address space and is
therefore a bit dangerous.
Thanks.
--
Pekka Paalanen
http://www.iki.fi/pq/
next prev parent reply other threads:[~2008-11-23 20:00 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 [this message]
2008-11-24 20:18 ` Pekka Paalanen
2008-11-24 20:30 ` Frédéric Weisbecker
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=20081123215953.52da4dca@daedalus.pq.iki.fi \
--to=pq@iki.fi \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®