Re: Userland headers available

From: jw schultz (jw_at_pegasys.ws)
Date: 01/24/04

  • Next message: Mike Gabriel: "Re: vt6410 in kernel 2.6" 
    Date:	Fri, 23 Jan 2004 15:47:18 -0800
To: linux-kernel@vger.kernel.org

    On Fri, Jan 23, 2004 at 02:39:57PM -0500, Chris Friesen wrote:
    > Friesen, Christopher [CAR:7Q28:EXCH] wrote:
    >
    > >The obvious way is to have the kernel headers include the userland
    > >headers, then everything below that be wrapped in "#ifdef __KERNEL__".
    > >Userland then includes the normal kernel headers, but only gets the
    > >userland-safe ones.
    >
    > I just realized this wasn't clear. I envision a new set of headers in
    > the kernel that are clean to export to userland. The current headers
    > then include the appropriate userland-clean ones, and everything below
    > that is kernel only.
    >
    > This lets the kernel maintain the userland-clean headers explicitly, and
    > we don't have the work of cleaning them up for glibc.

    This gets discussed every few months. I think the most
    recent was in August.

    http://groups.google.com/groups?q=linux-kernel+include/abi&hl=en&lr=&ie=UTF-8&selm=lXHU.431.1%40gated-at.bofh.it&rnum=1

            (google linux-kernel include/abi) 

    -- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws
		Remember Cernan and Schmitt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Mike Gabriel: "Re: vt6410 in kernel 2.6"

    Relevant Pages

    • Re: [PATCH] remove net driver ugliness that sparse complains about
      ... and when it points to kernel space. ... userland ones. ... and userland pointers, and set_fsis not enough to handle that. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RFC] Splitting kernel headers and deprecating __KERNEL__
      ... > just make one thing clear: the kernel headers are for the kernel, ... userland must duplicate the contents of headers in which the kernel ... defines the kerneluserland ABI, tracking changes in them in the ...
      (Linux-Kernel)
    • Re: [RFC] Splitting kernel headers and deprecating __KERNEL__
      ... >> two parties on an ABI doesn't imply that one party gets to define it ... imposition, kernel developers won't care. ... because there's a contract with userland that they don't want to ... change in the copy/extract/whatever of kernel headers that userland is ...
      (Linux-Kernel)
    • Re: "Enhanced" MD code avaible for review
      ... be required to make this work correctly using a userland approach. ... > kernel, and having to try harder to crash the kernel. ... protected *sooner* if the system crashes. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RFC] Splitting kernel headers and deprecating __KERNEL__
      ... If I understand correctly the above means "include/* userland breakage ... Potential breakage is mostly a non issue - since vanilla kernel headers are ... layer that will look like the old tree but in fact use the new tree.* And ...
      (Linux-Kernel)