Am 19.12.2014 um 05:26 schrieb Eduardo Habkost: > Many architectures manually call arch-specific TCG initialization at CPU init > time[1], instead of having tcg_init() doing all initialization steps. This > series introduces a tcg_arch_init() function that may be implemented by > architecture-specific code for TCG initialization.
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... Regards, Andreas -- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
