From: "Jan Beulich" Subject: Re: [PATCH] linux: allow pciback to be built as a module Date: Wed, 08 Mar 2006 17:38:48 +0100 Message-ID: <440F16A8.76F0.0078.0@novell.com> References: <440EC8DD.76F0.0078.0@novell.com> <1141833942.22889.56.camel@moss-tarheels.epoch.ncsc.mil> <560b2260a7406ac0c5b6833ebe99555c@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <560b2260a7406ac0c5b6833ebe99555c@cl.cam.ac.uk> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , Ryan Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >One way around that possible problem would be to define pciback_* >functions that call pcibios_* functions as in the current driver when >compiled into the kernel image, or call the pci_* functions when >compiled as a module. How does that sound? I thought about that option, too, but it seemed a hack to me. I'd like to go that route only when it is known that not using the pcibios_* functions has bad side effects beyond slightly worse performance. Jan