From owner-freebsd-threads@FreeBSD.ORG Sun May 9 06:52:56 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EB5916A4CE; Sun, 9 May 2004 06:52:56 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE8D643D1D; Sun, 9 May 2004 06:52:55 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i49DqtpW014467; Sun, 9 May 2004 09:52:55 -0400 (EDT) Date: Sun, 9 May 2004 09:52:55 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Tim Robbins In-Reply-To: <20040509034044.GA24124@cat.robbins.dropbear.id.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: KSE debugging support - status? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2004 13:52:56 -0000 On Sun, 9 May 2004, Tim Robbins wrote: > What is the current status of KSE debugging/GDB support? What's holding it > up, and when is it likely to be committed? I believe it's waiting for a GDB import and some kernel thread id changes. Marcel is working in perforce on GDB, julian in perforce on some KSE/thread/scheduling (kernel) restructuring, and dfr in perforce on TLS support. -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Sun May 9 23:55:56 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC0C316A4CE for ; Sun, 9 May 2004 23:55:56 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 594EA43D46 for ; Sun, 9 May 2004 23:55:56 -0700 (PDT) (envelope-from burpmaster@truffula.net) Received: from truffula.net (c-67-169-200-31.client.comcast.net[67.169.200.31]) by comcast.net (rwcrmhc12) with ESMTP id <2004051006555201400ju2sge>; Mon, 10 May 2004 06:55:56 +0000 Message-ID: <409F2770.9000604@truffula.net> Date: Sun, 09 May 2004 23:55:44 -0700 From: Brian Rogers User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7b) Gecko/20040503 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-threads@freebsd.org References: <20040507102350.B32793@fw.reifenberger.com> In-Reply-To: <20040507102350.B32793@fw.reifenberger.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: wine & -current & notes & networkaccess X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 06:55:57 -0000 Michael Reifenberger wrote: >Hi, >running the notes-client with wine under -current (after some changes to our >pthreads some months ago) gives me when accessing a database over the network: > >... >Fatal error 'Uninitialized mutex in pthread_mutex_trylock_basic' at line 474 in >file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 0) >wine: Unhandled exception (thread 000c), starting debugger... >fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on >this platform >WineDbg starting on pid 8 >... > >Is wine missing something or is libpthread doing something wrong? > >my /etc/libmap.conf BTW: > ># default >libc_r.so.5 libpthread.so.1 >libc_r.so libpthread.so >libkse.so.1 libpthread.so.1 >libkse.so libpthread.so >... > > I see this also. There are two wine binaries, wine-kthread and wine-pthread. On FreeBSD, just wine-kthread is built and it is installed as /usr/local/bin/wine. wine-kthread doesn't seem to like being linked with libpthread, but that will happen through the arts sound driver or any .dll.so file that links to the OpenGL library. If you build wine from CVS, you can configure it with --without-opengl. Then if you're not using the arts sound driver, wine-kthread will work just fine. I also found that you can cd into wine/loader and do "gmake wine-pthread" to build the pthread version of wine. It can handle libpthread just fine, but it has its own problems. (I don't think the wine people even realize that wine-pthread works on FreeBSD) From owner-freebsd-threads@FreeBSD.ORG Mon May 10 11:01:42 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 699BD16A4F6 for ; Mon, 10 May 2004 11:01:42 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D06F43D46 for ; Mon, 10 May 2004 11:01:42 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) i4AI1f9E095877 for ; Mon, 10 May 2004 11:01:42 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4AI1feF095871 for freebsd-threads@freebsd.org; Mon, 10 May 2004 11:01:41 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 10 May 2004 11:01:41 -0700 (PDT) Message-Id: <200405101801.i4AI1feF095871@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 18:01:42 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything s [2004/03/15] kern/64313 threads FreeBSD (OpenBSD) pthread implicit set/un o [2004/04/22] threads/65883threads libkse's sigwait does not work after fork 3 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/07/18] kern/20016 threads pthreads: Cannot set scheduling timer/Can o [2000/08/26] misc/20861 threads libc_r does not honor socket timeouts o [2001/01/19] bin/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] bin/24632 threads libc_r delicate deviation from libc in ha o [2001/01/25] misc/24641 threads pthread_rwlock_rdlock can deadlock o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/02/01] i386/34536 threads accept() blocks other threads o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/06/27] bin/39922 threads [PATCH?] Threaded applications executed w o [2002/08/04] misc/41331 threads Pthread library open sets O_NONBLOCK flag o [2003/03/02] bin/48856 threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] bin/49087 threads Signals lost in programs linked with libc a [2003/04/08] bin/50733 threads buildworld won't build, because of linkin o [2003/05/07] bin/51949 threads thread in accept cannot be cancelled 14 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/05/25] misc/18824 threads gethostbyname is not thread safe o [2000/10/21] misc/22190 threads A threaded read(2) from a socketpair(2) f o [2001/09/09] bin/30464 threads pthread mutex attributes -- pshared o [2002/05/02] bin/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwri s [2002/07/16] misc/40671 threads pthread_cancel doesn't remove thread from 5 problems total. From owner-freebsd-threads@FreeBSD.ORG Tue May 11 14:32:58 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F256D16A4CE for ; Tue, 11 May 2004 14:32:57 -0700 (PDT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BBB543D41 for ; Tue, 11 May 2004 14:32:57 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 8432 invoked from network); 11 May 2004 21:32:57 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 11 May 2004 21:32:57 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4BLWsp0006894; Tue, 11 May 2004 17:32:54 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: threads@FreeBSD.org Date: Tue, 11 May 2004 17:33:19 -0400 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200405111733.19783.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Bruce Evans Subject: Threads and userland profliing... X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 21:32:58 -0000 Currently in the pstats structure we have a uprof substructure that holds various values used for userland processing. Does anyone know what parts of that structure are supposed to be per-process and which are supposed to be per-thread? pr_addr and pr_ticks seem to be definite per-thread items, but the other values I'm not sure of. Specifically, is the userland table that pr_base, pr_size, pr_off, and pr_scale refer to per-thread or is it supposed to be shared among all threads in a process? If it's shared, do we need to be using casuptr() or something similar in addupc_intr() instead of a separate fetch and store? addupc_task() also has a race window between the copyin() and copyout() as well if it is shared. If its private, then I suppose each thread has to call profil(2) and gprof is supposed to be smart enough to make that happen? Does POSIX have anything to say regarding threads and profil(2)? I'm trying to lock this small structure and I'd like to know if all of uprof should be per-thread or just pr_addr and pr_ticks. P.S. Please cc me on replies as I am not subscribed. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-threads@FreeBSD.ORG Tue May 11 14:59:39 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D69316A4CE; Tue, 11 May 2004 14:59:39 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 813A943D1F; Tue, 11 May 2004 14:59:38 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i4BLxbke012044; Tue, 11 May 2004 17:59:37 -0400 (EDT) Date: Tue, 11 May 2004 17:59:37 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: John Baldwin In-Reply-To: <200405111733.19783.jhb@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: Bruce Evans Subject: Re: Threads and userland profliing... X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 21:59:39 -0000 On Tue, 11 May 2004, John Baldwin wrote: > Currently in the pstats structure we have a uprof substructure that holds > various values used for userland processing. Does anyone know what parts of > that structure are supposed to be per-process and which are supposed to be > per-thread? pr_addr and pr_ticks seem to be definite per-thread items, but > the other values I'm not sure of. > > Specifically, is the userland table that pr_base, pr_size, pr_off, and > pr_scale refer to per-thread or is it supposed to be shared among all threads > in a process? If it's shared, do we need to be using casuptr() or something > similar in addupc_intr() instead of a separate fetch and store? > addupc_task() also has a race window between the copyin() and copyout() as > well if it is shared. If its private, then I suppose each thread has to call > profil(2) and gprof is supposed to be smart enough to make that happen? Does > POSIX have anything to say regarding threads and profil(2)? POSIX does not define profil(2). Here's what Solaris 9 has to say about it: In Solaris releases prior to 2.6, calling profil() in a mul- tithreaded program would impact only the calling LWP; the profile state was not inherited at LWP creation time. To profile a multithreaded program with a global profile buffer, each thread needed to issue a call to profil() at threads start-up time, and each thread had to be a bound thread. This was cumbersome and did not easily support dynamically turning profiling on and off. In Solaris 2.6, the profil() system call for multithreaded processes has global impact - that is, a call to profil() impacts all LWPs/threads in the process. This may cause applications that depend on the previous per-LWP semantic to break, but it is expected to improve multithreaded programs that wish to turn profiling on and off dynamically at runtime. We should probably avoid the mistake that Solaris < 2.6 made. -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Tue May 11 15:35:14 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43F1816A4CF; Tue, 11 May 2004 15:35:14 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD00A43D3F; Tue, 11 May 2004 15:35:13 -0700 (PDT) (envelope-from davidxu@viatech.com.cn) Received: from viatech.com.cn (davidxu@localhost [127.0.0.1]) i4BMZASg022568; Tue, 11 May 2004 15:35:12 -0700 (PDT) (envelope-from davidxu@viatech.com.cn) Message-ID: <40A15602.9020902@viatech.com.cn> Date: Wed, 12 May 2004 06:38:58 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031206 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: threads@freebsd.org cc: Bruce Evans cc: John Baldwin Subject: Re: Threads and userland profliing... X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 22:35:14 -0000 Daniel Eischen wrote: >On Tue, 11 May 2004, John Baldwin wrote: > > > >>Currently in the pstats structure we have a uprof substructure that holds >>various values used for userland processing. Does anyone know what parts of >>that structure are supposed to be per-process and which are supposed to be >>per-thread? pr_addr and pr_ticks seem to be definite per-thread items, but >>the other values I'm not sure of. >> >>Specifically, is the userland table that pr_base, pr_size, pr_off, and >>pr_scale refer to per-thread or is it supposed to be shared among all threads >>in a process? If it's shared, do we need to be using casuptr() or something >>similar in addupc_intr() instead of a separate fetch and store? >>addupc_task() also has a race window between the copyin() and copyout() as >>well if it is shared. If its private, then I suppose each thread has to call >>profil(2) and gprof is supposed to be smart enough to make that happen? Does >>POSIX have anything to say regarding threads and profil(2)? >> >> > >POSIX does not define profil(2). Here's what Solaris 9 has to >say about it: > > In Solaris releases prior to 2.6, calling profil() in a mul- > tithreaded program would impact only the calling LWP; the > profile state was not inherited at LWP creation time. To > profile a multithreaded program with a global profile > buffer, each thread needed to issue a call to profil() at > threads start-up time, and each thread had to be a bound > thread. This was cumbersome and did not easily support > dynamically turning profiling on and off. In Solaris 2.6, > the profil() system call for multithreaded processes has > global impact - that is, a call to profil() impacts all > LWPs/threads in the process. This may cause applications > that depend on the previous per-LWP semantic to break, but > it is expected to improve multithreaded programs that wish > to turn profiling on and off dynamically at runtime. > >We should probably avoid the mistake that Solaris < 2.6 >made. > > > Because I never thought the profile buffer should be per-process, did you mean that it should be per-process too? David Xu From owner-freebsd-threads@FreeBSD.ORG Tue May 11 15:36:55 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48A1816A4CE; Tue, 11 May 2004 15:36:55 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E340543D1F; Tue, 11 May 2004 15:36:54 -0700 (PDT) (envelope-from davidxu@viatech.com.cn) Received: from viatech.com.cn (davidxu@localhost [127.0.0.1]) i4BMaq0i022595; Tue, 11 May 2004 15:36:53 -0700 (PDT) (envelope-from davidxu@viatech.com.cn) Message-ID: <40A15668.1030103@viatech.com.cn> Date: Wed, 12 May 2004 06:40:40 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031206 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <40A15602.9020902@viatech.com.cn> In-Reply-To: <40A15602.9020902@viatech.com.cn> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: threads@freebsd.org cc: Bruce Evans cc: John Baldwin Subject: Re: Threads and userland profliing... X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 22:36:55 -0000 David Xu wrote: > Daniel Eischen wrote: > >> On Tue, 11 May 2004, John Baldwin wrote: >> >> >> >>> Currently in the pstats structure we have a uprof substructure that >>> holds various values used for userland processing. Does anyone know >>> what parts of that structure are supposed to be per-process and >>> which are supposed to be per-thread? pr_addr and pr_ticks seem to >>> be definite per-thread items, but the other values I'm not sure of. >>> >>> Specifically, is the userland table that pr_base, pr_size, pr_off, >>> and pr_scale refer to per-thread or is it supposed to be shared >>> among all threads in a process? If it's shared, do we need to be >>> using casuptr() or something similar in addupc_intr() instead of a >>> separate fetch and store? addupc_task() also has a race window >>> between the copyin() and copyout() as well if it is shared. If its >>> private, then I suppose each thread has to call profil(2) and gprof >>> is supposed to be smart enough to make that happen? Does POSIX have >>> anything to say regarding threads and profil(2)? >>> >> >> >> POSIX does not define profil(2). Here's what Solaris 9 has to >> say about it: >> >> In Solaris releases prior to 2.6, calling profil() in a mul- >> tithreaded program would impact only the calling LWP; the >> profile state was not inherited at LWP creation time. To >> profile a multithreaded program with a global profile >> buffer, each thread needed to issue a call to profil() at >> threads start-up time, and each thread had to be a bound >> thread. This was cumbersome and did not easily support >> dynamically turning profiling on and off. In Solaris 2.6, >> the profil() system call for multithreaded processes has >> global impact - that is, a call to profil() impacts all >> LWPs/threads in the process. This may cause applications >> that depend on the previous per-LWP semantic to break, but >> it is expected to improve multithreaded programs that wish >> to turn profiling on and off dynamically at runtime. >> >> We should probably avoid the mistake that Solaris < 2.6 >> made. >> >> >> > Because I never thought the profile buffer should be per-process, OOPS, I thought it should be per-process, not per-thread. > did you mean that it should be per-process too? > > David Xu > > > > From owner-freebsd-threads@FreeBSD.ORG Tue May 11 15:47:43 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB6BD16A4CE; Tue, 11 May 2004 15:47:43 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48AED43D2F; Tue, 11 May 2004 15:47:43 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i4BMlgke025596; Tue, 11 May 2004 18:47:42 -0400 (EDT) Date: Tue, 11 May 2004 18:47:40 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: David Xu In-Reply-To: <40A15602.9020902@viatech.com.cn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: Bruce Evans cc: John Baldwin Subject: Re: Threads and userland profliing... X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 22:47:44 -0000 On Wed, 12 May 2004, David Xu wrote: > Daniel Eischen wrote: > > >On Tue, 11 May 2004, John Baldwin wrote: > > > >>Currently in the pstats structure we have a uprof substructure that holds > >>various values used for userland processing. Does anyone know what parts of > >>that structure are supposed to be per-process and which are supposed to be > >>per-thread? pr_addr and pr_ticks seem to be definite per-thread items, but > >>the other values I'm not sure of. > >> > >>Specifically, is the userland table that pr_base, pr_size, pr_off, and > >>pr_scale refer to per-thread or is it supposed to be shared among all threads > >>in a process? If it's shared, do we need to be using casuptr() or something > >>similar in addupc_intr() instead of a separate fetch and store? > >>addupc_task() also has a race window between the copyin() and copyout() as > >>well if it is shared. If its private, then I suppose each thread has to call > >>profil(2) and gprof is supposed to be smart enough to make that happen? Does > >>POSIX have anything to say regarding threads and profil(2)? > >> > >> > > > >POSIX does not define profil(2). Here's what Solaris 9 has to > >say about it: > > > > In Solaris releases prior to 2.6, calling profil() in a mul- > > tithreaded program would impact only the calling LWP; the > > profile state was not inherited at LWP creation time. To > > profile a multithreaded program with a global profile > > buffer, each thread needed to issue a call to profil() at > > threads start-up time, and each thread had to be a bound > > thread. This was cumbersome and did not easily support > > dynamically turning profiling on and off. In Solaris 2.6, > > the profil() system call for multithreaded processes has > > global impact - that is, a call to profil() impacts all > > LWPs/threads in the process. This may cause applications > > that depend on the previous per-LWP semantic to break, but > > it is expected to improve multithreaded programs that wish > > to turn profiling on and off dynamically at runtime. > > > >We should probably avoid the mistake that Solaris < 2.6 > >made. > > > > Because I never thought the profile buffer should be per-process, > did you mean that it should be per-process too? Yeah, I think so. Anyone know what Linux does? -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Wed May 12 00:43:36 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 457FE16A4CE for ; Wed, 12 May 2004 00:43:36 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D512143D45 for ; Wed, 12 May 2004 00:43:34 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc11) with ESMTP id <20040512074333013002i0j5e>; Wed, 12 May 2004 07:43:34 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id AAA52549 for ; Wed, 12 May 2004 00:43:33 -0700 (PDT) Date: Wed, 12 May 2004 00:43:32 -0700 (PDT) From: Julian Elischer To: threads@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Reminder! Call for March-April 2004 Status reports (fwd) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 07:43:36 -0000 anyone doing this? ---------- Forwarded message ---------- Date: Mon, 10 May 2004 15:12:05 -0600 From: Scott Long To: hackers@freebsd.org Subject: Reminder! Call for March-April 2004 Status reports All, It's time again for bi-monthly status reports. As always, the template is at http://www.freebsd.org/news/status/report-sample.xml. Please make submissions to monthly@freebsd.org by May 12 for inclusion. Any projects that relate to FreeBSD development, documentation, ports, etc, are welcome. Previous reports can be found at http://www.freebsd.org/news/status. Again, the due date is May 12. Thanks! Scott _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-threads@FreeBSD.ORG Wed May 12 05:57:45 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37AB416A4CE; Wed, 12 May 2004 05:57:45 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D65143D46; Wed, 12 May 2004 05:57:44 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i4CCvbke003076; Wed, 12 May 2004 08:57:38 -0400 (EDT) Date: Wed, 12 May 2004 08:57:37 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Julian Elischer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: dfr@freebsd.org cc: marcel@freebsd.org Subject: Re: Reminder! Call for March-April 2004 Status reports (fwd) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 12:57:45 -0000 On Wed, 12 May 2004, Julian Elischer wrote: > > anyone doing this? Not that I'm aware of. I'd do it but I need input from dfr (TLS), marcel (GDB, kernel thread ids), and you (KSE kernel reorg and scheduling). > > ---------- Forwarded message ---------- > Date: Mon, 10 May 2004 15:12:05 -0600 > From: Scott Long > To: hackers@freebsd.org > Subject: Reminder! Call for March-April 2004 Status reports > > All, > > It's time again for bi-monthly status reports. As always, the > template is at http://www.freebsd.org/news/status/report-sample.xml. > Please make submissions to monthly@freebsd.org by May 12 for > inclusion. Any projects that relate to FreeBSD development, > documentation, ports, etc, are welcome. Previous reports can be > found at http://www.freebsd.org/news/status. Again, the due date > is May 12. Thanks! > > Scott -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Wed May 12 12:42:26 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F64016A4CE for ; Wed, 12 May 2004 12:42:26 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF0A543D39 for ; Wed, 12 May 2004 12:42:21 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <2004051219422001400k4j2ue>; Wed, 12 May 2004 19:42:21 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA59070 for ; Wed, 12 May 2004 12:42:18 -0700 (PDT) Date: Wed, 12 May 2004 12:42:17 -0700 (PDT) From: Julian Elischer To: threads@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Reminder! Call for March-April 2004 Status reports (fwd) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 19:42:26 -0000 ok, I'll use: http://www.elischer.org/organization/submit.htm to generate it.. On Wed, 12 May 2004, Julian Elischer wrote: > > anyone doing this? > > > ---------- Forwarded message ---------- > Date: Mon, 10 May 2004 15:12:05 -0600 > From: Scott Long > To: hackers@freebsd.org > Subject: Reminder! Call for March-April 2004 Status reports > > All, > > It's time again for bi-monthly status reports. As always, the > template is at http://www.freebsd.org/news/status/report-sample.xml. > Please make submissions to monthly@freebsd.org by May 12 for > inclusion. Any projects that relate to FreeBSD development, > documentation, ports, etc, are welcome. Previous reports can be > found at http://www.freebsd.org/news/status. Again, the due date > is May 12. Thanks! > > Scott > > > > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" > From owner-freebsd-threads@FreeBSD.ORG Wed May 12 12:59:00 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09A0816A4CE; Wed, 12 May 2004 12:59:00 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8560F43D54; Wed, 12 May 2004 12:58:59 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc11) with ESMTP id <20040512195858013002mkmhe>; Wed, 12 May 2004 19:58:59 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA59226; Wed, 12 May 2004 12:58:56 -0700 (PDT) Date: Wed, 12 May 2004 12:58:55 -0700 (PDT) From: Julian Elischer To: Daniel Eischen In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: dfr@freebsd.org cc: marcel@freebsd.org Subject: Re: Reminder! Call for March-April 2004 Status reports (fwd) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 19:59:00 -0000 how about this as a start.. my little script only allows 3 names to be enterred... Status Report Sample David Xu davidxu@freebsd.org Doug Rabson dfr@freebsd.org Julian Elischer julian@freebsd.org {add dan, marcel here} basic data on TLS basic threads page

