From mboxrd@z Thu Jan 1 00:00:00 1970 From: etmartin101 Subject: KVM devices assignment; PCIe AER? Date: Tue, 26 Oct 2010 09:41:12 -0700 (PDT) Message-ID: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: kvm@vger.kernel.org To: Chris Wright , "Michael S. Tsirkin" Return-path: Received: from mail-pw0-f46.google.com ([209.85.160.46]:42621 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751123Ab0JZQms (ORCPT ); Tue, 26 Oct 2010 12:42:48 -0400 Received: by pwj8 with SMTP id 8so698327pwj.19 for ; Tue, 26 Oct 2010 09:42:47 -0700 (PDT) Sender: kvm-owner@vger.kernel.org List-ID: 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