From: <j_clifton@aerosimulation.com>
To: <gdb@sourceware.cygnus.com>
Subject: More mmap/Linux questions
Date: Thu, 31 Aug 2000 09:52:00 -0000 [thread overview]
Message-ID: <0008319677.AA967740722@mailserver.aerosimulation.com> (raw)
A previous thread on mmap stated that the problem is in Linux.
I have a cluster of Linux boxes connected via PCI reflective memory. They are
programmed in ADA and have 85 data structures mmaped into the reflective memory.
If I print or x any any structure which has been mmapped all I get are zeros. My
understanding is this is because of ptrace in the linux kernel.
The previous thread indicated this restriction was because some hardware devices
don't like arbitrary accesses. This restriction seems like swatting flies with a
sledgehammer. Can't MTTR or something be used to protect touchy hardware rather
than prohibiting all access to addresses above CPU memory?
Can someone familiar with the Linux Kernel (2.2 or higher) explain this in more
detail. Can I patch the kernel to get rid of this behaviour?
next reply other threads:[~2000-08-31 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-31 9:52 j_clifton [this message]
2000-08-31 13:23 ` Mark Kettenis
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=0008319677.AA967740722@mailserver.aerosimulation.com \
--to=j_clifton@aerosimulation.com \
--cc=gdb@sourceware.cygnus.com \
/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