From: Chris Wright <chrisw@sous-sol.org>
To: etmartin101 <etmartin101@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Isaku Yamahata <yamahata@valinux.co.jp>,
"Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org
Subject: Re: KVM devices assignment; PCIe AER?
Date: Tue, 26 Oct 2010 11:21:06 -0700 [thread overview]
Message-ID: <20101026182106.GS25455@sequoia.sous-sol.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1010260913380.22179@localhost.localdomain>
* etmartin101 (etmartin101@gmail.com) wrote:
> Part of the project I'm working on, we are looking at extending the
> device assignment capabilities to provide support for PCIe AER.
How did you plan to do this? Right now we only provide PCI capabilities
(not Extended Capabilities).
> Ideally, the host would register for AER (for every assigned
> devices) and pass them up to Qemu.
This should be so for devices iff they support AER to begin with.
Having proper chipset support in QEMU (PCIe + AER) also a step.
> As of now, one of the problem is that KVM is not a driver for the
> assigned devices. I've seen Chris's slides from KVM conf 2010 but I
> haven't seen any patches or discussion on that topic...
>
> On another front, I've seen the work from Michael around 'uio_pci_generic'
> and some of his comments:
> " It's expected that more features of interest to virtualization will be
> added to this driver in the future. Possibilities are: mmap for device
> resources, MSI/MSI-X, eventfd (to interface with kvm), iommu."
>
> I think that extending 'uio_pci_generic' to support AER is
> relatively straight forward (assuming eventfd support from UIO).
Did you look at VFIO?
thanks,
-chris
next prev parent reply other threads:[~2010-10-26 18:21 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 [this message]
2010-10-26 18:37 ` Michael S. Tsirkin
2010-10-26 20:24 ` Etienne Martineau
2010-10-26 20:42 ` Chris Wright
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=20101026182106.GS25455@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=etmartin101@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=yamahata@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.