Viewing profile — bytefire
bytefire
HN member- Joined
- Sun, Oct 07, 2018, 9:27 AM UTC
- HN karma
- 174
- Public activity
- 27 items
- HN profile
- View on Hacker News ↗
About bytefire
No profile information was provided.
Recent public activity
-
comment
Comment #44466196
Main problem with regular (forward-only time) debugging is a state -- memory, CPU, cache etc -- which is contributed to the bug but is completely lost. With time travel debugging t…
- story
- story
- story
-
comment
Comment #18479594
It's interesting how little known this exception handling mechanism is: https://stackoverflow.com/questions/51761688/linux-driver-tr...
- story
-
comment
Comment #18469021
Thanks. I am actually using this inside a kernel module whose job is to inspect Intel's virtualisation state: https://github.com/bytefire/vmtool
- story
-
comment
Comment #18217913
i see, makes sense. may be a different team from V86 worked on it? Conways law :)
-
comment
Comment #18217906
good point. may be the central idea of how it's implemented isn't too bad: i see hypervisor as a sort of OS kernel for VMs and the transitions from VM to hypervisor - VM exits - ak…
-
comment
Comment #18215745
hi userbinator :) isn't the purpose of virtual 8086 mode somewhat different? i.e. to run real mode applications while the cpu is in protected mode? or did you mean that virtual 808…
-
comment
Comment #18215421
very good, thank you. i'll try to tidy it up
-
comment
Comment #18213798
very interesting and creative use if EPT, will read the link. thanks for sharing
-
comment
Comment #18213791
thank you that means a lot! please do add any information you think is relevant :)
- story
-
comment
Comment #18164826
no you didn't overlook. the article doesn't discuss actual mechanics of DRAM init, so thank you for adding this info :) i know there is a process of memory training whose aim is to…
-
comment
Comment #18164810
you're right, MRC is a major part of FSP but i think FSP does more work than just initialise memory. it also performs some CPU init and also ICH.
-
comment
Comment #18164798
@userbinator thanks for clarification! this is indeed useful and helps understand contradictions.
-
comment
Comment #18162135
> The instruction pointer is the IP register. It is zero. it is 0xfff0, at least according to Intel Software Developer's Manual Volume 3, section 9.1.4 "First Instruction Executed"…
-
comment
Comment #18161315
this is interesting! i am not aware of how this logic is implemented, i.e. the logic of initial state where 12 most significant bits but thanks for enlightening
-
comment
Comment #18160683
@burfog i have updated the post with explanation of how the reset vector address is calculated. thanks for pointing out :)
-
comment
Comment #18160609
ah i see your point. here asserted defines a state and not a way of ensuring a certain condition is met (as in higher level languages). yes "initialised to 1" would also convey sam…
-
comment
Comment #18160528
sorry could you explain what pinned or fixed mean in this context. by asserted, i mean the corresponding bits being set. similar thing to when one says an interrupt line is asserte…
-
comment
Comment #18160130
yes CS not SS. i should fix that. regarding how the CPU addresses 0xffff.fff0 is not exactly specified in the post. actually CS register is loaded with 0xf000 and normally this wou…
-
comment
Comment #18160099
yes true. the article deliberately focuses on reset-vector onwards steps. perhaps it should make that clear in the beginning. the ME mention is just to create a context for the sta…