All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jim Cromie <jim.cromie@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [PATCH] Check for NPTL and factor user-space skins initialization.
Date: Tue, 18 Apr 2006 17:46:57 +0200	[thread overview]
Message-ID: <444509F1.5090107@domain.hid> (raw)
In-Reply-To: <44450359.2090203@domain.hid>

Jim Cromie wrote:
> Gilles Chanteperdrix wrote:
> 
>> For review...
>>
>>  
>>
>> +#ifndef __KERNEL__
>> +#include <stdio.h>
>> +#include <stdlib.h>
>> +#include <string.h>
>> +#include <unistd.h>
>> +
>> +static inline void xeno_x86_features_check(void)
>> +{
>> +#ifdef CONFIG_XENO_X86_SEP
>> +  size_t n = confstr(_CS_GNU_LIBPTHREAD_VERSION, NULL, 0);
>> +  if (n > 0)
>> +      {
>>
>>   
> 
> since this is user code, its possible to read /proc/cpuinfo,
> and find the sep flag.
> 
> Is this worth doing also ?

Some deeply embedded stuff (something like buried in the silicon 
actually...) might configure out CONFIG_PROC_FS, so we can't rely on 
this pseudo-fs to be always present.

> if so, I can work a patch up later, unless you feel the urge.
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
> 


-- 

Philippe.


  reply	other threads:[~2006-04-18 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 14:39 [Xenomai-core] [PATCH] Check for NPTL and factor user-space skins initialization Gilles Chanteperdrix
2006-04-18 15:02 ` Philippe Gerum
2006-04-18 15:08   ` Gilles Chanteperdrix
2006-04-18 15:23     ` Philippe Gerum
2006-04-18 16:57       ` Gilles Chanteperdrix
2006-04-21  8:52         ` Philippe Gerum
2006-04-18 15:18 ` Jim Cromie
2006-04-18 15:46   ` Philippe Gerum [this message]
2006-04-18 17:04     ` Gilles Chanteperdrix
2006-04-18 17:44       ` Philippe Gerum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=444509F1.5090107@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jim.cromie@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.