From: sheng qiu <herbert1984106@gmail.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Joerg.Roedel@amd.com, Chris Sanders <sanders.chris@gmail.com>,
kvm@vger.kernel.org
Subject: Re: AMD KVM Pci Passthrough reports device busy
Date: Tue, 5 Jun 2012 20:32:15 -0500 [thread overview]
Message-ID: <CAB7xdikO5B6_-ubBLuySLAjPgUq-6ykt=u71kGH5GGZfh-aGYA@mail.gmail.com> (raw)
In-Reply-To: <201206051039.q55AdXda002609@mail.maya.org>
test
On Tue, Jun 5, 2012 at 5:39 AM, Andreas Hartmann
<andihartmann@01019freenet.de> wrote:
> Hello Alex,
>
> thanks for your efforts!
>
> Maybe, you already know that I'm suffering the same problem :-( with a
> GA-990XA-UD3 (990X chipset).
>
>
> On Mon, 04 Jun 2012 21:44:05 -0600
> Alex Williamson <alex.williamson@redhat.com> wrote:
> [...]
>> I have a setup with an AMD 990FX system and a spare PVR-350 card that I
>> installed to reproduce. The sad answer is that it's nearly impossible
>> to assign PCI devices on these systems due to the aliasing of devices
>> below the PCIe-to-PCI bridge (PCIe devices are much, much easier to
>> assign). If you boot with amd_iommu_dump, you'll see some output like
>> this:
>>
>> AMD-Vi: DEV_ALIAS_RANGE devid: 05:00.0 flags: 00 devid_to: 00:14.4
>> AMD-Vi: DEV_RANGE_END devid: 05:1f.7
>
> here:
> AMD-Vi: DEV_ALIAS_RANGE devid: 06:00.0 flags: 00 devid_to: 00:14.4
> AMD-Vi: DEV_RANGE_END devid: 06:1f.7
>
>
> This means according to your description, the following devices have to
> be unbound here, too (0000:06:07.0 is the device I want to passthrough):
>
> 0000:00:14.0 -> ../../../../devices/pci0000:00/0000:00:14.0
> 0000:00:14.1 -> ../../../../devices/pci0000:00/0000:00:14.1
> 0000:00:14.2 -> ../../../../devices/pci0000:00/0000:00:14.2
> 0000:00:14.3 -> ../../../../devices/pci0000:00/0000:00:14.3
> 0000:00:14.4 -> ../../../../devices/pci0000:00/0000:00:14.4
> 0000:00:14.5 -> ../../../../devices/pci0000:00/0000:00:14.5
> 0000:06:07.0 -> ../../../../devices/pci0000:00/0000:00:14.4/0000:06:07.0
>
>
> These are the following additional devices:
>
> 00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller (rev 42)
> 00:14.1 IDE interface: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 IDE Controller (rev 40) (prog-if 8a [Master SecP PriP])
> 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) (rev 40)
> 00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
> 00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge (rev 40) (prog-if 01 [Subtractive decode])
> 00:14.5 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI2 Controller (prog-if 10 [OHCI])
>
>
> Among them is the sound device and the USB device - no good idea to
> disable them on a desktop.
>
> Disabling 00:14.1 seems to be possible (rmmod pata_atiixp works), but
> I'm getting errors after rebooting the system (the filesystems haven't
> been cleanly unmounted during shutdown).
>
> Anyway, I would have tested it, but I'm getting a compile error while
> compiling qemu. It complains about missing pci/header.h while
> processing hw/vfio_pci.c:49:24. I can't find any pci/header.h. Where
> should it come from?
>
> [...]
>
>> The downside is that VFIO is strict about
>> multifunction devices supporting ACS to prevent peer-to-peer between
>> domains, so will require all of the 14.x devices to be bound to pci-stub
>> as well. On my system, this includes an smbus controller, audio device,
>> lpc controller, and usb device. If AMD could confirm this device
>> doesn't allow peer-to-peer between functions, we could relax this
>> requirement a bit.
>
> Please Joerg, could you take a look at this problem?
>
>
> Thanks,
> kind regards,
> Andreas
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Sheng Qiu
Texas A & M University
Room 332B Wisenbaker
email: herbert1984106@gmail.com
College Station, TX 77843-3259
next prev parent reply other threads:[~2012-06-06 1:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 21:11 AMD KVM Pci Passthrough reports device busy Chris Sanders
2012-06-05 3:44 ` Alex Williamson
2012-06-05 10:39 ` Andreas Hartmann
2012-06-05 14:27 ` Alex Williamson
2012-06-05 15:17 ` Andreas Hartmann
2012-06-05 15:48 ` Alex Williamson
2012-06-05 15:58 ` Andreas Hartmann
2012-06-05 16:19 ` Alex Williamson
2012-06-05 16:55 ` Andreas Hartmann
2012-06-05 18:43 ` Alex Williamson
2012-06-05 20:37 ` Andreas Hartmann
2012-06-05 21:09 ` Alex Williamson
2012-06-05 22:02 ` Andreas Hartmann
2012-06-06 8:12 ` Andreas Hartmann
2012-06-06 8:46 ` Andreas Hartmann
2012-06-06 9:35 ` Andreas Hartmann
2012-06-06 16:39 ` Alex Williamson
2012-06-06 19:17 ` Andreas Hartmann
2012-06-06 10:11 ` Joerg Roedel
2012-06-25 5:55 ` Andreas Hartmann
2012-06-25 11:22 ` Joerg Roedel
2012-07-11 14:26 ` Andreas Hartmann
2012-07-11 16:58 ` Joerg Roedel
2012-07-11 19:32 ` Andreas Hartmann
2012-07-11 20:01 ` Alex Williamson
2012-06-06 1:32 ` sheng qiu [this message]
2012-06-06 3:07 ` Chris Sanders
2012-06-06 3:25 ` Alex Williamson
2012-06-06 3:31 ` Chris Sanders
2012-06-06 5:27 ` 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='CAB7xdikO5B6_-ubBLuySLAjPgUq-6ykt=u71kGH5GGZfh-aGYA@mail.gmail.com' \
--to=herbert1984106@gmail.com \
--cc=Joerg.Roedel@amd.com \
--cc=alex.williamson@redhat.com \
--cc=andihartmann@01019freenet.de \
--cc=kvm@vger.kernel.org \
--cc=sanders.chris@gmail.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).