From: Andi Kleen <andi@firstfloor.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Burt Triplett <burt@pbjtriplett.org>, linux-kernel@vger.kernel.org
Subject: Re: BITS handling of CPU microcode updates
Date: Thu, 24 Mar 2011 14:46:21 -0700 [thread overview]
Message-ID: <m2ipv8kx8y.fsf@firstfloor.org> (raw)
In-Reply-To: <20110324001451.GA7950@khazad-dum.debian.net> (Henrique de Moraes Holschuh's message of "Wed, 23 Mar 2011 21:14:51 -0300")
Henrique de Moraes Holschuh <hmh@hmh.eng.br> writes:
>
> Very well, I will send patches to fix that behaviour, as well as some
> other stuff I noticed that was not updated to match the recommended
> actions documented by the SDM and some Intel application notes.
I don't think you can easily -- there's no kernel interface
to distingush the "explicit user action" case from automatic loading.
This all would need a new kernel interface.
I suppose all the test labs have learned by now how to disable
automatic updates ...
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2011-03-24 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 5:36 [announce] Intel BIOS Implementation Test Suite (BITS) Burt Triplett
2011-03-12 2:30 ` BITS handling of CPU microcode updates Henrique de Moraes Holschuh
2011-03-21 23:44 ` Burt Triplett
2011-03-24 0:14 ` Henrique de Moraes Holschuh
2011-03-24 20:53 ` Burt Triplett
2011-03-25 0:57 ` Henrique de Moraes Holschuh
2011-03-24 21:46 ` Andi Kleen [this message]
2011-03-25 7:05 ` Burt Triplett
2011-03-25 2:09 ` x86/microcode: intel: correctly handle negative revisions Henrique de Moraes Holschuh
2011-03-25 7:14 ` Burt Triplett
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=m2ipv8kx8y.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=burt@pbjtriplett.org \
--cc=hmh@hmh.eng.br \
--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