All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	ian.jackson@eu.citrix.com,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 57852: regressions - FAIL
Date: Wed, 10 Jun 2015 19:00:00 +0100	[thread overview]
Message-ID: <1433959200.3342.72.camel@citrix.com> (raw)
In-Reply-To: <55787AF6020000780008331A@mail.emea.novell.com>

On Wed, 2015-06-10 at 16:59 +0100, Jan Beulich wrote:
> >>> On 10.06.15 at 16:34, <ian.campbell@citrix.com> wrote:
> > For Intel I'm less sure, I've got microcode-20150121.tgz containing
> > microcode.dat. Is that just to be placed at
> > kernel/x86/microcode/GenuineIntel.bin and done, or is there some
> > processing needed?
> 
> The full blob (albeit usually named microcode.bin; microcode.dat
> ordinarily is a text file) can be used if so desired, but there's also a
> tool to split it into more fine grained chunks.
> 
> > I've got a thing called iucode-tool in my hand from a Debian package if
> > I need it.
> 
> Or maybe there are multiple different tools - the one I know about
> is commonly named intel-microcode2ucode taking microcode.dat as
> input and producing microcode.bin as well as many individual
> <family>-<model>-<stepping> blobs.

Not sure if they are the same tool, but I seem to have managed to get
iucode-tool to take my microcode.dat and produce a suitable binary file.
I'm testing the integration with osstest now.

Thanks,

Ian.

  parent reply	other threads:[~2015-06-10 18:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 12:01 [xen-unstable test] 57852: regressions - FAIL osstest service user
2015-06-05  8:45 ` Ian Campbell
2015-06-05  9:00   ` Jan Beulich
2015-06-05  9:07     ` Ian Campbell
2015-06-05  9:18       ` Jan Beulich
2015-06-05 10:48         ` Ian Campbell
2015-06-05 16:46           ` Ian Campbell
2015-06-08  8:07           ` Jan Beulich
2015-06-08  8:53             ` Ian Campbell
2015-06-08  9:15               ` Jan Beulich
2015-06-08  9:27                 ` Ian Campbell
2015-06-08 10:17                   ` Jan Beulich
2015-06-08 14:43                     ` Ian Jackson
2015-06-08 12:16                   ` Ian Campbell
2015-06-08 12:19                     ` Andrew Cooper
2015-06-08 12:24                     ` Jan Beulich
2015-06-09  8:26                     ` Ian Campbell
2015-06-09  9:29                       ` Jan Beulich
2015-06-10  8:50                         ` Ian Campbell
2015-06-10  9:36                           ` Jan Beulich
2015-06-10 11:01                             ` Ian Campbell
2015-06-10 11:48                               ` Jan Beulich
2015-06-10 12:56                                 ` Ian Campbell
2015-06-10 13:23                                   ` Jan Beulich
2015-06-10 13:45                                   ` Jan Beulich
2015-06-10 14:08                                     ` Ian Campbell
2015-06-11  7:02                                       ` Jan Beulich
2015-06-11  8:45                                         ` Ian Campbell
2015-06-15  8:57                                           ` Ian Campbell
2015-06-15  9:03                                             ` Jan Beulich
2015-06-10 14:34                                   ` Ian Campbell
2015-06-10 15:59                                     ` Jan Beulich
2015-06-10 16:18                                       ` Don Slutz
2015-06-10 18:00                                       ` Ian Campbell [this message]
2015-06-08 13:50                   ` Konrad Rzeszutek Wilk
2015-06-08 14:02                     ` Ian Campbell
2015-06-08 14:47                     ` Ian Jackson
2015-06-08 15:21                       ` Konrad Rzeszutek Wilk
2015-06-08 15:29                         ` Ian Campbell
2015-06-08 10:10                 ` Ian Campbell

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=1433959200.3342.72.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.