From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9980 invoked by alias); 27 Feb 2014 05:06:28 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 9966 invoked by uid 89); 27 Feb 2014 05:06:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: p02c12o142.mxlogic.net Received: from p02c12o142.mxlogic.net (HELO p02c12o142.mxlogic.net) (208.65.145.75) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Thu, 27 Feb 2014 05:06:26 +0000 Received: from unknown [12.218.215.72] (EHLO smtpauth1.linear.com) by p02c12o142.mxlogic.net(mxl_mta-7.2.4-1) with ESMTP id 0d7ce035.0.1191.00-382.2518.p02c12o142.mxlogic.net (envelope-from ); Wed, 26 Feb 2014 22:06:25 -0700 (MST) X-MXL-Hash: 530ec7d163894e33-f84ff83ae579c848fed9310212397afba6dd3e80 Received: from [192.168.0.225] (174-24-4-43.clsp.qwest.net [174.24.4.43]) by smtpauth1.linear.com (Postfix) with ESMTPSA id 4AABA740AE for ; Wed, 26 Feb 2014 21:06:23 -0800 (PST) From: Michael Jones Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Date: Thu, 27 Feb 2014 05:06:00 -0000 To: ecos discuss Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-AnalysisOut: [v=2.0 cv=HrXB7TvS c=1 sm=1 a=glloKNylpeYNumXQcclYyA==:17 a] X-AnalysisOut: [=D2_GN2MmYMYA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=MqD] X-AnalysisOut: [INYqSAAAA:8 a=EsWRVXCyW3gA:10 a=HPbQ2Tw2sgZHJWVxS1IA:9 a=C] X-AnalysisOut: [juIK1q_8ugA:10] X-Spam: [F=0.5000000000; CM=0.500; MH=0.500(2014022625); S=0.200(2010122901)] X-MAIL-FROM: X-IsSubscribed: yes Subject: [ECOS] Scheduler startup question X-SW-Source: 2014-02/txt/msg00003.txt.bz2 I have a question about proper scheduler locking startup behavior. The context is I am cleaning up my iMX6 HAL and attempting to make things w= ork without a couple of kernel hacks I added to make it work. The question has to do with sched_lock. By default this has a value of 1, s= o during startup the scheduler is locked. When there is an interrupt, sched_lock is incremented in Vectors.S, and dec= remented in interrupt_end. However, I am getting an assert in sync.h which is part of the BSD stack. T= he assert is because it expects the lock to be zero. The question is, during the startup process, how does the lock get set to z= ero after initialization? Is it supposed to stay 1 while hardware is initia= lized and through all the constructors, etc? Is it cleared by the scheduler= somehow? Is the HAL supposed to zero it at some point during startup? My HAL is part of the ARM hal, so if this is device specific, it is the ARM= HAL I am working with. Mike -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss