|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0 |
|
| #
64f58bf4 |
| 12-Aug-2019 |
Andriy Gapon <[email protected]> |
MFC r349886: linuxcommon: add module version
|
|
Revision tags: release/11.3.0, release/12.0.0 |
|
| #
a14a7bbb |
| 08-Nov-2018 |
Tijl Coosemans <[email protected]> |
MFC r340181, r340185:
On amd64 both Linux compat modules, linux.ko and linux64.ko, provide linux_ioctl_(un)register_handler that allows other driver modules to register ioctl handlers. The ioctl sy
MFC r340181, r340185:
On amd64 both Linux compat modules, linux.ko and linux64.ko, provide linux_ioctl_(un)register_handler that allows other driver modules to register ioctl handlers. The ioctl syscall implementation in each Linux compat module iterates over the list of handlers and forwards the call to the appropriate driver. Because the registration functions have the same name in each module it is not possible for a driver to support both 32 and 64 bit linux compatibility.
Move the list of ioctl handlers to linux_common.ko so it is shared by both Linux modules and all drivers receive both 32 and 64 bit ioctl calls with one registration. These ioctl handlers normally forward the call to the FreeBSD ioctl handler which can handle both 32 and 64 bit.
Keep the special COMPAT_LINUX32 ioctl handlers in linux.ko in a separate list for now and let the ioctl syscall iterate over that list first. Later, COMPAT_LINUX32 support can be added to the 64 bit ioctl handlers via a runtime check for ILP32 like is done for COMPAT_FREEBSD32 and then this separate list would disappear again. That is a much bigger effort however and this commit is meant to be MFCable.
This enables linux64 support in x11/nvidia-driver*.
PR: 206711 Reviewed by: kib Approved by: re (gjb)
show more ...
|
|
Revision tags: release/11.2.0, release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0 |
|
| #
0edc82b5 |
| 24-May-2015 |
Dmitry Chagin <[email protected]> |
Move FEATURE macros for v4l and v4l2 to the common module.
Differential Revision: https://reviews.freebsd.org/D1075 Reviewed by: emaste
|
| #
bc273677 |
| 24-May-2015 |
Dmitry Chagin <[email protected]> |
Refund the proc emuldata struct for future use. For now move flags from thread emuldata to proc emuldata as it was originally intended.
As we can have both 64 & 32 bit Linuxulator running any eventh
Refund the proc emuldata struct for future use. For now move flags from thread emuldata to proc emuldata as it was originally intended.
As we can have both 64 & 32 bit Linuxulator running any eventhandler can be called twice for us. To prevent this move eventhandlers code from linux_emul.c to the linux_common.ko module.
Differential Revision: https://reviews.freebsd.org/D1073
show more ...
|
| #
67d39748 |
| 24-May-2015 |
Dmitry Chagin <[email protected]> |
Introduce a new module linux_common.ko which is intended for the following primary purposes:
1. Remove the dependency of linsysfs and linprocfs modules from linux.ko, which will be architecture spec
Introduce a new module linux_common.ko which is intended for the following primary purposes:
1. Remove the dependency of linsysfs and linprocfs modules from linux.ko, which will be architecture specific on amd64.
2. Incorporate into linux_common.ko general code for platforms on which we'll support two Linuxulator modules (for both instruction set - 32 & 64 bit).
3. Move malloc(9) declaration to linux_common.ko, to enable getting memory usage statistics properly.
Currently linux_common.ko incorporates a code from linux_mib.c and linux_util.c and linprocfs, linsysfs and linux kernel modules depend on linux_common.ko.
Temporarily remove dtrace garbage from linux_mib.c and linux_util.c
Differential Revision: https://reviews.freebsd.org/D1072 In collaboration with: Vassilis Laganakos.
Reviewed by: trasz
show more ...
|