From mboxrd@z Thu Jan 1 00:00:00 1970 From: Markus Armbruster Subject: What to do about non-qdevified devices? (was: KVM call minutes 2013-01-29) Date: Wed, 30 Jan 2013 08:02:03 +0100 Message-ID: <87pq0n887o.fsf_-_@blackfin.pond.sub.org> References: <871ud4gfoa.fsf@elfo.elfo> <510836DD.3010707@suse.de> <87sj5j7jo8.fsf@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain Cc: qemu-devel qemu-devel , Andreas =?utf-8?Q?F=C3=A4rber?= , Alexander Graf , KVM devel mailing list , quintela@redhat.com To: Anthony Liguori Return-path: In-Reply-To: <87sj5j7jo8.fsf@codemonkey.ws> (Anthony Liguori's message of "Tue, 29 Jan 2013 15:39:51 -0600") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org Anthony Liguori 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. [...]