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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] PV drivers for HVM guests
From: "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx>
Date: Wed, 04 Oct 2006 14:45:20 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 04 Oct 2006 11:45:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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

>>> On Wed, Oct 4, 2006 at  3:56 AM, in message
<C14927CD.2084%Keir.Fraser@xxxxxxxxxxxx>, Keir Fraser
<Keir.Fraser@xxxxxxxxxxxx> wrote: 
> 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

Thanks Kier; this is also my preference. To keep the shim layer small, we may 
still have some ifdefs in the driver code  though(to deal with non-existent 
header files that are included etc).

Regards,

K. Y 





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