Interrupts can only be handled between instructions (don't ask me how pipelining figures).... except, MVCL has the potential to delay that too long, so it (and a handful of others) were made to be interruptible. Probably, that just means the micro/milli-code program gets interrupted between micro/milli-code instructions. Possibly, that affects its performance negatively. Anyway, for MVCLE, the 4K limit means it can't run very long anyway, so yeah, it does help keep interrupts flowing.
sas On Tue, Oct 20, 2020 at 6:16 PM Keven <k...@k3n.us> wrote: > > > > > I’d say you were both correct. > Keven > > > > > > > > > > > On Tue, Oct 20, 2020 at 5:01 PM -0500, "Paul Gilmartin" < > 00000014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: > > > > > > > > > > > On 2020-10-20, at 14:58:52, Steve Smith wrote: > > > > There's actually a big difference between MVCL being interruptible, and > > MVCLE stopping periodically before it's finished. The latter is not > > interruptible, it just stops before completion periodically for the > program > > to do something else if it wants to. ... > > > I thought it was so that supervisor could dispatch another task. > > -- gil >
