linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Henroid <andy_henroid@yahoo.com>
To: Thomas Sailer <sailer@ife.ee.ethz.ch>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>, Linux-MM@kvack.org
Subject: Re: remap_page_range problem on 2.3.x
Date: Mon, 13 Mar 2000 11:16:59 -0800 (PST)	[thread overview]
Message-ID: <20000313191659.6976.qmail@web1306.mail.yahoo.com> (raw)

--- Thomas Sailer <sailer@ife.ee.ethz.ch> wrote:
> Andy Henroid wrote:
> 
> > Yes, the remap_page_range is done indirectly
> > through mmap call to the /dev/mem driver.
> 
> I think I saw this too some time ago.
> 
> I tried to duplicate the kernel's view of the
> address space above 0xc0000000 at an offset in
> a usermode program. I ended up being able to
> read the correct data from /dev/mem, but reading
> from an mmaped page from /dev/mem returned
> completely bogus data (all zero).

Yes, the read through /dev/mem work for me too.
It looks like remap_page_range is doing the right
thing and it certainly works for other remapping.
I wonder what the problem is?

Oh well, low priority compared to the other things
that need to get fixed as we move into pre2.4

Thanks,
Andy

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

             reply	other threads:[~2000-03-13 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-13 19:16 Andy Henroid [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-09 17:51 Andy Henroid
2000-03-13 13:19 ` Thomas Sailer
2000-03-08  2:05 Andy Henroid
2000-03-08  4:04 ` Jeff Garzik

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=20000313191659.6976.qmail@web1306.mail.yahoo.com \
    --to=andy_henroid@yahoo.com \
    --cc=Linux-MM@kvack.org \
    --cc=jgarzik@mandrakesoft.com \
    --cc=sailer@ife.ee.ethz.ch \
    /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