Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752523AbZJXWYP (ORCPT ); Sat, 24 Oct 2009 18:24:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752506AbZJXWYO (ORCPT ); Sat, 24 Oct 2009 18:24:14 -0400 Received: from relay1.vsu.ru ([62.76.169.14]:62108 "EHLO relay1.vsu.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752481AbZJXWYO (ORCPT ); Sat, 24 Oct 2009 18:24:14 -0400 X-Greylist: delayed 3602 seconds by postgrey-1.27 at vger.kernel.org; Sat, 24 Oct 2009 18:24:13 EDT X-drweb-hash: Date: Sat, 24 Oct 2009 22:09:06 +0100 (BST) From: Tigran Aivazian X-X-Sender: tigran@ginsburg.homenet To: Dmitry Adamushko cc: Mike Travis , Ingo Molnar , Thomas Gleixner , Andrew Morton , Jack Steiner , "H. Peter Anvin" , x86@kernel.org, Andreas Mohr , Hugh Dickins , Hannes Eder , linux-kernel@vger.kernel.org Subject: Re: [PATCH 6/8] SGI x86_64 UV: Limit the number of microcode messages In-Reply-To: Message-ID: References: <20091023233743.439628000@alcatraz.americas.sgi.com> <20091023233756.941535000@alcatraz.americas.sgi.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463810303-1689420186-1256418546=:2439" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1344 Lines: 33 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463810303-1689420186-1256418546=:2439 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sat, 24 Oct 2009, Dmitry Adamushko wrote: >> - =A0 =A0 =A0 printk(KERN_INFO "microcode: CPU%d sig=3D0x%x, pf=3D0x%x, = revision=3D0x%x\n", >> + =A0 =A0 =A0 if (cpu_num < 4 || !limit_console_output(false)) >> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 printk(KERN_INFO >> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 "microcode: CPU%d sig=3D0x= %x, pf=3D0x%x, revision=3D0x%x\n", >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0cpu_num, csig->sig, csig-= >pf, csig->rev); >> > > Hmm, I guess we wouldn't lose a lot by simply removing those messages > completely. Per-cpu pf/revision is available via /sys anyway. The reason for printing them is that the pf (possibly others?) can change= =20 by the update and so the log has this info handy. Kind regards Tigran ---1463810303-1689420186-1256418546=:2439-- -- 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/