Re: Balloon driver?

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Jun Koi wrote:
> On 6/7/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>> Carsten Otte wrote:
>> > The best approach into this direction I have seen so far is not our
>> > own vdev thing but Rusty's virtio infrastructure. That's what I think
>> > I would start with.
>> >
>> >
>>
>> I agree.  We need a Lego set containing the following bricks:
>>
>> - bus interfaces: pci bus, hypercall-based bus, xenbus
>> - functionality: net driver, block driver
>> - virtio data path: xen rings + grant tables + event channels, kvm rings
>> + kmap_atomic + interrupts
>>
>
> Avi, may you explain what is the role of the "bus interface" in the
> whole picture? To autodetect and probe new virtual device??
>

Yes.  I guess the most important part is to advertise the interrupt line
correctly to the guest OS, so it can apply its policies wrt sharing and
priorities as it wishes.  Hotplug/unplug and autodetection are also
important, but can probably be hacked even without pci.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/