linux-kernel - Re: [PATCH 1/2] tracing/ftrace: don't trace on early stage of secondary cpu boot

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: <c62985530812231903q59f1e1y4523b3e37b7f9b34@mail.gmail.com>
Date:	Wed, 24 Dec 2008 04:03:04 +0100
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Steven Rostedt" <rostedt@...dmis.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] tracing/ftrace: don't trace on early stage of secondary cpu boot

2008/12/24 Frédéric Weisbecker <fweisbec@...il.com>:
> One other solution, would be to define raw_smp_processor_id() to
> stack_smp_processor_id() and current to
> cpu_pda(stack_smp_processor_id()) if function_tracer is configured.


Sorry, I meant cpu_pda(stack_smp_processor_id())->pcurrent
--
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/