diff options
| author | John Levon <john.levon@nutanix.com> | 2021-03-09 16:24:27 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-09 16:24:27 +0000 |
| commit | 997536eee6609827b5053afef497f94bc6f6dbf4 (patch) | |
| tree | 5f2c556a8a1a8f5f991f84bb6e4ba975f0574d37 /include | |
| parent | a8242d117118d5191dad69a96e28a21d66fe8b50 (diff) | |
| download | libvfio-user-997536eee6609827b5053afef497f94bc6f6dbf4.zip libvfio-user-997536eee6609827b5053afef497f94bc6f6dbf4.tar.gz libvfio-user-997536eee6609827b5053afef497f94bc6f6dbf4.tar.bz2 | |
remove vfu_irq_message() (#389)
This sends a message to a vfio-user client to trigger an IRQ, instead of writing
to an eventfd. However, this isn't necessary on the cases we care about, where
eventfds *are* available. Furthermore, this isn't something an API user should
need to know about: if we ever care, the better way to do this is to make
vfu_irq_trigger() automatically use a message if an eventfd isn't available.
Signed-off-by: John Levon <john.levon@nutanix.com>
Reviewed-by: Thanos Makatos <thanos.makatos@nutanix.com>
Diffstat (limited to 'include')
| -rw-r--r-- | include/libvfio-user.h | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/include/libvfio-user.h b/include/libvfio-user.h index 4c9ac6f..06013d4 100644 --- a/include/libvfio-user.h +++ b/include/libvfio-user.h @@ -508,22 +508,6 @@ int vfu_irq_trigger(vfu_ctx_t *vfu_ctx, uint32_t subindex); /** - * Sends message to client to trigger an interrupt. - * - * libvfio-user takes care of using the IRQ type (INTx, MSI/X), the caller only - * needs to specify the sub-index. - * This api can be used to trigger interrupt by sending message to client. - * - * @vfu_ctx: the libvfio-user context to trigger interrupt - * @subindex: vector subindex to trigger interrupt on - * - * @returns 0 on success, or -1 on failure. Sets errno. - */ - -int -vfu_irq_message(vfu_ctx_t *vfu_ctx, uint32_t subindex); - -/** * Takes a guest physical address and returns a list of scatter/gather entries * than can be individually mapped in the program's virtual memory. A single * linear guest physical address span may need to be split into multiple |