mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: James Forcier <csssuf@csssuf.net>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>, Jan Beulich <JBeulich@suse.com>,
	X86 ML <x86@kernel.org>,
	"Juergen Gross <jgross@suse.com, Toshi Kani" <toshi.kani@hp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/mm: Export cpu_tlbstate as non-GPL symbol
Date: Sun, 27 Sep 2015 12:46:28 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1509271244140.4500@nanos> (raw)
In-Reply-To: <CALCETrVJbkAZr+TzmHnubnf+kGV=+Z5fezZTswNMZzHs_yf+Gg@mail.gmail.com>

On Thu, 24 Sep 2015, Andy Lutomirski wrote:
> On Sep 22, 2015 11:58 AM, "Thomas Gleixner" <tglx@linutronix.de> wrote:
> >
> > On Tue, 22 Sep 2015, Andy Lutomirski wrote:
> > > On Tue, Sep 22, 2015 at 11:51 AM, James Forcier <csssuf@csssuf.net> wrote:
> > > > Exporting cpu_tlbstate as a GPL symbol was introduced in 1e02ce4c; however, this
> > > > breaks non-GPL modules which need to link against it, particularly the AMD
> > > > Catalyst drivers.
> > >
> > > What is AMD Catalyst doing with cpu_tlbstate?
> >
> > Fiddling with it behind the kernels back. Out of tree graphic drivers
> > always have their special needs. Just lookup the discussions about
> > unexporting init_mm ....
> 
> Look for kcl_mem_pat_setup here:
> 
> https://github.com/kolasa/fglrx-13.152/blob/master/firegl_public.c

I stopped looking at this line:

MODULE_LICENSE("GPL\0Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY");
 
Thanks,

	tglx

  reply	other threads:[~2015-09-27 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1442947897-14487-1-git-send-email-csssuf@csssuf.net>
2015-09-22 18:53 ` Andy Lutomirski
2015-09-22 18:57   ` Thomas Gleixner
2015-09-24 19:03     ` Andy Lutomirski
2015-09-27 10:46       ` Thomas Gleixner [this message]
2015-09-27 11:28         ` Borislav Petkov
2015-09-27 11:16           ` Richard Weinberger

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=alpine.DEB.2.11.1509271244140.4500@nanos \
    --to=tglx@linutronix.de \
    --cc=JBeulich@suse.com \
    --cc=csssuf@csssuf.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mcgrof@suse.com \
    --cc=mingo@redhat.com \
    --cc=toshi.kani@hp.com \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®