* Anthony Liguori (anth...@codemonkey.ws) wrote: > The ioctl() interface is quite bad for what you're doing. You're > telling the kernel extra information about a VA range in userspace. > That's what madvise is for. You're tweaking simple read/write values of > kernel infrastructure. That's what sysfs is for.
I agree re: sysfs (brought it up myself before). As far as madvise vs. ioctl, the one thing that comes from the ioctl is fops->release to automagically unregister memory on exit. This needs to be handled anyway if some -p pid is added to add a process after it's running, so less weight there. thanks, -chris -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
