early_cpu_init() and identify_cpu()

["Jan Beulich" <jbeulich@novell.com>]

Is there any reason (other than having things inherited this way from Linux) that
we cannot call identify_cpu() for the boot CPU at the end of early_cpu_init()
rather than explicitly from __start_xen()? And if not, it would seem reasonable
to me to at once move the two CR4 twiddling pieces out of __start_xen, too.

(I'm not asking because I want to beautify the code, but because I want the
identify to happen earlier, namely I want to fully set up the VESA console as
early as possible, but there I'd like to be able to set MTRRs, which in turn
depends on identify_cpu() having executed.

Thanks, Jan