On 22 February 2012 15:37, Andreas Färber <afaer...@suse.de> wrote: > NB: Your cpu-vmstate patches were not applied so far and they appear to > conflict with the plans we've made for redesigning cp15 on ARM: We want > to convert today's static fields to some list and were hoping to have a > mapping function for backwards compatibility. That works easiest in > imperative code.
I thought the idea for cp15 for vmstate was (like ppc) to basically have a uint32_t cp15_regs[512] which we save/load the whole of, and then the mapping function just assigns semantics to some subset of that array? vmstate can do a plain array without problems. (There's an argument that this is just shoving the attempts to maintain backcompat out of vmstate's machinery and into some hand-written code though.) [I have 'write up results of the last week or two's conversations' on my todo list as the next cp15 thing to do...] -- PMM
