linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
To: James Simmons <jsimmons@edgeglobal.com>
Cc: linux-mm@kvack.org
Subject: Re: MMIO regions
Date: Mon, 04 Oct 1999 18:58:57 +0200	[thread overview]
Message-ID: <37F8DCD1.E726CBBC@switchboard.ericsson.se> (raw)
In-Reply-To: <Pine.LNX.4.10.9910041028350.7066-100000@imperial.edgeglobal.com>

James Simmons wrote:
> 
> Howdy again!!
> 
>    I noticed something for SMP machines with all the dicussion about
> concurrent access to memory regions. What happens when you have two
> processes that have both mmapped the same MMIO region for some card.
> Doesn't have to be a video card,. On a SMP machine it is possible that
> both processes could access the same region at the same time. This could
> cause the card to go into a indeterminate state. Even lock the machine.
> Does their exist a way to handle this? Also some cards have mulitple MMIO
> regions. What if a process mmaps one MMIO region of this card and another
> process mmaps another MMIO region of this card. Now process one could
> alter the card in such a way it could effect the results that process two
> is expecting. How is this dealt with? Is it dealt with? If not what would
> be a good way to handle this?

AFAIK no drivers except fbcon drivers map any IO-region to userspace.

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan/
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: mackan@stacken.kth.se
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  parent reply	other threads:[~1999-10-04 16:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04 14:38 James Simmons
1999-10-04 15:31 ` Stephen C. Tweedie
1999-10-04 15:52   ` James Simmons
1999-10-04 16:02     ` Benjamin C.R. LaHaise
1999-10-04 17:27       ` James Simmons
1999-10-04 17:56         ` Benjamin C.R. LaHaise
1999-10-04 18:26           ` James Simmons
1999-10-04 19:19         ` Stephen C. Tweedie
1999-10-06 20:15           ` James Simmons
1999-10-11 17:09             ` Stephen C. Tweedie
1999-10-11 17:26               ` Jeff Garzik
1999-10-11 23:14                 ` James Simmons
1999-10-11 17:57               ` James Simmons
1999-10-04 16:11     ` Stephen C. Tweedie
1999-10-04 18:29       ` James Simmons
1999-10-04 19:35         ` Stephen C. Tweedie
1999-10-07 19:40           ` James Simmons
1999-10-10 11:24             ` Rik Faith
1999-10-10 14:03               ` Eric W. Biederman
1999-10-10 18:46                 ` Rik Faith
1999-10-11  0:21                   ` James Simmons
1999-10-11 10:59                     ` Rik Faith
1999-10-11  3:38                   ` Eric W. Biederman
1999-10-10 14:21               ` James Simmons
1999-10-11 17:22             ` Stephen C. Tweedie
1999-10-04 16:58 ` Marcus Sundberg [this message]
1999-10-04 18:27   ` James Simmons

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=37F8DCD1.E726CBBC@switchboard.ericsson.se \
    --to=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=jsimmons@edgeglobal.com \
    --cc=linux-mm@kvack.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