Re: [RFC, PATCH 0/5] Paravirt: fix export of paravirt-ops to binary modules

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

 



On Mon, 2007-04-23 at 01:49 +0200, Andi Kleen wrote:
> > Less exports good.  Consistency with all config options isn't a hard
> > requirement: I'd be tempted not to export the pte functions.
> 
> Yes paravirt_ops should be probably split into two for internal and external
> available functions. Any takers? 

Hi Andi!

	I'm a little uncomfortable with cutting the struct this way: I always
thought it'd be a function split if we did one.

	With the new patch code we could simply shuffle all the exportables to
the front and fail to patch calls past this point (then fail the module
load).

I'll see what I can come up with...
Rusty.


_______________________________________________
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