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] Meeting Summary taken from Xen-ia64 Next Steps Disc

To: "Yang, Fred" <fred.yang@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Meeting Summary taken from Xen-ia64 Next Steps Discussion during Xen Summit
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Fri, 20 Jan 2006 08:31:13 -0700
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 Jan 2006 15:36:42 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7F740D512C7C1046AB53446D372001730698B625@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Organization: LOSL
References: <7F740D512C7C1046AB53446D372001730698B625@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2006-01-19 at 22:13 -0800, Yang, Fred wrote:

> 1. Physical Memory support for Domain0
>      * PPC port has the similar P2M issue as Xen-ia64
>      * Group agreed P2M is the route to take, the detail implementation
> can be between P2M & VP approaches to change XenLinux as  less as
> possible

   I thought I remember hearing that VP was the goal, but P2M has many
similarities with VP.  I know Dan briefly mentioned this in the BOF, but
we stuck with the P2M notation, presumably because of lack of time.  Can
anyone explain how we jumped back to P2M when it seemed clear after the
ia64 session that both PPC and ia64 were headed towards VP?

>      * To merge P2M into mainline code may cause Xen-ia64-unstable to be
> buggy or unstable for a period of time.
>         Since this is a must feature to go, we should merge the code and
> get community to work together to get system stablized

   I think there needs to be some qualification here.  There are likely
to be bugs and regressions (hopefully few), but we need to ensure some
significant degree of functionality is retained before integrating into
the mainline.  The memory model support is critical for development to
continue, so it's certainly a very high priority for inclusion.

   Thanks for the summary Fred.  It was a pleasure to get to meet
everyone and put faces with names.  Thanks,

        Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


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

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