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/
Home Products Support Community News


[XenPPC] upstream merge status

To: xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [XenPPC] upstream merge status
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Fri, 30 Jun 2006 16:29:25 -0500
Delivery-date: Fri, 30 Jun 2006 14:29:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
I *thought* once we got the grant table stuff ironed out, we would be
set to merge upstream. As it turns out though, we have some new
outstanding ELF patches.

I've just (re-)sent two patches of ELF stuff. Aside from those, there
are still a couple differences we have, such as this one:
-    unsigned long symtab_addr;
-    unsigned long symtab_len;
+    unsigned int  symtab_addr;
+    unsigned int  symtab_len;
Once I see how those first two patches are committed (or not), I'm
hoping the other outstanding changes in this area aren't critical and
can be reverted. (Maybe there aren't any other than this; I got somewhat
confused by the overlapping changes.)

Anyways, the one other change we're planning to make is changing all the
directory names from "ppc" to "powerpc". Just a cosmetic thing, but it
will match Linux at least.

Then I'll flatten our patch again (omitting domctrl, gpproxy, etc) to
make sure I haven't missed anything, and submit upstream via the
xenppc-merge.hg tree. I expect there will be some discussion and
revision that will need to happen at that point.

In the meantime, the more we add to the PPC tree, the more work we (I)
will have before we can merge, so let's be careful about what we commit

Hollis Blanchard
IBM Linux Technology Center

Xen-ppc-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [XenPPC] upstream merge status, Hollis Blanchard <=