1
0
mirror of https://github.com/0xAX/linux-insides.git synced 2024-12-22 14:48:08 +00:00

correct minor mistake - list 3 bits instead of 4

Sentence starts with "The next three bits(40, 41, 42, 43)" Should exclude 43.
This commit is contained in:
Tomas Juocepis 2017-06-06 08:41:10 -05:00 committed by GitHub
parent a5105b4c8d
commit f29bd4aebf

View File

@ -118,7 +118,7 @@ A segment can be of one of the following types:
| 15 1 1 1 1 | Code | Execute/Read, conforming, accessed
```
As we can see the first bit(bit 43) is `0` for a _data_ segment and `1` for a _code_ segment. The next three bits(40, 41, 42, 43) are either `EWA`(*E*xpansion *W*ritable *A*ccessible) or CRA(*C*onforming *R*eadable *A*ccessible).
As we can see the first bit(bit 43) is `0` for a _data_ segment and `1` for a _code_ segment. The next three bits (40, 41, 42) are either `EWA`(*E*xpansion *W*ritable *A*ccessible) or CRA(*C*onforming *R*eadable *A*ccessible).
* if E(bit 42) is 0, expand up other wise expand down. Read more [here](http://www.sudleyplace.com/dpmione/expanddown.html).
* if W(bit 41)(for Data Segments) is 1, write access is allowed otherwise not. Note that read access is always allowed on data segments.
* A(bit 40) - Whether the segment is accessed by processor or not.