Headers files included by vnode.h

[Gerry Weaver]

_____  

From: Robert Watson [mailto:rwatson at FreeBSD.org]
To: Gerry Weaver [mailto:gerryw at compvia.com]
Cc: gary.jennejohn at freenet.de, freebsd-fs at freebsd.org
Sent: Tue, 23 Dec 2008 05:41:13 -0600
Subject: Re: Headers files included by vnode.h


  On Mon, 22 Dec 2008, Gerry Weaver wrote:
  
  >  Because these files are dynamically generated it makes no sense to
  >  install them.  There are quite a few files like these which are used
  >  during the kernel generation process to dynamically create include
  >  files.  This allows greater flexibility.
  >
  > Thanks Gary. I appreciate your help.
  
  The usual question here is "what are you trying to do?".  Normally we 
  dynamically generate the implementations of the VOP interfaces when the kernel 
  (or a module built independently from the kernel) depends on them.  If you're 
  creating a kernel module, you can add a dependency on vnode_if.h, which will 
  cause the kernel module build framework to generate local copies of the file 
  in your build directory during the build, as seen in the Coda module:
  
     # $FreeBSD: src/sys/modules/coda/Makefile,v 1.17.2.1 2008/03/14 17:12:40 rwatson Exp $
  
     .PATH: ${.CURDIR}/../../fs/coda
  
     KMOD=   coda
     SRCS=   vnode_if.h \
             coda_fbsd.c coda_psdev.c coda_subr.c coda_venus.c coda_vfsops.c \
             coda_vnops.c opt_coda.h
  
     .include <bsd.kmod.mk>
  
  If it's for the purposes of debugging a kernel, you should be able to find the 
  generated copies of the files in the build directory for the kernel.
  
  Robert N M Watson
  Computer Laboratory
  University of CambridgeHi Robert,

Perfect. Yes, I am building a kernel module. This is exactly what I was looking for. 
I really appreciate your help. 

I am also trying to figure out a zero copy approach to kernel memory access from user space. Would you happen to know which list I should post the question to?


Have a great holiday all.

Thanks,
Gerry