Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756836Ab3EaVax (ORCPT ); Fri, 31 May 2013 17:30:53 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:41779 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754217Ab3EaVap (ORCPT ); Fri, 31 May 2013 17:30:45 -0400 X-Sasl-enc: cAt9V9I25WPSo+syfcyqB5ut6hihXDPgFf3oWjlijRGI 1370035843 Date: Fri, 31 May 2013 18:30:39 -0300 From: Henrique de Moraes Holschuh To: Andreas Herrmann Cc: Jacob Shin , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , x86@kernel.org, Fenghua Yu , Borislav Petkov , Joe Perches , linux-kernel@vger.kernel.org Subject: Re: [PATCH V3 4/4] microcode/x86/amd: early microcode patch loading support for AMD Message-ID: <20130531213039.GA13307@khazad-dum.debian.net> References: <1369940959-2077-1-git-send-email-jacob.shin@amd.com> <1369940959-2077-5-git-send-email-jacob.shin@amd.com> <20130531042649.GA4488@khazad-dum.debian.net> <20130531193200.GA8346@alberich> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130531193200.GA8346@alberich> X-GPG-Fingerprint: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04 3738 EE25 DE3F 1CDB 0FE3 User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1924 Lines: 46 On Fri, 31 May 2013, Andreas Herrmann wrote: > On Fri, May 31, 2013 at 01:26:49AM -0300, Henrique de Moraes Holschuh wrote: > > On Thu, 30 May 2013, Jacob Shin wrote: > > > mkdir initrd > > > cd initrd > > > -mkdir kernel > > > -mkdir kernel/x86 > > > -mkdir kernel/x86/microcode > > > -cp ../microcode.bin kernel/x86/microcode/GenuineIntel.bin > > > -find .|cpio -oc >../ucode.cpio > > > +mkdir -p kernel/x86/microcode > > > +cp ../microcode.bin kernel/x86/microcode/GenuineIntel.bin (or AuthenticAMD.bin) > > > > Can I just > > 'cat /lib/firmware/amd-ucode/*bin >kernel/x86/microcode/AuthenticAMD.bin' > > to get a valid microcode container for all amd processors? > > > > The answer for Intel is "yes". I sure hope it is the same for AMD... > > No, this doesn't work for AMD. > > The container file includes a header section with information how to > map CPU F/M/S to microcode revisions provided with a container > file. Concatenating several container files will not create an > all-embracing header section. > > More details were available on the amd64.org web pages. But it seems > that the web site is not available anymore ... Well, this is a problem for userspace. Maybe the easier solution would be to make kernel/x86/microcode/AuthenticAMD a folder, and look for files there with names we can derivate from the ones used by the firmware interface (or even the same names)? The early-initramfs API easily allows this to be implemented... -- "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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/