From: Borislav Petkov <bp@alien8.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
H Peter Anvin <hpa@zytor.com>, Fenghua Yu <fenghua.yu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: early intel microcode update violating alignment rules
Date: Mon, 11 Aug 2014 21:15:19 +0200 [thread overview]
Message-ID: <20140811191519.GF21607@pd.tnic> (raw)
In-Reply-To: <53E910F7.1040806@tmr.com>
On Mon, Aug 11, 2014 at 02:52:39PM -0400, Bill Davidsen wrote:
> Because if the requirement is enforced in some future revision, and
> updates then fail in some insane way, the vendor is justified in
> claiming "I told you so."
... provided that requirement is not some old relic which is not needed
anymore. I was questioning it, considering the fact that CPUs don't
enforce it (if they did, we'd be seeing explosions left and right).
Anyway, hpa is checking the whole deal internally as we speak.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-08-11 19:15 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 [this message]
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
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=20140811191519.GF21607@pd.tnic \
--to=bp@alien8.de \
--cc=davidsen@tmr.com \
--cc=fenghua.yu@intel.com \
--cc=hmh@hmh.eng.br \
--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