From: "Michael S. Tsirkin" <mst@redhat.com>
To: etmartin101 <etmartin101@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>, kvm@vger.kernel.org
Subject: Re: KVM devices assignment; PCIe AER?
Date: Tue, 26 Oct 2010 20:37:33 +0200 [thread overview]
Message-ID: <20101026183733.GA17477@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010260913380.22179@localhost.localdomain>
On Tue, Oct 26, 2010 at 09:41:12AM -0700, etmartin101 wrote:
> Chris, Michael et al.
>
> Part of the project I'm working on, we are looking at extending the
> device assignment capabilities to provide support for PCIe AER.
> Ideally, the host would register for AER (for every assigned
> devices) and pass them up to Qemu.
>
> 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).
>
> Any thought?
>
> thanks,
> -Etienne
On the qemu side, patches for aer support are being worked on,
pls take a look, likely there's some synergy there.
On the kernel side, AER for uio sounds fine, but the features listed
above are not yet supported, so you'd have to code them up too.
There's a uiommu driver from Tom Lyon that does the iommu bit.
Alex and Tom have been working on a VFIO driver which is not based on
the uio framework. You can try joining forces.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-26 18:44 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 [this message]
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=20101026183733.GA17477@redhat.com \
--to=mst@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=etmartin101@gmail.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