From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: [PATCH 0/10][v4] Enable MSI for KVM assigned device kernel part Date: Fri, 31 Oct 2008 12:50:37 +0800 Message-ID: <1225428647-27614-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]:7773 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752269AbYJaEx0 (ORCPT ); Fri, 31 Oct 2008 00:53:26 -0400 Sender: kvm-owner@vger.kernel.org List-ID: Hi, Avi Here is v4 for MSI on assigned devices. v3->v4 1. After discuss with Xiantao, we decide to delay MSI enabling for IA64, so I've temporary wrapped MSI critical part with #ifdef CONFIG_X86. These are expected to be removed soon before 2.6.28 release. 2. Fix two wrong usage of macro. The userspace patch would follow soon. Another significant change from v2 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