Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265353AbUF2Dqu (ORCPT ); Mon, 28 Jun 2004 23:46:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265383AbUF2Dqu (ORCPT ); Mon, 28 Jun 2004 23:46:50 -0400 Received: from mail3.speakeasy.net ([216.254.0.203]:38047 "EHLO mail3.speakeasy.net") by vger.kernel.org with ESMTP id S265353AbUF2Dqn (ORCPT ); Mon, 28 Jun 2004 23:46:43 -0400 Date: Mon, 28 Jun 2004 20:46:40 -0700 Message-Id: <200406290346.i5T3keo1022764@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Linus Torvalds Cc: Andrew Morton , Ingo Molnar , Andrew Cagney , Linux Kernel Mailing List Subject: Re: [RFC PATCH] x86 single-step (TF) vs system calls & traps In-Reply-To: Linus Torvalds's message of Monday, 28 June 2004 20:42:35 -0700 X-Fcc: ~/Mail/linus X-Windows: foiled again. Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 710 Lines: 19 > And I refuse to make the fast-path slower just because of this. You are talking about the int $0x80 system call path here? That is the only non-exception path touched by my changes. > Not only has Linux always worked like this, as far as I know all other > x86 OS's also tend to just do the Intel behaviour thing. The only other one I have at hand to test is NetBSD 1.6.1, which does indeed behave the same way for its int $0x80 system calls. Thanks, Roland - 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/