[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18720.63178.864933.911090@drongo.ozlabs.ibm.com>
Date: Mon, 17 Nov 2008 15:44:58 +1100
From: Paul Mackerras <paulus@...ba.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
David Miller <davem@...emloft.net>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Pekka Paalanen <pq@....fi>, linuxppc-dev@...abs.org,
Rusty Russell <rusty@...tcorp.com.au>,
Paul Mundt <lethal@...ux-sh.org>,
Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 4/7] ftrace, PPC: use probe_kernel API to modify code
Steven Rostedt writes:
> Impact: use cleaner probe_kernel API over assembly
>
> Using probe_kernel_read/write interface is a much cleaner approach
> than the current assembly version.
Possibly naive question: how is it possible for the accesses to the
instructions to fault, given that we are called through kstop_machine
(according to the comment) and nothing else should be happening?
Paul.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists