From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
Shaohua Li <shaohua.li@intel.com>,
Simon Trimmer <simon@urbanmyth.org>
Subject: microcode_intel: how to test extended signature codepath?
Date: Sun, 5 Sep 2010 02:01:28 -0300 [thread overview]
Message-ID: <20100905050128.GA6922@khazad-dum.debian.net> (raw)
I have noticed that there is no public Intel microcode file using the Intel
extended signature table. This means there is some code in
microcode_intel.c that can't be easily field-tested. In fact, for all I
know, it might never been tested at all or it has been left untested for
several years and could have bitrotted.
Does Intel have a different microcode file that has at least one extended
signature table we could use to test the kernel driver (and enhanced
userspace helpers)? Anyone knows how to obtain it?
I suppose I could create a hacked microcode file for testing purposes based
on the real microcode update entry for some processors and using some
impossible signatures so that the driver is forced to find the match though
the first, some middle, and the last extended signatures in the cooked up
table, but this is very sub-optimal for a large number of reasons, least of
all the fact that AFAIK I'd be forbidden to distribute it to anyone else
that needs to touch the code, and the fact that it would be as correct as my
understanding of the microcode datafile spec, which doesn't mean much.
Can anyone offer any help on this matter?
--
"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
reply other threads:[~2010-09-05 5:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100905050128.GA6922@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaohua.li@intel.com \
--cc=simon@urbanmyth.org \
--cc=tigran@aivazian.fsnet.co.uk \
/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®