From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: question on symbol exports
Date: Sat, 05 Feb 2005 20:19:08 +1100 [thread overview]
Message-ID: <1107595148.30302.5.camel@gaston> (raw)
In-Reply-To: <4203D793.1040604@nortel.com>
> It turns out that to call ptep_clear_flush_dirty() on ppc64 from a
> module I needed to export the following symbols:
>
> __flush_tlb_pending
> ppc64_tlb_batch
> hpte_update
Any reason why you need to call that from a module ? Is the module
GPL'd ?
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: question on symbol exports
Date: Sat, 05 Feb 2005 20:19:08 +1100 [thread overview]
Message-ID: <1107595148.30302.5.camel@gaston> (raw)
In-Reply-To: <4203D793.1040604@nortel.com>
> It turns out that to call ptep_clear_flush_dirty() on ppc64 from a
> module I needed to export the following symbols:
>
> __flush_tlb_pending
> ppc64_tlb_batch
> hpte_update
Any reason why you need to call that from a module ? Is the module
GPL'd ?
Ben.
next prev parent reply other threads:[~2005-02-05 9:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 0:15 question on symbol exports Chris Friesen
2005-02-01 7:36 ` Arjan van de Ven
2005-02-01 15:37 ` Chris Friesen
2005-02-01 15:50 ` Arjan van de Ven
2005-02-01 17:00 ` Chris Friesen
[not found] ` <20050204203050.GA5889@dmt.cnet>
2005-02-04 20:14 ` Chris Friesen
2005-02-04 20:14 ` Chris Friesen
2005-02-05 9:19 ` Benjamin Herrenschmidt [this message]
2005-02-05 9:19 ` Benjamin Herrenschmidt
2005-02-07 14:44 ` Chris Friesen
2005-02-07 14:44 ` Chris Friesen
2005-02-07 21:35 ` Benjamin Herrenschmidt
2005-02-07 21:35 ` Benjamin Herrenschmidt
2005-02-07 23:02 ` Chris Friesen
2005-02-07 23:02 ` Chris Friesen
2005-02-07 23:42 ` Dan Malek
2005-02-07 23:42 ` Dan Malek
2005-02-08 15:36 ` Chris Friesen
2005-02-08 15:36 ` Chris Friesen
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=1107595148.30302.5.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=arjan@infradead.org \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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.