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] bi-modal backends - fronend mode detection

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] bi-modal backends - fronend mode detection
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 04 Nov 2006 07:51:16 +0000
Delivery-date: Fri, 03 Nov 2006 23:52:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1715A5D.3FE4%Keir.Fraser@xxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acb/iKvS6iqtbGt7EduUiwAX8io7RQAXVW0d
Thread-topic: [Xen-devel] bi-modal backends - fronend mode detection
User-agent: Microsoft-Entourage/11.2.5.060620
On 3/11/06 8:43 pm, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> wrote:

>> Does anyone have a good suggestion how to have the backends (for
>> which I just created bi-modal functionality, so they can [on x86 for
>> now] support both 32-bit and 64-bit domUs) learn the mode of the
>> connecting frontends.
>> 
>> (Backends using blkif and tpmif need this, pci and networking seem
>> to be unaffected.)
> 
> Maybe using a new hypercall makes sense, to discover what Xen thinks is the
> mode of VCPU0. We'll need something similar for HVM guests in the long term,
> so making the decision at domain-build time doesn't really work.

Actually this doesn't necessarily work reliably. We don't know what mode the
HVM guest will happen to be running in when we query it via a hypercall. We
should add an address-bits field to the frontend device-info directory. This
can be filled in by frontend drivers, and also by the tools when creating PV
guests. In the absence of the address-bits field, backend can assume native
bit width or 32-bit width, whichever seems likely to work with most older
HVM clients.

 -- Keir



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