From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Borislav Petkov <bp@alien8.de>, Fenghua Yu <fenghua.yu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: early microcode: how to disable at runtime?
Date: Mon, 1 Sep 2014 16:59:21 -0300 [thread overview]
Message-ID: <20140901195921.GA18675@khazad-dum.debian.net> (raw)
In-Reply-To: <ea40f7c4-ec8d-4be5-8f8c-bbd11ab07252@email.android.com>
On Mon, 01 Sep 2014, H. Peter Anvin wrote:
> No, it is worse to rename it and have older kernels behave differently.
> Kernel options are basically super obscure to most people anyway.
Ok, so rename is out, although as long as the rename was accepted for
3.16-stable, it would be just 3.16 and 3.16.1 (and maybe 3.16.2) that would
not have the new name.
Options left are "keep it as is", or "add new and [optionally] deprecate
old". I can't really tell for sure which one you'd prefer from your
previous answer.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2014-09-01 19:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 23:19 BUG: early intel microcode update violating alignment rules Henrique de Moraes Holschuh
2014-08-11 10:22 ` Borislav Petkov
2014-08-11 13:16 ` Henrique de Moraes Holschuh
2014-08-11 14:00 ` Borislav Petkov
2014-08-11 14:50 ` H. Peter Anvin
2014-08-11 18:52 ` Bill Davidsen
2014-08-11 19:15 ` Borislav Petkov
2014-08-14 13:12 ` Henrique de Moraes Holschuh
2014-08-11 14:51 ` H. Peter Anvin
2014-08-11 18:18 ` Henrique de Moraes Holschuh
2014-08-11 18:48 ` H. Peter Anvin
2014-08-31 19:45 ` early microcode: how to disable at runtime? Henrique de Moraes Holschuh
2014-08-31 19:48 ` H. Peter Anvin
2014-08-31 20:11 ` Henrique de Moraes Holschuh
2014-09-01 5:13 ` Borislav Petkov
2014-09-01 10:19 ` Henrique de Moraes Holschuh
2014-09-01 16:35 ` H. Peter Anvin
2014-09-01 17:43 ` Henrique de Moraes Holschuh
2014-09-01 18:48 ` H. Peter Anvin
2014-09-01 19:59 ` Henrique de Moraes Holschuh [this message]
2014-09-02 6:33 ` Borislav Petkov
2014-09-02 13:16 ` Henrique de Moraes Holschuh
2014-09-03 6:40 ` Borislav Petkov
2014-09-03 12:43 ` Henrique de Moraes Holschuh
2014-09-04 15:42 ` Borislav Petkov
2014-09-04 17:45 ` Henrique de Moraes Holschuh
2014-09-05 8:50 ` Borislav Petkov
2014-09-05 14:23 ` Henrique de Moraes Holschuh
2014-09-04 18:37 ` Yu, Fenghua
2014-09-05 8:52 ` Borislav Petkov
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=20140901195921.GA18675@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®