-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should the mptl3.ppn be aligned with the mpt table size (16MB)? #111
Comments
yes (A). the address of the table should be naturally aligned to the size of the table. Will post a PR. |
OK. Then we can see that, when PAW(physical address width) > 46
|
Actually this is specified in Section 3.1
so for your example PAW of 48, mmpt.PPN will refer to a MPTL3 of size 2^5 bytes and aligned to that size, |
OK, thank you. |
This is not correct. mmpt.PPN is a physical page number, not a physical address, so the alignment is at least 4 KiB, regardless of the size of the table. In fact, the last sentence from that paragraph implies the minimum alignment is 16 KiB (4 pages), even though I think it was meant to imply that the minimum alignment is 4 bytes (as it would imply if empt.PPN was an address). |
thanks for catching my error @SiFiveHolland - I misspoke - I meant that the actual entries may occupy less than the min 4KiB page for the L3 entries. thanks for the PR #112 |
Should the mptL3 ppn be aligned with the mpt table size?
for MPTL3, the mptl3.ppn is the base addr for mptL2, which is size of 16MB,
should the mptl3.ppn be
A : aligned with the mpt table size(16MB)?
B: or any addr without any alignment restriction?
The text was updated successfully, but these errors were encountered: