OpenCourseWare https://www.youtube.com/watch?v=bY8f4DSkQ6M
Take what is one and make it many.
Take what is repeated and make it one, and fast.
Read 1000 patents and extract the abstract refactorings that made the idea possible.
Processors would need to temporarily hang to reconfigure hierarchy. Execution pipelines would stop issuing and resolve all in-process instructions and push registers to a stack, the memory system would need to quiesce the memory system and flush all structures, and finally the processor could rewrite low-level addressing crossbars. Once that's done, pop the registers back into the stack and hope there's no weird interactions with any number of legacy features in any older processor architecture. :)
On the other hand, when reading the title I was preparing for a gory Amiga article. In this case it should be on-chip memory or is my non native english fooling me here? But it was at least in the same spirit ;)