Threading developers have been active behind the scenes though not much has been visible. Real Life(TM) has been hard on us as a group however.

Marcel and Davidxu have both (individually) been looking at the support for debugging threaded programs. David has a set of patches that allow gdb to correctly handle KSE programs and patches are being considerred for libthr based processes. MArcell added a Thread ID to allow debugging code to unambiguously specify a thread to debug.

Dan Eischen continues to support people migrating to libpthreads and it seems to be going well.

Doug Rabson has done his usual miracle work and produced a set of preliminary pathces to implement TLS (Thread Local Storage) for the i386 platform.

Platforms: {fill in summary here}

On Wed, 12 May 2004, Daniel Eischen wrote: > On Wed, 12 May 2004, Julian Elischer wrote: > > > > anyone doing this? > > Not that I'm aware of. I'd do it but I need input from dfr > (TLS), marcel (GDB, kernel thread ids), and you (KSE kernel > reorg and scheduling). > > > > > ---------- Forwarded message ---------- > > Date: Mon, 10 May 2004 15:12:05 -0600 > > From: Scott Long > > To: hackers@freebsd.org > > Subject: Reminder! Call for March-April 2004 Status reports > > > > All, > > > > It's time again for bi-monthly status reports. As always, the > > template is at http://www.freebsd.org/news/status/report-sample.xml. > > Please make submissions to monthly@freebsd.org by May 12 for > > inclusion. Any projects that relate to FreeBSD development, > > documentation, ports, etc, are welcome. Previous reports can be > > found at http://www.freebsd.org/news/status. Again, the due date > > is May 12. Thanks! > > > > Scott > > -- > Dan Eischen > > From owner-freebsd-threads@FreeBSD.ORG Wed May 12 13:07:18 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B86516A4DF; Wed, 12 May 2004 13:07:18 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC5E043D53; Wed, 12 May 2004 13:07:17 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i4CK79ke025455; Wed, 12 May 2004 16:07:09 -0400 (EDT) Date: Wed, 12 May 2004 16:07:09 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Julian Elischer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: dfr@freebsd.org cc: marcel@freebsd.org Subject: Re: Reminder! Call for March-April 2004 Status reports (fwd) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 20:07:18 -0000 On Wed, 12 May 2004, Julian Elischer wrote: > how about this as a start.. > my little script only allows 3 names to be enterred... > > > Status Report Sample > > Marcel and Davidxu have both (individually) > been looking at the support > for debugging threaded programs. David has a set of > patches that allow gdb to correctly handle KSE programs and > patches are being considerred for libthr based processes. > Marcell added a Thread ID to allow debugging code to unambiguously > specify a thread to debug. I thought there was some question as to whether this would need to be revisited (I have no opinion on it myself, but seem to recall someone else mentioning it). >

