From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Avi Kivity <avi@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, aik@ozlabs.ru, benh@kernel.crashing.org
Subject: Re: [RFC PATCH] vfio: VFIO PCI driver for Qemu
Date: Thu, 26 Jul 2012 11:28:35 +0200 [thread overview]
Message-ID: <50110DC3.7000708@01019freenet.de> (raw)
In-Reply-To: <50110163.30209@redhat.com>
Avi Kivity wrote:
> On 07/25/2012 10:53 PM, Alex Williamson wrote:
>> On Wed, 2012-07-25 at 22:30 +0300, Avi Kivity wrote:
>>> On 07/25/2012 08:03 PM, Alex Williamson wrote:
>>>> This adds PCI based device assignment to Qemu using the Linux VFIO
>>>> userspace driver interface. After setting up VFIO device access,
>>>> devices can be added to Qemu guests using the vfio-pci device
>>>> option:
>>>>
>>>> -device vfio-pci,host=1:10.1,id=net0
>>>>
>>>>
>>>
>>> Let's use the same syntax as for kvm device assignment. Then we can
>>> fall back on kvm when vfio is not available. We can also have an
>>> optional parameter kernel-driver to explicitly select vfio or kvm.
>>
>> This seems confusing to me, pci-assign already has options like
>> prefer_msi, share_intx, and configfd that vfio doesn't. I'm sure vfio
>> will eventually get options that pci-assign won't have. How is a user
>> supposed to figure out what options are actually available from -device
>> pci-assign,?
>
> Read the documentation.
>
>> Isn't this the same as asking to drop all model specific
>> devices and just use -device net,model=e1000... hey, we've been there
>> before ;) Thanks,
>
> It's not. e1000 is a guest visible feature. vfio and kvm assignment do
> exactly the same thing, as far as the guest is concerned,
The big difference between vfio and old kvm assignment is: vfio does
work for PCI here, kvm doesn't!
Please let the users decide them self which tool to use!
Sorry,
kind regards,
Andreas
next prev parent reply other threads:[~2012-07-26 9:31 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 [this message]
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
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=50110DC3.7000708@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=benh@kernel.crashing.org \
--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).