From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [xen-unstable test] 57852: regressions - FAIL Date: Wed, 10 Jun 2015 19:00:00 +0100 Message-ID: <1433959200.3342.72.camel@citrix.com> References: <1433493915.7108.138.camel@citrix.com> <5571814C02000078000812F1@mail.emea.novell.com> <1433495266.7108.145.camel@citrix.com> <5571858C020000780008132E@mail.emea.novell.com> <1433501300.7108.208.camel@citrix.com> <557569610200007800081D4C@mail.emea.novell.com> <1433753590.7108.392.camel@citrix.com> <557579500200007800081DF0@mail.emea.novell.com> <1433755652.7108.405.camel@citrix.com> <1433765763.7108.482.camel@citrix.com> <1433838390.7108.523.camel@citrix.com> <5576CE2602000078000827F6@mail.emea.novell.com> <1433926213.30003.2.camel@citrix.com> <557821330200007800082F1C@mail.emea.novell.com> <1433934087.30003.32.camel@citrix.com> <55784041020000780008304A@mail.emea.novell.com> <1433940966.30003.81.camel@citrix.com> <1433946842.30003.89.camel@citrix.com> <55787AF6020000780008331A@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z2l1H-00043A-DH for xen-devel@lists.xenproject.org; Wed, 10 Jun 2015 18:46:35 +0000 In-Reply-To: <55787AF6020000780008331A@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Andrew Cooper , ian.jackson@eu.citrix.com, xen-devel List-Id: xen-devel@lists.xenproject.org On Wed, 2015-06-10 at 16:59 +0100, Jan Beulich wrote: > >>> On 10.06.15 at 16:34, 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 > -- 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.