[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC] Xen Virtual Framebuffer


  • To: Anthony Liguori <aliguori@xxxxxxxxxx>
  • From: Jon Smirl <jonsmirl@xxxxxxxxx>
  • Date: Sat, 10 Dec 2005 21:38:17 -0500
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 11 Dec 2005 02:39:27 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uOe/J3ZoNbNoeGxlOErDukvSVjgaDP7c+MfwlQurEqQOQELTfMOBb3fBU1Onw9hxaUotGGAG2pjWd4xFLgiTqZZK8JXojUVkvUE3SDExxAx6upd1N4UbM1G8A6BCMVxunmFGWcM3CI46PIgIqvDmJh1l7Yl7c+QYsta+ohKyXd8=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

It occurred to me that multiple Linux domains can all share the same
framebuffer. Just treat domain swaps as VT swap events.  You could
even set the different domains up so that something like
Ctrl-Alt-Shift-1, 2, 3 jumps between domains.

dom0 would catch the key stroke, send the current domain a VT save
event, switch to the new domain and send it a VT restore.  This
assumes that all domains have direct access to the video hardware.

This scheme will probably work for multiple basic Xservers one in each
domain, but it will not work for multiple OpenGL or composite users
since they will stomp on each other's use of video RAM.

--
Jon Smirl
jonsmirl@xxxxxxxxx

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.