Jeremy Fitzhardinge wrote:
I'm not keen on *requiring* patching to occur, in general. The
performance without patching is only a few percent worse than
native/patched, so its not like its a desperate problem to defer
implementing it. (I.e, requiring patching just raises the
implementation barrier for a pv_ops backend.)
Well, this approach could be used, but it is overloading a bit and does
make some extra burden on the backends. Can't argue that.
Overloading patching for dealing with module exports is interesting, but
well, I guess I don't see the problem in just exporting paravirt_ops.
The two arguments I've seen against it are "security" and "GPL issues",
but neither seems particularly good.
Yes, I agree on that. The other argument was "interface flux".
So, Rusty, back to splitting exports or just EXPORT_SYMBOL the thing?
Zach
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
