From: Zachary Amsden <zach@vmware.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: EXPORT_SYMBOL_GPL(paravirt_ops);
Date: Thu, 10 Aug 2006 13:23:59 -0700 [thread overview]
Message-ID: <44DB95DF.8010805@vmware.com> (raw)
In-Reply-To: <20060810194058.GK2654@sequoia.sous-sol.org>
Chris Wright wrote:
> * Zachary Amsden (zach@vmware.com) wrote:
>
>> EXPORT_SYMBOL_GPL is still possible - if you patch over every op in
>> paravirt_ops. Then only the paravirt modules need to be GPL, not all
>> modules.
>>
>
> Problem is the pervasive nature. So any old module that was doing
> local_irq_disable() will need access to the paravirt_ops structure via
>
> local_irq_disable() -> raw_local_irq_disable -> paravirt_ops.irq_disable()
>
> IOW, all modules need paravirt_ops access, otherwise non-GPL modules
> will fail to load with "Unknown symbol paravirt_ops." We can't make an
> interface change like that.
>
But my point is that if you patch everything in the paravirt_ops struct,
no module other than the paravirt_ops backend code needs paravirt_ops
access, so paravirt_ops can still be GPL only. The problem is you would
need to patch everything.
Zach
next prev parent reply other threads:[~2006-08-10 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 17:59 EXPORT_SYMBOL_GPL(paravirt_ops); Jeremy Fitzhardinge
2006-08-10 18:32 ` EXPORT_SYMBOL_GPL(paravirt_ops); Chris Wright
2006-08-10 19:11 ` EXPORT_SYMBOL_GPL(paravirt_ops); Zachary Amsden
2006-08-10 19:40 ` EXPORT_SYMBOL_GPL(paravirt_ops); Chris Wright
2006-08-10 20:23 ` Zachary Amsden [this message]
2006-08-10 20:44 ` EXPORT_SYMBOL_GPL(paravirt_ops); Jeremy Fitzhardinge
2006-08-10 20:55 ` EXPORT_SYMBOL_GPL(paravirt_ops); Chris Wright
2006-08-13 17:40 ` EXPORT_SYMBOL_GPL(paravirt_ops); Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44DB95DF.8010805@vmware.com \
--to=zach@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.