> > Dan Eischen continues to support people migrating to > libpthreads and it seems to be going well. >

> > Doug Rabson has done his usual miracle work and produced > a set of preliminary pathces to implement TLS (Thread > Local Storage) for the i386 platform. >

> > Platforms: Still no change. libpthread works on i386, amd64, and ia64, but no progress on alpha or sparc64. -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Wed May 12 15:57:54 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF42516A4CE; Wed, 12 May 2004 15:57:53 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A5B343D39; Wed, 12 May 2004 15:57:53 -0700 (PDT) (envelope-from davidxu@freebsd.org) Received: from freebsd.org (davidxu@localhost [127.0.0.1]) i4CMvoiv096201; Wed, 12 May 2004 15:57:51 -0700 (PDT) (envelope-from davidxu@freebsd.org) Message-ID: <40A2ABBD.9080807@freebsd.org> Date: Thu, 13 May 2004 06:57:01 +0800 From: David Xu User-Agent: Mozilla Thunderbird 0.5 (X11/20040503) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: threads@freebsd.org cc: dfr@freebsd.org cc: marcel@freebsd.org Subject: Re: Reminder! Call for March-April 2004 Status reports (fwd) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 May 2004 22:57:54 -0000 Julian Elischer wrote: > > how about this as a start.. > my little script only allows 3 names to be enterred... > > > Status Report Sample > > > > > David > Xu > > davidxu@freebsd.org > > > > Doug > Rabson > > dfr@freebsd.org > > > > Julian > Elischer > > julian@freebsd.org > > {add dan, marcel here} > > > > basic data on > TLS > basic threads > page > > > >

