WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdef ARCH_

To: Jun Kamada <kama@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdef ARCH_HAS_DEV_MEM" to archtecture specific file_operations.
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 11 Jul 2007 11:00:37 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Hollis Blanchard <hollisb@xxxxxxxxxx>
Delivery-date: Wed, 11 Jul 2007 02:58:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070711143610.7F6E.KAMA@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfDolRQkvA5PC+VEdyh5AAX8io7RQ==
Thread-topic: [Xen-devel] Re: [Xen-changelog] [linux-2.6.18-xen] Add "#ifdef ARCH_HAS_DEV_MEM" to archtecture specific file_operations.
User-agent: Microsoft-Entourage/11.3.3.061214
On 11/7/07 06:44, "Jun Kamada" <kama@xxxxxxxxxxxxxx> wrote:

>> We define it in asm/mach-xen/asm/io.h.
>> 
>> However, the patch *is* of questionable value. It guards the only non-static
>> definition in the file with #ifdef ARCH_HAS_DEV_MEM. Which begs the question
>> why you would build the file at all if !ARCH_HAS_DEV_MEM. I'll revert it.
> 
> I'm sorry that I had posted the incomplete patch. I will attach a new
> one modified. The patch resolves ploblems mentioned above?

The case of building drivers/xen/char/mem.c, yet not defining
ARCH_HAS_DEV_MEM, does not seem useful. Who will pick up and use the
mem_fops defined by drivers/xen/char/mem.c?

At the very least this seems abusive of ARCH_HAS_DEV_MEM, and you might be
better off defining a different macro name? But I think you need to explain
to us what it is you're actually trying to achieve.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>