Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752301AbWAGPNK (ORCPT ); Sat, 7 Jan 2006 10:13:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752303AbWAGPNJ (ORCPT ); Sat, 7 Jan 2006 10:13:09 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:27040 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S1752258AbWAGPNI (ORCPT ); Sat, 7 Jan 2006 10:13:08 -0500 Date: Sat, 7 Jan 2006 16:12:50 +0100 (MET) From: Jan Engelhardt To: Jeff Dike cc: Rob Landley , user-mode-linux-devel@lists.sourceforge.net, akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: [uml-devel] Re: [PATCH 4/9] UML - Better diagnostics for broken configs In-Reply-To: <20060107023713.GA13285@ccure.user-mode-linux.org> Message-ID: References: <200601042151.k04LpxbH009237@ccure.user-mode-linux.org> <20060105161436.GA4426@ccure.user-mode-linux.org> <200601061801.17497.rob@landley.net> <20060107023713.GA13285@ccure.user-mode-linux.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 743 Lines: 20 >> Doing both of these things (a seperate host process for each UML process, and >> calling getpid() for all system calls), is what "Tracing Thread" mode did. >> The UML kernel was one thread among several, and it was kinda slow. > >The skas vs tt distinction is the address space part of this. How we nullify >system calls is separate. That's the PTRACE_SYSCALL vs PTRACE_SYSEMU (which >is now in mainline) thing. > ... So there is no way to get UML compile on non-Linux. Jan Engelhardt -- - 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/