Peter Maydell <peter.maydell@xxxxxxxxxx> writes: > On 8 February 2011 17:13, Markus Armbruster <armbru@xxxxxxxxxx> wrote: >> As far as qdev's concerned, I can see two kinds of to-dos: >> >> * Further develop qdev so that more of the machine init code can becomes >> Âqdev declarations. ÂSpecific ideas welcome. ÂPatches even more, as >> Âalways. >> >> * Convert the remaining devices. ÂThey are typically used only with >> Âoddball machines, which makes the conversion hard to test for anyone >> Âwho's not already using them. >> >> ÂI've said this before: at some point in time (sooner rather than >> Âlater, if you ask me), we need to shoot the stragglers. ÂI'm pretty >> Âoptimistic that any victims worth keeping will receive timely >> Âattention then. > > So on IRC pbrook wrote: > <pbrook> So we have a bunch of devices that nominally claim to use the > qdev infrastructure, but are still making assumptions that qdev was > supposed to remove, so break horribly when you actually try to use it > as intended. > > ...and my question is: where is the documentation on how to do > a good conversion of a device to qdev, how it works, what the > assumptions you can/can't make are, etc ? I can't see anything > relevant in the source tree or on the website, but maybe I'm just > looking in the wrong places... Unfortunately, you're not. Paul created qdev. Others, including Gerd and myself, put it to use in targets we care for, working from the examples Paul set and not much else. We had to grow it some along the way. Still, the brain to pick for what assumptions qdev was supposed to remove is Paul's. -- 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
