From: Ingo Molnar <mingo@elte.hu>
To: Pekka Paalanen <pq@iki.fi>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Stuart Bennett <stuart@freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] mmiotrace: enhance01
Date: Mon, 2 Mar 2009 10:23:42 +0100 [thread overview]
Message-ID: <20090302092342.GA12924@elte.hu> (raw)
In-Reply-To: <20090301160643.05a2219b@daedalus.pq.iki.fi>
* Pekka Paalanen <pq@iki.fi> wrote:
> Hi all,
>
> the following patch set is mostly mmiotrace stability and bug fixes.
> It is meant for 2.6.30, has been developed on linus/master (post 2.6.29-rc6),
> and applies cleanly to tip/master.
>
> It has been tested on Athlon64 3000+ (x86_64) by testmmiotrace.ko and
> tracing the Nouveau driver, and also on Core 2 Duo (Thinkpad T61, x86_64)
> by testmmiotrace.ko and tracing the Nvidia proprietary driver.
>
> Special thanks to Stuart, who provided most of the fixes.
>
> arch/x86/mm/kmmio.c | 149 +++++++++++++++++++++++++++---------------
> arch/x86/mm/testmmiotrace.c | 70 ++++++++++++++++----
> 2 files changed, 153 insertions(+), 66 deletions(-)
Applied to tip:tracing/mmiotrace, thanks guys!
Ingo
prev parent reply other threads:[~2009-03-02 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090301160643.05a2219b@daedalus.pq.iki.fi>
2009-03-01 14:09 ` [PATCH 1/7] x86: count errors in testmmiotrace.ko Pekka Paalanen
2009-03-01 14:10 ` [PATCH 2/7] x86: add far read test to testmmiotrace Pekka Paalanen
2009-03-01 14:11 ` [PATCH 3/7] x86 mmiotrace: WARN_ONCE if dis/arming a page fails Pekka Paalanen
2009-03-01 14:11 ` [PATCH 4/7] x86 mmiotrace: fix save/restore page table state Pekka Paalanen
2009-03-01 14:12 ` [PATCH 5/7] x86 mmiotrace: split set_page_presence() Pekka Paalanen
2009-03-01 14:13 ` [PATCH 6/7] x86 mmiotrace: improve handling of secondary faults Pekka Paalanen
2009-03-01 14:14 ` [PATCH 7/7] x86 mmiotrace: fix race with release_kmmio_fault_page() Pekka Paalanen
2009-03-02 9:23 ` Ingo Molnar [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=20090302092342.GA12924@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.org \
--cc=stuart@freedesktop.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®