From owner-freebsd-emulation@FreeBSD.ORG Tue Jul 20 22:19:06 2004 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E41D916A4CE for ; Tue, 20 Jul 2004 22:19:06 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8657243D1D for ; Tue, 20 Jul 2004 22:19:06 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6KMJ6QW028631; Tue, 20 Jul 2004 15:19:06 -0700 (PDT) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.12.11/8.12.11/Submit) id i6KMJ60h028630; Tue, 20 Jul 2004 15:19:06 -0700 (PDT) (envelope-from marcel) Date: Tue, 20 Jul 2004 15:19:06 -0700 From: Marcel Moolenaar To: "Georg-W. Koltermann" Message-ID: <20040720221906.GA28599@ns1.xcllnt.net> References: <1090273635.1511.15.camel@localhost.muc.eu.mscsoftware.com> <20040719215845.GA12055@dhcp50.pn.xcllnt.net> <1090360772.1047.5.camel@localhost.muc.eu.mscsoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1090360772.1047.5.camel@localhost.muc.eu.mscsoftware.com> User-Agent: Mutt/1.5.5.1i cc: freebsd-emulation@freebsd.org Subject: Re: how to implement linux_gettid X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 22:19:07 -0000 On Tue, Jul 20, 2004 at 11:59:33PM +0200, Georg-W. Koltermann wrote: > Am Mo, den 19.07.2004 schrieb Marcel Moolenaar um 23:58: > > On Mon, Jul 19, 2004 at 11:47:15PM +0200, Georg-W. Koltermann wrote: > > > > > > Could someone explain how our threading works when accessed from Linux, > > > and maybe give me a hint how gettid() should be implemented correctly? > > > > It depends. If user threading under linux compatibility is still > > implemented using fork(2), then you'll have a process per user thread. > > In that case it doesn't matter how threading is natively implemented. > > I am not quite sure. I see that i386/linux/syscalls.master has fork, > vfork, and clone. clone is implemented by calling fork1(). Does this > make sure that Linux threading is implemented using fork()? You want to look at what the threading library calls when it needs to create a new thread. I think this will be clone(2) and if it is, then threading is basicly implemented using fork(1) and the thread IDs is the process ID. > Or could it depend on the application or library layer, e.g. libpthread > in linux_base? Yes. See above. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net