Ros-dev January 2010

ros-dev@reactos.org

41 participants
64 discussions

[ros-diffs] [sir_richard] 45052: Patch that fixes VMWare boot (and

by Dmitry Gorbachev

Hi, sir_richard wrote: > * We really have to get a good DS/ES first before touching any data. > * > * These two reads will either go in a register (with optimizations ON) or > * a stack variable (which is on SS:ESP, guaranteed to be good/valid). > * > * Because the assembly is marked volatile, the order of instructions is > * as-is, otherwise the optimizer could simply get rid of our DS/ES. Timo Kreuzer wrote: > 2.) Segements should be fixed up before entering C code, as not doing so > may introduce possible compiler dependend breakages. It's also much > cleaner and there's no reason to do the same stuff later in inline assembly > instead of direcly in the asm entry point. Ros Arm wrote: > Regarding #2, I unfortunately do not see the need to add more assembly > when it is not needed. There are no subtle compiler breakages involved, > since it is impossible for the compiler to add a DS/ES access for no reason > at all (can you come up with an example?), this is part of the contract the > compiler has to make (if compilers did this, it would break a whole class of > embedded and real-mode software). Because the stack is safe, I think it's > worth avoiding the extra lines of assembly. The C inlines will produce > exactly the same code anyway. Not as a guide to action, simply to note — there is no guarantee that volatile asm statements (and code around them) will never be reordered. As only two registers are needed to keep Ds and Es, it seems to work there. But in a general case, GCC does not hesitate to rearrange such stuff…

14 years, 9 months

Request for a project

by sudheer kumar

Hi, I am interested to work on reactos developement. I want to take my work on reactos as a credit in my university. I spoke toAleksey Bragin (Fireball) regarding this. He asked me to mail to the developer mailing list. I need some concrete work to work for like five months or more so that I can show to professor to get his acceptance. My skills involve mostly on developing .I am mostly a C++ programmer with some experience in assembly language. I have some prior experience on filesystems and kernel but mostly linux. I have some experience on windows drivers too. By the way I am a masters student in computer science from US. Thanks & Regards, sudhir. .

14 years, 9 months

bug in KiTrap0DHandler

by Timo Kreuzer

@Sir Richard, While fixing trunk breakage, I also fixed another bug in KiTrap0DHandler, which was always only checking one prefix. I attached the patch. Regards, Timo Index: traphdlr.c =================================================================== --- traphdlr.c (Revision 45057) +++ traphdlr.c (Arbeitskopie) @@ -1103,19 +1103,23 @@ /* Skip prefix instructions */ for (j = 0; j < sizeof(KiTrapPrefixTable); j++) { - /* Is this NOT a prefix instruction? */ - if (Instructions[i] != KiTrapPrefixTable[j]) + /* Is this a prefix instruction? */ + if (Instructions[i] == KiTrapPrefixTable[j]) { - /* We can go ahead and handle the fault now */ - Instruction = Instructions[i]; + /* Stop looking */ break; } } - /* Do we need to keep looking? */ - if (Instruction) break; + /* Is this NOT any prefix instruction? */ + if (Instructions[i] != KiTrapPrefixTable[j]) + { + /* We can go ahead and handle the fault now */ + Instruction = Instructions[i]; + break; + } } - + /* If all we found was prefixes, then this instruction is too long */ if (!Instruction) {

14 years, 9 months

Fwd: removing ReactOS (for lulz)

by Aleksey Bragin

:) Begin forwarded message: > From: Max Winter <maxwinter2001(a)yahoo.com> > Date: January 13, 2010 1:26:11 AM GMT+03:00 > To: xxxxxxx(a)reactos.org > Subject: removing ReactOS > > How do I get ReactOS off my computer? I downloaded a third of it > and for various reasons stopped the download. I want to get it off > my computer now but it is not giving me delete or cut options. > This is as bad as malware, or Hotel California, you can check it > in but you can't check out. > > M >

14 years, 9 months

Re: [ros-dev] [ros-diffs] [sir_richard] 45057: [NTOS]: Fix some bugs and cleanup V8086 code in regards to flags usage. [NTOS]: Add VDM debug spew to see why there's now an invalid opcode on Windows builds of VMWare and certain QEmu combinations. (Not

by James Tabor

Go into ntoskrnl and svn up -r 45013 should take care of it....... On Wed, Jan 13, 2010 at 3:31 AM, Ged Murphy <gedmurphy(a)gmail.com> wrote: > sir_richard, > > Trunk is still broken and is causing issues for some of the dev team. > > You can see the problems in our buildbot test machine: > - Go to the following address : http://build.reactos.org:8010 > - under the x86_(Test) machine, click on the stdio for the 'test' stage. > - You'll see stage 1 complete, the stage 2 bugchecks. > > Could you please address this problem before continuing your work as it's ruining the test system. > The problem is that because our test machine can't run we aren't able to monitor other commits in other areas, meaning we're potentially introducing other bugs that we're now missing. > According to our policy, failure to fix this soon (it's normally 24 hours) will result in us having to freeze development on trunk until the bug is fixed. If we're unable to fix it in a reasonable amount of time then the changes need to be reverted until we have a bootable OS again. > > Regards, > Ged Murphy. > > >

14 years, 9 months

by Ged Murphy

sir_richard, Trunk is still broken and is causing issues for some of the dev team. You can see the problems in our buildbot test machine: - Go to the following address : http://build.reactos.org:8010 - under the x86_(Test) machine, click on the stdio for the 'test' stage. - You'll see stage 1 complete, the stage 2 bugchecks. Could you please address this problem before continuing your work as it's ruining the test system. The problem is that because our test machine can't run we aren't able to monitor other commits in other areas, meaning we're potentially introducing other bugs that we're now missing. According to our policy, failure to fix this soon (it's normally 24 hours) will result in us having to freeze development on trunk until the bug is fixed. If we're unable to fix it in a reasonable amount of time then the changes need to be reverted until we have a bootable OS again. Regards, Ged Murphy. -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of sir_richard(a)svn.reactos.org Sent: 13 January 2010 03:43 To: ros-diffs(a)reactos.org Subject: [ros-diffs] [sir_richard] 45057: [NTOS]: Fix some bugs and cleanup V8086 code in regards to flags usage. [NTOS]: Add VDM debug spew to see why there's now an invalid opcode on Windows builds of VMWare and certain QEmu combinations. (Note: the double fault Author: sir_richard Date: Wed Jan 13 04:43:03 2010 New Revision: 45057 URL: http://svn.reactos.org/svn/reactos?rev=45057&view=rev Log: [NTOS]: Fix some bugs and cleanup V8086 code in regards to flags usage. [NTOS]: Add VDM debug spew to see why there's now an invalid opcode on Windows builds of VMWare and certain QEmu combinations. (Note: the double fault issue is fixed, this is a new issue). Modified: trunk/reactos/ntoskrnl/ke/i386/v86vdm.c Modified: trunk/reactos/ntoskrnl/ke/i386/v86vdm.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/v86vdm.c?… ============================================================================== --- trunk/reactos/ntoskrnl/ke/i386/v86vdm.c [iso-8859-1] (original) +++ trunk/reactos/ntoskrnl/ke/i386/v86vdm.c [iso-8859-1] Wed Jan 13 04:43:03 2010 @@ -12,6 +12,9 @@ #include <ntoskrnl.h> #define NDEBUG #include <debug.h> + +#define KiVdmGetInstructionSize(x) ((x) & 0xFF) +#define KiVdmGetPrefixFlags(x) ((x) & 0xFFFFFF00) /* GLOBALS ********************************************************************/ @@ -51,6 +54,7 @@ ULONG Esp, V86EFlags, TrapEFlags; /* Get current V8086 flags and mask out interrupt flag */ + DbgPrint("VDM: Handling PUSHF (PREFIX [0x%lx])\n", KiVdmGetPrefixFlags(Flags)); V86EFlags = *KiNtVdmState; V86EFlags &= ~EFLAGS_INTERRUPT_MASK; @@ -67,7 +71,7 @@ Esp -= 2; /* Check for OPER32 */ - if (Flags & PFX_FLAG_OPER32) + if (KiVdmGetPrefixFlags(Flags) & PFX_FLAG_OPER32) { /* Save EFlags */ Esp -= 2; @@ -81,7 +85,7 @@ /* Set new ESP and EIP */ TrapFrame->HardwareEsp = (USHORT)Esp; - TrapFrame->Eip += (Flags & 0xFF); + TrapFrame->Eip += KiVdmGetInstructionSize(Flags); /* We're done */ return TRUE; @@ -95,6 +99,7 @@ ULONG Esp, V86EFlags, EFlags, TrapEFlags; /* Build flat ESP */ + DbgPrint("VDM: Handling POPF (PREFIX [0x%lx])\n", KiVdmGetPrefixFlags(Flags)); Esp = (TrapFrame->HardwareSegSs << 4) + (USHORT)TrapFrame->HardwareEsp; /* Read EFlags */ @@ -102,7 +107,7 @@ Esp += 4; /* Check for OPER32 */ - if (!(Flags & PFX_FLAG_OPER32)) + if (!(KiVdmGetPrefixFlags(Flags) & PFX_FLAG_OPER32)) { /* Read correct flags and use correct stack address */ Esp -= 2; @@ -140,7 +145,7 @@ /* FIXME: Check for VDM interrupts */ /* Update EIP */ - TrapFrame->Eip += (Flags & 0xFF); + TrapFrame->Eip += KiVdmGetInstructionSize(Flags); /* We're done */ return TRUE; @@ -187,7 +192,7 @@ /* Push IP */ Esp -= 2; - *(PUSHORT)(Esp) = (USHORT)TrapFrame->Eip + (Flags & 0xFF) + 1; + *(PUSHORT)(Esp) = (USHORT)TrapFrame->Eip + KiVdmGetInstructionSize(Flags) + 1; /* Update ESP */ TrapFrame->HardwareEsp = (USHORT)Esp; @@ -196,11 +201,12 @@ Eip = (TrapFrame->SegCs << 4) + TrapFrame->Eip; /* Now get the *next* EIP address (current is original + the count - 1) */ - Eip += (Flags & 0xFF); + Eip += KiVdmGetInstructionSize(Flags); /* Now read the interrupt number */ Interrupt = *(PUCHAR)Eip; - + DbgPrint("VDM: Handling INT [0x%lx]\n", Interrupt); + /* Read the EIP from its IVT entry */ Interrupt = *(PULONG)(Interrupt * 4); TrapFrame->Eip = (USHORT)Interrupt; @@ -240,12 +246,13 @@ IN ULONG Flags) { ULONG Esp, V86EFlags, EFlags, TrapEFlags, Eip; - + /* Build flat ESP */ + DbgPrint("VDM: Handling IRET (PREFIX [0x%lx])\n", KiVdmGetPrefixFlags(Flags)); Esp = (TrapFrame->HardwareSegSs << 4) + TrapFrame->HardwareEsp; /* Check for OPER32 */ - if (Flags & PFX_FLAG_OPER32) + if (KiVdmGetPrefixFlags(Flags) & PFX_FLAG_OPER32) { /* Build segmented EIP */ TrapFrame->Eip = *(PULONG)Esp; @@ -292,6 +299,7 @@ /* Build flat EIP and check if this is the BOP instruction */ Eip = (TrapFrame->SegCs << 4) + TrapFrame->Eip; + DbgPrint("VDM: Handling IRET EIP @ 0x%p [OPCODE: %lx]\n", Eip, *(PUSHORT)Eip); if (*(PUSHORT)Eip == 0xC4C4) { /* Dispatch the BOP */ @@ -313,11 +321,12 @@ { /* FIXME: Support VME */ - /* disable interrupts */ + /* Disable interrupts */ + DbgPrint("VDM: Handling CLI\n"); KiVdmClearVdmEFlags(EFLAGS_INTERRUPT_MASK); /* Skip instruction */ - TrapFrame->Eip += (Flags & 0xFF); + TrapFrame->Eip += KiVdmGetInstructionSize(Flags); /* Done */ return TRUE; @@ -331,10 +340,11 @@ /* FIXME: Support VME */ /* Enable interrupts */ + DbgPrint("VDM: Handling STI\n"); KiVdmSetVdmEFlags(EFLAGS_INTERRUPT_MASK); /* Skip instruction */ - TrapFrame->Eip += (Flags & 0xFF); + TrapFrame->Eip += KiVdmGetInstructionSize(Flags); /* Done */ return TRUE; @@ -351,7 +361,8 @@ /* Get flat EIP of the *current* instruction (not the original EIP) */ Eip = (TrapFrame->SegCs << 4) + TrapFrame->Eip; - Eip += (Flags & 0xFF) - 1; + DbgPrint("VDM: Handling Opcode @ 0x%p\n", Eip); + Eip += KiVdmGetInstructionSize(Flags) - 1; /* Read the opcode entry */ switch (*(PUCHAR)Eip) @@ -409,6 +420,7 @@ IN ULONG Flags) { /* Increase instruction size */ + DbgPrint("VDM: Handling PREFIX [%lx] Opcode @ 0x%p\n", KiVdmGetPrefixFlags(Flags), TrapFrame->Eip); Flags++; /* Handle the next opcode */ @@ -623,7 +635,9 @@ Tss->IoMapBase = (USHORT)IOPM_OFFSET; /* Switch stacks and work the magic */ + DbgPrint("VDM: Entering V8086 Mode\n"); Ki386SetupAndExitToV86Mode(VdmTeb); + DbgPrint("VDM: Exiting V8086 Mode\n"); /* Restore IOPM */ RtlCopyMemory(&Tss->IoMaps[0].IoMap, Ki386IopmSaveArea, PAGE_SIZE * 2);

