From owner-freebsd-sparc64@FreeBSD.ORG  Thu May 20 12:38:51 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 689AF16A4D0
	for <sparc64@freebsd.org>; Thu, 20 May 2004 12:38:51 -0700 (PDT)
Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.246])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4C02C43D41
	for <sparc64@freebsd.org>; Thu, 20 May 2004 12:38:51 -0700 (PDT)
	(envelope-from drosihn@gmail.com)
Received: by mproxy.gmail.com with SMTP id u33so56191cwc
        for <sparc64@freebsd.org>; Thu, 20 May 2004 12:38:45 -0700 (PDT)
Received: by 10.11.98.15 with SMTP id v15mr144092cwb;
        Thu, 20 May 2004 12:38:45 -0700 (PDT)
Message-ID: <97880ae040520123841ba954e@mail.gmail.com>
Date: Thu, 20 May 2004 15:38:45 -0400
From: Garance Drosehn <drosihn@gmail.com>
To: Thomas Moestl <t.moestl@tu-bs.de>
In-Reply-To: <20040520122411.GA795@timesink.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <20040510010301.GA6829@timesink.dyndns.org>
	<20040520122411.GA795@timesink.dyndns.org>
cc: sparc64@freebsd.org
cc: Julian Elischer <julian@elischer.org>
cc: FreeBSD current users <current@freebsd.org>
Subject: Re: sparc64 kernel code question..
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2004 19:38:51 -0000

On Thu, 20 May 2004 14:24:11 +0200, Thomas Moestl <t.moestl@tu-bs.de> wrote:
> 
> On Tue, 2004/05/18 at 12:57:34 -0700, Julian Elischer wrote:
>   > to answer question 2...
>   > nothing.. in my sources I renamed it to cpu_exit2()
> 
> The name probably derives from the fact that it needs to be called
> after the sched lock is obtained, as was mentioned in the commit
> message.

Maybe call it:  cpu_exit_postsched()
:-)