Re: Role of the code segment register during "far" CALLs
- From: "anton bassov" <soviet_bloke@xxxxxxxxxxx>
- Date: 18 Aug 2006 15:23:12 -0700
Hi mate
Windows does not use far calls, because it uses only 2 code segments
(privileged and non-privileged ones), and makes a transition from
non-privileged to privileged via interrupts and SYSENTER, rather than
far calls via the call gate
Anton Bassov
Ranjit wrote:
Hello,
My question is in view of the memory management unit's role in address
translation, whereby for example, to access code (CALL <address>), the
CS register is first used as a selector to retrieve a Segment
Descriptor that specifies the base of the code segment, to which an
offset gets added to form a linear address which is then forwarded to
the paging unit to generate a physical address. Fine?
The question is, at what step, in the course of executing a far CALL
does the CS register change, and who changes it and where are segment
information for each module stored (PE file?). Since a far call crosses
code segment boundaries i presume that the code segment register also
should change to point to the code segment of the module in which the
called function resides. Just not sure when it happens and who makes it
happen after the far CALL instruction is issued.
I might also be doing something wrong in my experiments, but i don't
see the CS register value (register window) change when i call
CoInitialize (which resides in ole32.dll) from my application's main
method.
Thanks for any guidance on this one.
Ranjit
.
- References:
- Role of the code segment register during "far" CALLs
- From: Ranjit
- Role of the code segment register during "far" CALLs
- Prev by Date: Re: CreateTimerQueueTimer
- Next by Date: Re: Role of the code segment register during "far" CALLs
- Previous by thread: Role of the code segment register during "far" CALLs
- Next by thread: Re: Role of the code segment register during "far" CALLs
- Index(es):
Relevant Pages
|