If any bits or encoding that are reserved for future standard use are set within pdte, stop and report "PDT entry misconfigured" (cause = 267).
However, when pdte.reserved bits are set high, it gives "DDT_ENTRY_MISCONFIGURED(cause = 259)" instead of "PDT_ENTRY_MISCONFIGURED(cause = 259)" which is wrong.
Here is the counter-example where we can see that in the 10th cycle when pdt_walk is high, and in the 11th cycle when the process directory entry is accessed, pdte.reserved bits are set high, and in the next cycle, cause_code == 259(DDT_ENTRY_MISCONFIGURED), which is wrong.
malejo97
commented
2 months ago
The Specs state that:
However, when pdte.reserved bits are set high, it gives "DDT_ENTRY_MISCONFIGURED(cause = 259)" instead of "PDT_ENTRY_MISCONFIGURED(cause = 259)" which is wrong.
Here is the counter-example where we can see that in the 10th cycle when pdt_walk is high, and in the 11th cycle when the process directory entry is accessed, pdte.reserved bits are set high, and in the next cycle, cause_code == 259(DDT_ENTRY_MISCONFIGURED), which is wrong.