From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suresh Siddha Subject: Re: Q: smp.c && barriers (Was: [PATCH 1/4] generic-smp: remove single ipi fallback for smp_call_function_many()) Date: Wed, 18 Feb 2009 10:33:46 -0800 Message-ID: <1234982026.29823.17.camel@vayu> References: <20090217112657.GE26402@wotan.suse.de> <20090217192810.GA4980@redhat.com> <20090217213256.GJ6761@linux.vnet.ibm.com> <20090217214518.GA13189@redhat.com> <20090217223910.GM6761@linux.vnet.ibm.com> <20090218135212.GB23125@wotan.suse.de> <20090218162116.GC29863@elte.hu> <20090218165808.GA9120@elte.hu> <20090218170517.GA9769@elte.hu> Reply-To: Suresh Siddha Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from mga03.intel.com ([143.182.124.21]:13622 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756150AbZBRSfP (ORCPT ); Wed, 18 Feb 2009 13:35:15 -0500 In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Linus Torvalds Cc: Ingo Molnar , "Pallipadi, Venkatesh" , Yinghai Lu , Nick Piggin , "Paul E. McKenney" , Oleg Nesterov , Peter Zijlstra , Jens Axboe , Rusty Russell , Steven Rostedt , "linux-kernel@vger.kernel.org" , "linux-arch@vger.kernel.org" , asit.k.mallick@intel.com On Wed, 2009-02-18 at 09:14 -0800, Linus Torvalds wrote: > > On Wed, 18 Feb 2009, Ingo Molnar wrote: > > > > an off-list comment pointed out this piece of information as > > well: > > > > http://www.sandpile.org/ia32/coherent.htm > > > > A WRMSR to one of the x2APIC MSRs (0000_0800h...0000_0BFFh) is > > not guaranteed to be serializing. > > > > So i suspect we should just enclose it in smp_mb() pairs to make > > sure it's a full barrier in both directions? > > Why would we care about "both directions"? on x86 we don't need in both directions. > > I think putting an sfence _before_ the wrmsr (and not even all of them - > just put it in front of the "send IPI" sequence) should be fine. Any other > ordering sounds like just unnecessary overhead to me. For x2apic ipi's, we should use a serializing instruction or a "mfence" instruction. "sfence" will not help in this scenario. thanks, suresh