Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 15 Feb 2003 16:57:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 15 Feb 2003 16:57:11 -0500 Received: from faui11.informatik.uni-erlangen.de ([131.188.31.2]:41664 "EHLO faui11.informatik.uni-erlangen.de") by vger.kernel.org with ESMTP id ; Sat, 15 Feb 2003 16:57:10 -0500 From: Ulrich Weigand Message-Id: <200302152207.XAA09202@faui11.informatik.uni-erlangen.de> Subject: Re: [PATCH][2.5][8/14] smp_call_function_on_cpu - s390 To: zwane@holomorphy.com (Zwane Mwaikambo) Date: Sat, 15 Feb 2003 23:07:01 +0100 (MET) Cc: weigand@immd1.informatik.uni-erlangen.de (Ulrich Weigand), linux-kernel@vger.kernel.org (Linux Kernel), schwidefsky@de.ibm.com (Martin Schwidefsky) In-Reply-To: from "Zwane Mwaikambo" at Feb 15, 2003 02:01:06 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 921 Lines: 24 Zwane Mwaikambo wrote: > This could be achieved if s390 (or if we had a generic one, this is > another story...) had a for_each_cpu type iterator, which would also > cover aforementioned mask &= cpu_online_map issue, but as an aside, it is > harder to track down lockups from things like IPIs to invalid cpus than a busy loop > waiting for num_cpus. I'm not sure I understand what you mean here. In any case, at least on S/390, doing a SIGP to an invalid CPU will simply get you an 'not operational' indication (condition code 3), so in fact the only problem *is* the busy loop on num_cpus ... Bye, Ulrich -- Dr. Ulrich Weigand weigand@informatik.uni-erlangen.de - 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/