On 07/20/2011 11:55 AM, Jan Kiszka wrote:
On 2011-07-20 10:52, Avi Kivity wrote: > On 07/20/2011 11:43 AM, Jan Kiszka wrote: >>> >>> How do you implement this 3a, if your consumers are outside the main >>> process? I guess you could have an additional synchonize API (for >>> in-kernel consumers) or RPC (for external process consumers), but then >>> this is no longer a simple API. >> >> I'm not planning to leave the hypervisor process for now, not to speak >> of in-kernel models. Already for many other reasons, a synchronization >> API between a hypothetical decoupled device model and the core will be >> quite complex. The first step is to get it scalable using a single process. > > If we design a new kvm API, we must look a little more into the future > than satisfying immediate needs. That's true, but synchronization requirements are widely unrelated to this API and will have to by satisfied generically anyway.
I'm trying to see if they can be satisfied at all, for the more esoteric consumers, and if so, if it's in a palatable way and performant way.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
