Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754179AbYKGIgZ (ORCPT ); Fri, 7 Nov 2008 03:36:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753902AbYKGIgI (ORCPT ); Fri, 7 Nov 2008 03:36:08 -0500 Received: from mga09.intel.com ([134.134.136.24]:60286 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751281AbYKGIgH (ORCPT ); Fri, 7 Nov 2008 03:36:07 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.33,563,1220252400"; d="scan'208";a="357279278" Message-ID: <4913FDE3.8050804@intel.com> Date: Fri, 07 Nov 2008 16:35:47 +0800 From: "Zhao, Yu" User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Greg KH CC: "linux-pci@vger.kernel.org" , "achiang@hp.com" , "grundler@parisc-linux.org" , "mingo@elte.hu" , "jbarnes@virtuousgeek.org" , "matthew@wil.cx" , "randy.dunlap@oracle.com" , "rdreier@cisco.com" , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , "virtualization@lists.linux-foundation.org" Subject: Re: [PATCH 16/16 v6] PCI: document the new PCI boot parameters References: <20081022083809.GA3757@yzhao12-linux.sh.intel.com> <20081022084531.GP3773@yzhao12-linux.sh.intel.com> <20081106043235.GA30292@kroah.com> <4913AA03.5060807@intel.com> <20081107025032.GA12824@kroah.com> <4913B8A5.5010806@intel.com> <20081107061603.GC3860@kroah.com> <4913F34A.8020805@intel.com> <20081107080222.GA6284@kroah.com> <4913F97E.7030408@intel.com> <20081107082432.GA6601@kroah.com> In-Reply-To: <20081107082432.GA6601@kroah.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1477 Lines: 32 Greg KH wrote: > On Fri, Nov 07, 2008 at 04:17:02PM +0800, Zhao, Yu wrote: >>> Well, to do it "correctly" you are going to have to tell the driver to >>> shut itself down, and reinitialize itself. >>> Turns out, that doesn't really work for disk and network devices without >>> dropping the connection (well, network devices should be fine probably). >>> So you just can't do this, sorry. That's why the BIOS handles all of >>> these issues in a PCI hotplug system. >>> How does the hardware people think we are going to handle this in the >>> OS? It's not something that any operating system can do, is it part of >>> the IOV PCI spec somewhere? >> No, it's not part of the PCI IOV spec. >> >> I just want the IOV (and whole PCI subsystem) have more flexibility on >> various BIOSes. So can we reconsider about resource rebalance as boot >> option, or should we forget about this idea? > > As you have proposed it, the boot option will not work at all, so I > think we need to forget about it. Especially if it is not really > needed. I guess at least one thing would work if people don't want to boot twice: give the bus number 0 as rebalance starting point, then all system resources would be reshuffled :-) Thanks, Yu -- 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/