14 years, 9 months

Re: [ros-dev] [ros-diffs] [sir_richard] 45052: Patch that fixes VMWare boot (and should fix QEMu/KVM boot on the testbot): [NTOS]: A trap can get us into a state where DS/ES are invalid, making any pointer dereference (on DS/ES segmented memory, not SS, the stack) crash (and probably double-fault). Therefore, we have to be careful to switch to a good DS/ES before touching the TrapFrame pointer, which we don't have in ESP like the ASM code, but in a DS/ES-segmented register. For V8086 traps we can switch to

by Timo Kreuzer

Hi, I suggest the following changes to the current implementation: 1.) Replace the PUSHA in the trap entry code, by a series of MOVs to the correct stack positions. The same for the trap exit code. KiTrapFrameFromPushaStack can be removed then. This would result in more clear, less complex and faster code, with only a few additional assembly instructions in the trap entry macro. The exit could be done either by normal call/return or by a jmp to an exit handler. 2.) Segements should be fixed up before entering C code, as not doing so may introduce possible compiler dependend breakages. It's also much cleaner and there's no reason to do the same stuff later in inline assembly instead of direcly in the asm entry point. The resulting code might looks something like this: /* Allocate KTRAP_FRAME */ sub esp, KTRAP_FRAME_LENGTH - 10 * 4 /* Save integer registers */ mov [esp + KTRAP_FRAME_EBP], ebp mov [esp + KTRAP_FRAME_EBX], ebx mov [esp + KTRAP_FRAME_ESI], esi mov [esp + KTRAP_FRAME_EDI], edi mov [esp + KTRAP_FRAME_EAX], eax mov [esp + KTRAP_FRAME_ECX], ecx mov [esp + KTRAP_FRAME_EDX], edx mov [esp + KTRAP_FRAME_EBX], ebx /* Save segment regs */ mov [esp + KTRAP_FRAME_SEGDS], ds mov [esp + KTRAP_FRAME_SEGES], es /* Fixup segment regs */ mov ax, KGDT_R3_DATA | RPL_MASK mov ds, ax mov es, ax Timo

