From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4A3010BE.9020107@domain.hid> Date: Wed, 10 Jun 2009 21:59:58 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <6a782b880906051338r401163b2m7e1d1a53f7f0800@domain.hid> <4A299794.6010504@domain.hid> <6a782b880906101236l625792d5p6fcd3dad53e965a2@domain.hid> In-Reply-To: <6a782b880906101236l625792d5p6fcd3dad53e965a2@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Get ready queue List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Thiago Lima Cc: xenomai@xenomai.org Thiago Lima wrote: > Sorry, i didnt understand you answer. The question was vague, so was the answer. > I get the global queue doing this: > > threads = &pod->threadq; // GLOBAL QUEUE > holder = getheadq(&nkpod->threadq); //HEAD NODE These are internal data, you are not supposed to access them that way. Besides threadq is not the ready queue. And with the recent advent of the scheduler classes, you could not do the same modification for the latest version of Xenomai. In short, it is a bad idea, really. If you explained us what you are trying to do (and not how you are trying to do it), maybe we could help. Chances are that you can do what you do without changing Xenomai core, simply using hooks for instance. -- Gilles.