From: Dave Jones <davej@redhat.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
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 16:17:17 -0400 [thread overview]
Message-ID: <20060803201717.GG16927@redhat.com> (raw)
In-Reply-To: <20060803201402.GA6828@martell.zuzino.mipt.ru>
On Fri, Aug 04, 2006 at 12:14:02AM +0400, Alexey Dobriyan wrote:
> On Thu, Aug 03, 2006 at 03:44:10PM -0400, Dave Jones wrote:
> > 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.
>
> Feature bits are only (indirectly) visible via /proc/cpuinfo.
> struct cpuinfo_x86, AFAICS, is never copied to userspace. So, it's safe
> to remove this header.
Most of the bits (all but the linux specific ones), are the same bits you
can get from /dev/cpu/0/cpuid, or from calling the cpuid instruction by hand.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-03 20:18 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
2006-08-03 20:14 ` Alexey Dobriyan
2006-08-03 20:17 ` Dave Jones [this message]
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=20060803201717.GG16927@redhat.com \
--to=davej@redhat.com \
--cc=adobriyan@gmail.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 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.