linux-kernel - Re: x86-32: Early microcode loading stumbles over disabled DYNAMIC

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]

Date:	Fri, 30 Aug 2013 19:33:59 +0200
From:	Jan Kiszka <jan.kiszka@...mens.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Fenghua Yu <fenghua.yu@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	x86 <x86@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: x86-32: Early microcode loading stumbles over disabled DYNAMIC_FTRACE

On 2013-08-30 19:25, Steven Rostedt wrote:
> On Fri, 30 Aug 2013 10:16:00 -0700
> "H. Peter Anvin" <hpa@...or.com> wrote:
>  
>>> Who uses static tracing? I only use it to test that it still works ;-)
>>
>> Can we get rid of it?
>>
> 
> I've though about it. But as some archs only have static tracing
> available (I need to revisit to make sure that's still the case), I
> kept it because I only test static tracing on x86.
> 
> I'm not sure if people still use it for x86 or not.
> 
> Jan, you use static tracing on x86?

Yes, due to out-of-tree code that is not compatible with dynamic
tracing. It might be feasible to change this, I didn't try again
recently. If static tracing goes away upstream, I'll have to sooner or
later.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
--
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/