From: Zhao Yan <yan.y.zhao@intel.com>
To: qemu-devel@nongnu.org
Cc: anthony.perard@citrix.com, sstabellini@kernel.org,
xen-devel@lists.xenproject.org, "Zhao Yan" <yan.y.zhao@intel.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>
Subject: [Qemu-devel] [PATCH v3] xen/pt: allow passthrough of devices with bogus interrupt pin
Date: Tue, 4 Dec 2018 02:50:49 -0500 [thread overview]
Message-ID: <20181204075049.10285-1-yan.y.zhao@intel.com> (raw)
For some pci device, even its PCI_INTERRUPT_PIN is not 0, it actually
doesn't support INTx mode, so its machine irq read from host sysfs is 0.
In that case, report PCI_INTERRUPT_PIN as 0 to guest and let passthrough
continue.
Cc: Roger Pau Monné <roger.pau@citrix.com>
Cc: Jan Beulich <JBeulich@suse.com>
Signed-off-by: Zhao Yan <yan.y.zhao@intel.com>
---
v2: fix some coding style issue
v3:
1. let subject be more descriptive (roger)
2. disable INTx assertion if machine irq is 0.(roger)
3. in xen_pt_irqpin_reg_init(), drop the else branch as the default
value for *data is 0. (roger)
---
hw/xen/xen_pt.c | 7 +++++++
hw/xen/xen_pt_config_init.c | 4 +++-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
index e5a6eff..b563837 100644
--- a/hw/xen/xen_pt.c
+++ b/hw/xen/xen_pt.c
@@ -847,6 +847,13 @@ static void xen_pt_realize(PCIDevice *d, Error **errp)
}
machine_irq = s->real_device.irq;
+ if (machine_irq == 0) {
+ XEN_PT_LOG(d, "machine irq is 0\n");
+ cmd |= PCI_COMMAND_INTX_DISABLE;
+ s->machine_irq = 0;
+ goto out;
+ }
+
rc = xc_physdev_map_pirq(xen_xc, xen_domid, machine_irq, &pirq);
if (rc < 0) {
error_setg_errno(errp, errno, "Mapping machine irq %u to"
diff --git a/hw/xen/xen_pt_config_init.c b/hw/xen/xen_pt_config_init.c
index aee31c6..12f71c1 100644
--- a/hw/xen/xen_pt_config_init.c
+++ b/hw/xen/xen_pt_config_init.c
@@ -300,7 +300,9 @@ static int xen_pt_irqpin_reg_init(XenPCIPassthroughState *s,
XenPTRegInfo *reg, uint32_t real_offset,
uint32_t *data)
{
- *data = xen_pt_pci_read_intx(s);
+ if (s->real_device.irq) {
+ *data = xen_pt_pci_read_intx(s);
+ }
return 0;
}
--
2.7.4
next reply other threads:[~2018-12-04 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 7:50 Zhao Yan [this message]
2018-12-04 9:30 ` [Qemu-devel] [PATCH v3] xen/pt: allow passthrough of devices with bogus interrupt pin Roger Pau Monné
2018-12-05 4:59 ` Zhao Yan
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=20181204075049.10285-1-yan.y.zhao@intel.com \
--to=yan.y.zhao@intel.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).