You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello! i have a confusion about convert to va
why when enable long mode the current instruction address(rip register) still look like a physical address in gdb,
and untill these instructions be excuted, then all address show in gdb is virtual address
another question:
in long-mode(.code64), call __startup_64 still use pa 0x1000014 call 0x10001d0, while $1f is va movq $1f, %rax
at this moment, PG is already enabled, why call instruction still use pa 0x10001d0 (__startup_64)
or i make a mistake, 0x10001d0 is already a va, if so, how can i find corresponding pa by boot page table manually
The text was updated successfully, but these errors were encountered:
hello! i have a confusion about convert to va
why when enable long mode the current instruction address(rip register) still look like a physical address in gdb,
and untill these instructions be excuted, then all address show in gdb is virtual address
another question:
in long-mode(.code64),
call __startup_64
still use pa0x1000014 call 0x10001d0
, while $1f is vamovq $1f, %rax
at this moment, PG is already enabled, why call instruction still use pa
0x10001d0 (__startup_64)
or i make a mistake, 0x10001d0 is already a va, if so, how can i find corresponding pa by boot page table manually
The text was updated successfully, but these errors were encountered: