From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hironobu Ishii Date: Thu, 29 Jan 2004 12:24:52 +0000 Subject: Re: [RFC/PATCH, 2/4] readX_check() performance evaluation Message-Id: <00ad01c3e662$e893ce10$2987110a@lsd.css.fujitsu.com> List-Id: 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> <20040128233948.26a36ff7.ak@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Linus Torvalds , Andi Kleen Cc: willy@debian.org, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org From: "Linus Torvalds" To: "Andi Kleen" Cc: ; ; ; Sent: Thursday, January 29, 2004 7:59 AM Subject: Re: [RFC/PATCH, 2/4] readX_check() performance evaluation > > > On Wed, 28 Jan 2004, Andi Kleen wrote: > > > 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. > > read_pcix_error() _does_ know the device. The driver tells it. > > Remember: none of this should be done at machine check time. > > Linus Thank you for a lot of comments. I prefer Linus's I/F than callback(exception) I/F, because I can recover from intermittent errors. I'd need time to consider how to map these I/F onto ia64 platform. Later, I will post the result. Thank you. Hironobu Ishii