Thread (1 message) 1 message, 1 author, 2009-06-10

Re: [Qemu-devel] [PATCH 05/11] qemu: MSI-X support functions

From: "Michael S. Tsirkin" <mst@redhat.com>
Date: 2009-06-10 14:47:39

On Wed, Jun 10, 2009 at 03:39:05PM +0100, Paul Brook wrote:
quoted
quoted
If we really need to avoid MSI-X capable devices then that should be done
explicity per-device. i.e. you have a different virtio-net device that
does not use MSI-X.

Paul
Why should it be done per-device?

Because otherwise you end up with the horrible hacks that you're currently 
tripping over: devices have to magically morph into a different device when 
you load a VM.
No, the hacks are there so I that I can support loading and saving from
non-MSI setups in a backward-compatible way.

The flag we are discussing is set at qemu startup and can't change
across load/store.
That's seems just plain wrong to me.
Loading a VM shouldn't not 
do anything that can't happen during normal operation.
At least wrt pci, we are very far from this state: load just overwrites
all registers, readonly or not, which can never happen during normal
operation. And if we "fix" it, and only edit BAR registers, the happy
result will be that we can't add functionality to PCI devices without
breaking guests and/or breaking loading from old images each time.
Paul


-- 
MST
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help