Date: Fri, 24 Sep 2004 21:20:21 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: execute a user process in the kernel Message-ID: <xzpacvfwk22.fsf@dwp.des.no> In-Reply-To: <Pine.NEB.3.96L.1040924140940.82478L-100000@fledge.watson.org> (Robert Watson's message of "Fri, 24 Sep 2004 14:11:19 -0400 (EDT)") References: <Pine.NEB.3.96L.1040924140940.82478L-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson <rwatson@freebsd.org> writes:
> Well, we have kproc/kthread APIs, but none of that is semantically
> compatible with the notion of execve(), which is a very user-centric
> concept ("replace the address space with a mapping of binary <x>"). You
> could fudge together a related notion, though, involving loadable kernel
> modules that have a main() routine run from a thread. That said, the
> notion of simply running user code in kernel (as has been pointed out) is
> fraught with peril, primarily because the kernel is basically one big
> program with many special requirements, and user applications are written
> with the assumption that they are the only program, not running in the
> context of another program.
I believe the OP actually wanted the kernel to spawn a userland
process, but I may have misunderstood.
DES
--=20
Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpacvfwk22.fsf>