From: Grant Coady <grant_lkml@dodo.com.au>
To: "Daniel Rosenthal" <danielrosenthal@acm.org>
Cc: linux-kernel@vger.kernel.org, jdike@linux.com
Subject: Re: linux object file containing all kernel symbols and suitable for userspace linking?
Date: Sun, 28 Sep 2008 13:13:52 +1000 [thread overview]
Message-ID: <4httd4pt37d715nqfvge2fau7nahbq6u3a@4ax.com> (raw)
In-Reply-To: <4b6fba110809271957t78d7c0c6m97b2b6c1386f7700@mail.gmail.com>
On Sat, 27 Sep 2008 22:57:10 -0400, "Daniel Rosenthal" <danielrosenthal@acm.org> wrote:
>Is there an object file generated by the kernel build process just
>before vmlinuz and arch/x86/boot/bzImage are created that contains all
>the requisite kernel symbols to complete compilation? I understand
>that such an object file wouldn't make a lot of sense to keep around,
>because at the point at which such a file were able to be generated
>the compilation process could just be completed instead. If it's not
>available is there some easy way to generate it? I am trying to test
>some kernel code I wrote, and I wanted to test it by running it in
>userspace by linking it to a *.o file with a main() function (just to
>test out various API facilities; i.e. unit tests). This is so I can
>use the API provided by the kernel without having to rewrite it for
>userspace. User-Mode Linux won't work for this because the code in
>question relies on some architecture specific features and thread
>flags of x86, but I guess the approach would probably similar to what
>UML uses.
There's a vmlinux.o in top-level directory after a kernel compile, is
that what you're after?
Grant.
next prev parent reply other threads:[~2008-09-28 3:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 2:57 Daniel Rosenthal
2008-09-28 3:13 ` Grant Coady [this message]
2008-09-28 7:22 ` Daniel Rosenthal
2008-09-28 14:06 ` Jeff Dike
2008-09-29 6:18 ` Daniel Rosenthal
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=4httd4pt37d715nqfvge2fau7nahbq6u3a@4ax.com \
--to=grant_lkml@dodo.com.au \
--cc=danielrosenthal@acm.org \
--cc=gcoady.lk@gmail.com \
--cc=jdike@linux.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
all inboxes | Powered by JetHome®