From: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] user-cr: Extract headers from kernel source tree.
Date: Sat, 03 Oct 2009 16:40:41 -0500 [thread overview]
Message-ID: <1254606041.2928.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1254554424-2979-2-git-send-email-matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Sat, 2009-10-03 at 00:20 -0700, Matt Helsley wrote:
> Sanitize kernel headers for userspace by extracting non-__KERNEL__
> portions of the various checkpoint headers and placing them in a
> similar organization of userspace headers.
>
> The script is run from the top level of the user-cr source tree like:
>
> ./scripts/extract-headers.sh -s <path-to-kern-source> -o ./include
>
> The patch includes a copy of the auto-generated headers and adjusts
> the user-cr programs to use them.
I appreciate the effort put into this, but why isn't the
"headers_install" target of the kernel Makefile sufficient to produce
headers that are usable by userspace? So far as I know, other projects
with complex kernel/user interfaces (e.g. kvm) haven't had to resort to
special-purpose programs like this.
next prev parent reply other threads:[~2009-10-03 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 7:20 [PATCH] user-cr: Extract headers from kernel source tree Matt Helsley
[not found] ` <1254554424-2979-2-git-send-email-matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-03 7:26 ` Matt Helsley
2009-10-03 21:40 ` Nathan Lynch [this message]
[not found] ` <1254606041.2928.3.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-10-05 18:00 ` Matt Helsley
[not found] ` <20091005180000.GD18101-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2009-10-06 2:25 ` Serge E. Hallyn
2009-10-23 18:38 ` Oren Laadan
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=1254606041.2928.3.camel@localhost.localdomain \
--to=ntl-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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