From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Qemu-devel] [uq/master PATCH 0/7] x86 CPU subclasses, take 7 Date: Fri, 31 Jan 2014 15:50:23 +0100 Message-ID: <52EBB82F.7020001@redhat.com> References: <1391111339-6958-1-git-send-email-ehabkost@redhat.com> <20140131154853.34c41154@thinkpad> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, libvir-list@redhat.com, Jiri Denemark , =?ISO-8859-1?Q?Andreas_F=E4rber?= To: Igor Mammedov , Eduardo Habkost Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32756 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753906AbaAaOuk (ORCPT ); Fri, 31 Jan 2014 09:50:40 -0500 In-Reply-To: <20140131154853.34c41154@thinkpad> Sender: kvm-owner@vger.kernel.org List-ID: Il 31/01/2014 15:48, Igor Mammedov ha scritto: > that's abusing of object-add interface and due to recent changes, object-add > won't accept arbitrary objects. I hope that sooner or later device hotplug will be doable with object-add too. But yes, in the meanwhile device_add could work, and this patch series is in the right direction anyway. > see "[PATCH v1 3/4] add optional 2nd stage initialization to > -object/object-add commands" > > libvirt probably could use device_add instead to the same effect. > > BTW how libvirt would discover values for qom-type=foo? > With qom-list-types. Paolo