From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander von Gluck IV <kallisti5@unixzen.com>
Cc: qemu-devel@nongnu.org, alex.williamson@redhat.com
Subject: Re: [Qemu-devel] Debugging PCI Enhanced Allocation - IOMMU of a bridge?
Date: Wed, 12 Sep 2018 13:38:59 -0400 [thread overview]
Message-ID: <20180912133355-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <72e9368e256e81fd69e3f6c65e6dd435@unixzen.com>
On Wed, Sep 12, 2018 at 05:30:29PM +0000, Alexander von Gluck IV wrote:
> Good morning!
>
> I'm working through adding support (or at least ignoring) PCI Enhance
> Allocation devices under Haiku.
> We run into one of these devices, and crash at boot due to attempting to read
> an invalid address.
>
> Our testing showed that with a USB C dongle plugged in, we don't crash. Without
> it plugged in we get
> invalid addresses from PCI
>
> (for a long-drawn out debug ticket, see https://dev.haiku-os.org/ticket/12885 )
>
>
> So, i'm trying to see if I can emulate a PCI bridge with EA under QEMU, I found
> this patch, but it seems
> it wasn't accepted:
> https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg02073.html
v2 never surfaced I think.
> My other thought is since I have access to two laptops implementing this, I
> could attach the bridge to
> qemu via iommu, but the new vfio stuff doesn't seem to work with bridges. :-|
It's fixable, AFAIK no one bothered though. BTW old style kvm dev
assignment is still around but probably doesn't work with bridges
either.
> Anyone know of a way to:
> * emulate a PCI EA in qemu.
Start with above patch, add bios support?
> * attach the local PCI EA bridge to qemu to troubleshoot using real hardware.
> For context, here is the suspect EA device:
>
>
> (no USB C dongle)
> $ lspci -tvnn
> -[0000:00]-+-00.0 Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core
> Processor Host Bridge/DRAM Registers [8086:1910]
> +-1d.6-[06-3e]--
>
> vs
>
> (USB C dongle)
> $ lspci -tvnn
> -[0000:00]-+-00.0 Intel Corporation Skylake Host Bridge/DRAM Registers
> [8086:1904]
> +-1d.6-[06-3e]----00.0-[07-3e]--+-00.0-[08]--
> | +-01.0-[09-3d]--
> | \-02.0-[3e]----00.0 Intel Corporation DSL6340 USB 3.1 Controller [Alpine
> Ridge] [8086:15b5]
>
>
> The bride is at 1d.6 in it's own IOMMU group:
>
> IOMMU group 12
> 00:1d.6 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset
> Family PCI Express Root Port #15 [8086:a11e] (rev f1)
>
> -- Alex
next prev parent reply other threads:[~2018-09-12 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 17:30 [Qemu-devel] Debugging PCI Enhanced Allocation - IOMMU of a bridge? Alexander von Gluck IV
2018-09-12 17:38 ` Michael S. Tsirkin [this message]
2018-09-12 18:21 ` Alex Williamson
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=20180912133355-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kallisti5@unixzen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.