Page MenuHomeFreeBSD

Introduce a new module linux_common.ko which is intended for the following primary purposes:
ClosedPublic

Authored by dchagin on Nov 1 2014, 2:11 PM.

Details

Reviewers
trasz
Group Reviewers
Linux Emulation
Summary
  1. Remove the dependency of linsysfs and linprocfs modules from linux.ko,

which will be architecture specific on amd64.

  1. Incorporate into linux_common.ko general code for platforms on which

we'll support two Linuxulator modules (for both instruction set - 32 & 64 bit).

  1. 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

In collaboration with Vassilis Laganakos.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
No Linters Available
Unit
No Unit Test Coverage

Event Timeline

dchagin retitled this revision from to Introduce a new module linux_common.ko which is intended for the following primary purposes:.
dchagin updated this object.

Updating D1072: Introduce a new module linux_common.ko which is intended for the

following primary purposes:
#
After r268138 we cant split device_handler

linux_common is amd64 specific.

Updating D1072: Introduce a new module linux_common.ko which is intended for the

following primary purposes:

What's the eventual plan for dtrace in here?

In D1072#7, @emaste wrote:

What's the eventual plan for dtrace in here?

Now this is not the most important. Later, I will restore this shit.

Erm, but why was the whole SDT stuff removed? Build problem?

first of all I do not quite understand the reason for this SDT crap in the Linuxulator.
it cant be used by developers for debug purposes nor for user debug. What for?
secondly, linux_common is a common module for both linuxulators at runtime.
so I do not understand how to share SDT provider between them.
I'd prefer Leidinger should care about its own crap. sorry for the my ruglish )

In D1072#12, @dchagin wrote:

first of all I do not quite understand the reason for this SDT crap in the Linuxulator.
it cant be used by developers for debug purposes nor for user debug. What for?

Why can't it be used? Anyway, it seems OK if we remove it for now, and add it back later with a use case.

In D1072#13, @emaste wrote:
In D1072#12, @dchagin wrote:

first of all I do not quite understand the reason for this SDT crap in the Linuxulator.
it cant be used by developers for debug purposes nor for user debug. What for?

Why can't it be used? Anyway, it seems OK if we remove it for now, and add it back later with a use case.

Unlike ktkr(9) dtrace is not available in ddb, but Ok, I return to this later, as I said

trasz added a reviewer: trasz.
This revision is now accepted and ready to land.Mar 25 2015, 11:11 AM