Arnd Bergmann wrote:
> On Sunday 08 July 2007, Avi Kivity wrote:
>
>
>>> Alternatively, we could have a mechanism separate from the
>>> virtqueue concept, like a synchronous get_config_data/set_config_data
>>> callback into the host driver.
>>>
>>>
>> You also need to allow the host to notify the guest about configuration
>> changes.
>>
>
> That is much harder to do, it would require a separate interrupt if you
> want to have a device independent mechanism. Most real buses (like PCI)
> don't have this, so I'm not sure it's good to do this at the virtio
> layer. You already listed the media change notification, which can
> be handled without this by either removing and adding the complete
> virtio device, or by using a channel for out-of-band data like scsi.
>
At the very least, we need an interrupt for device hotplug. That same
interrupt can be used to notify the guest about configuration changes
within a device ("rescan the virtbus and all who sail in her").
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/virtualization
