From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Andreas Hartmann <andihartmann@01019freenet.de>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
jan.kiszka@siemens.com
Subject: Re: [PATCH] PCI: Add Ralink RT2800 broken INTx masking quirk
Date: Fri, 08 Jun 2012 12:56:27 +0200 [thread overview]
Message-ID: <4FD1DA5B.9040404@01019freenet.de> (raw)
In-Reply-To: <4FD15BE1.40004@01019freenet.de>
Andreas Hartmann wrote:
> Alex Williamson wrote:
[...]
>> I just pushed a vfio-3.4 branch to my tree at
>> git://github.com/awilliam/linux-vfio.git. Please let me know what you
>> find with this.
>
> Works fine :-) vfio and fglrx and PCIe passthrough.
I rebuild the vfio patch on base of your vfio-3.4 branch and applied it
with the additional quirks patch to the opensuse kernel 3.4.1 (desktop
flavor). Now it's working fine with opensuse, too (PCIe passthrough, PCI
passthrouh and fglrx with a board with AMD chipset 990X)! There have
been slight differences in the two different ways of creating the
complete patch for 3.4 which raised the problem.
Downside is (as you already mentioned), that a lot of devices have to be
unbind to get it working. Would be great, if this could be optimized :-).
Your vfio-3.4 branch helped me a lot!
BTW:
If anybody is interested, I could attach a complete vfio patch for 3.4.
Thanks for your great support and patience,
Andreas
prev parent reply other threads:[~2012-06-08 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 21:23 [PATCH] PCI: Add Ralink RT2800 broken INTx masking quirk Alex Williamson
2012-06-06 21:47 ` Alex Williamson
2012-06-07 6:13 ` Andreas Hartmann
2012-06-07 6:18 ` Andreas Hartmann
2012-06-07 17:05 ` Alex Williamson
2012-06-07 17:18 ` Jan Kiszka
2012-06-07 17:43 ` Alex Williamson
2012-06-07 21:01 ` Andreas Hartmann
2012-06-07 21:25 ` Alex Williamson
2012-06-07 21:42 ` Andreas Hartmann
2012-06-07 22:09 ` Alex Williamson
2012-06-08 1:56 ` Andreas Hartmann
2012-06-08 10:56 ` Andreas Hartmann [this message]
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=4FD1DA5B.9040404@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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).