diff options
author | Alexey Kardashevskiy <aik@ozlabs.ru> | 2012-07-19 10:35:07 +1000 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2012-07-19 17:56:42 +0300 |
commit | 932d4a42afa28829fadf3cbfbb0507cc09aafd8b (patch) | |
tree | aac382560039bf5e0404f6ce138db06b60e78c39 /hw/msi.h | |
parent | 0ae1625177aba9ac70beb1556615530ddb18086d (diff) |
msi/msix: added API to set MSI message address and data
Added (msi|msix)_set_message() function for whoever might
want to use them.
Currently msi_notify()/msix_notify() write to these vectors to
signal the guest about an interrupt so the correct values have to
written there by the guest or QEMU.
For example, POWER guest never initializes MSI/MSIX vectors, instead
it uses RTAS hypercalls. So in order to support MSIX for virtio-pci on
POWER we have to initialize MSI/MSIX message from QEMU.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'hw/msi.h')
-rw-r--r-- | hw/msi.h | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -31,6 +31,7 @@ struct MSIMessage { extern bool msi_supported; +void msi_set_message(PCIDevice *dev, MSIMessage msg); bool msi_enabled(const PCIDevice *dev); int msi_init(struct PCIDevice *dev, uint8_t offset, unsigned int nr_vectors, bool msi64bit, bool msi_per_vector_mask); |