qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: chrisw@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
	kvm@vger.kernel.org, pugs@cisco.com
Subject: [Qemu-devel] Re: [RFC PATCH 0/5] QEMU VFIO device assignment
Date: Sun, 11 Jul 2010 12:37:17 -0600	[thread overview]
Message-ID: <1278873437.20397.29.camel@x201> (raw)
In-Reply-To: <4C3A0AB1.3070302@redhat.com>

On Sun, 2010-07-11 at 21:17 +0300, Avi Kivity wrote:
> On 07/11/2010 09:09 PM, Alex Williamson wrote:
> > The following series implements QEMU device assignment using the
> > proposed VFIO/UIOMMU kernel interfaces.  See the last patch for
> > further vfio description.  I've tested this on the v2 VFIO patch,
> > with a number of fixes hacked in along the way.  I'll update when
> > Tom releases a new version of VFIO.  Hopefully this will provide
> > some support for the usefulness of such an interfaces.  Thanks,
> >
> >    
> 
> What's the plan for supporting this alongside the existing kvm device 
> assignment code?
> 
> vfio will only exist in very new kernels, so we have to support the old 
> code for a while to give people chance to adjust (say 12-18 months).  

I was thinking that vfio device assignment might be the qemu acceptable
version of device assignment, and we can let kvm style device assignment
live out it's remaining time in the qemu-kvm tree, before it gets
deprecated.

> Ideally we'd have compatible command line syntax with qemu choosing vfio 
> if available and falling back to kvm device assignment if not.

Ideally, yes, but I'm not sure how how feasible that is.  For the
command line root user, the syntax is nearly same (s/pci-assign/vfio/),
but once we start trying to do libvirt based assignment, passing vfiofd
& uiommufd, it will need to know the difference anyway.  Thanks,

Alex

  reply	other threads:[~2010-07-11 18:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-11 18:09 [Qemu-devel] [RFC PATCH 0/5] QEMU VFIO device assignment Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 1/5] qemu_ram_map/unmap: Allow pre-allocated space to be mapped Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 2/5] Minimal RAM API support Alex Williamson
2010-07-11 18:18   ` [Qemu-devel] " Alex Williamson
2010-07-11 18:20   ` Avi Kivity
2010-07-11 18:24     ` Alex Williamson
2010-07-11 18:29       ` Avi Kivity
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 3/5] RAM API: Make use of it for x86 PC Alex Williamson
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 4/5] APIC/IOAPIC EOI callback Alex Williamson
2010-07-11 18:14   ` [Qemu-devel] " Avi Kivity
2010-07-11 18:26     ` Alex Williamson
2010-07-11 18:30       ` Avi Kivity
2010-07-11 18:54         ` Michael S. Tsirkin
2010-07-11 19:21           ` Alex Williamson
2010-07-11 19:23             ` Michael S. Tsirkin
2010-07-11 20:03               ` Alex Williamson
2010-07-11 20:05                 ` Michael S. Tsirkin
2010-07-11 20:12                 ` Michael S. Tsirkin
2010-07-11 21:59                   ` Alex Williamson
2010-07-12  6:33         ` Avi Kivity
2010-07-12  9:05           ` Gleb Natapov
2010-07-12  9:13             ` Avi Kivity
2010-07-11 18:09 ` [Qemu-devel] [RFC PATCH 5/5] VFIO based device assignment Alex Williamson
2010-07-11 18:27   ` [Qemu-devel] " Avi Kivity
2010-07-11 19:38     ` Alex Williamson
2010-07-12  6:37       ` Avi Kivity
2010-07-11 18:17 ` [Qemu-devel] Re: [RFC PATCH 0/5] QEMU VFIO " Avi Kivity
2010-07-11 18:37   ` Alex Williamson [this message]
2010-07-11 18:43     ` Avi Kivity
2010-07-11 20:24       ` Alex Williamson
2010-07-12  6:29         ` Avi Kivity
2010-07-12 11:03           ` Michael S. Tsirkin

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=1278873437.20397.29.camel@x201 \
    --to=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pugs@cisco.com \
    --cc=qemu-devel@nongnu.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).