From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdef ARCH_HAS_DEV_MEM" to archtecture specific file_operations. Date: Mon, 09 Jul 2007 14:20:21 -0500 Message-ID: <1184008821.26508.56.camel@basalt> References: Reply-To: Hollis Blanchard Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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 Cc: Jun Kamada , xen-devel@lists.xensource.com, xen-ppc-devel List-Id: xen-devel@lists.xenproject.org On Sat, 2007-07-07 at 10:01 +0100, Keir Fraser wrote: > > By the way, I wonder how PPC manages to build both drivers/char/mem.c and > drivers/xen/char/mem.c without ARCH_HAS_DEV_MEM? The model is supposed to be > that mem_fops defined by the Xen file is picked up by the generic file. If > !ARCH_HAS_DEV_MEM then that doesn't happen -- so who picks up the Xen > mem_fops? Hmmm, yeah. Looks like we haven't tested that... :) -- Hollis Blanchard IBM Linux Technology Center