All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Christian.Limpach@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 1/2] Virtual frame buffer: frontend
Date: Mon, 10 Jul 2006 09:37:06 +0200	[thread overview]
Message-ID: <87veq5syfx.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <3d8eece20607070945saad66c2hfc29b765db0c06bc@mail.gmail.com> (Christian Limpach's message of "Fri, 7 Jul 2006 17:45:30 +0100")

"Christian Limpach" <christian.limpach@gmail.com> writes:

> On 6/26/06, Markus Armbruster <armbru@redhat.com> wrote:
>> Derived from
>> http://www.cs.utexas.edu/users/aliguori/vfb-20060124.bundle
>>
>> 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

D'oh!

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

Understood.

>  + 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.

I'll look into this.

>  + 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...

Will do.

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

Will do.

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

There's been some discussion on this.  I'm not sure what bottom line
emerged, if any.  Do we have to improve this before it can be merged?
Or before it can be declared stable?  Or just eventually?  Unless it's
the latter: do we already know in which direction to go?

  reply	other threads:[~2006-07-10  7:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 13:38 [PATCH 0/2] Virtual frame buffer Markus Armbruster
2006-06-26 13:39 ` [PATCH 1/2] Virtual frame buffer: frontend Markus Armbruster
2006-07-07  7:18   ` Markus Armbruster
2006-07-07 16:45   ` Christian Limpach
2006-07-10  7:37     ` Markus Armbruster [this message]
2006-07-10 10:57       ` Christian Limpach
2006-07-10 18:29     ` Markus Armbruster
2006-07-26 20:28       ` Christian Limpach
2006-07-27  5:11         ` Markus Armbruster
2006-07-27  7:26           ` Gerd Hoffmann
2006-08-04  8:00           ` Markus Armbruster
2006-08-04  8:34             ` Christian Limpach
2006-07-28 13:52   ` Laurent Vivier
2006-08-04  7:54     ` Markus Armbruster
2006-06-26 13:40 ` [PATCH 2/2] Virtual frame buffer: user space backend Markus Armbruster
2006-07-07  7:18   ` Markus Armbruster
2006-07-28 15:55     ` Laurent Vivier
2006-08-04  7:57       ` Markus Armbruster
2006-07-07 16:57   ` Christian Limpach
2006-07-07 17:31     ` Anthony Liguori
2006-07-07 18:33       ` Christian Limpach
2006-07-07 18:50         ` Anthony Liguori
2006-07-07 22:50           ` Christian Limpach
2006-07-07 23:05             ` Anthony Liguori
2006-07-08  1:10               ` Christian Limpach
2006-07-08  1:49                 ` Anthony Liguori
2006-07-08 10:20                   ` Christian Limpach
2006-07-08  0:35             ` Rik van Riel
2006-07-08  1:38               ` Christian Limpach
2006-07-10  7:37     ` Markus Armbruster
2006-07-10 18:29     ` Markus Armbruster
2006-07-07  7:17 ` [PATCH 0/2] Virtual frame buffer Markus Armbruster

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=87veq5syfx.fsf@pike.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.