Hi, For consistency in git-log, please use "qom:" rather than "object:".
Am 23.03.2015 um 13:06 schrieb Paolo Bonzini: > On 23/03/2015 11:36, Peter Crosthwaite wrote: >> I don't think TypeInfo is the right place for this. You can however >> define function hooks for Object in ObjectClass. See the unparent >> field of ObjectClass for a precedent. Agree. > In this case, the right place could be UserCreatable. Maybe, not so familiar with that interface myself. Does object_del allow to delete non-UserCreatable objects? Then it wouldn't help much. > Alternatively... > >> But is a better way to do this to add error handling to >> object_unparent API and override object_unparent for your device in >> question to throw the error? Then your change doesn't have to be >> limited to QMP. > > ... this is also a good choice. Well, I have doubts about asking someone who's not ultimately familiar with that code to refactor the API. For instance, we wouldn't want QEMU on shutdown or in error cases refusing to unparent some object. Doing it at QMP level (ObjectClass/UserCreatable) seems safer, given that Chun Yan's trivial block option fix ended up respinning a QemuOpts refactoring some twenty times before it got merged. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg)