14 years, 9 months

Re: [ros-dev] [ros-diffs] [dreimer] 45050: Ok, last time I delete my built main tree while playing with clean in a branch! Now clean cleans the branch you are in!

by Colin Finck

dreimer(a)svn.reactos.org wrote: > URL: http://svn.reactos.org/svn/reactos?rev=45050&view=rev FYI, I already have a change like this ready for some months, see http://reactos.colinfinck.de/files/Other_Stuff/Clean.cmd I won't commit it though, because after a suggestion from KJK, I agree that it would be the best if RosBE's basic clean logic goes into the Makefile itself and RosBE's clean scripts only call "make rosbe-clean" (or whatever it'll be called) afterwards. Then no RosBE clean script would ever need to care about the environment variables for object and output pathes again. We would stop duplicating logic in the Makefile and in RosBE and a simple "clean" would always operate on the same tree as a "make" by design. This is another change that should be finished before we release RosBE 1.5, because it'll break compatibility with older revisions (just like the new toolchain will do), and I want to avoid doing this too often. Best regards, Colin

14 years, 9 months

Re: [ros-dev] [ros-diffs] [dreimer] 45050: Ok, last time I delete my built main tree while playing with clean in a branch! Now clean cleans the branch you are in!

by Timo Kreuzer

\o/ <3 <3 <3 dreimer(a)svn.reactos.org schrieb: > Author: dreimer > Date: Mon Jan 11 22:22:52 2010 > New Revision: 45050 > > URL: http://svn.reactos.org/svn/reactos?rev=45050&view=rev > Log: > Ok, last time I delete my built main tree while playing with clean in a branch! > Now clean cleans the branch you are in! > >

