From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: Two processes accessing the same mapped physical memory
Date: Wed, 6 Aug 2008 04:17:08 -0700 (PDT) [thread overview]
Message-ID: <18849083.post@talk.nabble.com> (raw)
Hi all,
In my driver i have mapped the SDRAM memory to user space using mmap.
Application can directly access to this physical memory but how can i ensure
that no other process will write to this memory location as long as my
application is having the access to this memory (unlees it unmaps)
For testing this i have written a simul driver which also maps the same
memory of SDRAM and a test application to access it when i run the two
application (actual and test ) ,both of them were accessing the memory and
writing and reading to it.
What is the mechanism to lock this memory (SDRAM in my case )so that no
other process should access it unless and until my process unmaps it or gets
killed.
--- Misbah <><
--
View this message in context: http://www.nabble.com/Two-processes-accessing-the-same-mapped-physical-memory-tp18849083p18849083.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
reply other threads:[~2008-08-06 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=18849083.post@talk.nabble.com \
--to=misbah_khan@engineer.com \
--cc=linuxppc-embedded@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).