Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261663AbVD1Gp4 (ORCPT ); Thu, 28 Apr 2005 02:45:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261673AbVD1Gpz (ORCPT ); Thu, 28 Apr 2005 02:45:55 -0400 Received: from 70-56-217-9.albq.qwest.net ([70.56.217.9]:23447 "EHLO montezuma.fsmlabs.com") by vger.kernel.org with ESMTP id S261663AbVD1Gpu (ORCPT ); Thu, 28 Apr 2005 02:45:50 -0400 Date: Thu, 28 Apr 2005 00:48:04 -0600 (MDT) From: Zwane Mwaikambo To: Ashok Raj cc: linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu, tony.luck@intel.com, gregkh@suse.de, hch@infradead.org Subject: Re: Deferred handling of writes to /proc/irq/xx/smp_affinity In-Reply-To: <20050427221538.A30702@unix-os.sc.intel.com> Message-ID: References: <20050427221538.A30702@unix-os.sc.intel.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: 1171 Lines: 28 On Wed, 27 Apr 2005, Ashok Raj wrote: > Hi Andrew and all > > It is safe to re-program rte entries in ioapic only when an intr is pending. > Existing code does this incorrectly by reprogamming rte entries immediatly > when a value is written to /proc/irq/xx/smp_affinity. IRQ_BALANCE code in > kernel does this right, but /proc/irq needs to be handled the same way so that > user mode irq_balancer wont lock up systems or loose interrupts in the race. > > This is already fixed in ia64, introduced for i386 and x86_64. > > since this touches 3 arch's managing in -mm for trial would be best to make > sure nothing is broken, before considering for main line. Ashok, thanks for doing this, i only have minor nitpicks, can we avoid the wrapper for irq_desc and just index it directly? And could we use static inline functions for MOVE_IRQ and SET_IRQ_INFO macros and use nop functions where required. Thanks, Zwane - 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/