From owner-freebsd-threads@FreeBSD.ORG  Fri Sep 17 12:32:06 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 1774816A4CE
	for <freebsd-threads@freebsd.org>;
	Fri, 17 Sep 2004 12:32:06 +0000 (GMT)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B7A4C43D1F
	for <freebsd-threads@freebsd.org>;
	Fri, 17 Sep 2004 12:32:05 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	i8HCW4ML017452;	Fri, 17 Sep 2004 08:32:05 -0400 (EDT)
Date: Fri, 17 Sep 2004 08:32:04 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: Andrew Belashov <bel@orel.ru>
In-Reply-To: <414AD11D.5000403@orel.ru>
Message-ID: <Pine.GSO.4.43.0409170827080.29249-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
cc: freebsd-threads@freebsd.org
Subject: Re: Need help for debugging libkse
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2004 12:32:06 -0000

On Fri, 17 Sep 2004, Andrew Belashov wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello, All!
>
> I'm debugging libkse library for FreeBSD/sparc64.
>
> Please, explain for me this ktrace dump:
>
> ========================================================
> ~  7877 ss       CALL  kse_create(0x26a000,0)
> ~  7877 ss       RET   kse_create 0
> ~  7877 ss       CALL  write(0x1,0x7fdffffdc68,0x1)
> ~  7877 ss       RET   write 2531328/0x26a000
> ~                            ^^^^^^^^^^^^^^^^

That is an upcall.  The kse_mailbox is being returned (same as in
the first kse_create()).

> ~  7877 ss       CALL  kse_switchin(0x270440,0x1)

This resumes the thread after it has become unblocked.

> ~  7877 ss       RET   kse_switchin JUSTRETURN
> ~  7877 ss       CALL  write(0x1,0x7fdffffdc68,0x1)
> ~  7877 ss       RET   write 1
> ~  7877 ss       CALL  write(0x1,0x7fdffffdc68,0x1)
> ~  7877 ss       RET   write 1
> ========================================================
>
> This is normal?
> writing one byte, but write(2) return 0x26a000.

It looks normal but it would be nice if "write 2531328/0x26a000"
were labeled "kse_create 0x26a000" or something more appropriate.

-- 
Dan Eischen