Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756154AbYJNEqy (ORCPT ); Tue, 14 Oct 2008 00:46:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751635AbYJNEqo (ORCPT ); Tue, 14 Oct 2008 00:46:44 -0400 Received: from palinux.external.hp.com ([192.25.206.14]:34305 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751496AbYJNEqn (ORCPT ); Tue, 14 Oct 2008 00:46:43 -0400 Date: Mon, 13 Oct 2008 22:46:26 -0600 From: Matthew Wilcox To: "Dong, Eddie" Cc: "Zhao, Yu" , linux-pci@vger.kernel.org, Jesse Barnes , Randy Dunlap , Grant Grundler , Alex Chiang , Roland Dreier , Greg KH , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org Subject: Re: [PATCH 6/6 v3] PCI: document the change Message-ID: <20081014044626.GB25780@parisc-linux.org> References: <20081001160706.GI13822@parisc-linux.org> <08DF4D958216244799FC84F3514D70F00235CC69@pdsmsx415.ccr.corp.intel.com> <20081014010827.GX25780@parisc-linux.org> <08DF4D958216244799FC84F3514D70F00235CE27@pdsmsx415.ccr.corp.intel.com> <20081014021435.GA1482@yzhao12-linux.sh.intel.com> <20081014040105.GA25780@parisc-linux.org> <08DF4D958216244799FC84F3514D70F00235CF5E@pdsmsx415.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <08DF4D958216244799FC84F3514D70F00235CF5E@pdsmsx415.ccr.corp.intel.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1685 Lines: 40 On Tue, Oct 14, 2008 at 12:18:40PM +0800, Dong, Eddie wrote: > Matthew Wilcox wrote: > > On Tue, Oct 14, 2008 at 10:14:35AM +0800, Yu Zhao wrote: > >> As Eddie said, we have two problems here: > >> 1) User has to set device specific parameters of a VF > >> when he wants to use this VF with KVM (assign this > >> device to KVM guest). In this case, > >> VF driver is not loaded in the host environment. So > >> operations which > >> are implemented as driver callback (e.g. > >> set_mac_address()) are not supported. > > > > I suspect what you want to do is create, then configure > > the device in the host, then assign it to the guest. > > That is not true. Rememver the created VFs will be destroyed no matter > for PF power event or error recovery conducted reset. > So what we want is: > > Config, create, assign, and then deassign and destroy and then > recreate... Yes, but my point is this all happens in the _host_, not in the _guest_. > Sorry can u explain a little bit more? The SR-IOV patch won't define > what kind of entries should be created or not, we leave network > subsystem to decide what to do. Same for disk subsstem etc. No entries should be created. This needs to be not SR-IOV specific. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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/