> > > > Trusted code should only be allowed access to the feature, at the moment > > it is enforced by requiring the applications to have root permissions to > > open the character device driver. > > This is a serious problem. There is a reason why we normally do things > with system calls. Unless you can come up with a safe and reasonably clean > way for unprivileged applications to use your code, I don't see how you > expect it to get merged in the kernel.
Yeh, may be this won't be possible, but ya never know till you try. In any case, I've posted to this list because I thought being able to efficiently and symmetrically communicate between an guest thread and the host kernel might be of interest. What I was thinking was using kshmem and ACE it should be possible to implement a more efficient para-virtualize devices. So even though there is some loss separation between kernel it might be worth it in this case and possibly other cases as well. > > > Can't you put this into the vdso? Calling into the right place sounds > > > like a problem that is already solved. > > > > Possibly, but it isn't universally available, I hope to use this technique > > on other architectures. > > It should be possible to implement vdso on any architecture that is still > missing it. Not easy, but it's an established way of doing things and a lot > cleaner than making up your own linkage model. > I will take a look at vdso. Wink ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
