linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
To: "William J. Earl" <wje@cthulhu.engr.sgi.com>
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: page faults
Date: 26 Oct 1999 15:50:08 +0200	[thread overview]
Message-ID: <kfy7lkaqlin.fsf@kieraypc01.p.y.ki.era.ericsson.se> (raw)
In-Reply-To: "William J. Earl"'s message of "Mon, 25 Oct 1999 10:27:26 -0700 (PDT)"

"William J. Earl" <wje@cthulhu.engr.sgi.com> writes:

> Eric W. Biederman writes:
> ...
>  > If the hardware cannot support two processors hitting the region simultaneously,
>  > (support would be worst case the graphics would look strange)
>  > you could have problems.
> ...
>       One could reasonably take the view that a threads-aware graphics library
> should be thread-safe.  That is, if the hardware needs to have concurrent
> threads in a single process serialize access to the hardware, then the 
> library plugin for that hardware should do the required serialization.
> 
>       This of course the neglects the question of whether a broken
> user-mode program could damage the hardware, but then a broken
> single-threaded user-mode program, with no other programs using the
> hardware, could just as easily damage the hardware.  That is, if the
> hardware is not safe for direct access in general, threading does not
> make it any less safe.

The hardware _is_ safe for direct access, but _not_ while the
accelerator is running.

//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/

  reply	other threads:[~1999-10-26 13:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-21 16:31 James Simmons
1999-10-21 19:40 ` Benjamin C.R. LaHaise
1999-10-22  0:47   ` Wang Yong
1999-10-22 13:06   ` Stephen C. Tweedie
1999-10-22 14:59     ` James Simmons
1999-10-22 15:15       ` Benjamin C.R. LaHaise
1999-10-22 17:35       ` Stephen C. Tweedie
1999-10-22 23:31         ` James Simmons
1999-10-24 17:15           ` Eric W. Biederman
1999-10-25 17:27             ` William J. Earl
1999-10-26 13:50               ` Marcus Sundberg [this message]
1999-10-26 14:00               ` Eric W. Biederman
1999-10-26 15:11                 ` James Simmons
1999-10-26 18:04                 ` William J. Earl
1999-10-26  9:05             ` Ralf Baechle
1999-10-29 14:52               ` James Simmons
1999-11-01 11:57                 ` Stephen C. Tweedie

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=kfy7lkaqlin.fsf@kieraypc01.p.y.ki.era.ericsson.se \
    --to=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=linux-mm@kvack.org \
    --cc=wje@cthulhu.engr.sgi.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