Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758221AbZC3JHi (ORCPT ); Mon, 30 Mar 2009 05:07:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755609AbZC3JH3 (ORCPT ); Mon, 30 Mar 2009 05:07:29 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:40865 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755158AbZC3JH2 (ORCPT ); Mon, 30 Mar 2009 05:07:28 -0400 Message-ID: <49D08BC7.6070002@jp.fujitsu.com> Date: Mon, 30 Mar 2009 18:07:19 +0900 From: Hidetoshi Seto User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Andi Kleen CC: linux-kernel@vger.kernel.org, Ingo Molnar Subject: Re: [PATCH -tip 3/3] x86, mce: Add mce=nopoll option to disable timer polling References: <49CB3F4B.8070406@jp.fujitsu.com> <49CB4453.6000407@linux.intel.com> <49CCA122.8070908@jp.fujitsu.com> <49CCBC07.6000004@linux.intel.com> In-Reply-To: <49CCBC07.6000004@linux.intel.com> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1609 Lines: 40 Andi Kleen wrote: >>> Also I'm not sure a boot argument is really needed. Isn't it >>> good enough to do this early at boot through sysfs? >> Maybe it is good for this option, as far as polling never run >> so soon. Because sysfs is available after start of polling >> timer, boot argument is required just in theory of logics. > > I think the best way would be to just not run mcelog if you want > the BIOS to log all. The only problem I guess is that users might be confused > by the printk. So perhaps just do a patch to shut down the printk? How to prevent banks from clearing? >> One another problem is that there are multiple documentations for >> machinecheck parameters, but not linked well: >> >> - Documentation/kernel-parameters.txt >> ("See Documentation/x86/x86_64/boot-options.txt" for "mce=") >> - Documentation/x86/x86_64/boot-options.txt >> ("AMD64 specific boot options" is not true now!) >> - Documentation/x86/x86_64/machinecheck >> (which I had not noticed the existence at first, oops!) > > machinecheck is for the sysfs interface, boot options is for the boot parameters. > > I guess a reference could be added to machinecheck to point to boot-options.txt Vice verse, I suppose. boot-options.txt just have "Everything else is in sysfs now." without pointing machinecheck that describe the sysfs well. Thanks, H.Seto -- 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/