[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <928CFBE8E7CB0040959E56B4EA41A77E0CDD7BE0@irsmsx504.ger.corp.intel.com>
Date: Fri, 16 Jan 2009 16:19:25 +0000
From: "Metzger, Markus T" <markus.t.metzger@...el.com>
To: Steven Rostedt <srostedt@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...e.hu" <mingo@...e.hu>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>,
"markus.t.metzger@...il.com" <markus.t.metzger@...il.com>
Subject: RE: [patch 4/5] x86, ftrace, hw-branch-tracer: reset trace on close
>-----Original Message-----
>From: Steven Rostedt [mailto:srostedt@...hat.com]
>Sent: Friday, January 16, 2009 4:02 PM
>To: Metzger, Markus T
>On Fri, 2009-01-16 at 12:01 +0100, Markus Metzger wrote:
>> Reset the ftrace buffer on close. Since we use cyclic buffers to store
>> the trace, the trace is not contiguous, anyway. This behaviour should
>> be more natural.
>
>So you want multiple reads of /debug/tracing/trace to return different
>output? Kind of like the trace_pipe? But trace_pipe is a real consumer.
Yes.
The trace chunks are not contiguous (in this version), so it does not make sense to append them.
I don't expect trace_pipe to work with the hw-branch-tracer.
>BTW, can you run your diff with the -p option. This will help in knowing
>which function the change is in. There's some hunks where it is
>ambiguous. If you use quilt, you can add:
>
> QUILT_DIFF_OPTS='-p'
>
>to you .quiltrc file.
Thanks.
markus.
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
--
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