Xen devel - May 2007 - Is is possible to use the latest changeset and old linux kernel?

Hi,

I tried to use the latest changeset of xen-unstable with an old linux 
kernel (2.6.16.33), because some of my codes are developed based on that 
Linux version. It seems that 2.6.18 changes quite a bit interfaces from 
2.6.16.33.

I set the "LINUX_VER    = 2.6.16.33" in the file 
"buildconfigs/mk.linux-2.6-xen". When I did "make world",
the xen
builder did download 2.6.16.33 tarball. But the compiling procedure 
failed with the following error message:

/****************************************************/
include2/asm/i387.h: In function â__save_init_fpuâ:
include2/asm/i387.h:63: error: expected expression before â[â token
include2/asm/i387.h:63: error: âfxâ undeclared (first use in this function)
include2/asm/i387.h:63: error: (Each undeclared identifier is reported 
only once
include2/asm/i387.h:63: error: for each function it appears in.)
include2/asm/i387.h:73: error: expected expression before â[â token
include2/asm/i387.h:73: error: âaddrâ undeclared (first use in this 
function)
/tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c: 
In function âfooâ:
/tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c:58: 
error: âstruct thread_infoâ has no member named âsysenter_returnâ
/tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c:79: 
error: âVDSO_PRELINKâ undeclared (first use in this function)
/tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c:81: 
error: âstruct crypto_tfmâ has no member named â__crt_ctxâ
make[7]: *** [arch/i386/kernel/asm-offsets.s] Error 1
make[6]: *** [prepare0] Error 2
make[5]: *** [modules] Error 2
make[4]: *** [modules] Error 2
/****************************************************/

So my question is how to use the latest Xen changeset with old Linux 
kernel?

Thanks,
Xin


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

> I tried to use the latest changeset of xen-unstable with an old linux
> kernel (2.6.16.33), because some of my codes are developed based on that
> Linux version. It seems that 2.6.18 changes quite a bit interfaces from
> 2.6.16.33.
>
> I set the "LINUX_VER    = 2.6.16.33" in the file
> "buildconfigs/mk.linux-2.6-xen". When I did "make
world", the xen
> builder did download 2.6.16.33 tarball. But the compiling procedure
> failed with the following error message:
>
> /****************************************************/
> include2/asm/i387.h: In function â__save_init_fpuâ:
> include2/asm/i387.h:63: error: expected expression before â[â token
> include2/asm/i387.h:63: error: âfxâ undeclared (first use in this function)
> include2/asm/i387.h:63: error: (Each undeclared identifier is reported
> only once
> include2/asm/i387.h:63: error: for each function it appears in.)
> include2/asm/i387.h:73: error: expected expression before â[â token
> include2/asm/i387.h:73: error: âaddrâ undeclared (first use in this
> function)
> /tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c:
> In function âfooâ:
> /tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c:58:
> error: âstruct thread_infoâ has no member named âsysenter_returnâ
> /tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c:79:
> error: âVDSO_PRELINKâ undeclared (first use in this function)
> /tmp/xen-unstable.hg/linux-2.6.16.33-xen/arch/i386/kernel/asm-offsets.c:81:
> error: âstruct crypto_tfmâ has no member named â__crt_ctxâ
> make[7]: *** [arch/i386/kernel/asm-offsets.s] Error 1
> make[6]: *** [prepare0] Error 2
> make[5]: *** [modules] Error 2
> make[4]: *** [modules] Error 2
> /****************************************************/
>
> So my question is how to use the latest Xen changeset with old Linux
> kernel?
You can''t just build it in the xen-unstable sparse tree, because of the
conflicts you''ve just seen.  The happy news is that you don''t
need to do
this.

I assume you''re dealing with dom0 here?  Otherwise, binary
compatibility for
old changeset ought always to be maintained.  Since at least 3.0.4, the dom0 
kernel binary interfaces are stabilised too, so you can use an older dom0 
kernel with a newer Xen.  (nb. possibly you lose a few features this way, 
e.g. 32-on-64 support).

Are you using 3.0.4 already?  If so, just build dom0 Linux in the tree you 
already have, then use that kernel with the latest changesets of Xen.  You 
just have to make sure you match the dom0 toolset with the Xen you''re 
running.

Does this make sense?

Hope this helps,
Cheers,
Mark
-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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