Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757326AbYHALZg (ORCPT ); Fri, 1 Aug 2008 07:25:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753192AbYHALZ2 (ORCPT ); Fri, 1 Aug 2008 07:25:28 -0400 Received: from rv-out-0506.google.com ([209.85.198.234]:55575 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752388AbYHALZ1 (ORCPT ); Fri, 1 Aug 2008 07:25:27 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=X2yxXMYk91x0DNYSkiLP/irCvPztNGu2VJRFosb5UBGxYLFGX+PyG+N1PZ2FqBHwYv sNjfh0dikKBYl8dYO0kZlOIMVv6zU7WFefV+v/PX5kbvIH9bRvP3AcjDmfpXUJYxtPs5 i5Cv7B9F5gdb3HPvy6opIkrbCQ/hVLme94vrw= Message-ID: Date: Fri, 1 Aug 2008 13:25:26 +0200 From: "Dmitry Adamushko" To: "Peter Oruba" , "Tigran Aivazian" Subject: Re: [patch 0/4] x86: AMD microcode patch loading v2 fixes Cc: "Max Krasnyansky" , "Ingo Molnar" , "Thomas Gleixner" , "H. Peter Anvin" , LKML In-Reply-To: <48903431.9060707@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080729154103.007575982@amd.com> <488F581B.7060009@qualcomm.com> <48903431.9060707@amd.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 958 Lines: 29 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? TIA, -- Best regards, Dmitry Adamushko -- 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/