dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Prof. Dr. Klaus Kusche" <klaus.kusche@computerix.info>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Feature request] Multiple X servers on one graphics card?
Date: Tue, 02 Aug 2011 13:10:32 +0200	[thread overview]
Message-ID: <4E37DB28.5020003@computerix.info> (raw)
In-Reply-To: <CACna6ryPNaa=F3ZC===VpbdQha2y5Ow9s+bXLPWfUojoXv09CA@mail.gmail.com>

On 2011-08-02 12:28, Rafał Miłecki wrote:
> 2011/8/2 Alan Cox<alan@lxorguk.ukuu.org.uk>:
>>> But I believe this is a problem of all approaches which provide
>>> multiple hardware-accelerated (or Xv-enabled) seats on a single GPU,
>>> no matter if based on multiple DRM devices, on Xephyr or Xnest
>>> with some kind of OpenGL or DRI passthrough, or on Wayland:
>>> If one has direct access to the graphics engine, he also can access
>>> any video memory he wants.
>>
>> Not always. It's a bit more complicated than that. Some hardware supports
>> write only memory spaces, some hardware supports contexts in the GTT). On
>> other cards you need some kind of security model and verifier to handle
>> this. I don't think reloading the GTT is enough on most of the cards
>> because the display scanout for all the framebuffers is needed all the
>> time.
>
> I believe you respond to Klaus Kusche here?
>
> Klaus: please, CC mailing list so everyone can see your messages.

My mail Alan cited above was CC'd to the list.
No idea where it got eaten.
Is there some spam filter filtering list postings?

-- 
Prof. Dr. Klaus Kusche
Private address: Rainstraße 9/1, 88316 Isny, Germany
+49 7562 6211377 Klaus.Kusche@computerix.info http://www.computerix.info
Office address: NTA Isny gGmbH, Seidenstraße 12-35, 88316 Isny, Germany
+49 7562 9707 36 kusche@nta-isny.de http://www.nta-isny.de

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2011-08-02 11:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 18:48 [Feature request] Multiple X servers on one graphics card? Prof. Dr. Klaus Kusche
2011-07-31 20:09 ` Dave Airlie
2011-08-01  8:14   ` Prof. Dr. Klaus Kusche
2011-08-01 19:41   ` Prof. Dr. Klaus Kusche
2011-08-01 19:47     ` Dave Airlie
2011-08-01 20:22       ` Alan Cox
2011-08-02  8:17         ` Prof. Dr. Klaus Kusche
2011-08-02 10:26           ` Alan Cox
2011-08-02 10:28             ` Rafał Miłecki
2011-08-02 11:10               ` Prof. Dr. Klaus Kusche [this message]
2011-08-02 15:27                 ` Michel Dänzer
2011-08-02 11:54             ` Prof. Dr. Klaus Kusche
2011-08-02 15:43         ` Christoph Bumiller
2011-08-02 12:59     ` Alex Deucher
2011-08-02 14:22       ` Prof. Dr. Klaus Kusche
2011-08-02 14:34         ` Alex Deucher
2011-08-02 15:28           ` Prof. Dr. Klaus Kusche
2011-08-02 15:48             ` Alex Deucher
2011-08-02 19:11               ` Prof. Dr. Klaus Kusche
2011-08-03 17:51                 ` Alex Deucher
2011-08-03 19:25                   ` Prof. Dr. Klaus Kusche
2011-08-02 23:31               ` Chi-Thanh Christopher Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2011-08-02 13:34 Tomasz Borowik
2011-08-03  6:35 Prof. Dr. Klaus Kusche

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=4E37DB28.5020003@computerix.info \
    --to=klaus.kusche@computerix.info \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=zajec5@gmail.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