mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Timur Alperovich" <timur.alperovich@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: exported version of page_is_ram?
Date: Mon, 5 May 2008 17:13:46 -0400	[thread overview]
Message-ID: <52950c3f0805051413r7d41c4f0tcdc21dc7938d05e8@mail.gmail.com> (raw)
In-Reply-To: <20080505125035.719feaa5@infradead.org>

I put the whole driver on pastebin http://pastebin.com/m24c50118
For now I tried to use the code for page_is_ram in there, only to
realize that e820 struct is also not exported. Is there a way to do
this with the existing code in the kernel, since I'd like the code to
run on older 2.6 kernels as well?

Timur

On Mon, May 5, 2008 at 3:50 PM, Arjan van de Ven <arjan@infradead.org> wrote:
>
> On Mon, 5 May 2008 13:58:59 -0400
>  "Timur Alperovich" <timur.alperovich@gmail.com> wrote:
>
>  > Hi,
>  >
>  > I need to check if a given page is in ram or not. It seems that
>  > page_is_ram does the trick, but since it's not exported, I end up with
>  > "unknown symbol" errors when I try to insert the module. I'm trying to
>  > hash the contents of every page in physical memory, and iterating
>  > through pages from 0 to num_physpages, while checking if they are
>  > actually in ram seemed reasonable. Is there a better way to do it or
>  > is there another function rather than page_is_ram that can do the
>  > trick?
>
>  sounds like the right way is to make a "for each ram page" function
>  in the core, export_symbol_gpl that so that you can then use that...
>  We could even make it scale and numa friendly in the core that way.
>
>  Do you have a url for your code?
>

  reply	other threads:[~2008-05-05 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 17:58 Timur Alperovich
2008-05-05 19:50 ` Arjan van de Ven
2008-05-05 21:13   ` Timur Alperovich [this message]
2008-05-06 13:56     ` Arjan van de Ven

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=52950c3f0805051413r7d41c4f0tcdc21dc7938d05e8@mail.gmail.com \
    --to=timur.alperovich@gmail.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.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®