From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Userspace visible of 3 include/asm/ headers
Date: Thu, 3 Aug 2006 15:44:10 -0400 [thread overview]
Message-ID: <20060803194410.GC16927@redhat.com> (raw)
In-Reply-To: <20060803193952.GF25692@stusta.de>
On Thu, Aug 03, 2006 at 09:39:52PM +0200, Adrian Bunk wrote:
> Could anyone help me regarding the desired userspace visibility of the
> following three headers under include/asm/?
>
>
> Header : cpufeature.h
> Architectures : i386, x86_64
> Is there any reason why this header is exported to userspace?
Probably not. The only apps I've seen that care about feature bits
define them theirselves rather than use these.
> Header : setup.h
> Architectures : i386, ia64, x86_64
> Contents:
> - COMMAND_LINE_SIZE on ia64, x86_64
> - much more on i386
> Should COMMAND_LINE_SIZE be visible to userspace?
Bootloaders probably need to know this.
> Header : timex.h
> Architectures : all architectures
> Offers CLOCK_TICK_RATE on all architectures, but on some architectures
> (like i386) this depends on the kernel configuration.
> -> not a userspace header?
Also longer term, CLOCK_TICK_RATE will make no sense should we go
to a tickless kernel.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-03 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 19:39 Userspace visible of 3 include/asm/ headers Adrian Bunk
2006-08-03 19:44 ` Dave Jones [this message]
2006-08-03 20:14 ` Alexey Dobriyan
2006-08-03 20:17 ` Dave Jones
2006-08-03 21:28 ` H. Peter Anvin
2006-08-03 21:52 ` Adrian Bunk
2006-08-03 23:51 ` H. Peter Anvin
2006-08-04 0:12 ` Adrian Bunk
2006-08-04 0:59 ` H. Peter Anvin
2006-08-04 1:00 ` H. Peter Anvin
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=20060803194410.GC16927@redhat.com \
--to=davej@redhat.com \
--cc=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox