linux-kernel - Re: [PATCH 4/5] tracing/core: drop the cpu field from trace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090209134744.GC4705@nowhere>
Date:	Mon, 9 Feb 2009 14:47:46 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/5] tracing/core: drop the cpu field from trace_entry

On Mon, Feb 09, 2009 at 10:53:24AM +0100, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@...il.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...

Anyway, thanks for having applied the other patches :-)

--
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/