Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932293AbWKGRhK (ORCPT ); Tue, 7 Nov 2006 12:37:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932712AbWKGRhK (ORCPT ); Tue, 7 Nov 2006 12:37:10 -0500 Received: from mx.pathscale.com ([64.160.42.68]:2493 "EHLO mx.pathscale.com") by vger.kernel.org with ESMTP id S932293AbWKGRhI (ORCPT ); Tue, 7 Nov 2006 12:37:08 -0500 Date: Tue, 7 Nov 2006 09:37:07 -0800 (PST) From: Dave Olson Reply-To: olson@pathscale.com To: "Eric W. Biederman" Cc: "Bryan O'Sullivan" , Adrian Bunk , Linux Kernel Mailing List Subject: Re: 2.6.19-rc4: known unfixed regressions (v3) In-Reply-To: Message-ID: References: <20061105064801.GV13381@stusta.de> <20061107042214.GC8099@stusta.de> <45501730.8020802@serpentine.com> <4550B22C.1060307@serpentine.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1457 Lines: 35 On Tue, 7 Nov 2006, Eric W. Biederman wrote: | Huh? As I read the ipath code I am passing you the value that needs to go | into ipath->int_config and thus into dd->ipath_kregs->kr_interrupt_config. Yes. | Sure it is coming as 2 32bit words instead of a one big 64 bit one, but | that is simple to fix. It would be cleaner, but not absolutely necessary. | If your card doesn't pay attention to configuration space access cycles then | there should be no reason to write the value there. If your card does pay | attention to the configuration space access cycles it should be trivial to | make this work. The card does pay attention, and other programs such as lspci and the like also look at the config space. They should definitely be kept in sync, and config writes are fairly cheap, anyway. | If you really need to write to both the config space registers and your | magic shadow copy of the register I can certainly do the config space | writes for you. I just figured it would be more efficient not to. The HT layer should always do the config updates, since you are trying to clean up that layer. Only the "extra" stuff (if any) should be done by the callback. Dave Olson dave.olson@qlogic.com - 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/