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 Fri, 2007-04-20 at 14:36 -0700, Zachary Amsden wrote:
> Jeremy Fitzhardinge wrote:
> > Zachary Amsden wrote:
> >   
> >> Yes, I don't know either - but we should be consistent about their
> >> export regardless of whether PAE is selected or not.  So we should
> >> either have 5 arg macros or not export set_pte_at* at all, even in 4
> >> arg version.
> >>     
> >
> > So can you separately control exportability independently from patchability?
> >   
> 
> Nope.  But I think we should maintain parity between PAE and non-PAE - 
> and probably also maintain parity between non-paravirt-ops and 
> paravirt-ops, which means the 5 arg macros are a good idea.  It's not 
> like they are very hard to create or maintain.

Less exports good.  Consistency with all config options isn't a hard
requirement: I'd be tempted not to export the pte functions.

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