Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751288AbVIURZx (ORCPT ); Wed, 21 Sep 2005 13:25:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751290AbVIURZx (ORCPT ); Wed, 21 Sep 2005 13:25:53 -0400 Received: from nevyn.them.org ([66.93.172.17]:54459 "EHLO nevyn.them.org") by vger.kernel.org with ESMTP id S1751288AbVIURZw (ORCPT ); Wed, 21 Sep 2005 13:25:52 -0400 Date: Wed, 21 Sep 2005 13:25:50 -0400 From: Daniel Jacobowitz To: Laurent Vivier , linux-kernel@vger.kernel.org Cc: Jeff Dike , "Paolo 'Blaisorblade' Giarrusso" , Bodo Stroesser Subject: PTRACE_SYSEMU numbering Message-ID: <20050921172550.GA10332@nevyn.them.org> Mail-Followup-To: Laurent Vivier , linux-kernel@vger.kernel.org, Jeff Dike , Paolo 'Blaisorblade' Giarrusso , Bodo Stroesser Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.8i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 929 Lines: 26 Here's a bit of the PTRACE_SYSEMU patch, committed three weeks ago: --- a/include/linux/ptrace.h +++ b/include/linux/ptrace.h @@ -20,6 +20,7 @@ #define PTRACE_DETACH 0x11 #define PTRACE_SYSCALL 24 +#define PTRACE_SYSEMU 31 /* 0x4200-0x4300 are reserved for architecture-independent additions. */ #define PTRACE_SETOPTIONS 0x4200 OK, I admit I could have made the comment clearer. But can we fix this? You've added PTRACE_SYSEMU on top of PTRACE_GETFDPIC, which presumably will mess up either debugging or UML on that architecture (if the latter were ported). That's exactly the problem we defined the 0x4200-0x4300 range to prevent. -- Daniel Jacobowitz CodeSourcery, LLC - 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/