[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] passing hypercall parameters by pointer
> The current mlock() scheme in libxc is screwed anyway -- we > mlock/munlock regions that may overlap at page granularity. > Fixing this would lead naturally to a preallocation scheme. That's a very good point. For the moment, we should remove all the munlock() calls for safety. The amount of unnecessary memory we'll end up pinning will be tiny, so we shouldn't worry about it. Post 3.0 we can completely redo the dom0 op interface, but the rest of the hypercall interface will have to remain backward compatible, at least for x86_*. Since passing by VA is so convenient on the architectures that support it we may not want to do anything different on these anyhow. For VT paravirt drivers I think pre-registration will work fine. The set of hypercalls we need to support is small anyhow. Ian _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |