Page MenuHomeFreeBSD

In preparation for switching linuxulator to the use the native 1:1 threads print out thread id in the debug messages.
ClosedPublic

Authored by dchagin on Oct 30 2014, 4:27 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Feb 7, 2:38 PM
Unknown Object (File)
Jan 1 2025, 2:42 PM
Unknown Object (File)
Nov 26 2024, 12:13 AM
Unknown Object (File)
Nov 24 2024, 11:26 AM
Unknown Object (File)
Oct 24 2024, 1:00 PM
Unknown Object (File)
Oct 12 2024, 3:06 PM
Unknown Object (File)
Oct 3 2024, 4:45 PM
Unknown Object (File)
Sep 29 2024, 12:26 AM
Subscribers

Details

Reviewers
emaste
Group Reviewers
Linux Emulation

Diff Detail

Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

dchagin retitled this revision from to In preparation for switching linuxulator to the use the native 1:1 threads print out thread id in the debug messages..
emaste added a reviewer: emaste.
emaste added a subscriber: emaste.

Possible bikeshedding comment, the nested () seem a bit odd to me - e.g. linux(517 (100123)): foo. Consider if you like something like pid/tid: linux(517/100123): foo.

In the commit message I would mention that tid is an addition - i.e. print out thread id in the debug messages -> print the thread id in addition to the pid in debug messages

sys/amd64/linux32/linux.h
43–44

Sorry for possibly bikeshedding here, but the nested () seem a bit odd - e.g. linux(517 (100123)): foo

What about something like pid/tid: linux(517/100123): foo

This revision is now accepted and ready to land.Oct 30 2014, 4:45 PM

Roger!
I will close the revision that are ready to commit.

Btw, if you end your commit message with
Differential Revision: https://reviews.freebsd.org/D1026
it will close automatically when you commit.