From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: syscall __NR_mmap2
Date: Tue, 8 Jul 2003 07:56:49 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307080754550.24488@chaos> (raw)
In-Reply-To: <3F09E6EF.8000806@redhat.com>
On Mon, 7 Jul 2003, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Richard B. Johnson wrote:
>
> > write(1, "Addr = 000b8000\n", 16) = 16
> > open("/dev/mem", O_RDWR) = 3
> > mmap2(0xb8000, 8192, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_FIXED, 3, 0xb8000) = 0xb8000
>
> mmap64() (and if you compile glibc with an adequate minimal kernel
> requirement mmap as well) is implemented using mmap2. It works nicely.
> Admittedly, I haven't used the stock 2.4 kernel. And I also haven't
> used /dev/mem. But at least for the first part I would expect to see
> problem reports since the code is used and glibc wouldn't work.
>
> In your code, assuming this is x86, do you really want to read the
> memory starting at address 0xb8000000? This is what your code does. I
> don't know enough about the kernel memory layout to say whether
> something is supposed to be there or not.
>
Yes. Thanks. There is no known documentation that states that
the address to the function is in PAGES. Certainly, this will
work once I use pages instead of bytes.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-07-08 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 21:00 Richard B. Johnson
2003-07-07 21:32 ` Ulrich Drepper
2003-07-08 11:56 ` Richard B. Johnson [this message]
2003-07-08 0:36 ` Jamie Lokier
2003-07-08 11:54 ` Richard B. Johnson
2003-07-08 13:59 ` Kurt Wall
2003-07-08 14:05 ` Jamie Lokier
2003-07-08 14:40 ` Richard B. Johnson
2003-07-08 14:49 ` Randy.Dunlap
2003-07-08 14:51 ` Kurt Wall
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=Pine.LNX.4.53.0307080754550.24488@chaos \
--to=root@chaos.analogic.com \
--cc=drepper@redhat.com \
--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®