Re: [RFC, PATCH 4/5] Paravirt_ops drop internal patches.patch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
Some of these boot hooks do not need to be patched, in fact, it is better not
to patch them at all and thus keep them totally private.

I think I generally backed off on patching init functions and the like. Are these really the only ones which need adjustment? I bet things like
the descriptor functions could be indirect/private with very little impact.

Perhaps, but I'd rather not split hairs on it just yet - I actually have no idea exactly which paravirt-ops will be needed, and so far, my conclusions have led me to believe that a fare bit more than the obvious paravirt-ops need to be available to modules. So I would rather just split off pure init functions, which really have no business being exported to modules.

Zach
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization

[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux