From: Takashi Iwai <tiwai@suse.de>
To: Zachary Amsden <zach@vmware.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Tobias Powalowski <t.powa@gmx.de>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/paravirt: revert exports to restore old behaviour
Date: Mon, 19 Nov 2007 18:05:16 +0100 [thread overview]
Message-ID: <s5hlk8ujhdf.wl%tiwai@suse.de> (raw)
In-Reply-To: <1195001464.6352.109.camel@bodhitayantram.eng.vmware.com>
At Tue, 13 Nov 2007 16:51:04 -0800,
Zachary Amsden wrote:
>
> On Tue, 2007-11-13 at 22:22 +0000, Christoph Hellwig wrote:
> > On Tue, Nov 13, 2007 at 12:21:16PM -0800, Jeremy Fitzhardinge wrote:
> > > Subject: x86/paravirt: revert exports to restore old behaviour
> > >
> > > Subdividing the paravirt_ops structure caused a regression in certain
> > > non-GPL modules which try to use mmu_ops and cpu_ops. This restores
> > > the old behaviour, and makes it consistent with the
> > > non-CONFIG_PARAVIRT case.
> >
> > NACK, both of these are internal and graphics drivers should not be
> > using them.
>
> Some of them are internal, but some are not, they just happened to be
> privileged CPU operations available to anyone.
>
> Does anyone know what hooks they are actually using? Something like
> reading MSRs is not internal at all, it is CPU specific, and the
> graphics drivers might have very good reasons to read them to figure out
> how AGP is configured for example.
>
> The graphics drivers most certainly don't need to be paravirtualized
> however, so they could always work around this with raw asm constructs.
>
> The mmu_ops hook is more debatable. But until someone figures out what
> hooks they want, we can't know whether they are internal or not. In any
> case, this is a regression.
I took at this problem (as I have an nvidia card on one of my
workstations), and found out that the following suffer from
EXPORT_SYMBOL_GPL changes:
* local_disable_irq(), local_irq_save*(), etc.
* MSR-related macros like rdmsr(), wrmsr(), read_cr0(), etc.
wbinvd(), too.
* pmd_val(), pgd_val(), etc are all involved with pv_mm_ops.
pmd_large() and pmd_bad() is also indirectly involved.
__flush_tlb() and friends suffer, too.
The easiest workaround I found was to undefine CONFIG_PARAVIRT before
inclusion of linux kernel headers, but it is really ugly and hacky.
Redefinig with raw_*() and native_*() is another way, but it takes
much more work than defining these primitive functions in assembly.
So, in short, with EXPORT_SYMBOL_GPL change, it's pretty hard to write
a non-GPL driver in a same manner...
Takashi
next prev parent reply other threads:[~2007-11-19 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 10:39 REGRESSION: 2.6.24 breaks nvidia and amd/ati binary drivers, by exporting paravirt symbols as GPL Tobias Powalowski
2007-11-13 20:21 ` [PATCH] x86/paravirt: revert exports to restore old behaviour Jeremy Fitzhardinge
2007-11-13 22:22 ` Christoph Hellwig
2007-11-14 0:51 ` Zachary Amsden
2007-11-19 17:05 ` Takashi Iwai [this message]
2007-11-20 1:14 ` Jeremy Fitzhardinge
2007-11-20 6:25 ` Takashi Iwai
2007-11-14 1:22 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2007-11-27 22:57 Jeremy Fitzhardinge
2007-11-28 20:40 ` Adrian Bunk
2007-11-28 21:15 ` Jeremy Fitzhardinge
2007-11-28 22:39 ` Adrian Bunk
2007-11-28 23:57 ` Jeremy Fitzhardinge
2007-11-29 22:06 ` Adrian Bunk
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=s5hlk8ujhdf.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=t.powa@gmx.de \
--cc=tglx@linutronix.de \
--cc=zach@vmware.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox