At 09:55 27/11/19 -0700, Jeff Rhyason wrote:
>Is there a way that I can log a large amount of statistics
>regarding kernel memory allocator activity and make that
>accessible to a user process? (Something like Solaris'
>crash(1m) and kmalog)
The quick solution is to config -g your kernel, and extract statistics
via gdb
gdb -x extract-reset-script -k -wcore unstripped-kernel /dev/mem
where extract-reset-script prints the current values, resets, and
then exits.
Otherwise, write a character device driver and matching user land
facility to extract the information you want.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Re: Collecting waiting statistics (simulation question) Peter Jeremy
- Re: Collecting waiting statistics (simulation question) Jeff Rhyason
- Re: Collecting waiting statistics (simulation question) Jeff Rhyason
- Collecting waiting statistics (simulation question) Jeff Rhyason
- Re: Collecting waiting statistics (simulation questi... Alfred Perlstein
- Re: Collecting waiting statistics (simulation qu... Jeff Rhyason
- Re: Collecting waiting statistics (simulatio... Robert Watson
- Re: Collecting waiting statistics (simul... Jeff Rhyason
- Re: Collecting waiting statistics (simulation questi... mouss
- Editors/Reviewers? (was Re: Collecting waiting ... Jeff Rhyason
- Drew Eckhardt

