[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Byrne, John (HP Labs)" <john.l.byrne@xxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 8 Sep 2005 14:16:43 -0700
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 08 Sep 2005 21:14:14 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWvZqLq66NFDvT0SxG0t4WzIxQpTQAANxPQAPEyzMAABo/zoAAhfg1QABNlThAAJ/NpUA==
  • Thread-topic: [Xen-ia64-devel] Community effort neededtocatch upwithxen-unstable

> >> BTW, I'll send out the tools change
> >> to xen mailing list, since some common code is changed upon ia64.
> >
> >Yes, it will be interesting to see if it gets in.  I hope it
> >does, but in the past Keir has been resistant to ifdef code.
> >
> >Please keep track of it and let us all know if it gets in!
> 
> Yes, too many ifdefs are unacceptable. If the news is bad, we 
> have to find other way, like trying to catch up with x86 
> behavior closely to reduce such branches. ;-(

Per Keir's response/permission, we can put the patch into
xen-ia64-unstable and he will pull it in the next update.

First, however, it appears that we are behind again... I tried
applying the patch against xen-unstable tip and the patch
applied only with many hunk offsets.  The result didn't
compile (though probably not due to this specific patch).

Dan

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.