2 ms·
hlt handling would be neat to know. IIRC from your earlier posts (and Andrew Jenner's) that was random logic when I kind of expected that to be handled by ucod
by monocasa 4y ago
hlt handling would be neat to know. IIRC from your earlier posts (and Andrew Jenner's) that was random logic when I kind of expected that to be handled by ucode (but I guess makes sense that it's probably one off logic anyway and doesn't really make sense to abstract out into ucode for that one instruction). Do parts of the core get clock gated? Particularly the dynamic pieces that one would expect to drain out. What does recovery from halted state look like internal to the core and is there any other cleanup that needs to occur when starting back up?
- kens 4y agoWhat do you mean "hit handling"? Edit: I guess I need a bigger font :-) There's no clock gating; everything gets the clock. There's not a lot to say about HALT. It stops memory operations and the prefetch queue, so the processor stops processing until it gets an interrupt.
- monocasa 4y ago> What do you mean "hit handling"? Not hit, hlt instruction. > There's no clock gating; everything gets the clock. There's not a lot to say about HALT. It stops memory operations and the prefetch queue, so the processor stops processing until it gets an interrupt. Oh, ok. So ucode is just sitting in that state waiting for Q to fill in for an extra long time is all? Is the prefetch queue flushed or are the next bytes sitting in Q prefetched, simply not presented to ucode?