CPU为什么会有段？why segment/segmentation ?

最新推荐文章于 2024-09-21 18:24:07 发布

tyt2222008

最新推荐文章于 2024-09-21 18:24:07 发布

阅读量1.5k

点赞数 1

CC 4.0 BY-SA版权

分类专栏：汇编/底层

本文链接：https://blog.youkuaiyun.com/kevin_ut/article/details/8798632

汇编/底层专栏收录该内容

11 篇文章

订阅专栏

本文探讨了CPU中段（segment）存在的历史原因，源于早期16位微计算机的内存限制。IBM PC在1981年引入了段地址系统，以解决1MB内存的寻址问题，而不需要超过16位的地址。通过使用复合地址，每个包含两个16位数，实现了超过64K的内存访问。这种设计允许通过不同的组合方式来指代同一内存位置，如763可以通过多种段偏移组合表示。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

CPU为什么会有段？像cs, ds, ss等等。这个问题困扰了我很久，感觉有了段地址后把问题复杂化了，没必要这么做。

后来翻查资料后才发现，段（segment）的存在原来是有历史因素的：http://homepage.smc.edu/morgan_david/cs40/segmentation.htm

以下是摘抄和个人见解

“Vintage 1980 microcomputers used physical addressing, and confined themselves to using 4-digit hexadecimal numbers (which is the same thing as 16 bits) as addresses. The highest you can count with a 4-digit hexadecimal number is FFFF in hex, equivalent to 65535 in decimal. So no more than 65536 bytes or 64K of memory could be used. Even if you could have installed more, the computer could not have used it for lack of ability to refer to it.”

1980年的程序是只有16bit大小的内存空间的，也就是只支持64k的内存，寻址只能从0000-FFFF，也就是汇编里的

mov edx AFFFF

这样的指令和程序是不会被执行通过的。

The IBM PC appeared in 1981 and was a fundamental redesign of the earlier microcomputer generation. The designers wanted to allow for 1MB of memory, or 16 times as much as the previous 64K limit. However for design reasons they did not wish to use numbers wider than 16 bits in their addressing system. So they overcame the limit by inventing a system of compound addresses. Each compound address contained 2 16-bit numbers, to be interpreted in a special way. These were the first "segmented addresses" in microcomputers. Coinciding with this was the appearance of a new CPU chip design with new registers to facilitate the new addressing method. (The CPU designers at Intel and the PC architects at IBM worked hand-in-glove designing each piece with the other in mind.)

谁知道，一年后的 1981的IBM PC 改版了ＣＰＵ的设计，是为了让内存可以达到１ＭＢ以上，但最关键的一点是又要保持与１９８０年的程序兼容，所以聪明的设计者们就想出了‘复合地址’这样的概念。用两个　１６位的地址复合在一起，来决定实际的物理地址。

在这里有几问题，

问题１.　ｓｅｇｍｅｎｔ地址是谁输入给CPＵ的？程序自己吗？还是定义宏？　

（待回答）

问题２：

when he wishes to talk about 763. He now has a way to talk about it, but has successfully avoided using 3-digit numbers. Note he could land on 763 several other ways. For example, by starting at 750 instead of 760, then advancing 13 instead of 3. Just as the 43 yard line on the gridiron is equivalently a 3 yard gain from the 40, a 13 yard gain from the 30, or a 23 yard gain from the 10. All, same thing. So our engineer could write any of the following to refer to 763:

76:03
75:13
74:23
73:33
72:43
71:53
70:63
69:73
68:83
67:93

问题２：那么，同一个物理地址７６３，竟然有那么多的表达方式，所以有很多地址组合都指向同一个物理地址，那会产生什么后果吗？

问题３：

That's it. He can't let his first number go any lower than 67, because that would leave him short of 763 by more than 99, and the second number can only raise him 99 beyond his first one. You can make up the following rule for converting one of these compound addresses into a non-compound (i.e., regular 3-digit) one: to find the 3-digit linear address, take the left number of the compound address, shift it left one place (i.e., multiply it by 10), then add the right number.

这里意思是说，第一个两位数（像地址67:93里的９３）最多只能给前一个两位数（６７）贡献一个９９的位移，再大过百了，就不行了，于是为了达到　７６３的地址，这里的第一个两位数不能低于６７，如果用的是　６６：９９这样的组合，最大也只是６６０＋９９＝７５９这样的组合，产生不了７６３地址。

结论是：段地址是有限制！那在实际的ＣＰＵ中，这个限制是如何实现的呢？是通过硬件呢？还是通过软件呢？

问题４，在linux里，已经有了paging 这种技术，那么就不用segmentation这样的地址寻址了，是吗？那就给32-bit 寄存器 register们，赋一个 0000 0000 (假设在32位机器里面)，剩下的寻址那就让Offset 地址来做不就行了吗？Offset 地址也是32位的，就是从 0000 0000 ~ FFFF FFFF ，那就是linear address 直接等于 Virtual address, 实际的linux是这么实现的吗？

答：被我猜对了！！！好激动，在Understanding Linux Kernel 第 42页，我们可以看到linux 就是给这些segment descriptor 的 base 值全部赋起了0x0000 0000！！！！