From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Armbruster Subject: Re: PVFB: Add offset event? Date: Tue, 04 Mar 2008 18:08:18 +0100 Message-ID: <87prua5se5.fsf@pike.pond.sub.org> References: <20080304164128.GC9852@implementation.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080304164128.GC9852@implementation.uk.xensource.com> (Samuel Thibault's message of "Tue\, 4 Mar 2008 16\:41\:28 +0000") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Samuel Thibault Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Samuel Thibault writes: > Samuel Thibault, le Tue 04 Mar 2008 16:12:20 +0000, a =C3=A9crit : >> Markus Armbruster, le Tue 04 Mar 2008 16:48:20 +0100, a =C3=A9crit : >> > I imagine (perhaps naively): >> >=20 >> > * The domU writes to a framebuffer provided by the frontend. >> > >> > * The framebuffer (not a copy of it) can be shared with the backend, >> > which only reads. >>=20 >> Well, that's not always the case, when the guest is in text mode for >> instance, the PV shared buffer is converted from the guest text buffer. > > BTW, that leads me to another extension which would be useful: since > the interface I have with the guest is the cirrus VGA card, I'm not > supposed to know in advance where the guest will choose to make its > frame buffer start, so at the same time of a resize event, or as an > independant event, it would be useful to be able to tell the offset > (within the big shared buffer) where the actual framebuffer starts. > > Samuel I guess that could be worked into the dynamic modes feature.