kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, aik@ozlabs.ru, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH] vfio: VFIO PCI driver for Qemu
Date: Thu, 26 Jul 2012 23:23:42 +0200	[thread overview]
Message-ID: <5011B55E.4040707@01019freenet.de> (raw)
In-Reply-To: <1343329880.3125.91.camel@ul30vt>

Alex Williamson wrote:

[I removed qemu-devel because I'm not registered there]

> On Thu, 2012-07-26 at 19:40 +0300, Avi Kivity wrote:
>> On 07/26/2012 07:33 PM, Alex Williamson wrote:
>>>>
>>>> In the common case, on x86 (but I'm repeating myself), the iommu group
>>>> includes just one device, yes?  Could we make pci-stub an alias for the
>>>> corresponding vfio steps?
>>>
>>> PCI bridges masking devices is not as uncommon as you'd like, that's
>>> exactly why Andreas is using VFIO instead of KVM assignment.  
>>
>> Well, we are using it in production for quite a while with few such reports.
>
> In the enterprise space, sure.  In the hobbiest/power user space, I
> suspect users are too often finding that it doesn't work and move on to
> something else.  Maybe we'll know if it's working better if we get more
> complaints about random oddball devices not working because people are
> actually able to get far enough to try it.

I think it's the complete 900-chipset series of AMD (990FX, 990X [the
one I'm using] and 970 - Socket AM3+), which provides the desktop user
with payable IOMMU support (e.g.
http://www.gigabyte.us/products/list.aspx?s=42&jid=7&p=2&v=26 ). I
already read from other users having the same problem.



Thanks,
kind regards,
Andreas

  reply	other threads:[~2012-07-26 21:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 17:03 [RFC PATCH] vfio: VFIO PCI driver for Qemu Alex Williamson
2012-07-25 19:30 ` Avi Kivity
2012-07-25 19:53   ` Alex Williamson
2012-07-26  8:35     ` Avi Kivity
2012-07-26  9:28       ` Andreas Hartmann
2012-07-26  9:40         ` Avi Kivity
2012-07-26 13:45           ` Andreas Hartmann
2012-07-26 14:56       ` Alex Williamson
2012-07-26 15:59         ` Avi Kivity
2012-07-26 16:33           ` Alex Williamson
2012-07-26 16:40             ` Avi Kivity
2012-07-26 19:11               ` [Qemu-devel] " Alex Williamson
2012-07-26 21:23                 ` Andreas Hartmann [this message]
2012-07-26 21:37                   ` Alex Williamson
2012-07-26 16:06         ` Avi Kivity
2012-07-26 16:40           ` Alex Williamson
2012-07-26 16:47             ` Avi Kivity
2012-07-26 15:09 ` Alex Williamson
2012-07-26 16:34 ` Avi Kivity
2012-07-26 17:40   ` [Qemu-devel] " Alex Williamson
2012-07-29 13:47     ` Avi Kivity
2012-07-30 22:29       ` [Qemu-devel] " Alex Williamson
2012-07-31 12:34         ` Avi Kivity
2012-07-31 16:56           ` Alex Williamson
2012-07-27 19:22 ` [Qemu-devel] " Blue Swirl
2012-07-27 20:28   ` Alex Williamson
2012-07-28  2:55   ` Alexey Kardashevskiy

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=5011B55E.4040707@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@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).