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-ia64-devel

Re: [Xen-ia64-devel] [PATCH] paravirtualize /dev/mem to use X

To: Alex Williamson <alex.williamson@xxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH] paravirtualize /dev/mem to use X
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Mon, 20 Nov 2006 11:47:16 +0900
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 19 Nov 2006 18:47:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1163980199.9305.5.camel@lappy>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20061115061527.GE15884%yamahata@xxxxxxxxxxxxx> <20061116024239.GA20608%yamahata@xxxxxxxxxxxxx> <1163980199.9305.5.camel@lappy>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Sun, Nov 19, 2006 at 04:49:59PM -0700, Alex Williamson wrote:
> On Thu, 2006-11-16 at 11:42 +0900, Isaku Yamahata wrote:
> > The previous patch wasn't transparent.
> > Please apply the attached transparent version.
> > Sorry for confusion.
> > 
> > On Wed, Nov 15, 2006 at 03:15:27PM +0900, Isaku Yamahata wrote:
> > > paraviatualize IA64 /dev/mem to use X.
> > > 
> > > NOTE:
> > > I found that X doens't boot on IA64 with vanilla linux 2.6.16, 2.6.17
> > > because of IA64 valid_mmap_phys_addr_range() definition.
> > > It is fixed on 2.6.18.
> 
> Hi Isaku,
> 
>    Why would we add our own mem.c instead of modifying the existing Xen
> mem.c to support ia64?  I'm a little concerned about the code duplicated
> between these files and the meaning of CONFIG_XEN_DEVMEM.  Thanks,

Reviewing code, I suppose that we need only mmap_mem() to be IA64-specific.
I'll give it a try.

-- 
yamahata

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