From: Borislav Petkov <bp@alien8.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Jan Kiszka <jan.kiszka@siemens.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: Sat, 31 Aug 2013 07:07:37 +0200 [thread overview]
Message-ID: <20130831050737.GB12617@x1.alien8.de> (raw)
In-Reply-To: <20130830201741.07fea07f@gandalf.local.home>
On Fri, Aug 30, 2013 at 08:17:41PM -0400, Steven Rostedt wrote:
> On Fri, 30 Aug 2013 13:48:55 -0700
> "H. Peter Anvin" <hpa@zytor.com> wrote:
>
> > >> You *could* bail out of the calling address is < PAGE_OFFSET.
> >
> > Anyway... can we add this to the static tracing code? It is two
> > instructions and is only needed on x86-32. For performance, use dynamic.
>
> Sure, do you want to add it ?
Another, simpler option could be to make static tracing depend on
!MICROCODE until the first has been removed.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2013-08-31 5:07 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
2013-08-30 20:48 ` H. Peter Anvin
2013-08-31 0:17 ` Steven Rostedt
2013-08-31 5:07 ` Borislav Petkov [this message]
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=20130831050737.GB12617@x1.alien8.de \
--to=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.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.