Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754995AbZCIDmp (ORCPT ); Sun, 8 Mar 2009 23:42:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753451AbZCIDme (ORCPT ); Sun, 8 Mar 2009 23:42:34 -0400 Received: from mga09.intel.com ([134.134.136.24]:32127 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752864AbZCIDmc (ORCPT ); Sun, 8 Mar 2009 23:42:32 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.38,327,1233561600"; d="scan'208";a="496136928" From: "Yang, Sheng" Organization: Intel Opensource Technology Center To: Avi Kivity Subject: Re: [PATCH v10 0/7] PCI: Linux kernel SR-IOV support Date: Mon, 9 Mar 2009 11:42:05 +0800 User-Agent: KMail/1.11.0 (Linux/2.6.27-11-generic; KDE/4.2.0; x86_64; ; ) Cc: Matthew Wilcox , "Zhao, Yu" , "jbarnes@virtuousgeek.org" , "linux-pci@vger.kernel.org" , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" References: <1235112888-9524-1-git-send-email-yu.zhao@intel.com> <20090306193329.GB25995@parisc-linux.org> <49B3D678.4050004@redhat.com> In-Reply-To: <49B3D678.4050004@redhat.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200903091142.06628.sheng.yang@intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1377 Lines: 34 On Sunday 08 March 2009 22:30:16 Avi Kivity wrote: > Matthew Wilcox wrote: > > On Tue, Feb 24, 2009 at 12:47:38PM +0200, Avi Kivity wrote: > >> Do those patches allow using a VF on the host (in other words, does the > >> kernel emulate config space accesses)? > > > > SR-IOV hardware handles config space accesses to virtual functions. No > > kernel changes needed for that aspect of it. > > Patches 2 and 3 of the patchset that enables SR/IOV in kvm [1] suggest > that at the config space is only partially implemented. > > [1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/29034 Hi Avi For kernel side, patch 2 is not necessary. Because kernel would read VID/DID directly from pci_dev rather than configuration space, which have been set properly already. And very sorry, for the patch 3. We haven't known exactly what's happened. I think the problem is caused by guest driver, but didn't confirm(and I have some misunderstandings with ZhaoYu for I thought we are agree on the reason, but after confirm with him, he didn't agree). I am doing more investigations to find the real cause. -- regards Yang, Sheng -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/