From: Steven Smith Subject: Re: [PATCH] Paravirt framebuffer frontend kernel support [1/5] Date: Thu, 21 Sep 2006 20:33:47 +0100 Message-ID: <20060921193347.GB6748@cam.ac.uk> References: <874pv1m59y.fsf@pike.pond.sub.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2080194227==" Return-path: In-Reply-To: <874pv1m59y.fsf@pike.pond.sub.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Markus Armbruster Cc: Jeremy Katz , aliguori , xen-devel , sos22@srcf.ucam.org List-Id: xen-devel@lists.xenproject.org --===============2080194227== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y7xTucakfITjPcLV" Content-Disposition: inline --Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > > Another option after 3.0.3 is to allow grant tables to support these la= rge > > mappings. I have some ideas how to do this fairly efficiently, given th= at > > 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? >=20 > 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 easier. -- You don't need to write any code now. -- I think it's a bit cleaner than potentially artificially tying features together. Thoughts? Steven. --Y7xTucakfITjPcLV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFEukbO4S8/gLNrjcRApdJAKCFMbBbagrw3RgSoC50I1DjLaPWiACguD86 JTfizZFQhtzhbUSXLZUYYX8= =5Btc -----END PGP SIGNATURE----- --Y7xTucakfITjPcLV-- --===============2080194227== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============2080194227==--