From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 10F5BDDED7 for ; Sun, 22 Jun 2008 10:20:43 +1000 (EST) Subject: Re: [PATCH][WIP][RFC] powerpc: fixup lwsync at runtime From: Benjamin Herrenschmidt To: Kumar Gala In-Reply-To: <81690AB9-9D0A-4CB4-8A0A-B0D8653FECE7@kernel.crashing.org> References: <1214004193.8011.184.camel@pasglop> <81690AB9-9D0A-4CB4-8A0A-B0D8653FECE7@kernel.crashing.org> Content-Type: text/plain Date: Sun, 22 Jun 2008 10:20:36 +1000 Message-Id: <1214094036.8011.192.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 2008-06-21 at 11:07 -0500, Kumar Gala wrote: > > > Remind me why we want to do that ? ie. can't we just use lwsync > > unconditionally ? It's supposed to degrade to sync on CPUs that > don't > > support it, or is that broken on some parts ? > > I believe its broken on e500v1/v2. However I'll double check. An option is that if you get a program check instead, you can "fixup" the sync from the exception too... Ben.