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] PV drivers for HVM guests

To: Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] PV drivers for HVM guests
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 04 Oct 2006 08:56:45 +0100
Delivery-date: Wed, 04 Oct 2006 01:07:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45229025.E57C.0030.0@xxxxxxxxxx>
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: AcbniqLU4aMTiVN9EduVNgANk04WTA==
Thread-topic: [Xen-devel] PV drivers for HVM guests
User-agent: Microsoft-Entourage/11.2.5.060620
On 3/10/06 9:31 pm, "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx> wrote:

> These differences can be dealt with in a couple of different ways:
> 1) Modify the code in the PV drivers under appropriate compilation switches to
> deal with the differences in the base kernels.
> 2)  Introduce  a compatibility component that bridges the gap between the
> current PV code and a given Linux target and leave much of the PV driver  code
> untouched.
> 
> I have implemented both these schemes for the sles9 kernel and would like to
> get your input on your preference. I personally like option 2. Going forward,
> the evolution of PV drivers needs to be constrained by the required support
> for legacy Linux environments.

A shim layer (i.e., a set of compat macros) that avoids ifdef'ing the core
driver code is definitely the way to go.

 -- Keir



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