public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Etienne Martineau <etmartin101@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: KVM devices assignment; PCIe AER?
Date: Tue, 26 Oct 2010 13:42:08 -0700	[thread overview]
Message-ID: <20101026204208.GV25455@sequoia.sous-sol.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1010261321390.755@localhost.localdomain>

* Etienne Martineau (etmartin101@gmail.com) wrote:
> ***Background context:
> We are using kvm on a x86 based platform. For performance reason, we
> use devices assignment. The type of devices we have to deal with is
> mostly custom ASICs but we also have standard stuff (ex 82599EB
> 10-GigabitSR-IOV).
> 
> AER handling in guest VM is very important to us. Most of our
> drivers assume timely notification in cases of PCIe AER. Failure to
> provide such support will result in very undesireable behavior at
> the other end :)
> 
> In our cases, AER is not strictly function of the hardware 'quality'
> but also tied to the way the user can interact with the system (by
> pulling a card on the fly for example).
> 
> ***Q35, VFIO:
> I'm aware of the PCIe Q35 chipset work that Isaku is working on. I
> have a college that is working actively on merging the change into
> our qemu-kvm branch.
> 
> I'm also familiar with VFIO. I've seen the work from Alex on the
> qemu VFIO front. Not too sure how this is going to work on qemu-kvm?
> OR maybe it's because I'm confused about the long term plan for user
> space [qemu vs qemu-kvm] branch?

The Plan (TM) is for qemu-kvm to be just a staging branch for qemu.
There are a few bits left in qemu-kvm (I'm sure you're aware since
you're working with them ;) that aren't yet upstream.  The device
assignment code is one of those bits.

Ideally, we could get KVM out of the business of being a device driver
for assigned host devices and move all of that functionality to VFIO.
And when looking at adding significant new functionality like AER,
scoping VFIO would be very useful.

> ***One of the aspect I'm not clear is the strategy for
> device-assignment under KVM?
> A) Move to VFIO; [/dev/iommu, /dev/vfio]

Long term, hopefully VFIO

> B) KVM as a driver for the assigned devices; [sysfs/ ioctls..]

Short term (i.e. current qemu-kvm tree...this is what we have now and
will continue to until plan A) gets more mature).

thanks,
-chris

  reply	other threads:[~2010-10-26 20:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 16:41 KVM devices assignment; PCIe AER? etmartin101
2010-10-26 18:10 ` Alex Williamson
2010-10-26 18:21 ` Chris Wright
2010-10-26 18:37 ` Michael S. Tsirkin
2010-10-26 20:24   ` Etienne Martineau
2010-10-26 20:42     ` Chris Wright [this message]
2010-10-26 22:08       ` Etienne Martineau
2010-10-26 22:15         ` Chris Wright
2010-10-26 22:17           ` Michael S. Tsirkin
2010-10-26 22:47           ` Etienne Martineau
2010-10-26 23:05             ` Chris Wright
2010-10-27  3:51               ` Etienne Martineau
2010-10-27 14:54                 ` Alex Williamson
2010-10-27 18:23                   ` Etienne Martineau
2010-10-27 19:16                     ` Alex Williamson
2010-10-27 21:43                       ` Etienne Martineau
2010-10-27 22:58                         ` Alex Williamson
2010-10-28  4:58                           ` Michael S. Tsirkin
2010-10-28  5:17                             ` Alex Williamson
2010-10-28  5:39                               ` Michael S. Tsirkin
2010-10-28 23:36                           ` Etienne Martineau
2010-10-26 20:54     ` Michael S. Tsirkin
2010-10-26 18:38 ` 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=20101026204208.GV25455@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=alex.williamson@redhat.com \
    --cc=etmartin101@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.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