On 19/12/2014 10:47, Andreas Färber wrote:
> How do you imagine this to work with multiple CPU types? From the looks
> of it, this is for the target CPU, not the TCG architecture, so
> tcg_arch_init() limits us to one implementation unlike now.
> On the other hand it doesn't seem to be a per-CPU, i.e. CPUClass,
> initialization either...

I think these should go in a separate CPUClass method that is called by
tcg_exec_init (only for first_cpu now; later for all CPUs if each CPU
gets a separate tcg_ctx).

Paolo


Reply via email to