[Top][All Lists]

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

Re: [Qemu-devel] [RFC][PATCH 14/16] kvm: x86: Add user space part for in

From: Avi Kivity
Subject: Re: [Qemu-devel] [RFC][PATCH 14/16] kvm: x86: Add user space part for in-kernel i8259
Date: Mon, 05 Dec 2011 15:14:32 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0

On 12/05/2011 02:47 PM, Jan Kiszka wrote:
> > 
> > (the memory API added unstable names, hopefully the QOM can take over
> > the stable ones and we'll have a good way to denote the unstable ones).
> > 
> OK, maybe - or likely - we should make those device models have the same
> names in QOM once instantiated. But I'm still convinced they should
> remain separated models in contrast to a single model with a property.

What do you mean by separate models?  You share all the code you can,
and don't share the code you can't.  To me, single model == single name.

> The kvm ioapic, e.g., requires an additional property (gsi_base) that is
> meaningless for user space devices. And its interrupts have to be
> wired&configured differently at board model level. So, from the QEMU
> POV, it is a very different device. Just the guest does not notice.

It's like qcow2 and raw/native IO are wire differently, or virtio-net
and vhost-net.  But it's the same IDE device or virtio NIC.

error compiling committee.c: too many arguments to function

reply via email to

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