Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265797AbUA1WpA (ORCPT ); Wed, 28 Jan 2004 17:45:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266044AbUA1WpA (ORCPT ); Wed, 28 Jan 2004 17:45:00 -0500 Received: from ns.suse.de ([195.135.220.2]:21994 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S265797AbUA1Wo5 (ORCPT ); Wed, 28 Jan 2004 17:44:57 -0500 Date: Wed, 28 Jan 2004 23:39:48 +0100 From: Andi Kleen To: Linus Torvalds Cc: willy@debian.org, ishii.hironobu@jp.fujitsu.com, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org Subject: Re: [RFC/PATCH, 2/4] readX_check() performance evaluation Message-Id: <20040128233948.26a36ff7.ak@suse.de> In-Reply-To: References: <00a301c3e541$c13a6350$2987110a@lsd.css.fujitsu.com> <20040128182003.GL11844@parcelfarce.linux.theplanet.co.uk> <20040128204049.627e6312.ak@suse.de> <20040128211554.0cc890fb.ak@suse.de> <20040128220921.7ba0bb78.ak@suse.de> <20040128225205.02193769.ak@suse.de> X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1189 Lines: 34 On Wed, 28 Jan 2004 14:21:40 -0800 (PST) Linus Torvalds wrote: > > > On Wed, 28 Jan 2004, Andi Kleen wrote: > > > > I have no idea how to do such an synchronization on i386/x86-64. E.g. Opteron > > chipsets would likely support MCEs for bus aborts, but there is no way to > > synchronize it for writes. > > Doing a status read from the device should do it (just read the config > space, for example). The device is just not known. iirc you only get a bit in the bridge, which leaves a wide choice. Ok, I guess you could read all config spaces in this case (I don't remember the ordering rules well enough - maybe one single config space read is enough for all devices behind the bridge) > But remember: I suspect there are very _very_ few people who care at that > stage. Driver writers caring would be a good start. I definitely agree that it shouldn't be enabled on anything near a production kernel. -Andi - 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/