From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright Subject: Re: KVM devices assignment; PCIe AER? Date: Tue, 26 Oct 2010 11:21:06 -0700 Message-ID: <20101026182106.GS25455@sequoia.sous-sol.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Chris Wright , Isaku Yamahata , "Michael S. Tsirkin" , kvm@vger.kernel.org To: etmartin101 Return-path: Received: from sous-sol.org ([216.99.217.87]:35201 "EHLO sequoia.sous-sol.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753224Ab0JZSVm (ORCPT ); Tue, 26 Oct 2010 14:21:42 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: * 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