[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v5 06/16] apic: Introduce backend/frontend infra

From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH v5 06/16] apic: Introduce backend/frontend infrastructure for KVM reuse
Date: Tue, 20 Dec 2011 14:57:39 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1

On 12/20/2011 02:54 PM, Anthony Liguori wrote:
In QOM parlance Jan implemented this:

abstract class Object
    abstract class Device
        class APIC: { backend: link<APICBackend> }
    abstract class APICBackend
        class QEMU_APICBackend
        class KVM_APICBackend

I don't fundamentally object to modeling it like this provided that it's
modeled (and visible) through qdev and not done through a one-off

There is no superclass of DeviceState, hence doing it through qdev would mean introducing a new bus type and so on. This would be a superb example of a useless bus that can disappear with QOM, but I don't see why we should take the pain to add it in the first place. :)

We sure can revisit this when the subclassing and interface infrastructures of QOM are merged.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]