Ros-diffs July 2008

ros-diffs@reactos.org
  • 25 participants
  • 761 discussions

[ros-arm-bringup] 34489: - Remove DPRINT1s all over the context switching code.
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34488: - Clean up KTRAP_FRAME and KEXCEPTION_FRAME definition. - Add assembly offsets for KEXCEPTION_FRAME to ksarm.h.
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34487: - Force a 5 second wait before loading drivers, on ARM. - Context switching doesn't really work -- but we've been lucky since we're stuck on a priority 31 thread. - Instead of worrying about this later when the system will be fully operational, this forces us to expose these bugs, and to make sure everything works. - This will stress our context switching, waiting, unwaiting and scheduling code on ARM but once it all works well, after 5 seconds we'll be back on track.
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34486: - Increment the PC by 4 during a DebugService-style trap, just like on x86, so that we can skip the actual instruction when we're done. - Exit the trap after a prefetch abort. DbgPrint fully works now, and we're back where we started -- RamdiskCreateDiskDevice.
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34485: - ARM instructions are 4 bytes long, not 1, so decrement the PC by four during breakpoints (so the caller gets the address of the previous instruction, just like on x86).
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34484: - Also bump PC for ARM after a KD exception.
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34483: - Implement KeContextToTrapFrame. - No, we don't sanitize anything right now. There's no user-mode at this point, so it doesn't matter. If you think we should sanitize right now, you need to get out and get laid. - So this brings us back to KiPrefetchAbortHandler's while (TRUE). - We have to make sure the funky PC modifications are going to work well, and after that, we can exit the trap.
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34482: - Implement KeTrapFrameToContext. - We now get to the point where we call KiDebugRoutine, which is registered as KdpEnterDebuggerException. - KdpEnterDebuggerException reads our exception record and understands this is a BREAKPOINT_PRINT. - It then calls the KdpServiceDispatcher. - This, in turn, calls KdpPrintString. - Which in turn loops the "debug providers" and calls KdpSerialPrintString. - Which calls into KDCOM. - And we see this on the debug log: (ntoskrnl/kd/kdio
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34481: - Okay so we've got a basic KiDispatchException, we now need KiTrapFrameToContext and KiContextToTrapFrame. - We aren't really sure where the hell we are since we can't printf anything otherwise we'll trap again and end up in an infinite loop. - So we're debugging with while (TRUE).
by ros-arm-bringup@svn.reactos.org
16 years, 2 months

[ros-arm-bringup] 34480: - Start implementing KiPrefetchAbortHandler for BKPT instructions. - We pretty much try to duplicate what happens on x86, and build an exception record with the right information. - We are seeing the debug string in R1 and its length in R2, so we're on the right track. - We call KiDispatchException now, which isn't yet implemented. - Yup, all this work just to see a damn debug string the "*proper* NT way". Thanks, asshole.
by ros-arm-bringup@svn.reactos.org
16 years, 2 months
Results per page: