VOGONS


First post, by superfury

User metadata
Rank l33t
Rank
l33t

What is the parameter for the INVLPG instruction? I know it must be a modr/m byte with all it's requirements. But what happens to it? Is the address in memory(mod<>3) or register(if MOD=3) read for the address to invalidate? Or are registers read and memory used directly(like LEA does)?
Does INVLPG throw page faults when addressing a non-present page?

UniPCemu Git repository
UniPCemu for Android, Windows and PSP on itch.io
Older UniPCemu PC/Android/PSP releases

Reply 2 of 5, by superfury

User metadata
Rank l33t
Rank
l33t

What happens when mod==3 in V86 mode? Will it throw a #UD(because of the MOD) or a #GP(0) because of CPL?

UniPCemu Git repository
UniPCemu for Android, Windows and PSP on itch.io
Older UniPCemu PC/Android/PSP releases

Reply 4 of 5, by superfury

User metadata
Rank l33t
Rank
l33t

Looking at Dosbox, all other opcodes seem to have higher priority on the CPL check than the #UD check, but in the case of INVLPG it's reversed?

So does it throw #UD or #GP when in V86 mode with MOD=3? Which one is checked first?

In the end, #UD and #GP are two totally different exception handlers. The Virtual 8086 monitor might handle them differently.

Looking at Dosbox and Bochs, it seems that in Bochs the #UD is generated AFTER the CPL(thus lower priority), but Dosbox seems to first check the MOD, then CPL after that, which is the reversed order?

Edit: I've just modified it to handle #GP(0) over #UD. So V86 mode will always throw #GP(0), while real/privileged(CPL=0) protected mode will throw #UD when invalid. So privilege having higher priority than #UD.
Would that be correct behaviour(matching Bochs' behaviour)?

Edit: OK. The last I see is a verify sectors command sent to the INT13h handler, after which it starts single-stepping through the code/BIOS, because the trap flag was set?

So perhaps there's some kind of unknown issue with the INT13h function 04h handling?

UniPCemu Git repository
UniPCemu for Android, Windows and PSP on itch.io
Older UniPCemu PC/Android/PSP releases

Reply 5 of 5, by superfury

User metadata
Rank l33t
Rank
l33t

Just have been thinking: does INVLPG use the offset as the linear address, or does it translate the offset of the segment:offset pair to a linear address using the segment descriptor cache first? What if the segment descriptor cache entry(e.g. DS's descriptor cache) used isn't present?

Or what happens when you execute INVLPG on a non-zero based descriptor(e.g. DS.base=0x10000, INVLPG DS:[0])? Does it invalidate page for linear address 0 or the page for linear address 0x10000?

Edit: OK. So if I have to believe Bochs' behaviour, the offset is combined with the descriptor to obtain a linear address(like I thought), then the resulting linear address is used to evict said page from the TLB. So the latter case will happen: the page at 0x10000 will be invalidated.

UniPCemu Git repository
UniPCemu for Android, Windows and PSP on itch.io
Older UniPCemu PC/Android/PSP releases