On Mon, Jan 5, 2015 at 8:05 PM, Antti Kantee <[email protected]> wrote: > Hi, > > The attached patch makes sysproxy a separate component instead of it always > being embedded in librump. Two issues are addressed: > > 1) librumpuser no longer needs to provide stubs for the sysproxy hypercalls > in case sysproxy is never used on said platform > 2) it becomes easy to ensure that remote system calls are not possible in a > given configuration > > Old binaries using sysproxy will now fail to link due to a missing > rump_init_server(). This is by design so that you get an explicit > compile-time failure instead of a "huh it just stopped working" runtime > failure. There are just a handful of cases on repo.rumpkernel.org, I'll fix > them: > http://nxr.netbsd.org/search?q=&project=src-rumpkernel&defs=&refs=rump_init_server&path=&hist= > > Part two of the patch will move the sysproxy hypercalls from the rumpuser > interface to the sysproxy component (*), but that's not done yet, and won't > cause a flag day like the proposed change. > > thoughts?
Seems good to me. Have several use cases where remote calls are not appropriate/not implemented yet. Justin ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
