Jeremy Fitzhardinge wrote:
>> It also has one
>> negative side-effect, which is promoting external module code that links
>> with the kernel. IOW, there's much less incentive to get code merged
>> if it's just a matter of linking.
>>
>
> It wouldn't be something we'd promote by making it easy to bind
> out-of-tree code to the interface. And it would still be a
> kernel-version-specific ABI; no guarantees of stability.
BTW, my intention is definitely that all the pv-ops implementations are
linked into the kernel at build time; its just the binding references
get updated at boot time, and the unused code pages can be recycled.
But they're all part of the same kernel image.
J
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
