From owner-freebsd-mips@FreeBSD.ORG Thu May 26 19:47:04 2011 Return-Path: Delivered-To: mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EEEA106564A for ; Thu, 26 May 2011 19:47:04 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by mx1.freebsd.org (Postfix) with ESMTP id 981978FC18 for ; Thu, 26 May 2011 19:47:03 +0000 (UTC) Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTd6uNhJe3uan5V3zFhigFEhSiSLwymoq@postini.com; Thu, 26 May 2011 12:47:03 PDT Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 26 May 2011 12:44:16 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 26 May 2011 15:44:15 -0400 From: Andrew Duane To: "mips@freebsd.org" Date: Thu, 26 May 2011 15:44:14 -0400 Thread-Topic: More ramblings/work on Octeon Thread-Index: Acwb3UsT936muxajSYGWfuD6+bEg8w== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: More ramblings/work on Octeon X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 19:47:04 -0000 I've completed the first stage of my work on our Octeon blades, and have 2 = ramblings to ramble about before I send out some diffs. 1) I still constantly get the KASSERT panic "sched_priority: invalid priori= ty". I don't really know why this is a KASSERT, so I just changed it to bou= nd the computed priority at PRI_MIN_BATCH and PRI_MAX_BATCH (it was always = going over the MAX). Nothing has caught fire yet after 24 hours (as opposed= to <5 minutes to KASSERT). This isn't really a MIPS issue, but has anyone = seen it, or know why this is a KASSERT and not just a limit check? 2) I also have to work around a panic in pmap_pte that was trying to refere= nce something at 0x9800000010100800. This is in the PCPU area, but I think = it's out of range and causes a bus error. Only bringing up one CPU makes th= e system stable. On to the work I've finished: I've completed support for using either the octeon_bootinfo structure curre= ntly used by the octeon port, or the generic MIPS bootinfo structure from b= ootinfo.h (which our bootstraps use). The entire boot path is now completel= y agnostic, and has a switch point to determine the boot interface by looki= ng at the magic numbers in the a0-a3 registers passed in at start and calli= ng the appropriate init routine. Right now, octeon_bootinfo and bootinfo ar= e the only two options, but there's an architecture in place to add more as= needed. This also includes a more open architecture to add new platforms. The bootinfo structure now has an optional platform extension structure tha= t can be defined in a platform-specific file along with defining BOOTINFO_P= EXT. That triggers the main bootinfo.h to add the field to the main structu= re. This seems a better way to manage additions, and I am going to move our= in-house code to use it. All traces of octeon_bootinfo are now gone from outside octeon_machdep.c (i= t is made static to insure it doesn't creep out again). Everything needed i= s copied into the cvmx_sysinfo structure (available through cvmx_sysinfo_ge= t() in the Octeon SDK), or read directly from the hardware as needed. Some = of the fields are really just hardware registers, and it's actually faster = to read from them than reference a structure member. There are some things = not included in cvmx_sysinfo_minimal_initialize from the SDK, I just added = the other fields we need directly. Maybe someone has a better idea. There is some other cleanup work such as platform_start_ap now checks to se= e if cores are still in reset and releases them first. Some bootstraps do n= ot start all cores before calling the kernel. -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 =20 From owner-freebsd-mips@FreeBSD.ORG Fri May 27 08:34:16 2011 Return-Path: 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 6D455106564A for ; Fri, 27 May 2011 08:34:16 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id 3EADD8FC1A for ; Fri, 27 May 2011 08:34:15 +0000 (UTC) Received: by pxi11 with SMTP id 11so981040pxi.7 for ; Fri, 27 May 2011 01:34:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=y9pIXXAvT2ptZg5Vdfo98iJL4CTxOZ9vm+4ihFKsWuo=; b=QQJA3dpLjC6oDzYcM3EsR2y7oT/grbxQK+S/mFwUbQ8JhveiNVLOTewr+sPMu1GJNZ L1QntZjfPTbySuisV0z72K0qt88ipHzeBPLmRABWhL4L4tVd8P72yW9bY1A3WZyKWcUd HtJn9OU6OfBD3wtBQsD/hJ66TINpLbHiDV6Yw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=AoH3wIBvrX9CI4IagUpI5WYU3LyU53YmlynEVi0l/J1umjBekdiOoCruMbF689Jq2x /GVPRkBY5683UrDYhEnpnVKcHiSVEbqsEJNShp41e04toMic4htwrN3LjlWdk9yJPjRk H4yeUKdtqFJJy0KGVkud1b/dc+f49s7mA+2v0= MIME-Version: 1.0 Received: by 10.142.250.25 with SMTP id x25mr292798wfh.195.1306485255679; Fri, 27 May 2011 01:34:15 -0700 (PDT) Received: by 10.142.231.16 with HTTP; Fri, 27 May 2011 01:34:15 -0700 (PDT) In-Reply-To: References: <4DD31231.5010000@freebsd.org> <4DD41715.2050203@freebsd.org> Date: Fri, 27 May 2011 14:04:15 +0530 Message-ID: From: "Jayachandran C." To: "freebsd-mips@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Trouble with dynamic executables X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 08:34:16 -0000 On Sat, May 21, 2011 at 12:37 AM, Jayachandran C. wrote: > On Sat, May 21, 2011 at 12:30 AM, Andrew Duane wrote: >> By the way, this did fix my issue. The MIPS toolchain guy here thinks that it might really just be spackling over the real problem though. I can't really say. >> > > I wonder why I don't see this on XLR, can you post your buildworld env > and command line? Apparently I have been living in the past. Looks like the the binutils update(r218822) caused this breakage. JC. From owner-freebsd-mips@FreeBSD.ORG Fri May 27 12:46:50 2011 Return-Path: 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 3F7221065677 for ; Fri, 27 May 2011 12:46:50 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by mx1.freebsd.org (Postfix) with ESMTP id D45108FC1D for ; Fri, 27 May 2011 12:46:48 +0000 (UTC) Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKTd+dN1qWKl5vWr5+NszPh0EZXvzu+AU1@postini.com; Fri, 27 May 2011 05:46:49 PDT Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 27 May 2011 05:45:10 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 27 May 2011 08:45:09 -0400 From: Andrew Duane To: Jayachandran C. , "freebsd-mips@freebsd.org" Date: Fri, 27 May 2011 08:45:06 -0400 Thread-Topic: Trouble with dynamic executables Thread-Index: AcwcSQBr7LSsMI++SDqEzwGMd5OxiQAIsxRg Message-ID: References: <4DD31231.5010000@freebsd.org> <4DD41715.2050203@freebsd.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: Trouble with dynamic executables X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 12:46:50 -0000 Is there a plan to fix? Oleksander provided me a patch which does seem to w= ork, but our local toolchain guy thinks the patch pretty much just spackles= over the real problem, rather than fixing it. It's nice to have a root cau= se. =A0................................... Andrew Duane Juniper Networks o=A0=A0=A0+1 978 589 0551 m=A0 +1 603-770-7088 aduane@juniper.net =A0 -----Original Message----- From: owner-freebsd-mips@freebsd.org [mailto:owner-freebsd-mips@freebsd.org= ] On Behalf Of Jayachandran C. Sent: Friday, May 27, 2011 4:34 AM To: freebsd-mips@freebsd.org Subject: Re: Trouble with dynamic executables On Sat, May 21, 2011 at 12:37 AM, Jayachandran C. wrote: > On Sat, May 21, 2011 at 12:30 AM, Andrew Duane wrote= : >> By the way, this did fix my issue. The MIPS toolchain guy here thinks th= at it might really just be spackling over the real problem though. I can't = really say. >> > > I wonder why I don't see this on XLR, can you post your buildworld env > and command line? Apparently I have been living in the past. Looks like the the binutils update(r218822) caused this breakage. JC. _______________________________________________ freebsd-mips@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-mips To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org"