LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "vignesh babu bm" <vigneshbabu@gmail.com>
To: "rohit h" <hrohit85@gmail.com>
Cc: "Jan Engelhardt" <jengelh@computergmbh.de>,
"Joonwoo Park" <joonwpark81@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [LINUX-KERNEL] C++ in linux kernel
Date: Mon, 11 Feb 2008 17:19:34 +0530 [thread overview]
Message-ID: <3d1754a30802110349n684ed0b5ja47f12213e65c2ff@mail.gmail.com> (raw)
In-Reply-To: <90d987c0802110337i42082a7ew905a096028fe347b@mail.gmail.com>
http://www.vmware.com/download/server/open_source.html
On Feb 11, 2008 5:07 PM, rohit h <hrohit85@gmail.com> wrote:
>
> On Feb 8, 2008 9:24 PM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> >
> > On Feb 9 2008 00:14, Joonwoo Park wrote:
> > >2008/2/8, rohit h <hrohit85@gmail.com>:
> > >> Hi,
> > >> I am a kernel newbie.
> > >> I tried to insmod a C++ module containing classes, inheritance.
> > >> I am getting 'unresolved symbol' error when I use the 'new' keyword.
> > >> What could the problem be?
> > >>
> > >> What kind of runtime support is needed ( arm linux kernel)? Is a
> > >> patch available for it?
> > >>
> > >Please take a look at click modular router which is using c++ as a
> > >linux kernel module.
> > >http://www.read.cs.ucla.edu/click/
> > >The lib/glue.cc provides custom operator new.
> >
> > Uh, let's not make the world worse :)
> > Just call malloc from C++, and carefully select what C++ features
> > you are going to use. The VMware source for example does it right.
> >
>
> From the links given, I dig that following C++ features need runtime support:
> a. Pure virtual functions
> b. Global objects : Needs compiler dependent changes
> c. new & delete : Can use kmalloc / kfree instead
> d. Run time type info
> e. Exceptions
> I guess features d & e need considerable effort.
> Apart from these, am I free to use other C++ features?
> Where could I see the VMWare sources?
>
>
>
> > Compiling the kernel module with g++ is not a simple work, you may
> > need big patch for kernel itself.
>
> I don't want to compile entire kernel.
> I only want to compile my module with g++ and insmod it.
> Any hint on how to write the Makefile.
>
> Thanks in advance,
> Rohit
>
>
>
> --
> 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/
>
--
----------------------------------------------
"Why is it that every time I'm with you, makes me believe in magic?"
next prev parent reply other threads:[~2008-02-11 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 5:21 rohit h
2008-02-08 5:28 ` KOSAKI Motohiro
2008-02-08 10:17 ` [LINUX-KERNEL] " Bernd Petrovitsch
2008-02-08 13:39 ` Andi Kleen
2008-02-08 15:14 ` [LINUX-KERNEL] " Joonwoo Park
2008-02-08 15:54 ` Jan Engelhardt
2008-02-09 0:45 ` Joonwoo Park
2008-02-11 11:37 ` rohit h
2008-02-11 11:49 ` vignesh babu bm [this message]
2008-02-11 12:20 ` Bernd Petrovitsch
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=3d1754a30802110349n684ed0b5ja47f12213e65c2ff@mail.gmail.com \
--to=vigneshbabu@gmail.com \
--cc=hrohit85@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=joonwpark81@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [LINUX-KERNEL] C++ in linux kernel' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).