Date: Mon, 25 Jan 2010 19:42:07 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: rrs@lakerest.net Cc: attilio@FreeBSD.org, freebsd-mips@FreeBSD.org Subject: Re: AR71XX RTC Message-ID: <20100125.194207.1000278277145525469.imp@bsdimp.com> In-Reply-To: <20100125.191959.956847443352467531.imp@bsdimp.com> References: <489828.45501.qm@web34403.mail.mud.yahoo.com> <74D48EE5-544E-44D4-9644-2349E9AA9796@lakerest.net> <20100125.191959.956847443352467531.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20100125.191959.956847443352467531.imp@bsdimp.com>
"M. Warner Losh" <imp@bsdimp.com> writes:
: 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...
Looks like the oddness was due to problems in octeon init code...
We're past that now...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100125.194207.1000278277145525469.imp>