Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 26 Sep 2002 13:13:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 26 Sep 2002 13:13:01 -0400 Received: from pc1-cwma1-5-cust128.swa.cable.ntl.com ([80.5.120.128]:16890 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Thu, 26 Sep 2002 13:12:59 -0400 Subject: Re: [ANNOUNCE] Native POSIX Thread Library 0.1 From: Alan Cox To: dean gaudet Cc: "Eric W. Biederman" , Bill Davidsen , Bill Huey , Ingo Molnar , Ulrich Drepper , linux-kernel In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 26 Sep 2002 18:21:07 +0100 Message-Id: <1033060867.1269.152.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1056 Lines: 20 On Sun, 2002-09-22 at 23:13, dean gaudet wrote: > given that the existing code uses self-modifying-code for the safe-points > i'm guessing there are so many safe-points that the above if statement > would be excessive overhead (and the save/flag/wait stuff would probably > cause a huge amount of code bloat -- but could probably be a subroutine). It might be worth reminding people here that you cannot implement self modifying code safely on x86 SMP systems without a lot of care. Several common chips take a long walk off a short bus when the code they are currently executing is modified as they execute it. Not just because of write atomicity (which could be fixed) but because of hardware errata. So if you are patching something that another cpu could be executing at the same time - you already lost. - 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/