Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761873AbZANLtY (ORCPT ); Wed, 14 Jan 2009 06:49:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757664AbZANLtJ (ORCPT ); Wed, 14 Jan 2009 06:49:09 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:57815 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755900AbZANLtI (ORCPT ); Wed, 14 Jan 2009 06:49:08 -0500 Date: Wed, 14 Jan 2009 12:48:29 +0100 From: Ingo Molnar To: Joerg Roedel Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, dwmw2@infradead.org, fujita.tomonori@lab.ntt.co.jp, netdev@vger.kernel.org, iommu@lists.linux-foundation.org Subject: Re: [PATCH 08/16] dma-debug: add core checking functions Message-ID: <20090114114829.GI8625@elte.hu> References: <1231517970-20288-1-git-send-email-joerg.roedel@amd.com> <1231517970-20288-9-git-send-email-joerg.roedel@amd.com> <20090110231127.GK17917@elte.hu> <20090114114401.GL20283@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090114114401.GL20283@amd.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian 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: 1381 Lines: 36 * Joerg Roedel wrote: > On Sun, Jan 11, 2009 at 12:11:27AM +0100, Ingo Molnar wrote: > > > > * Joerg Roedel wrote: > > > > > +#define err_printk(dev, format, arg...) do { \ > > > + error_count += 1; \ > > > + if (show_all_errors || show_num_errors > 0) { \ > > > + WARN(1, "%s %s: " format, \ > > > + dev_driver_string(dev), \ > > > + dev_name(dev) , ## arg); \ > > > + } \ > > > + if (!show_all_errors && show_num_errors > 0) \ > > > + show_num_errors -= 1; \ > > > > Note that the arithmetics here is SMP-unsafe: we only hold the hash bucket > > so if two errors hit at once on two CPUs then the error tracking variables > > can be accessed at once. > > > > I'd suggest a simple global lock for this error case (taken inside the > > hash bucket lock), to be on the safe side. > > As I wrote in a previous email, a race here is no big deal. I add a > comment to document it. Or do we want another global lock here? we commonly use global locks in debug exception cases - to serialize console output. But it's certainly no big deal. 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/