From: Jan Kiszka <jan.kiszka@siemens.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86 <x86@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: x86-32: Early microcode loading stumbles over disabled DYNAMIC_FTRACE
Date: Fri, 30 Aug 2013 19:33:59 +0200 [thread overview]
Message-ID: <5220D787.1060304@siemens.com> (raw)
In-Reply-To: <20130830132525.06a944e8@gandalf.local.home>
On 2013-08-30 19:25, Steven Rostedt wrote:
> On Fri, 30 Aug 2013 10:16:00 -0700
> "H. Peter Anvin" <hpa@zytor.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
next prev parent reply other threads:[~2013-08-30 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 16:40 x86-32: Early microcode loading stumbles over disabled DYNAMIC_FTRACE Jan Kiszka
2013-08-23 20:17 ` Borislav Petkov
2013-08-26 8:50 ` Jan Kiszka
2013-08-30 15:36 ` H. Peter Anvin
2013-08-30 15:51 ` Steven Rostedt
2013-08-30 16:35 ` H. Peter Anvin
2013-08-30 17:03 ` Steven Rostedt
2013-08-30 17:16 ` H. Peter Anvin
2013-08-30 17:25 ` Steven Rostedt
2013-08-30 17:33 ` Jan Kiszka [this message]
2013-08-30 20:48 ` H. Peter Anvin
2013-08-31 0:17 ` Steven Rostedt
2013-08-31 5:07 ` Borislav Petkov
2013-08-31 5:23 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5220D787.1060304@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.