From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alex Williamson <alex.williamson@redhat.com>Alex Williamson
<alex.williamson@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Gibson <david@gibson.dropbear.id.au>,
anthony@codemonkey.ws, Alex Graf <agraf@suse.de>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] vfio with iommu groups
Date: Sat, 12 May 2012 17:31:40 +1000 [thread overview]
Message-ID: <4FAE11DC.1050401@ozlabs.ru> (raw)
Hi!
I pulled new VFIO from github, ported to POWER and got some issues/thoughts which I post as patches.
However PCI bridges handling is an open question to discuss.
My test setup includes PCIe card Intel E1000E which looks in the host like this
(cut device names in the tree below as they were too long to look nice):
aik@vpl2:~$ lspci -vt
+-[0003:00]---00.0-[01-ff]----00.0-[02-04]--+-02.0-[03]--+-00.0 Intel Gigabit Ethernet
| | \-00.1 Intel Gigabit Ethernet
| \-04.0-[04]--+-00.0 Intel Gigabit Ethernet
| \-00.1 Intel Gigabit Ethernet
aik@vpl2:~$ lspci
...
0003:00:00.0 PCI bridge: IBM Device 02ea (rev 02)
0003:01:00.0 PCI bridge: Integrated Device Technology, Inc. PES12N3A PCI Express Switch (rev 0e)
0003:02:02.0 PCI bridge: Integrated Device Technology, Inc. PES12N3A PCI Express Switch (rev 0e)
0003:02:04.0 PCI bridge: Integrated Device Technology, Inc. PES12N3A PCI Express Switch (rev 0e)
0003:03:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper)
(rev 06)
0003:03:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper)
(rev 06)
0003:04:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper)
(rev 06)
0003:04:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper)
(rev 06)
At the moment I bind all devices from domain 0003 to the vfio_pci driver and give as many
devices from it to QEMU as I want. vfio-pci owns devices, the guest sees what he needs to see -
ethernet adapters, it works.
However theoretically we might want to show these 3 PCIe bridges as well (but not the root complex).
For example, INTx lines should be swizzled when the guest parses a device tree and
tries to calculate a real IRQ number. VFIO does not handles bridges at all, it treats them as PCI
functions.
Is there any idea what to do with bridges?
--
Alexey
next reply other threads:[~2012-05-12 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 7:31 Alexey Kardashevskiy [this message]
2012-05-14 4:16 ` [Qemu-devel] vfio with iommu groups Alex Williamson
2012-05-14 4:29 ` Benjamin Herrenschmidt
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=4FAE11DC.1050401@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=alex.williamson@redhat.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).