This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Paravirt framebuffer frontend kernel support [1/

To: Markus Armbruster <armbru@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Paravirt framebuffer frontend kernel support [1/5]
From: Steven Smith <sos22-xen@xxxxxxxxxxxxx>
Date: Thu, 21 Sep 2006 20:33:47 +0100
Cc: Jeremy Katz <katzj@xxxxxxxxxx>, aliguori <aliguori@xxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, sos22@xxxxxxxxxxxxx
Delivery-date: Thu, 21 Sep 2006 12:34:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <874pv1m59y.fsf@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C124AE2E.23E8%Keir.Fraser@xxxxxxxxxxxx> <874pv1m59y.fsf@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > Another option after 3.0.3 is to allow grant tables to support these large
> > mappings. I have some ideas how to do this fairly efficiently, given that
> > it'll be okay to track mappings to all the pages as an aggregate. It's not
> > going to happen for now though -- it'll just be a shame if we add
> > grant-table support later that it'll change the setup protocol. However, we
> > can probably maintain backward compatibility if we think about it a bit.
> Is there anything we can do now to help with maintaining backward
> compatibility later?
> Evolving interfaces are a fact of life.  What about versioning?
> Frontend puts its interface version in xenstore, bump it when we
> change stuff (which should happen very rarely, of course), backend
> queries the version and does the right thing.
If we're going to do this, it'd probably be worth exporting a backend
version number as well.

Even better would be having a bunch of separate feature flags, like we
do now for the different netif protocols.  You might, for instance,
have backends which can use grant tables export feature-large-grants
to their area of xenbus, and then have frontends notice that and set
request-large-grants in their area if they support it.  If the
relevant nodes aren't present, you conclude that the other end either
doesn't support the feature or doesn't want to use it for some reason.

This has a couple of advantages over a pure version number scheme:

-- If either end doesn't like the new protocol, it's trivial to make
   it fall back to the old one.  We might want to kill the old
   protocol eventually, but this at least makes the transition a bit
-- You don't need to write any code now.
-- I think it's a bit cleaner than potentially artificially tying
   features together.



Attachment: signature.asc
Description: Digital signature

Xen-devel mailing list