-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 09.03.2012 21:52, schrieb Jan Kiszka: > Andreas, do you expect CPU devices to be ready for qemu 1.1? We > would need them to pass a feature exclusion mask from > machine.compat_props to the (x86) CPU init code. I was sure hoping to! Marcelo and Avi both going into vacation have let me down with the kvmclock patch that you wanted to go through uq/master. http://patchwork.ozlabs.org/patch/141721/ After it didn't make it into Avi's next PULL, I resubmitted it as part of the qom-user series. That's still on the list. Review and tags appreciated. http://patchwork.ozlabs.org/patch/144529/ Also on the list is a patch for a new object_class_get_list() function for sensible -cpu ? handling. http://patchwork.ozlabs.org/patch/143076/ I have been waiting for progress on these prerequisites before posting huge follow-on batches, but I can spam the list right away... The remaining issue was how to solve the struct CPU vs. CPU() issue - my solution on qom-cpu branch is to free the identifier CPUState in a quite invasive but half-scripted renaming. Based on struct CPUState, all targets are long successfully converted and keep needing to be rebased whenever someone moves code to a new microblaze file, adds a new arm board or in-kernel device using "CPUState", etc. Since there's a configure change involved in *-user QOM support, virtually all files get rebuilt on each rebase and that takes quite some time, so getting that in soonish would be appreciated. http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/qom-cpu Andreas - -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iQIcBAEBAgAGBQJPWqljAAoJEPou0S0+fgE/u+kQAInqv/OYlL2zU+hyeKXdJcZ4 RJ9Ne7J1+MOYcOI0p2T4lTImawHmZbF1HQyM9gTYv3EcGoSLm/SgYnHhFOulvPaE dbpuwk3KPHU+1ekvMVhEX89F62rXvMTz8JxO7hSmNAwIU2fIeKKWEAo0tED2tY16 OC2ExnE46+xLpandGJmfnx8vUJ1/PaO6fpd/FLOZbACT75zmdDxjDpF85e6NNsct ysMQ3kNMWcc0RfTU02dPgrhCPc5irEbalaX6BtOnquVQZDH4ypwzKHOZpMfoTF4u QWyxy+NaOVMVBHgHJeGek0wQ4nbihIhrQAn+Hg/h0P+NPuxQ8s7zX4xwqlYwhAHn cdDfN1sVbIvRWkGCXSRJR5eIkPKV+81Afm7/pL26eNlVtSrVV9UnsOJyfyDrtFs/ tSE90n8ZecjARGXUaACboZRalt7Pxl4EGWJwBhsNd5+3xaYvc9/WuTYP1FK1nltk KiBETQXnSY5aTh13erKLjbtYGR5YexXiLIOXvnBD0qQ/LDryHNjslgM8HcShrx4S U9LFAqEq78fgpCXZlzwtnzed341Wuerw3z4jELrSW8GH+R21jMfT9L8lwaHexabh 7YlulgdSpsmCxzhHOUCMeUTFFY6TlPxVk2NhEhQxlzDXdDmm6nd67R9qJIf7d42z CPzkIX+OpKBmorMQREIg =a+ZQ -----END PGP SIGNATURE----- -- 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
