From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Zhao Yan <yan.y.zhao@intel.com>,
anthony.perard@citrix.com, sstabellini@kernel.org,
roger.pau@citrix.com, JBeulich@suse.com, qemu-devel@nongnu.org
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH v2] xen/pt: Fix a xen passthrough failure
Date: Mon, 3 Dec 2018 14:12:58 +0000 [thread overview]
Message-ID: <f056b5d1-02c2-2ee7-3e37-bc5e4869f0cb@citrix.com> (raw)
In-Reply-To: <20181203050438.6034-1-yan.y.zhao@intel.com>
On 03/12/2018 05:04, Zhao Yan wrote:
> 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.
What causes this problem? It it a non-PCI compliant device? Is it a
device which has legacy lines prohibited?
~Andrew
next prev parent reply other threads:[~2018-12-03 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 5:04 [Qemu-devel] [PATCH v2] xen/pt: Fix a xen passthrough failure Zhao Yan
2018-12-03 11:20 ` Roger Pau Monné
2018-12-04 7:32 ` Zhao Yan
2018-12-03 14:12 ` Andrew Cooper [this message]
2018-12-04 7:36 ` [Qemu-devel] [Xen-devel] " 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=f056b5d1-02c2-2ee7-3e37-bc5e4869f0cb@citrix.com \
--to=andrew.cooper3@citrix.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 \
--cc=yan.y.zhao@intel.com \
/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).