Chris Wright wrote:
> this is the only things left on the todo i made today.
>
> Xen config
> PREEMPT?
>
Remove. Should work; any problems are bugs.
> Consistently wrap paravirt ops callsites
> "ugh" - mingo
Had a thought. What if we do a kind of reverse/two-way module linkage?
Somehow compile each pv-op implementation like a module, and then link
the appropriate one in at boot time.
Tricky parts: it would need two-way unresolved references between kernel
and module, and it would need to be able to run very early in the
kernel's life. It would also limit us to plain old calls rather than
any inlining (though that could be done separately).
On the upside, it removes pv_ops, and it might simplify the question of
how normal module exports work, since by that time they would just be
normal kernel functions. All the calls would be normal direct calls
rather than indirect. And it would allow us to free the memory for the
unused pv-ops backends.
Plausible?
J
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
