lkml.org 
[lkml]   [2009]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 4/5] tracing/core: drop the cpu field from trace_entry

On Mon, 9 Feb 2009, Ingo Molnar wrote:

>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > On Mon, Feb 09, 2009 at 10:53:24AM +0100, Ingo Molnar wrote:
> > >
> > > * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > >
> > > > Impact: fix a bug on cpu output
> > > >
> > > > While looking on the function tracer traces, I first cheered up:
> > > >
> > > > TASK-PID CPU# TIMESTAMP FUNCTION
> > > > | | | | |
> > > > firefox-4622 [081] 1315.790405: lapic_next_event <-clockevents_program_event
> > > > firefox-4622 [178] 1315.790405: native_apic_mem_write <-lapic_next_event
> > > > firefox-4622 [020] 1315.790406: perf_counter_unthrottle <-smp_apic_timer_interrupt
> > > >
> > > > But no, actually I don't have so many cpus...
> > >
> > > incidentally, Steve came up with the exact same patch :)
> > >
> > > Ingo
> >
> > Heh, I guess the moon inspired both of us in the name of tracing, or
> > something like that...
>
> It was exactly at around the time Thomas complained over IRC
> about the visible CPU# breakage in the tracer output.
>
> So i blame it on telepathy ;-)

Thomas was the full moon, his complaint to me was the reason I pushed it
out ASAP.

-- Steve



\
 
 \ /
  Last update: 2009-02-09 17:11    [W:0.041 / U:0.924 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site