Kernel logging implementation

[Valery V. Sedletski]

Implement kernel logging. We need a logging function for all ring0 components.

1) Probably, we'll need a ring buffer like in DaniS506 (we could look in DaniS sources to use Daniela's implementation). Then we can copy it to a file with

copy vboxdrv$ vbox.log

2) OS/4 kernel has KernPrintf KEE call, so we can use it too, as an option. Then use:

copy kernlog$ kernlog.txt

Note that it should not be limited in vboxdrv.sys, but use the single API for all Ring0 components, like *.r0, *.rc, VboxGuest.sys from guest OS's, TAP driver etc.

[Valery V. Sedletski]

Heh,

N:\src\vbox>copy vboxdrv$ vboxdrv.txt
\DEV\VBOXDRV$ => N:\src\vbox\vboxdrv.txt
     1 file copied

vboxdrv: e7454020 VMMR0.r0
vboxdrv: e7454020 VMMR0.r0
vboxdrv: e7434020 VMMR0.r0
vboxdrv: e7394020 VMMR0.r0
vboxdrv: e7454020 VMMR0.r0
vboxdrv: e7454020 VMMR0.r0
vboxdrv: e7424020 VMMR0.r0
vboxdrv: e7454020 VMMR0.r0
vboxdrv: ea8be020 VMMR0.r0
vboxdrv: e8965020 VBoxDDR0.r0
vboxdrv: ea805020 VBoxDD2R0.r0
HMR0InitVM: ea89d000

-- it seems that Knut had implemented some functionality related to logging :) But the logger in RTLogWriteDebugger-generic.cpp is still a dummy.

[Valery V. Sedletski]

Added r0drv\os2\RTLogWriteDebugger-r0drv-os2.c instead of generic dummy, now I see debug from ring0 components in the buffer.

[dmik]

This is fixed in r64.