Peter Maydell <peter.maydell@xxxxxxxxxx> writes: > On 30 January 2013 07:02, Markus Armbruster <armbru@xxxxxxxxxx> wrote: >> Anthony Liguori <aliguori@xxxxxxxxxx> writes: >> >> [...] >>> The problems I ran into were (1) this is a lot of work (2) it basically >>> requires that all bus children have been qdev/QOM-ified. Even with >>> something like the ISA bus which is where I started, quite a few devices >>> were not qdevified still. >> >> So what's the plan to complete the qdevification job? Lay really low >> and quietly hope the problem goes away? We've tried that for about >> three years, doesn't seem to work. > > Do we have a list of not-yet-qdevified devices? Maybe we need to > start saying "fix X Y and Z or platform P is dropped from the next > release". (This would of course be easier if we had a way to let users > know that platform P was in danger...) I think that's a good idea. Only problem is identifying pre-qdev devices in the code requires code inspection (grep won't do, I'm afraid). If we agree on a "qdevify or else" plan, I'd be prepared to help with the digging up of devices. -- 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
