public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Splitting out kernel<=>userspace ABI headers
Date: Sat, 3 Sep 2005 00:41:24 -0600	[thread overview]
Message-ID: <20050903064124.GA31400@codepoet.org> (raw)
In-Reply-To: <43193A4F.5030906@zytor.com>

On Fri Sep 02, 2005 at 10:53:19PM -0700, H. Peter Anvin wrote:
> Erik Andersen wrote:
> >On Fri Sep 02, 2005 at 10:22:20PM -0700, H. Peter Anvin wrote:
> >
> >>Exportable types need to be double-underscore types, because the header 
> >>files in user space that would include them can generally not include 
> >><stdint.h>.
> >
> >
> >I'm not talking about kernel headers that have to worry about
> >eventually being included in user space headers.  Those nearly
> >all live in include/asm.  I'm talking about the kernel headers
> >that define how userspace is supposed to interface with
> >particular kernel drivers or hardware.  Headers such as
> >linux/cdrom.h and linux/loop.h and linux/fb.h.
> >
> 
> What are you going to do with them if you're not going to include them 
> in userspace?!!!
> 
> If you're proposing one policy for linux/loop.h and one for sys/stat.h, 
> I would have to classify that as insane.  Everything that gets exported 
> to userspace should behave the same way, please.

That is certainly not what I was proposing.  Why are you bringing
sys/stat.h into this?  The contents of sys/stat.h are entirely up
to SUSv3 and the C library to worry about.  Nobody has proposed
mucking with that.  I dunno about your C library, but mine
doesn't include linux/* header files (not even sys/stat.h).  And
I'd really like to fix uClibc to not use any asm/* either, since
much of it is entirely unsuitable for user space.

I am proposing a single consistant policy for all of linux/* such
that all linux/* headers that need integer types of a specific
size shall #include unistd.h and use ISO C99 types rather that
the ad-hoc kernel types they now use.

The policy has _long_ been that user space must never include
linux/* header files.  Since we are now proposing a project to
reverse this policy, the long standing policy making linux/*
verboten now leaves us completely free to do pretty much anything
with linux/*.  And what I want is for linux/* to use the shiny
ISO C99 types.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  reply	other threads:[~2005-09-03  6:41 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02  3:00 [RFC] Splitting out kernel<=>userspace ABI headers Kyle Moffett
2005-09-02 13:41 ` Erik Andersen
2005-09-02 20:51   ` Kyle Moffett
2005-09-02 23:58     ` Erik Andersen
2005-09-03  0:07       ` H. Peter Anvin
2005-09-03  0:30         ` Kyle Moffett
2005-09-03  0:34           ` H. Peter Anvin
2005-09-03  0:50             ` Kyle Moffett
2005-09-03  4:28         ` Erik Andersen
2005-09-03  5:22           ` H. Peter Anvin
2005-09-03  5:50             ` Erik Andersen
2005-09-03  5:53               ` H. Peter Anvin
2005-09-03  6:41                 ` Erik Andersen [this message]
2005-09-03 15:01                   ` H. Peter Anvin
2005-09-03 15:19                   ` H. Peter Anvin
2005-09-03 16:55                     ` Kyle Moffett
2005-09-05 16:35                       ` H. Peter Anvin
2005-09-05 23:28                         ` Kyle Moffett
2005-09-06  1:29                           ` [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS) Kyle Moffett
2005-09-10  8:40                             ` Kyle Moffett
2005-09-10  8:45                               ` Andrew Morton
2005-09-10 17:38                                 ` Kyle Moffett
2005-09-10 22:04                                   ` Andrew Morton
2005-09-11  0:33                                     ` Kyle Moffett
2005-09-11  0:48                                       ` Andrew Morton
2005-09-11  3:15                                         ` Kyle Moffett
2005-09-12  8:09                                           ` Paul Jackson
2005-09-12 15:19                                             ` H. Peter Anvin
2005-09-12 15:47                                               ` Paul Jackson
2005-09-12 17:17                                                 ` Sam Ravnborg
2005-09-12 21:14                                                   ` Paul Jackson
2005-09-12 21:39                                                     ` Kyle Moffett
2005-09-12 17:18                                                 ` H. Peter Anvin
2005-09-12 17:51                                                 ` Kyle Moffett
2005-09-12 21:04                                                   ` Paul Jackson
2005-09-14 13:56                                                   ` Bill Davidsen
2005-09-15 21:53                                           ` Jeremy Fitzhardinge
2005-09-03  5:55           ` [RFC] Splitting out kernel<=>userspace ABI headers Kyle Moffett
2005-09-03  5:57             ` H. Peter Anvin
2005-09-03  6:05               ` Kyle Moffett
2005-09-03 15:36             ` Denis Vlasenko
2005-09-03 16:33               ` Kyle Moffett
2005-09-03 16:51                 ` Denis Vlasenko
2005-09-14 13:46         ` Bill Davidsen
2005-09-14 17:01           ` Sam Ravnborg
2005-09-14 17:01             ` H. Peter Anvin
2005-09-14 18:14           ` Kyle Moffett
2005-09-14 19:09             ` linux-os (Dick Johnson)
2005-09-14 19:20               ` H. Peter Anvin
2005-09-14 19:46               ` Kyle Moffett
2005-09-02 21:42 ` Jeff Dike
2005-09-02 21:55   ` H. Peter Anvin
2005-09-02 22:44     ` Kyle Moffett
2005-09-02 23:24       ` H. Peter Anvin
2005-09-02 23:41         ` Kyle Moffett
2005-09-02 23:53           ` 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=20050903064124.GA31400@codepoet.org \
    --to=andersen@codepoet.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