Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754495AbYHAPcQ (ORCPT ); Fri, 1 Aug 2008 11:32:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751337AbYHAPcB (ORCPT ); Fri, 1 Aug 2008 11:32:01 -0400 Received: from terminus.zytor.com ([198.137.202.10]:36817 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751177AbYHAPcA (ORCPT ); Fri, 1 Aug 2008 11:32:00 -0400 Message-ID: <48932B1B.70303@zytor.com> Date: Fri, 01 Aug 2008 08:26:19 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Dmitry Adamushko CC: Peter Oruba , Tigran Aivazian , Max Krasnyansky , Ingo Molnar , Thomas Gleixner , LKML Subject: Re: [patch 0/4] x86: AMD microcode patch loading v2 fixes References: <20080729154103.007575982@amd.com> <488F581B.7060009@qualcomm.com> <48903431.9060707@amd.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1048 Lines: 27 Dmitry Adamushko wrote: > Tigran, Peter, > > may a firmware package contain a few 'microcode' updates for a specific cpu? > > And if so, does each of them provide independent 'errata' fixes? [*] > > (or they are just different versions of the same self-consistent/full > 'microcode' update and we may need to apply each of them just e.g. > because we can't jump from stepping X.1 to X.3 without applying X.2 in > between? > > if it's [1], then I wonder why only a single 'microcode' update (which > has been previously cached in 'uci->mc') is being applied for the case > of system-wide resume (apply_microcode_check_cpu()). Don't we need to > go through the full cpu_request_microcode() cycle to consider all > updates? > No, there is only ever one microcode; you only run the latest one. -hpa -- 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/