From owner-freebsd-arm@FreeBSD.ORG Sun Aug 25 15:58:22 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E88DA62B for ; Sun, 25 Aug 2013 15:58:21 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B5E8424C3 for ; Sun, 25 Aug 2013 15:58:21 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id 10so3696121ied.0 for ; Sun, 25 Aug 2013 08:58:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=qZE3gLuV2ZtYaHZvYncgkHd+ysewpIMCR1Wy/kvAlDM=; b=fU3fFJ8hGoi52l0ujWy1FegUhZKvfR2O+5riff/WYrK4jL5pXlLCgxLcYD748qEkPw FLNu3AQx8qOZQ/yXcoyadYlbnJV7+G+2xcn65D86cHJmQKipHDhX65mz5ROxyBlESHgn N+YUg46/tMI6LmOa10IhtyLDWX6wWcw76ZDqq40Iy7M41eoagy4xieSKXEWzEngOPo5Z 6UpDJW8SaryjPl5E8MQnP+Aol4QGnX/0/YJkb/Mqxz/kgFdVQvIBbjqD0Vn8PjAqtBOB A+wk1gDBgfr/lm4hpyT1ZJ0KH0grZhikfXwFrRXt6uuvAKsV87E3lLhqdGEM9D2zwXt1 YU8g== X-Gm-Message-State: ALoCoQlxSLN8Pll5u4pjuKIJKdqVJcy3RUg9XLQIKmt1ZVlx64gMZXgHcfbT4G8eDWAwd55GSJfc X-Received: by 10.42.12.8 with SMTP id w8mr1467415icw.1.1377446295654; Sun, 25 Aug 2013 08:58:15 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id yt10sm11574010igb.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 25 Aug 2013 08:58:14 -0700 (PDT) Sender: Warner Losh Subject: Re: Pretty good RPi version? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sun, 25 Aug 2013 09:58:12 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <2DF35AA8-01C3-4F99-848A-34BD52EA5193@bsdimp.com> References: <5218FBE2.2000907@m5p.com> <20130825.195532.59669686.shigeru@os-hackers.jp> To: Tim Kientzle X-Mailer: Apple Mail (2.1085) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2013 15:58:22 -0000 On Aug 25, 2013, at 9:34 AM, Tim Kientzle wrote: >=20 > On Aug 25, 2013, at 5:07 AM, Adrian Chadd wrote: >=20 >> Hi! >>=20 >> All - if it's unstable, please complain loudly on -arm and -current = and >> file PRs. If you have the time, please help figure out which = commit(s) >> broke things. >>=20 >> There's been plenty of "stuff is unstable" talk, but I'm not sure = it's >> percolated its way up to the people doing VM hacking on other = platforms >> (notably amd64) so they are likely unaware they've broken things. >>=20 >> It's possible they've also broken things for MIPS, which has me = worried. :( >=20 > On a similar note: FreeBSD is starting the process for branching > and releasing FreeBSD 10.0. (The whole process will take a few > months, but it means we need to get bugs isolated and fixed NOW.) >=20 > I would *love* to have a solid, stable FreeBSD/ARM for 10.0. > (If nothing else, I started tinkering with BeagleBone in late 2011 > specifically so I could move my personal email server onto one. ;-) >=20 > To get there, we need as many people as possible: > * Running the bleeding edge FreeBSD. > * Reporting problems. > * Helping to diagnose those problems. >=20 > Q: Does anyone know a good way to test userland locking? >=20 > Diane Bruce has been continuing to dig into the issue that > broke sshd a while back; the clues point to some issue in > jemalloc (possibly locking related?). Once upon a time, back in the RAS/armv4 days, I found a bug. Locks were = getting stuck in threads in my employer's command and control program. = After much debugging, it came down to the atomic operations implemented = by RAS were less than atomic. There was a one or two instruction race in = them. Usually they'd work, and you needed a very high interrupt load, = like in my employer's hardware, to see the problem reliably. It would be = useful to eliminate this possibility, even though RAS is off the table = for armv6, this is really the first release with armv6 support and the = atomics haven't been through the torture test of that process yet. Warner > Q: Has anyone tried running some or all of the FreeBSD > regression tests? >=20 > Tim >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"