[openib-general] patch trouble

[Bryan Green]

"Michael S. Tsirkin" writes:
> Quoting r. Bryan Green <bgreen at nas.nasa.gov>:
> > Subject: patch trouble
> > 
> > Hello,
> > Many of the patches in subversion fail to have an effect when I apply them to a kernel,
> > because they create headers in 'drivers/infiniband/include' which depend on being inclu
> ded
> > before the like-named headers in the toplevel 'include'.  Is there a step I am missing 
> to
> > make the headers in 'drivers/infiniband/include' get chosen for inclusion first?
> 
> Note that backport patches are intended to be applied in an out-of-kernel
> fashion - they are not changing the kernel at all.
> 
> So you build as an out-of-tree driver, and dd something like this to make
> command line:
> 
>                 LINUXINCLUDE='-I$(CWD)/include \
>                 -I$(CWD)/drivers/infiniband/include \
>                 -Iinclude \
>                 $$(if $$(KBUILD_SRC),-Iinclude2 -I$$(srctree)/include) \
>                 -include include/linux/autoconf.h \
>                 -include $(CWD)/include/linux/autoconf.h \
>                 ' \
> 
> You can find an example here
> https://openib.org/svn/gen2/trunk/ofed/openib/scripts/Makefile
> 
> BTW, Mellanox is not actively supporting backport patches on the svn trunk.
> If you want code that works on something other than 2.6.17,
> I suggest you pull backports for the ofed branch (forked from
> 2.6.18-rc6) from ofed_1_1 tree by pulling
> git://www.mellanox.co.il/~git/infiniband ofed_1_1
> and looking in ofed_scripts directory.
> 

Thanks.  I am looking at the git repository, and I see a number of patches in
'kernel_patches/fixes' which are apparently applied before the kernel patches under
'kernel_patches/backport'.  I also see the discrepancies between the patches in git and
svn.  I am currenly putting together a gentoo overlay (a series of gentoo installation
scripts) for openib.  Since there are no source tar files available for download, I am
downloading the code from subversion - I have already done this for the 1.0 subversion
branch, and mvapich2 from the 1.1 branch.  My interest in the 2.6.12 kernel comes from a
need to evaluate the lustre filesystem (production version), which has support for the
2.6.12 vanilla kernel.

Is there a great discrepancy between the git repository and the svn repository?
If I am downloading the kernel modules from subversion, should I still use the patchset
from the git repository?   What about putting a source tar file for openib up for
download?  There is currently only a source tarball for libibverbs, while ofed is too
RPM-centric.

Thanks,

-bryan