Could somebody at XenSource comment on the details of the planned repo changes, i.e. how things will work in the non-sparse world? For example, what header files will live in the HV vs. the kernel? Will the HV, tools, kernel typically be built simultaneously as they are now, or will they be built separately? Thanks, Aron _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 2007-05-30 at 17:46 -0400, Aron Griffis wrote:> Could somebody at XenSource comment on the details of the planned repo > changes, i.e. how things will work in the non-sparse world? For > example, what header files will live in the HV vs. the kernel? > Will the HV, tools, kernel typically be built simultaneously as they > are now, or will they be built separately?>From the point of view of someone who has cloned xen-unstable.hg and run"make world/dist/etc" there should be no difference in what gets built. The current tarball download+unpack+patch+sparse phases will simply be replaced by an hg clone phase. There are already options to build other trees as well, i.e. "make linux-2.6-paravirt-build" will build the latest release of the paravirt_ops tree with Xen support from http://xenbits.xensource.com/ext/paravirt_ops/ Each OS tree is expected to carry its own set of self-contained headers consistent with its needs -- this has always been the case for all trees apart from the sparse tree. For the tree which is going to be derived from the sparse tree the build will check that the hypervisor headers (xen/include/public) and the kernel headers (linux-FOO.hg/include/xen/interface/) are in sync and error out in order to prevent those two trees diverging. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, 2007-05-31 at 09:04 +0100, Ian Campbell wrote:> On Wed, 2007-05-30 at 17:46 -0400, Aron Griffis wrote: > > Could somebody at XenSource comment on the details of the planned repo > > changes, i.e. how things will work in the non-sparse world? For > > example, what header files will live in the HV vs. the kernel? > > Will the HV, tools, kernel typically be built simultaneously as they > > are now, or will they be built separately? > > From the point of view of someone who has cloned xen-unstable.hg and run > "make world/dist/etc" there should be no difference in what gets built. > The current tarball download+unpack+patch+sparse phases will simply be > replaced by an hg clone phase. There are already options to build other > trees as well, i.e. "make linux-2.6-paravirt-build" will build the > latest release of the paravirt_ops tree with Xen support from > http://xenbits.xensource.com/ext/paravirt_ops/ > > Each OS tree is expected to carry its own set of self-contained headers > consistent with its needs -- this has always been the case for all trees > apart from the sparse tree. For the tree which is going to be derived > from the sparse tree the build will check that the hypervisor headers > (xen/include/public) and the kernel headers > (linux-FOO.hg/include/xen/interface/) are in sync and error out in order > to prevent those two trees diverging.Hi Ian, when can we expect to see the new Linux tree created? I''m doing a lot of forward-porting of the PowerPC Linux patches, and so I will have a few generic Linux patches for the new tree. -- Hollis Blanchard IBM Linux Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, 2007-05-31 at 11:02 -0500, Hollis Blanchard wrote:> Hi Ian, when can we expect to see the new Linux tree created? I''m doing > a lot of forward-porting of the PowerPC Linux patches, and so I will > have a few generic Linux patches for the new tree.I want to do it as close to the cut-over point as possible so that I don''t have to keep moving patches across as development continues in the meantime. I hope the cut over in the next week, all that needs to be done is to teach the regression test suite about the new layout. The first version of the new tree will be precisely equal to the patches +sparse at the time it is created -- there''s no actual "development" changes involved in the change so if you have patches which are ready now you may as well add them to the patches/linux-2.6.18 directory and/or sparse tree and I''ll pick them up when the time comes. If they aren''t ready now then so long as they apply on top of the current patches+sparse tree they should be trivial to add to the new tree once it exists. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Ian, I see the sparse tree has been removed from staging now. How do you envision architecture maintained trees fit into this new build system? For instance, I''d like for a tree cloned from xen-ia64-unstable.hg to pull a linux-2.6.18-xen-ia64.hg tree rather than the default upstream tree. I see there''s support for cloning linux-2.6.18-xen.hg from a directory, but it would be quite an error prone kludge to sneak different arch trees in that way. Thoughts? Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2007-06-04 at 08:39 -0600, Alex Williamson wrote:> Hi Ian, > > I see the sparse tree has been removed from staging now. How do you > envision architecture maintained trees fit into this new build system? > For instance, I''d like for a tree cloned from xen-ia64-unstable.hg to > pull a linux-2.6.18-xen-ia64.hg tree rather than the default upstream > tree. I see there''s support for cloning linux-2.6.18-xen.hg from a > directory, but it would be quite an error prone kludge to sneak > different arch trees in that way. Thoughts? Thanks,Hmm. xen-unstable will look at a URL derived from it''s own parent to find the Linux tree this means that for the ppc and ia64 trees it will currently be looking on xenbits for /ext/linux-2.6.18-xen.hg for both archs, this tree doesn''t even exist and I don''t think you''ll want to share a Linux tree. If we define $(XEN_LINUX_ARCH) as "" in the $(XEN_TARGET_ARCH)==x86* case and -$(XEN_TARGET_ARCH) in != x86 case. Mixing that into XEN_LINUX_HGREPO would yield /ext/linux-2.6.18-xen-ia64.hg etc. Does that seem OK to you? Another option would be to move the ia64 and ppc trees into separate subdirectories of /ext/. I''m open to other alternatives. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Ian, On Mon, 2007-06-04 at 17:14 +0100, Ian Campbell wrote:> > Hmm. > > xen-unstable will look at a URL derived from it''s own parent to find the > Linux tree this means that for the ppc and ia64 trees it will currently > be looking on xenbits for /ext/linux-2.6.18-xen.hg for both archs, this > tree doesn''t even exist and I don''t think you''ll want to share a Linux > tree.Agreed, synchronizing updates and pulls would be too much of a headache.> If we define $(XEN_LINUX_ARCH) as "" in the $(XEN_TARGET_ARCH)==x86* > case and -$(XEN_TARGET_ARCH) in != x86 case. Mixing that into > XEN_LINUX_HGREPO would yield /ext/linux-2.6.18-xen-ia64.hg etc. Does > that seem OK to you?But that would only need to be the case if the parent of the xen tree contained xenbits.xensource.com/ext in the path (or some other locally defined path if the parent is a local clone). If we''re building xen-unstable.hg on ia64, it needs to pull linux-2.6.18-xen.hg just as it would on x86. This quickly starts to sound like rather complicated rules.> Another option would be to move the ia64 and ppc trees into separate > subdirectories of /ext/. I''m open to other alternatives.So far, this sounds like the best option. This way it would work just like the staging tree builds and would hopefully be less likely to get broken. We might also gain some flexibility in being able to create new repos in the subdirectory. Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2007-06-04 at 11:25 -0600, Alex Williamson wrote:> > > Another option would be to move the ia64 and ppc trees into separate > > subdirectories of /ext/. I''m open to other alternatives. > > So far, this sounds like the best option. This way it would work > just like the staging tree builds and would hopefully be less likely > to get broken. We might also gain some flexibility in being able to > create new repos in the subdirectory. Thanks,If you''re suggesting moving all PPC repositories, including the Linux tree, into http://xenbits.xensource.com/ext/powerpc/ , then that''s fine with me. Also, we want to replace xenppc-unstable.hg with a copy of xenppc-unstable-merge.hg, so it would make sense to do this at the same time. The issue is that xenppc-unstable.hg has a *lot* of non-upstream history, and Keir doesn''t want to pull it all into xen-unstable.hg. xenppc-unstable-merge.hg is much cleaner. -- Hollis Blanchard IBM Linux Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2007-06-04 at 12:46 -0500, Hollis Blanchard wrote:> On Mon, 2007-06-04 at 11:25 -0600, Alex Williamson wrote: > > > > > Another option would be to move the ia64 and ppc trees into separate > > > subdirectories of /ext/. I''m open to other alternatives. > > > > So far, this sounds like the best option. This way it would work > > just like the staging tree builds and would hopefully be less likely > > to get broken. We might also gain some flexibility in being able to > > create new repos in the subdirectory. Thanks, > > If you''re suggesting moving all PPC repositories, including the Linux > tree, into http://xenbits.xensource.com/ext/powerpc/ , then that''s fine > with me.Yep, I think this is the way to go. So we''ll have: http://xenbits.xensource.com/ext/powerpc/ http://xenbits.xensource.com/ext/ia64/ Each will have a linux-2.6.18-xen.hg repo in it that will be maintained by the arch maintainers and used for pulls into upstream. The default arch Xen branch needs to be moved into the directory as well. I also think it might be good to standardize on names. I''d like the xen-ia64-unstable.hg repo to be renamed to xen-unstable.hg. This way we''ll end up with common names like: /xen-unstable.hg /linux-2.6.18-xen.hg /staging/xen-unstable.hg /staging/linux-2.6.18-xen.hg /ext/ia64/xen-unstable.hg /ext/ia64/linux-2.6.18-xen.hg Sound good? Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2007-06-04 at 13:02 -0600, Alex Williamson wrote:> On Mon, 2007-06-04 at 12:46 -0500, Hollis Blanchard wrote: > > On Mon, 2007-06-04 at 11:25 -0600, Alex Williamson wrote: > > > > > > > Another option would be to move the ia64 and ppc trees into separate > > > > subdirectories of /ext/. I''m open to other alternatives. > > > > > > So far, this sounds like the best option. This way it would work > > > just like the staging tree builds and would hopefully be less likely > > > to get broken. We might also gain some flexibility in being able to > > > create new repos in the subdirectory. Thanks, > > > > If you''re suggesting moving all PPC repositories, including the Linux > > tree, into http://xenbits.xensource.com/ext/powerpc/ , then that''s fine > > with me. > > Yep, I think this is the way to go. So we''ll have: > > http://xenbits.xensource.com/ext/powerpc/ > http://xenbits.xensource.com/ext/ia64/ > > Each will have a linux-2.6.18-xen.hg repo in it that will be maintained > by the arch maintainers and used for pulls into upstream. The default > arch Xen branch needs to be moved into the directory as well. I also > think it might be good to standardize on names. I''d like the > xen-ia64-unstable.hg repo to be renamed to xen-unstable.hg. This way > we''ll end up with common names like: > > /xen-unstable.hg > /linux-2.6.18-xen.hg > /staging/xen-unstable.hg > /staging/linux-2.6.18-xen.hg > /ext/ia64/xen-unstable.hg > /ext/ia64/linux-2.6.18-xen.hg > > Sound good? Thanks,Sounds good to me. -- Hollis Blanchard IBM Linux Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2007-06-04 at 14:15 -0500, Hollis Blanchard wrote:> > This way we''ll end up with common names like: > > > > /xen-unstable.hg > > /linux-2.6.18-xen.hg > > /staging/xen-unstable.hg > > /staging/linux-2.6.18-xen.hg > > /ext/ia64/xen-unstable.hg > > /ext/ia64/linux-2.6.18-xen.hg > > > > Sound good? Thanks, > > Sounds good to me.I''ll look into making these changes tomorrow, with symlinks so the old names remain valid hopefully. (I presume you need someone at XenSource to do the moves for you?) Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2007-06-04 at 22:38 +0100, Ian Campbell wrote:> On Mon, 2007-06-04 at 14:15 -0500, Hollis Blanchard wrote: > > > This way we''ll end up with common names like: > > > > > > /xen-unstable.hg > > > /linux-2.6.18-xen.hg > > > /staging/xen-unstable.hg > > > /staging/linux-2.6.18-xen.hg > > > /ext/ia64/xen-unstable.hg > > > /ext/ia64/linux-2.6.18-xen.hg > > > > > > Sound good? Thanks, > > > > Sounds good to me. > > I''ll look into making these changes tomorrow, with symlinks so the old > names remain valid hopefully. > > (I presume you need someone at XenSource to do the moves for you?)Yes. Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian, Any chance you can wire up the email notifications again? -JX On Jun 4, 2007, at 5:38 PM, Ian Campbell wrote:> On Mon, 2007-06-04 at 14:15 -0500, Hollis Blanchard wrote: >>> This way we''ll end up with common names like: >>> >>> /xen-unstable.hg >>> /linux-2.6.18-xen.hg >>> /staging/xen-unstable.hg >>> /staging/linux-2.6.18-xen.hg >>> /ext/ia64/xen-unstable.hg >>> /ext/ia64/linux-2.6.18-xen.hg >>> >>> Sound good? Thanks, >> >> Sounds good to me. > > I''ll look into making these changes tomorrow, with symlinks so the old > names remain valid hopefully. > > (I presume you need someone at XenSource to do the moves for you?) > > Ian. > > > _______________________________________________ > Xen-ppc-devel mailing list > Xen-ppc-devel@lists.xensource.com > http://lists.xensource.com/xen-ppc-devel_______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
On Mon, 2007-06-18 at 13:40 -0400, Jimi Xenidis wrote:> Any chance you can wire up the email notifications again?I''d gladly do so if I had even the foggiest clue how. I''d assumed there would be a hook in .hg/hgrc, ~/.hgrc or /etc/hgrc but I can''t find anything of the sort anywhere on xenbits. James? What''s the secret? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
We''re using our own "patchbot" script which pre-dates hg notification support. I''d be keen to change to the latter for these trees. Any objections? James> -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@XenSource.com] > Sent: 18 June 2007 19:14 > To: Jimi Xenidis > Cc: Hollis Blanchard; xen-devel@lists.xensource.com; James > Bulpin; Aron Griffis; xen-ppc-devel; Alex Williamson; xen-ia64-devel > Subject: Re: [XenPPC] Re: [Xen-devel] new repo layout? > > On Mon, 2007-06-18 at 13:40 -0400, Jimi Xenidis wrote: > > Any chance you can wire up the email notifications again? > > I''d gladly do so if I had even the foggiest clue how. I''d > assumed there would be a hook in .hg/hgrc, ~/.hgrc or > /etc/hgrc but I can''t find anything of the sort anywhere on xenbits. > > James? What''s the secret? > > Ian. > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Jun 18, 2007, at 3:19 PM, James Bulpin wrote:> We''re using our own "patchbot" script which pre-dates hg notification > support. I''d be keen to change to the latter for these trees. Any > objections?Oh that would be awesome! -JX _______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Jimmy Markakis
2007-Jun-18 19:26 UTC
[Xen-ia64-devel] RE: [XenPPC] Re: [Xen-devel] new repo layout?
Where may one obtain the latest copy of XEN for PPC? Also, will XEN support x86 virtualization (emulation or something similar) on POWER architecture? Thanks, James Markakis -----Original Message----- From: xen-ppc-devel-bounces@lists.xensource.com [mailto:xen-ppc-devel-bounces@lists.xensource.com] On Behalf Of James Bulpin Sent: Monday, June 18, 2007 3:20 PM To: Ian Campbell; Jimi Xenidis Cc: xen-devel@lists.xensource.com; Hollis Blanchard; James Bulpin; Aron Griffis; xen-ppc-devel; Alex Williamson; xen-ia64-devel Subject: RE: [XenPPC] Re: [Xen-devel] new repo layout? We''re using our own "patchbot" script which pre-dates hg notification support. I''d be keen to change to the latter for these trees. Any objections? James> -----Original Message----- > From: Ian Campbell [mailto:Ian.Campbell@XenSource.com] > Sent: 18 June 2007 19:14 > To: Jimi Xenidis > Cc: Hollis Blanchard; xen-devel@lists.xensource.com; James > Bulpin; Aron Griffis; xen-ppc-devel; Alex Williamson; xen-ia64-devel > Subject: Re: [XenPPC] Re: [Xen-devel] new repo layout? > > On Mon, 2007-06-18 at 13:40 -0400, Jimi Xenidis wrote: > > Any chance you can wire up the email notifications again? > > I''d gladly do so if I had even the foggiest clue how. I''d > assumed there would be a hook in .hg/hgrc, ~/.hgrc or > /etc/hgrc but I can''t find anything of the sort anywhere on xenbits. > > James? What''s the secret? > > Ian. > > >_______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ Campbell & Company, Inc.: The information in this e-mail may contain privileged/confidential information. If you are not the intended recipient, you must not read, use, copy or disseminate the information or take any action in reliance thereupon. If you have received this e-mail in error, please notify Campbell & Company, Inc. immediately by e-mail or telephone and delete the e-mail and any attachments from any computer. The information in this e-mail does not constitute an offer to sell or the solicitation of an offer to buy any securities in any jurisdiction or for the benefit of any person. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Dramatically pruning CC list.] You can get it from xen-unstable.hg. It only runs on PowerPC 970, and unfortunately that does not include Apple G5s due to firmware lockout. Xen does not allow you to run x86 code on PowerPC because that is emulation. For that problem, you might try qemu or IBM''s "System p Application Virtual Environment". On Mon, 2007-06-18 at 15:26 -0400, Jimmy Markakis wrote:> Where may one obtain the latest copy of XEN for PPC? Also, will XEN > support x86 virtualization (emulation or something similar) on POWER > architecture? > Thanks, > James Markakis > > -----Original Message----- > From: xen-ppc-devel-bounces@lists.xensource.com > [mailto:xen-ppc-devel-bounces@lists.xensource.com] On Behalf Of James > Bulpin > Sent: Monday, June 18, 2007 3:20 PM > To: Ian Campbell; Jimi Xenidis > Cc: xen-devel@lists.xensource.com; Hollis Blanchard; James Bulpin; Aron > Griffis; xen-ppc-devel; Alex Williamson; xen-ia64-devel > Subject: RE: [XenPPC] Re: [Xen-devel] new repo layout? > > We''re using our own "patchbot" script which pre-dates hg notification > support. I''d be keen to change to the latter for these trees. Any > objections? > > James > > > -----Original Message----- > > From: Ian Campbell [mailto:Ian.Campbell@XenSource.com] > > Sent: 18 June 2007 19:14 > > To: Jimi Xenidis > > Cc: Hollis Blanchard; xen-devel@lists.xensource.com; James > > Bulpin; Aron Griffis; xen-ppc-devel; Alex Williamson; xen-ia64-devel > > Subject: Re: [XenPPC] Re: [Xen-devel] new repo layout? > > > > On Mon, 2007-06-18 at 13:40 -0400, Jimi Xenidis wrote: > > > Any chance you can wire up the email notifications again? > > > > I''d gladly do so if I had even the foggiest clue how. I''d > > assumed there would be a hook in .hg/hgrc, ~/.hgrc or > > /etc/hgrc but I can''t find anything of the sort anywhere on xenbits. > > > > James? What''s the secret? > > > > Ian. > > > > > > > > _______________________________________________ > Xen-ppc-devel mailing list > Xen-ppc-devel@lists.xensource.com > http://lists.xensource.com/xen-ppc-devel > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > ______________________________________________________________________ > Campbell & Company, Inc.: The information in this e-mail may contain privileged/confidential information. If you are not the intended recipient, you must not read, use, copy or disseminate the information or take any action in reliance thereupon. If you have received this e-mail in error, please notify Campbell & Company, Inc. immediately by e-mail or telephone and delete the e-mail and any attachments from any computer. The information in this e-mail does not constitute an offer to sell or the solicitation of an offer to buy any securities in any jurisdiction or for the benefit of any person. > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________-- Hollis Blanchard IBM Linux Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel