On Mon, 2007-08-27 at 19:47 +0300, Avi Kivity wrote: > Avi Kivity wrote: > > > > Thinking a little more about this, it isn't about handling hypercalls > > in userspace, but about handling a virtio sync() in userspace. > > > > So how about having a KVM_HC_WAKE_CHANNEL hypercall (similar to Xen's > > event channel, but assymetric) that has a channel parameter. The > > kernel handler for that hypercall dispatches calls to either a kernel > > handler or a userspace handler. That means we don't need a separate > > ETH_SEND, ETH_RECEIVE, or BLOCK_SEND hypercalls. > > And thinking a tiny little bit more about this, we can have the kernel > (optionally) fire an eventfd, so a separate userspace thread or process > can be woken up to service the device, without a heavyweight exit.
Yes, I think this is much nicer. By "calls to ... a userspace handler" I presume you mean generating an exit to userspace with a new exit type similar to how hypercalls work today? Regards, Anthony Liguori ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
