From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 11 Nov 2002 16:56:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 11 Nov 2002 16:56:02 -0500 Received: from palrel13.hp.com ([156.153.255.238]:29416 "HELO palrel13.hp.com") by vger.kernel.org with SMTP id ; Mon, 11 Nov 2002 16:56:01 -0500 To: "Van Maren, Kevin" Cc: "'Mario Smarduch '" , "'davidm+AEA-hpl.hp.com '" , "'Mario Smarduch '" , "'linux-ia64+AEA-linuxia64.org '" , "'linux-kernel+AEA-vger.kernel.org '" , grundler@cup.hp.com Subject: Re: [Linux-ia64] RE: +AFs-Linux-ia64+AF0- reader-writer livelock proble In-Reply-To: Your message of "Mon, 11 Nov 2002 14:36:38 CST." <3FAD1088D4556046AEC48D80B47B478C0101F4F7@usslc-exch-4.slc.unisys.com> References: <3FAD1088D4556046AEC48D80B47B478C0101F4F7@usslc-exch-4.slc.unisys.com> Date: Mon, 11 Nov 2002 14:02:32 -0800 From: Grant Grundler Message-Id: <20021111220232.C94F712C0C@debian.cup.hp.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Van Maren, Kevin" wrote: > It is also possible that a processor can get stuck +ACI-forever+ACI- > spinning in the kernel with interrupts disabled trying to > acquire a lock, and never succeed, without the rest of the > kernel going south. If that happens, and application will > be livelocked, but the rest of the system will function. Probably not. ia64 systems (and x86 systems with IO xapic) direct IO interrupts to specific CPUs. Devices would not get serviced in the above case and IO to/from those devices would come to a grinding halt. It would look more like "dead" lock than "live" lock. > It really depends on the particular circumstances. yes. But it sounds very likely to me. grant