A newbie question ..... (please cc me as I'm not on linux-rdma list yet)
The system was on RHEL 5.4. I used a source tar-ball to build RHEL 5.5
(2.6.18-194.el5). The kernel build was placed at: /usr/src/linux.
Rebooted to pick up the new kernel .. worked fine... Then
1. On the new 2.6.18-192.el5 system, install OFED-1.5.2 ... succeed.
2. Reboot to pick up new ofa kernel ..succeed (check with modinfo)
3. Run user mode rdma application ... succeed
4. The new ofa kernel modules are placed (by OFED scripts) at:
/lib/modules/2.6.18-194.el5/updates/ directory
5. Build a kernel module (xx.ko) using the attached Makefile
Now .. trying to load (or run after forced loading) xx.ko (on top of
ofa kernel kmod(s)) .. It fails .. as the build apparently picks up
IB kmods from
/lib/modules/2.6.18-194.el5/drivers/infiniband directory, instead of
/lib/modules/2.6.18-194.el5/updates directory, together with wrong
header files from
/lib/modules/2.6.18-194.el5/source/include, where source is
/usr/src/linux directory.
Anyone can help me with a correct procedure ?
I do understand the primary usage of OFED RDMA is for user mode
applications .. but I need to have a kernel mode driver on top of OFED
RDMA for some experiment works.
Thanks,
Wendy
== Make File ==
EXTRA_CFLAGS := -I/usr/src/linux/drivers/xx/include
EXTRA_CFLAGS += -DXX_KMOD_DEF
obj-m := xx_kmod.o
xx_kmod-y := main/xx_main.o main/xx_init.o \
libxxverbs/xx_device.o libxxverbs/xx_cm.o \
libxxverbs/xx_ar.o libxxverbs/xx_mr.o \
libxxverbs/xx_cq.o libxxverbs/xx_sq.o
xx_kmod-y += util/xx_perf.o
xx_kmod-y += brd/xx_brd.o
kmod:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
install:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules_install
run:
/sbin/depmod -a; echo 5 > /proc/sys/kernel/panic; modprobe
--force-modversion xx_kmod
=== End attachment ===
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
