WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] 32-on-64: pvfb issue

To: Markus Armbruster <armbru@xxxxxxxxxx>
Subject: Re: [Xen-devel] 32-on-64: pvfb issue
From: Gerd Hoffmann <kraxel@xxxxxxx>
Date: Thu, 18 Jan 2007 16:35:03 +0100
Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 18 Jan 2007 07:34:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <87wt3kz8fg.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: <45AF7CDD.6090709@xxxxxxx> <87wt3kz8fg.fsf@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20060911)
Markus Armbruster wrote:
> Gerd Hoffmann <kraxel@xxxxxxx> writes:
> 
>> and probably (hmm, does fc6 ship it?) not widely used yet that might be
>> an option.
> 
> Breaking the API now is right out of the question, I fear :)

Yep, I've seen in the release notes fc6 ships pvfb, so it is used in the
wild now and breaking the API is clearly out of question.  Damn.  Should
have reviewed the patches earlier ...

> You can evolve the API.  Let the frontend put something in xenstore[*]
> that lets the backend detect which page layout to use.  Make sure the
> backend can deal with old and new frontend.  I doubt it's worthwhile
> here.

Well, the problem are the *existing* guests, we already have two
different versions *without* indication out there:  The 32bit and the
64bit ones.  And with the upcoming 32-on-64 support the backend suddenly
must be able to deal with both of them.  Ideally it should work
automatically, without updating the frontends, and without manual
configuration.

> Excuse my ignorance, but why do you have to guess the guest's size?
> Doesn't dom0 know?

No, right now there is no hypercall to get that information.  Which
brings the discussion back onto the table:  Should we add one?  pvfb
isn't the only driver with that kind of problems.

And it better shouldn't be a dom0-only hypercall, otherwise driver
domains will not be able to use it ...

> [*] I suggested to put version ID right into the page, but that was
> shot down in favor of xenstore.

Too bad.  The configuration is in the shared page anyway, so what is the
point of *not* placing the version info there as well?

cheers,
  Gerd

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel