From owner-freebsd-mips@FreeBSD.ORG  Tue Jan 26 02:20:27 2010
Return-Path: <owner-freebsd-mips@FreeBSD.ORG>
Delivered-To: freebsd-mips@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 041B9106566B;
	Tue, 26 Jan 2010 02:20:27 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mx1.freebsd.org (Postfix) with ESMTP id A324F8FC15;
	Tue, 26 Jan 2010 02:20:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o0Q2JAVk061311;
	Mon, 25 Jan 2010 19:19:11 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Mon, 25 Jan 2010 19:19:59 -0700 (MST)
Message-Id: <20100125.191959.956847443352467531.imp@bsdimp.com>
To: rrs@lakerest.net
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <74D48EE5-544E-44D4-9644-2349E9AA9796@lakerest.net>
References: <489828.45501.qm@web34403.mail.mud.yahoo.com>
	<74D48EE5-544E-44D4-9644-2349E9AA9796@lakerest.net>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: attilio@FreeBSD.org, freebsd-mips@FreeBSD.org
Subject: Re: AR71XX RTC
X-BeenThere: freebsd-mips@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to MIPS <freebsd-mips.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
	<mailto:freebsd-mips-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mips>
List-Post: <mailto:freebsd-mips@freebsd.org>
List-Help: <mailto:freebsd-mips-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
	<mailto:freebsd-mips-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2010 02:20:27 -0000

In message: <74D48EE5-544E-44D4-9644-2349E9AA9796@lakerest.net>
            Randall Stewart <rrs@lakerest.net> writes:
: Thanks that makes a LOT of sense.. So basically the
: mtx passed is NOT what is currently in td_lock and we
: want it updated as we switch.

Yes.

I think there still might be a bit of oddness here and there, since
the cavium port has a weird access to sysctl issue when a rm_lock is
involved.  I'm not at all sure why that would be...  It may be
scheduling related, but it may also just be some minor init the cavium
is doing that's just a bit off...

Warner