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

Thanks Ian. I am currently testing my implementation on sles9. I will certainly 
look at how I can leverage your work.

Regards,

K. Y

>>> On Thu, Oct 5, 2006 at 11:21 AM, in message
<1160061687.3755.101.camel@xxxxxxxxxxxxxxxxxxxxx>, Ian Campbell
<Ian.Campbell@xxxxxxxxxxxxx> wrote: 
> On Tue, 2006- 10- 03 at 16:31 - 0400, Ky Srinivasan wrote:
>> 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 
> 
> FWIW I have a half complete implementation (compile tested only) of such
> a scheme which I've attached, perhaps you can crib something useful from
> it ;- ).
> 
> Basically it adds a compat- include directory to the end of the include
> search path which contains compatibility versions of headers which may
> not present in older kernels and adds compat.h which defines other
> missing bits where necessary.
> 
> It covers most of the issues compiling against a RHEL4 (2.6.9) or SLES9
> (2.6.5) kernel, although compatibility shims for
> schedule_timeout_interruptible() and nonseekable_open() are still
> missing and the versions used for triggering compatibility code are
> certainly totally wrong (just right for RHEL4 and SLES9 though ;- )).
> 
> I'm fairly unhappy about the number of ifdef's in xenbus_probe.c. I
> reckon some function reordering could coalesce a lot of them. Perhaps
> they are candidates for splitting into a separate file.
> 
> This work will also be useful for the fully PV vendor kernel ports which
> is why I'm interested.
> 
> Ian.


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