14 years, 9 months

Re: [ros-dev] [ros-diffs] [sir_richard] 45041: [NTOS]: Put ASM macros back since the HAL also uses them.

by Gabriel ilardi

Hi, Just for the record, with this revision I can't enter in graphic mode in 2nd stage, I always get this at the end of the drivers loading: (subsystems/win32/win32k/ntuser/sysparams.c:1499) UserSystemParametersInfo called without active windowstation. PuTTYEntered debugger on last-chance exception (Exception Code: 0xc000001d) (Invalid Opcode) kdb:> bt Eip: <00010002> Frames: <43504420> Couldn't access memory at 0x2A2A2A0E! kdb:> Best regards, Gabriel. > Date: Mon, 11 Jan 2010 06:41:19 +0000 > To: ros-diffs(a)reactos.org > From: sir_richard(a)svn.reactos.org > Subject: [ros-diffs] [sir_richard] 45041: [NTOS]: Put ASM macros back since the HAL also uses them. > > Author: sir_richard > Date: Mon Jan 11 07:41:19 2010 > New Revision: 45041 > > URL: http://svn.reactos.org/svn/reactos?rev=45041&view=rev > Log: > [NTOS]: Put ASM macros back since the HAL also uses them. > > > Modified: > trunk/reactos/ntoskrnl/include/internal/i386/asmmacro.S > > Modified: trunk/reactos/ntoskrnl/include/internal/i386/asmmacro.S > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/… > ============================================================================== > --- trunk/reactos/ntoskrnl/include/internal/i386/asmmacro.S [iso-8859-1] (original) > +++ trunk/reactos/ntoskrnl/include/internal/i386/asmmacro.S [iso-8859-1] Mon Jan 11 07:41:19 2010 > @@ -114,6 +114,28 @@ > .endm > > // > +// @name UNHANDLED_V86_PATH > +// > +// This macro prints out that the current code path is for unhandled VDM support > +// > +// @param None > +// > +// @remark None. > +// > +.macro UNHANDLED_V86_PATH > + /* Get EIP */ > + call $+5 > + > + /* Print debug message */ > + push offset _V86UnhandledMsg > + call _DbgPrint > + add esp, 8 > + > + /* Loop indefinitely */ > + jmp $ > +.endm > + > +// > // @name IDT > // > // This macro creates an IDT entry for the given handler > @@ -255,6 +277,58 @@ > .endm > > // > +// @name INVALID_V86_OPCODE > +// > +// This macro creates one or more entries for unhandled V86 Opcodes > +// in the V86 Opcode Table. > +// > +// @param count. > +// Number of entries to generate. > +// > +// @remark None. > +// > +.macro INVALID_V86_OPCODE count > + .rept \count > + .byte 0 > + .endr > +.endm > + > +// > +// @name GENERATE_PREFIX_HANDLER > +// > +// This macro creates a prefix opcode handler. > +// > +// @param None. > +// > +// @remark None. > +// > +.macro GENERATE_PREFIX_HANDLER Name > +.func Opcode&Name&PrefixV86 > +_Opcode&Name&PrefixV86: > + or ebx, PREFIX_FLAG_&Name > + jmp _OpcodeGenericPrefixV86 > +.endfunc > +.endm > + > +// > +// @name INVALID_V86_OPCODE > +// > +// This macro prints out visible message and hangs the computer. > +// > +// @param None. > +// > +// @remark Temporary debugging use. > +// > +.macro UNHANDLED_V86_OPCODE > + /* Print debug message, breakpoint and freeze */ > + push ecx > + push offset V86DebugMsg > + call _DbgPrint > + add esp, 8 > + jmp $ > +.endm > + > +// > // @name TRAP_FIXUPS > // > // This macro contains out-of-line code for various Trap Frame Fixups, such as: > @@ -448,6 +522,96 @@ > cli > jmp 1b > 2: > +.endm > + > +// > +// @name TRAP_PROLOG > +// > +// This macro creates a standard trap entry prologue. > +// It should be used for entry into any kernel trap (KiTrapXx), but not for > +// system calls, which require special handling. > +// > +// @param Label > +// Identifying name of the caller function; will be used to append > +// to the name V86 and DR helper functions, which must already exist. > +// > +// @remark Use as follows: > +// _KiTrap00: > +// /* Push fake error code */ > +// push 0 > +// > +// /* Enter common prologue */ > +// TRAP_PROLOG(0) > +// > +// /* Handle trap */ > +// <Your Trap Code Here> > +// > +.macro TRAP_PROLOG Label EndLabel > + /* Just to be safe, clear out the HIWORD, since it's reserved */ > + mov word ptr [esp+2], 0 > + > + /* Save the non-volatiles */ > + push ebp > + push ebx > + push esi > + push edi > + > + /* Save FS and set it to PCR */ > + push fs > + mov ebx, KGDT_R0_PCR > + .byte 0x66 > + mov fs, bx > + > + /* Save exception list and bogus previous mode */ > + push fs:[KPCR_EXCEPTION_LIST] > + push -1 > + > + /* Save volatiles and segment registers */ > + push eax > + push ecx > + push edx > + push ds > + push es > + push gs > + > + /* Set the R3 data segment */ > + mov ax, KGDT_R3_DATA + RPL_MASK > + > + /* Skip debug registers and debug stuff */ > + sub esp, 0x30 > + > + /* Load the segment registers */ > + .byte 0x66 > + mov ds, ax > + .byte 0x66 > + mov es, ax > + > + /* Check if this interrupt happened in 16-bit mode */ > + cmp esp, 0x10000 > + jb _Ki16BitStackException > + > + /* Set up frame */ > + mov ebp, esp > + > + /* Check if this was from V86 Mode */ > + test dword ptr [ebp+KTRAP_FRAME_EFLAGS], EFLAGS_V86_MASK > + jnz V86_&Label > + > +V86_&EndLabel: > + /* Get current thread */ > + mov ecx, fs:[KPCR_CURRENT_THREAD] > + cld > + > + /* Flush DR7 */ > + and dword ptr [ebp+KTRAP_FRAME_DR7], 0 > + > + /* Check if the thread was being debugged */ > + test byte ptr [ecx+KTHREAD_DEBUG_ACTIVE], 0xFF > + jnz Dr_&Label > + > + /* Set the Trap Frame Debug Header */ > +Dr_&EndLabel: > + SET_TF_DEBUG_HEADER > .endm > > // > @@ -735,6 +899,164 @@ > .endm > > // > +// @name V86_TRAP_PROLOG > +// > +// This macro creates a V86 Trap entry prologue. > +// It should be used for entry into any fast-system call (KiGetTickCount, > +// KiCallbackReturn, KiRaiseAssertion) and the generic system call handler > +// (KiSystemService) > +// > +// @param Label > +// Unique label identifying the name of the caller function; will be > +// used to append to the name of the DR helper function, which must > +// already exist. > +// > +// @remark None. > +// > +.macro V86_TRAP_PROLOG Label EndLabel > + > + /* Skip everything to the error code */ > + sub esp, KTRAP_FRAME_ERROR_CODE > + > + /* Clear the error code */ > + mov word ptr [esp+KTRAP_FRAME_ERROR_CODE+2], 0 > + > + /* Save the registers we'll trample */ > + mov [esp+KTRAP_FRAME_EBX], ebx > + mov [esp+KTRAP_FRAME_EAX], eax > + mov [esp+KTRAP_FRAME_EBP], ebp > + mov [esp+KTRAP_FRAME_ESI], esi > + mov [esp+KTRAP_FRAME_EDI], edi > + > + /* Save PCR and Ring 3 segments */ > + mov ebx, KGDT_R0_PCR > + mov eax, KGDT_R3_DATA + RPL_MASK > + > + /* Save ECX and EDX too */ > + mov [esp+KTRAP_FRAME_ECX], ecx > + mov [esp+KTRAP_FRAME_EDX], edx > + > + /* Set debugging markers */ > + mov dword ptr [esp+KTRAP_FRAME_PREVIOUS_MODE], -1 > + mov dword ptr [esp+KTRAP_FRAME_DEBUGARGMARK], 0xBADB0D00 > + > + /* Now set segments (use OVERRIDE, 0x66) */ > + .byte 0x66 > + mov fs, bx > + .byte 0x66 > + mov ds, ax > + .byte 0x66 > + mov es, ax > + > + /* Set the trap frame in the stack and clear the direction flag */ > + mov ebp, esp > + cld > + > + /* Save the exception list */ > + mov eax, fs:[KPCR_EXCEPTION_LIST] > + mov [esp+KTRAP_FRAME_EXCEPTION_LIST], eax > + > + /* Check if we need debugging */ > + mov eax, dr7 > + test eax, ~DR7_RESERVED_MASK > + mov [esp+KTRAP_FRAME_DR7], eax > + jnz Dr_&Label > + > +Dr_&EndLabel: > +.endm > + > +// > +// @name V86_TRAP_EPILOG > +// > +// This macro creates an epilogue for leaving V86 traps > +// > +// @param None. > +// > +// @remark None. > +// > +.macro V86_TRAP_EPILOG > + > + /* Get the current thread and make it unalerted */ > +ExitBegin: > + mov ebx, PCR[KPCR_CURRENT_THREAD] > + mov byte ptr [ebx+KTHREAD_ALERTED], 0 > + > + /* Check if it has User-mode APCs pending */ > + cmp byte ptr [ebx+KTHREAD_PENDING_USER_APC], 0 > + jne PendingUserApc > + > + /* It doesn't, pop the frame */ > + add esp, KTRAP_FRAME_EDX > + pop edx > + pop ecx > + pop eax > + > + /* Check if DR registers should be restored */ > + test dword ptr [ebp+KTRAP_FRAME_DR7], ~DR7_RESERVED_MASK > + jnz V86DebugRestore > + > + /* Finish popping the rest of the frame, and return to P-mode */ > +V86DebugContinue: > + add esp, 12 > + pop edi > + pop esi > + pop ebx > + pop ebp > + add esp, 4 > + iretd > + > +V86DebugRestore: > + > + /* Get DR0, 1 */ > + xor ebx, ebx > + mov esi, [ebp+KTRAP_FRAME_DR0] > + mov edi, [ebp+KTRAP_FRAME_DR1] > + > + /* Clear DR 7 */ > + mov dr7, ebx > + > + /* Get DR2 and load DR0-2 */ > + mov ebx, [ebp+KTRAP_FRAME_DR2] > + mov dr0, esi > + mov dr1, edi > + mov dr2, ebx > + > + /* Get DR3-7 */ > + mov esi, [ebp+KTRAP_FRAME_DR0] > + mov edi, [ebp+KTRAP_FRAME_DR1] > + mov ebx, [ebp+KTRAP_FRAME_DR7] > + > + /* Load them */ > + mov dr3, esi > + mov dr6, edi > + mov dr7, ebx > + jmp V86DebugContinue > + > +PendingUserApc: > + > + /* Raise to APC level */ > + mov ecx, APC_LEVEL > + call @KfRaiseIrql@4 > + > + /* Save KIRQL and deliver APCs */ > + push eax > + sti > + push ebp > + push 0 > + push UserMode > + call _KiDeliverApc@12 > + > + /* Restore IRQL */ > + pop ecx > + call @KfLowerIrql@4 > + cli > + > + /* Check if we're not in V86 anymore */ > + test dword ptr [ebp+KTRAP_FRAME_EFLAGS], EFLAGS_V86_MASK > + jnz ExitBegin > +.endm > + > +// > // @name TRAP_EPILOG > // > // This macro creates an epilogue for leaving any system trap. > > _________________________________________________________________ Non sei a casa? Prova il nuovo Web Messenger http://www.messenger.it/web/default.aspx

14 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev January 2010