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

Re: [Xen-devel] [PATCH 1/2] Virtual frame buffer: frontend

  • To: "Markus Armbruster" <armbru@xxxxxxxxxx>
  • From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
  • Date: Fri, 7 Jul 2006 17:45:30 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 07 Jul 2006 09:45:58 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NoOoR6khX5xRYDoMJQVnqrhxFzR/kdDQuMqzUqQYFamyu8WFC9pklg+2UIvuDEcQXO1lKR6D6mK9jFVoudAwjW5vrqyJUYR3qrTkolVFe3fr7q1oHEPyIJUeVX3FOA03ISdqpvYUD/FfOjPfb4iHDJZlc8Y60gk2FR6fCarLiXI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 6/26/06, Markus Armbruster <armbru@xxxxxxxxxx> wrote:
Derived from

Converted to Xenstore and ported to current kernels.

This looks good.

Could you address the following issues:

- the patch which defined struct xenfb_page seems to be missing

- handling of the ring indexes:
 + we generally prefer to store ring indexes in their unmasked form,
it makes debugging easier and it allows the ring to be used to its
full capacity instead of requiring leaving one slot empty to be able
distinguish empty/full
 + unless I misread the code, the producer (for frontend to backend
messages) seems to write to out_prod + 1 > out_cons, then increment
out_prob (xenfb_do_update) and then the consumer processes entries
from out_cons upto but not include the updated out_prod
(xenfb_on_fb_event) -- the producer for the other way around (backend
to frontend, xenfb_fb_event) seems to be correcter.
 + the lack of barriers -- /* FIXME barriers */ doesn't really cut it ;-)
==> I would suggest looking at the block or net frontend/backend
drivers and copy/pasting some code from there...

- xenbus transactions can fail and there's no code to retry failed transactions

Additionally, I think that the dirty region protocol doesn't really
perform too well in quite simple usage cases like having video play in
one corner of the screen and the mouse being moved in the opposite
corner.  It's probably good enough for this version and supporting
this protocol in the future isn't too bad.

I'm looking forward to seeing a new version of this patch, thanks!


Xen-devel mailing list



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