> Threading developers have been active behind the scenes > though not much has been visible. Real Life(TM) has been > hard on us as a group however. >

> Marcel and Davidxu have both (individually) > been looking at the support > for debugging threaded programs. David has a set of > patches that allow gdb to correctly handle KSE programs and > patches are being considerred for libthr based processes. > MArcell added a Thread ID to allow debugging code to unambiguously > specify a thread to debug. >

> I have trouble to add Marcell's thread id to pthread debug code, since in my patch, I just use kernel thread address and user thread address as thread id, simply because there are unique in address space, sometimes a kernel thread not mapped to user thread will be caught by debugger, in this case, managing the thread id is hard. > Dan Eischen continues to support people migrating to > libpthreads and it seems to be going well. >

> > Doug Rabson has done his usual miracle work and produced > a set of preliminary pathces to implement TLS (Thread > Local Storage) for the i386 platform. >

> > Platforms: > {fill in summary here} > > > >

> > > > > > On Wed, 12 May 2004, Daniel Eischen wrote: > > >>On Wed, 12 May 2004, Julian Elischer wrote: >> >>>anyone doing this? >> >>Not that I'm aware of. I'd do it but I need input from dfr >>(TLS), marcel (GDB, kernel thread ids), and you (KSE kernel >>reorg and scheduling). >> >> >>>---------- Forwarded message ---------- >>>Date: Mon, 10 May 2004 15:12:05 -0600 >>>From: Scott Long >>>To: hackers@freebsd.org >>>Subject: Reminder! Call for March-April 2004 Status reports >>> >>>All, >>> >>>It's time again for bi-monthly status reports. As always, the >>>template is at http://www.freebsd.org/news/status/report-sample.xml. >>>Please make submissions to monthly@freebsd.org by May 12 for >>>inclusion. Any projects that relate to FreeBSD development, >>>documentation, ports, etc, are welcome. Previous reports can be >>>found at http://www.freebsd.org/news/status. Again, the due date >>>is May 12. Thanks! >>> >>>Scott >> >>-- >>Dan Eischen >> >> > > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" > >