From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755922Ab2APSfR (ORCPT ); Mon, 16 Jan 2012 13:35:17 -0500 Received: from cantor2.suse.de ([195.135.220.15]:41862 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755069Ab2APSfP (ORCPT ); Mon, 16 Jan 2012 13:35:15 -0500 Date: Mon, 16 Jan 2012 10:34:38 -0800 From: Greg KH To: "Luck, Tony" Cc: Linus Torvalds , Kay Sievers , "Srivatsa S. Bhat" , Ming Lei , Djalal Harouni , Borislav Petkov , Hidetoshi Seto , Ingo Molnar , Andi Kleen , "linux-kernel@vger.kernel.org" , "gouders@et.bocholt.fh-gelsenkirchen.de" , Marcos Souza , Linux PM mailing list , "Rafael J. Wysocki" , "tglx@linutronix.de" , "prasad@linux.vnet.ibm.com" , "justinmattock@gmail.com" , Jeff Chua , "Siddha, Suresh B" , Peter Zijlstra , Mel Gorman , Gilad Ben-Yossef Subject: Re: x86/mce: machine check warning during poweroff Message-ID: <20120116183438.GA14792@suse.de> References: <4F10929E.8070007@linux.vnet.ibm.com> <4F10BDF7.8030306@linux.vnet.ibm.com> <4F10EB5B.5060804@linux.vnet.ibm.com> <20120114144938.GA32033@suse.de> <20120116181135.GA2680@suse.de> <3908561D78D1C84285E8C5FCA982C28F01C672@ORSMSX104.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F01C672@ORSMSX104.amr.corp.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 16, 2012 at 06:27:16PM +0000, Luck, Tony wrote: > > The "correct" way to fix this up would be to have a per-cpu structure > > for all of the different mce things that are created in this driver > > (struct device, struct mce, exception counts, work queues, polling > > banks, etc.), but that seems pretty messy, and I imagine some of these > > want to stay as-is for some performance issues. As I don't know this > > code at all, I'm a bit leary to make that kind of change. > > If you get so many machine checks that you care about the performance > of the handler - you may be worrying about the wrong things. > > I'm more concerned about maintainability of the code. Seto-san has > submitted many patches re-grouping the functions inside mce.c into > functional areas - keeping the data structures separated makes > sense - especially if there is some goal of splitting mce.c into > separate files. Ok, I'll leave that alone, and just focus on the struct device stuff, as that I know can't be performance critical :) thanks, greg k-h