Am 02.01.2012 13:09, schrieb Juan Quintela: > First of all, Happy New Year to everybody (even for the people whose > calendar is different O:-) +1 > Please send in any agenda items you are interested in covering. QOM: If Anthony is available, I'd be interested in hearing an update on the roadmap. In particular, * when can we expect to be able to model SoCs rather than CPUs? Will this affect command line usage - are we going to have '-device ti-tms570' rather than '-cpu cortex-r4' then, or -cpu overriding the container's default? * are the announced remaining 3 series going to touch CPUState? a) Are CPU features being refactored (standardized) for QOM or should we copy current x86 code for controlling ARM FPU? b) Any plans for adding inheritence, e.g., for CPU_COMMON and CPU reset? * what's the effect on VMState? Will VMState continue to coexist with QOM, or does QOM replace VMState at some point? Is it worth introducing new size mechanisms now or should we postpone SD/AHCI migration until QOM is merged? Testing: A brief clarification on scope, goals and relations (overlap?) of all frameworks proposed might be better than a flame war? ;) Regards, Andreas -- 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
