From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Wright <chrisw@osdl.org>
Subject: Re: Fix blatant non-archdep'isms... need help with build
	env change?
Date: Mon, 12 Sep 2005 17:23:25 -0700
Message-ID: <20050913002325.GS7901@shell0.pdx.osdl.net>
References: <516F50407E01324991DD6D07B0531AD5695A20@cacexc12.americas.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <516F50407E01324991DD6D07B0531AD5695A20@cacexc12.americas.cpqcorp.net>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

* Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@hp.com) wrote:
> The problem files (in sparse/include/asm-xen):

I hit some of these as well.

> - synch_bitops.h: explicitly includes
>   asm-i386/synch_bitops.h, should include
>   <asm-xen/asm/synch_bitops.h>

I wondered about that.  Does that mean you have implementation of this,
or it it unnecessary on ia64?

> - hypervisor.h: about half of this header is
>   generic and half is x86-specific.  Should
>   include <asm-xen/asm/hypervisor.h> for
>   arch-dep code.

There's already arch specific files (for hypercall), I wonder if they
could be reused?