Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754450Ab1EYL3U (ORCPT ); Wed, 25 May 2011 07:29:20 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:38459 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752714Ab1EYL3T (ORCPT ); Wed, 25 May 2011 07:29:19 -0400 Date: Wed, 25 May 2011 13:28:52 +0200 From: Ingo Molnar To: Borislav Petkov Cc: Borislav Petkov , Andi Kleen , x86@kernel.org, linux-kernel@vger.kernel.org, Andi Kleen , Thomas Gleixner , "H. Peter Anvin" Subject: Re: [PATCH 1/3] x86, intel: Output microcode revision Message-ID: <20110525112852.GD30983@elte.hu> References: <1306278210-18285-1-git-send-email-andi@firstfloor.org> <20110525065451.GC429@elte.hu> <20110525080042.GA27183@liondog.tnic> <20110525090501.GA28500@elte.hu> <20110525105057.GA21830@gere.osrc.amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110525105057.GA21830@gere.osrc.amd.com> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1106 Lines: 33 * Borislav Petkov wrote: > Btw, can we dump the ucode version in hex since ours are much easier to > read that way: > > [86483.770976] microcode: CPU0: patch_level=0x010000c4 > [86483.826987] microcode: CPU1: patch_level=0x010000c4 > [86483.835071] microcode: CPU2: patch_level=0x010000c4 > ... How is that version constructed and iterated, or example is the 0x01000000 bit always set? If it's always set then it might make sense to turn this into a more human-readable version number: mask out the 0x01000000 and report 0xc4 as 194? Or is the *real* version above just '4'? Should 0x010000c4 perhaps be printed as 1.10.4? > I guess for Intel the ucode version format won't matter that much. Well, if Intel does similar encodings as AMD, then it would be nice to turn that into human-readable version strings as well. Thanks, Ingo -- 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/