[Xen-ia64-devel] RE: xen-ia64-mm

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

Hi Horms --  

I agree that we need to have a separate public tree
temporarily while we are switching domain0 from
P==M to VP+DMA as:

- there are several different components that all need
  to be changed and debugged together which will likely
  take at least several weeks
- several community members will want to contribute
- it will be difficult to use ifdef's for all of these
  changes
- we don't want xen-ia64-unstable.hg to be broken for
  more than a day or two as it is the primary tree
  for merging in core Xen changes from xen-unstable.hg.

Calling it xen-ia64-unstable-mm.hg sounds good,
especially since the primary use (for now) is
to integrate memory management changes.

IMHO, only patches that are necessary for the
domain0 transition (P==M to VP+DMA) should be
accepted into -mm as otherwise it will be difficult
to merge later.

Thanks,
Dan

> -----Original Message-----
> From: Horms [mailto:horms@xxxxxxxxxxxx] 
> Sent: Monday, February 06, 2006 1:15 AM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Cc: Magenheimer, Dan (HP Labs Fort Collins); Isaku Yamahata
> Subject: Re: xen-ia64-mm
> 
> Hi Dan, Hi All,
> 
> I understand from my colleague Yamahata-san that one of the ideas that
> came out of the Xen Summit (which unfortunately I was not able to
> attend) was a proposal for an mm-like tree for ia64-xen. A tree that
> could stand between the bleeding-edge development and 
> breakage, such as
> the VP+DMA work, and the current xen-ia64-unstable.hg and
> xen-unstable.hg trees.  A bit like the role that the
> xen-ia64-unstable-Intel.hg tree has played in the past, but 
> with a more
> generic name.
> 
> I'd like to throw my name hat into the ring to co-ordinate merging and
> maintaining such a tree. I must confess that I am still 
> coming to grips
> with Xen. Though in the course of that I have been getting plenty of
> practice with patching and merging. I also help maintain the Debian
> kernel, which has also given me lots of exposure to patching, merging,
> and coordinating such things over email.
> 
> I'd like to start by kicking off a discussion of what the 
> tree should be
> called (mm is fine by me, but I'm by no means attached to it) and what
> sort of patch acceptance policy we should have - anything as 
> long as it
> builds?
> 
> -- 
> Horms
> 

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