Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
642bc4c72b
NetBSD/sys/dev/Makefile

25 lines
586 B
Makefile
Raw Normal View History

Remove filemon(4). Discussed on tech-kern: https://mail-index.NetBSD.org/tech-kern/2020/01/13/msg025938.html This was never (intentionally) enabled by default, and the design has some shortcomings. You can get mostly the same results with ktrace, as in usr.bin/make/filemon/filemon_ktrace.c which is now used instead of filemon for make's meta mode. If applications require higher performance than ktrace, or nesting that ktrace doesn't support, we might consider adding something back into the vfs system calls themselves, without hijacking the syscall table. (Might want a more reliable output format too, e.g. one that can handle newlines in file names.)
2020-01-19 23:41:17 +03:00
# $NetBSD: Makefile,v 1.44 2020/01/19 20:41:18 riastradh Exp $
Rework the way kernel include files are installed. In the new method, as with user-land programs, include files are installed by each directory in the tree that has includes to install. (This allows more flexibility as to what gets installed, makes 'partial installs' easier, and gives us more options as to which machines' includes get installed at any given time.) The old SYS_INCLUDES={symlinks,copies} behaviours are _both_ still supported, though at least one bug in the 'symlinks' case is fixed by this change. Include files can't be build before installation, so directories that have includes as targets (e.g. dev/pci) have to move those targets into a different Makefile.
1998-06-13 03:22:30 +04:00
Remove filemon(4). Discussed on tech-kern: https://mail-index.NetBSD.org/tech-kern/2020/01/13/msg025938.html This was never (intentionally) enabled by default, and the design has some shortcomings. You can get mostly the same results with ktrace, as in usr.bin/make/filemon/filemon_ktrace.c which is now used instead of filemon for make's meta mode. If applications require higher performance than ktrace, or nesting that ktrace doesn't support, we might consider adding something back into the vfs system calls themselves, without hijacking the syscall table. (Might want a more reliable output format too, e.g. one that can handle newlines in file names.)
2020-01-19 23:41:17 +03:00
SUBDIR= apm ata bluetooth dec dm dmover dtv hdaudio hdmicec hid hpc \
Install filemon.h
2012-06-21 01:38:26 +04:00
i2c i2o ic ieee1394 ir isa \
install dtvio.h, dtvio_demux.h, dtvio_frontend.h
2011-07-09 18:52:02 +04:00
microcode ofw pci pckbport pcmcia pud putter raidframe sbus scsipi \
Hook spi.
2019-02-24 05:30:38 +03:00
spi sun tc usb vme wscons
Rework the way kernel include files are installed. In the new method, as with user-land programs, include files are installed by each directory in the tree that has includes to install. (This allows more flexibility as to what gets installed, makes 'partial installs' easier, and gives us more options as to which machines' includes get installed at any given time.) The old SYS_INCLUDES={symlinks,copies} behaviours are _both_ still supported, though at least one bug in the 'symlinks' case is fixed by this change. Include files can't be build before installation, so directories that have includes as targets (e.g. dev/pci) have to move those targets into a different Makefile.
1998-06-13 03:22:30 +04:00
Add NVMM - for NetBSD Virtual Machine Monitor -, a kernel driver that provides support for hardware-accelerated virtualization on NetBSD. It is made of an MI frontend, to which MD backends can be plugged. One MD backend is implemented, x86-SVM, for x86 AMD CPUs. We install /usr/include/dev/nvmm/nvmm.h /usr/include/dev/nvmm/nvmm_ioctl.h /usr/include/dev/nvmm/{arch}/nvmm_{arch}.h And the kernel module. For now, the only architecture where we do that is amd64 (arch=x86). NVMM is not enabled by default in amd64-GENERIC, but is instead easily modloadable. Sent to tech-kern@ a month ago. Validated with kASan, and optimized with tprof.
2018-11-07 10:43:07 +03:00
.if ${MACHINE_ARCH} == "x86_64"
SUBDIR+= nvmm
.endif
Make the test for MKISCSI actually work by including bsd.own.mk and testing the expanded variable, not just the variable name(!) Fixes the build for sun2.
2011-11-17 13:58:21 +04:00
.include <bsd.own.mk>
.if ${MKISCSI} != "no"
Build and install new in-kernel iscsi initiator kernel module and associated binaries (iscsid, iscsictl) if MKISCSI != no. Initiator can also be built into a kernel by adding 'pseudo-device iscsi' in kernel configuration.
2011-11-15 20:50:43 +04:00
SUBDIR+= iscsi
.endif
Rework the way kernel include files are installed. In the new method, as with user-land programs, include files are installed by each directory in the tree that has includes to install. (This allows more flexibility as to what gets installed, makes 'partial installs' easier, and gives us more options as to which machines' includes get installed at any given time.) The old SYS_INCLUDES={symlinks,copies} behaviours are _both_ still supported, though at least one bug in the 'symlinks' case is fixed by this change. Include files can't be build before installation, so directories that have includes as targets (e.g. dev/pci) have to move those targets into a different Makefile.
1998-06-13 03:22:30 +04:00
INCSDIR= /usr/include/dev
Only install headers which are actually used by our userland. This saves about 2.2MB under /usr/include/dev/. Discussed on tech-kern@ recently. I HOPE to get the list right. The headers I left in are ones used for MI tools and those whose usage I discovered by grep over tree sources. Feel free to put needed includes back in if you encounter anything which should not be removed from lists.
2001-04-11 11:42:31 +04:00
# Only install includes which are used by userland
Add keylock.h to INCS so that it's actually installed (hi, marc!)
2009-08-15 18:22:54 +04:00
INCS= biovar.h ccdvar.h cgdvar.h fssvar.h keylock.h kttcpio.h lockstat.h \
move spkrio.h out of isa
2016-12-09 07:46:39 +03:00
md.h vndvar.h spkrio.h
Rework the way kernel include files are installed. In the new method, as with user-land programs, include files are installed by each directory in the tree that has includes to install. (This allows more flexibility as to what gets installed, makes 'partial installs' easier, and gives us more options as to which machines' includes get installed at any given time.) The old SYS_INCLUDES={symlinks,copies} behaviours are _both_ still supported, though at least one bug in the 'symlinks' case is fixed by this change. Include files can't be build before installation, so directories that have includes as targets (e.g. dev/pci) have to move those targets into a different Makefile.
1998-06-13 03:22:30 +04:00
.include <bsd.kinc.mk>
Reference in New Issue Copy Permalink