From: Thanos Makatos <thanos.makatos@nutanix.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Felipe Franciosi <felipe@nutanix.com>
Subject: question about handling MSI-X by VFIO
Date: Tue, 21 Jan 2020 13:36:26 +0000 [thread overview]
Message-ID: <MN2PR02MB6205CD9F680E4E7AEA7E5E518B0D0@MN2PR02MB6205.namprd02.prod.outlook.com> (raw)
I'm passing through a virtual PCI device to a QEMU guest via VFIO/mdev and I
notice that MSI-X interrupts are disabled in the device (MSIXCAP.MXC.MXE is
zero) and the BARs containing the table and PBA (4 and 5 in my case) are never
accessed. However, whenever I fire an MSI-X interrupt from the virtual device
(although I'm not supposed to do so as they're disabled), the guest seems to
correctly receive it. I've started looking at hw/vfio/pci.c and it seems that
VFIO handles MSI-X interrupts there, including masking etc?
next reply other threads:[~2020-01-21 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 13:36 Thanos Makatos [this message]
2020-01-21 17:19 ` question about handling MSI-X by VFIO Alex Williamson
2020-01-23 15:01 ` Thanos Makatos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MN2PR02MB6205CD9F680E4E7AEA7E5E518B0D0@MN2PR02MB6205.namprd02.prod.outlook.com \
--to=thanos.makatos@nutanix.com \
--cc=alex.williamson@redhat.com \
--cc=felipe@nutanix.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).