----- Andreas Färber <afaerber@xxxxxxx> 写道： > Am 26.05.2014 11:57, schrieb Alexander Graf: > > > > Any reason we're so incredibly inconsistent in what we do during realize > > with reset? I would really prefer to ensure we're doing the same thing > > on all targets. > > > > > > Alex > > > > $ grep -R -A 3 -B 3 qemu_init_vcpu target-* > > target-alpha/cpu.c- CPUState *cs = CPU(dev); > > target-alpha/cpu.c- AlphaCPUClass *acc = ALPHA_CPU_GET_CLASS(dev); > > target-alpha/cpu.c- > > target-alpha/cpu.c: qemu_init_vcpu(cs); > > target-alpha/cpu.c- > > target-alpha/cpu.c- acc->parent_realize(dev, errp); > > target-alpha/cpu.c-} > > Alpha is the main blocker for unifying CPU reset iirc. It does not > implement reset at all and thus is not calling it. The struct was not > designed for zero'ing things, so there's a mix of data fields and > pointers without clear separation to allow memset(), and I have neither > a working alpha test image nor the time to investigate this at the moment. > > WIP here: > https://github.com/afaerber/qemu-cpu/commits/qom-cpu-alpha > https://github.com/afaerber/qemu-cpu/commits/qom-cpu-reset > > According to my commit unicore32 is another odd sock that doesn't reset > the CPU - despite implemented iirc. I'm sorry. I haven't implemented and tested reset function for unicore32 image, but only left the codes there. So, if any change for this function, please modify unicore32's codes correspondingly, and I'll test it later. Regards and thanks, Xuetao > > Regards, > Andreas > > > target-unicore32/cpu.c-{ > > target-unicore32/cpu.c- UniCore32CPUClass *ucc = > > UNICORE32_CPU_GET_CLASS(dev); > > target-unicore32/cpu.c- > > target-unicore32/cpu.c: qemu_init_vcpu(CPU(dev)); > > target-unicore32/cpu.c- > > target-unicore32/cpu.c- ucc->parent_realize(dev, errp); > > target-unicore32/cpu.c-} > > -- > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
