From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH V3] x86, amd_ucode: Support multiple container files appended together Date: Fri, 27 Jun 2014 08:47:55 -0400 Message-ID: <53AD67FB.80409@oracle.com> References: <53AC43EF.807@oracle.com> <53AC4C60.7080206@amd.com> <53AC7BC4.6070902@oracle.com> <53AD4458020000780001DDAA@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53AD4458020000780001DDAA@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: keir@xen.org, Aravind Gopalakrishnan , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 06/27/2014 04:15 AM, Jan Beulich wrote: >>>> On 26.06.14 at 22:00, wrote: >> The trouble is that if I have two files in my hands, both called >> microcode_amd_fam15h.bin, I don't know which one is the more up-to-date >> (would be nice to have a tool to print file info). >> >> Of course, one can argue that in that case I shouldn't be using neither >> but HW makes its own verification of patches so in principle trying both >> should be safe (provided that SW tries not to load older revision). > I think we should focus on getting things to work with realistic > blobs, i.e. such that distros and their tools would generate. If you > update a respective package, it'll be clear which blob is the latest, > and there's generally not going to be two blobs for the same family > put on a single system. People obtaining ucode blobs manually from > elsewhere should know what they're doing and not try to paste > together two of them targeting the same family. Ok. I only mention this scenario because I myself needed to deal with this (on more than one occasion, in fact) when I had two containers and didn't know which one is which. -boris