From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030323AbWGMTec (ORCPT ); Thu, 13 Jul 2006 15:34:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030324AbWGMTec (ORCPT ); Thu, 13 Jul 2006 15:34:32 -0400 Received: from mx.pathscale.com ([64.160.42.68]:909 "EHLO mx.pathscale.com") by vger.kernel.org with ESMTP id S1030323AbWGMTeb (ORCPT ); Thu, 13 Jul 2006 15:34:31 -0400 Date: Thu, 13 Jul 2006 12:34:30 -0700 (PDT) From: Dave Olson Reply-To: olson@pathscale.com To: "Eric W. Biederman" Cc: Andi Kleen , linux-kernel@vger.kernel.org, Benjamin Herrenschmidt , discuss@x86-64.org Subject: Re: [PATCH 2/2] Initial generic hypertransport interrupt support. In-Reply-To: Message-ID: References: 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 On Thu, 13 Jul 2006, Eric W. Biederman wrote: | > I imagine at least some other drivers would like to know when their interrupt | > configuration changes, also, so an interface where a driver can register | > a callback handler seems like the right generic answer, or more simply, | > a way for a driver to say it doesn't want it's interrupt handler | > migrated (which we would like anyway, for performance reasons). | | As I recall that is "killall irqbalanced" That's the way for the user or admin to do it. It would be good for a driver to be able to say "I like my interrupt here, please don't move it". It can be advisory, rather than mandatory, but there are often cases where one driver is hurt by something that is generally beneficial, and disabling it everywhere is a big hammer. It works, but it's not ideal. Different issue than you are dealing with, but I thought it was worth bringing up, as long as we are talking about moving interrupts. Dave Olson dave.olson@qlogic.com