Are we considering virtualization? Because that gets you something like 16 per memory operand.
-
-
-
Replying to @johnregehr @RichFelker
What about xsave? What's the maximum amount of data it writes?
1 reply 0 retweets 1 like -
what about faults when accessing the page table?
1 reply 0 retweets 1 like -
was wanting to avoid all that and get the basic answer :)
1 reply 0 retweets 1 like -
Replying to @johnregehr @gannimo and
Don't forget page faults on the interrupt table when the page fault occurs
3 replies 0 retweets 7 likes -
Replying to @Myriachan @johnregehr and
I think usually at this point the CPU just goes "Oh Sh!!!" and automatically reboots... (IIRC, would need to check)
1 reply 0 retweets 1 like -
Replying to @cr88192 @Myriachan and
I think this would cause a double fault which would try to execute the double fault handler. A triple fault reboots. I'm not positive though
1 reply 0 retweets 1 like -
Replying to @stevecheckoway @Myriachan and
though, if your page-fault handler page-faults in the IDT, likely so too will the double-fault handler, so it is a de-facto triple-fault...
1 reply 0 retweets 0 likes -
Replying to @cr88192 @Myriachan and
Unless you do something insane like locate the IDT near the end of a page so
#PF faults but#DF does not. Otherwise, yeah, triple fault.2 replies 0 retweets 1 like
Yes, tricks with where you put the page boundaries are what my part of the thread was all about, though.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.