From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: [RFC][PATCH 0/10][v3] Enable MSI for KVM assigned device Date: Thu, 30 Oct 2008 16:20:08 +0800 Message-ID: <1225354818-16963-1-git-send-email-sheng@linux.intel.com> Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mga01.intel.com ([192.55.52.88]:6241 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750705AbYJ3IWb (ORCPT ); Thu, 30 Oct 2008 04:22:31 -0400 Sender: kvm-owner@vger.kernel.org List-ID: Hi, Avi Here is v3 for MSI on assigned devices. Still not conclude userspace patch, but the patchset changes a lot since v2. After discuss with Xiantao, we decide to reuse MSI dispatch function for x86 and IA64. I am working on that now. After get it done, I will send out v4. Another significant change is, this patchset not only enable MSI for MSI capable guests(patch 1-9), also enable MSI by default for all guests(patch 10). I implement a MSI to INTx convert in patch 10, which is a little tricky, but don't have much trouble in theory (the only thing we are worried is about device would use different "register" to indicate interrupt reason for INTx mode and MSI mode, but didn't find this kind of device yet). We may need a black/white list for device which can work in this way. This also avoid host sharing interrupt trouble, and provide better scalability for the guest which lacks of MSI capablility. The patch also provide non-sharing host INTx support for legacy devices. So we suggest this can be a default solution for current KVM device assignment support. Comments are welcome! -- regards Yang, Sheng