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: Tue, 08 Feb 2005 08:35:01 +1100 [thread overview]
Message-ID: <1107812101.7734.42.camel@gaston> (raw)
In-Reply-To: <42077EE0.2060505@nortel.com>
On Mon, 2005-02-07 at 08:44 -0600, Chris Friesen wrote:
> Benjamin Herrenschmidt wrote:
> >>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 ?
>
> I explained this at the beginning of the thread, but I'll do so again.
> The module will be released under the GPL.
>
> The basic idea is that we want to be able to track pages dirtied by a
> userspace process. The system has no swap, so we use the dirty bit for
> this. On demand we look up the page tables for an address range
> specified by the caller, store the addresses of any dirty pages, then
> mark them clean so that the next write causes them to get marked dirty
> again. It is this act of marking them clean that requires the
> additional exports.
>
> I've included the current code below. If there is any way to accomplish
> this without the additional exports, I'd love to hear about it.
Interesting... more than no swap, you must also make sure you have no
r/w mmap'ed file (which are technically equivalent to swap).
I'm not too fan about exporting those symbols, but I'll talk to paulus,
it should be possible at least to EXPORT_SYMBOL_GPL them...
Ben.
next prev parent reply other threads:[~2005-02-07 21:35 UTC|newest]
Thread overview: 12+ 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-05 9:19 ` Benjamin Herrenschmidt
2005-02-07 14:44 ` Chris Friesen
2005-02-07 21:35 ` Benjamin Herrenschmidt [this message]
2005-02-07 23:02 ` Chris Friesen
2005-02-07 23:42 ` Dan Malek
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=1107812101.7734.42.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).