Hi Ian Campbell,
My name is Takanori Kasai, work for FUJITSU.
My current patch is below, it cross-compiles for IA64 without warnings
against RHEL4.4 and SLES9sp3. Could you let me know if it works for you?
If so would you mind submitting the ia64 bits via the ia64 maintainer.
I'll apply the unmodified_drivers bits.
I confirmed this patch. (cs:12004)
However, it failed in the compile of linux-sparse.
BTW, We try to port it for RHEL4U4.
We appended typedef gfp_t, because it is not defined in linux2.6.16.
But it has already been defined in RHEL4U4.
We made patch compiling for RHEL4U4.
How do you think of this patch?
My best regards.
-
Takanori Kasai
As follows:
------------------------------------------------------------------------------
CC drivers/input/joydev.o
In file included from include/asm/page.h:268,
from include/asm/ptrace.h:86,
from include/asm/hypervisor.h:59,
from include/asm/io.h:69,
from drivers/input/joydev.c:13:
include/asm/maddr.h: In function `pfn_to_mfn_for_dma':
include/asm/maddr.h:33: warning: implicit declaration of function
`HYPERVISOR_phystomach'
include/asm/maddr.h: In function `mfn_to_pfn_for_dma':
include/asm/maddr.h:53: warning: implicit declaration of function
`HYPERVISOR_machtophys'
In file included from include/asm/hypervisor.h:60,
from include/asm/io.h:69,
from drivers/input/joydev.c:13:
include/asm/hypercall.h: At top level:
include/asm/hypercall.h:322: error: conflicting types for
'HYPERVISOR_phystomach'
include/asm/maddr.h:33: error: previous implicit declaration of
'HYPERVISOR_phystomach' was here
include/asm/hypercall.h:339: error: conflicting types for
'HYPERVISOR_machtophys'
include/asm/maddr.h:53: error: previous implicit declaration of
'HYPERVISOR_machtophys' was here
make[6]: *** [drivers/input/joydev.o] Error 1
make[5]: *** [drivers/input] Error 2
make[4]: *** [drivers] Error 2
make[4]: Leaving directory
`/xen/source/xen-ia64-unstable.hg-12004-Ian/linux-2.6.16.29-xen'
make[3]: *** [build] Error 2
make[3]: Leaving directory `/xen/source/xen-ia64-unstable.hg-12004-Ian'
make[2]: *** [linux-2.6-xen-install] Error 2
make[2]: Leaving directory `/xen/source/xen-ia64-unstable.hg-12004-Ian'
make[1]: *** [install-kernels] Error 1
make[1]: Leaving directory `/xen/source/xen-ia64-unstable.hg-12004-Ian'
make: *** [world] Error 2
------------------------------------------------------------------------------
----- Original Message -----
From: "Kasai Takanori" <kasai.takanori@xxxxxxxxxxxxxx>
To: "xen-ia64-devel" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, October 26, 2006 9:06 PM
Subject: [Xen-ia64-devel] [Patch] PV-on-HVM backport patch for IPF
Hi All,
We've ported PV-on-HVM drivers for IPF.
I post a part of PV-on-HVM backport patch for IPF.
We tested compiling and simple test on RHEL4U2.
BTW, We try to port it for RHEL4U4.
We appended typedef gfp_t, because it is not defined in linux2.6.9.
But it has already been defined in RHEL4U4.
We made pv-RHEL4U4-ia64.patch compiling for RHEL4U4.
However, we don't think that this idea is so good.
Do you have any idea for cleanup to switch of version?
And I found insmod to RHEL4U4 is always fail.
I still investigating it.
pv-backport-ia64.patch:
- Add infrastructure for a compatibility shim on IPF
- Append IS_ERR_VALUE to hypercall.h for backport
- Append to include pgtable-nopud.h for linux-2.6.11 before
- Append pud_bad macro for linux-2.6.11 before
pv-RHEL4U4-ia64.patch(preliminary):
- Modify build rule for RHEL4_U4 specific
- Append typedef gfp_t to xencomm.h for linux-2.6.14 before
- we tested only compiling.
My best regards.
-
Takanori Kasai
pv-backport-ia64.patch
Description: Binary data
pv-RHEL4U4-ia64.patch
Description: Binary data
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
| 
Home