Re: Role of the code segment register during "far" CALLs



Hi Skywing

Windows uses a flat address space and does not utilize segmentation (other
than to allow for a convenient way to access the TEB through fs on x86 or gs
on x64).

If Windows did not utilize segmentation, how would it separate
privileged code and stack from non-privileged ones???? Therefore, the
above statement holds only as long as you don't cross the privilege
level.

Anton Bassov


Skywing [MVP] wrote:
Windows uses a flat address space and does not utilize segmentation (other
than to allow for a convenient way to access the TEB through fs on x86 or gs
on x64).

--
Ken Johnson (Skywing)
Windows SDK MVP

"Ranjit" <ranjitiyer@xxxxxxxxx> wrote in message
news:1155937472.309032.37300@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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


.



Relevant Pages

  • Re: Role of the code segment register during "far" CALLs
    ... I read some of your article from which i understood that Windows ... reading it to understand how intersegment far calls are made across ... privilege level as the code segment of my "main" program. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Role of the code segment register during "far" CALLs
    ... Windows uses a flat address space and does not utilize segmentation (other ... CS register is first used as a selector to retrieve a Segment ... code segment boundaries i presume that the code segment register also ...
    (microsoft.public.win32.programmer.kernel)
  • Re: NX bit versus standard permissions?
    ... > seen so far says something like "it will prevent code from executing ... > are normally not given execution privileges, only the code segment. ...
    (comp.lang.asm.x86)
  • Re: Role of the code segment register during "far" CALLs
    ... I read some of your article from which i understood that Windows ... does'nt use call gates to implement intersegment calls. ... privilege level as the code segment of my "main" program. ...
    (microsoft.public.win32.programmer.kernel)
  • Wrong file?
    ... I have a code segment that is occasionally logging an error. ... gcsnapshot is the alias for the table gctempdir\snapgcuserid.dbf. ...
    (microsoft.public.fox.programmer.exchange)