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

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>From: Magenheimer, Dan (HP Labs Fort Collins)
>
>Thanks, Kevin and John, for all your hard work to get
>this working again.
>
>I haven't looked closely at the patches (Kevin's, and
>John's which haven't yet been posted :-)...
>
>Are there any files changed that are NOT ia64-specific?
>I want to be very careful about putting files into
>xen-ia64-unstable.hg that, if pulled into xen-unstable.hg,
>might break Xen/x86.  These should probably be separate
>patches so Keir can look at them individually.

Agree that this should be careful. Due to in middle of the whole debug
process, the previous patches I sent out may contain some dirty code.
Once John gets his cleanup done, please send out and I'll cover the
rest:

- libxc: most code are in ia64 specific file or ifdef section. Several
lines to Makefile are necessary to promise ia64 compilation. There's
also change to one python script, to allocate one extra pfn for ia64.
I'll check today to see whether there's better way to do it.

- xen: most changes are from grant_table code merge, which I think
there's possibility to merge with common code without ifdef. (But let's
shoot for later). There's also a dirty hack about tot_pages, and I'll
clean it.

-xeno: Many ifdefs exist in this repository, which however is difficult
to change in current stage if the whole mechanism doesn't conform to x86
side (Mainly mean the guest va <-> guest pfn<->machine pfn). So agree
next step is to consider how to merge it into sparse tree.

Please help review.

Thanks
Kevin
>
>Also, once this is all working, we should look at what
>it would take to get xenlinux/ia64 built directly from
>the xen(-sparse) tree so we won't have to play
>"catch up" again.
>
>Logging out for the evening now...
>Dan
>
>> -----Original Message-----
>> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
>> Of Byrne, John (HP Labs)
>> Sent: Wednesday, August 31, 2005 7:24 PM
>> To: Tian, Kevin
>> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-ia64-devel] Community effort neededtocatch
>> upwithxen-unstable
>>
>> Tian, Kevin wrote:
>> >>From: Tian, Kevin
>> >>Sent: Thursday, September 01, 2005 8:55 AM
>> >>
>> >>>From: John Byrne [mailto:john.l.byrne@xxxxxx]
>> >>>
>> >>>I've gotten blkfront/blkback to work based on your patches and
>> >>>re-merging Matt's changes to them before the xen-unstable
>> merge. I'm
>> >>>trying to get the netback/netfront drivers to come up,
>> now. I'll have
>> >>
>> >>to
>> >>
>> >>>clean up some debugging before I can generate a patch. I
>> will generate
>> >>
>> >>a
>> >>
>> >>>patch that is added in addition to your hg_cleanup_0831 patches.
>> >>
>> >>Good to know that.
>> >
>> >
>> >
>> > BTW, I just checked the previous repository before latest
>> merge, and it
>> > seems that netback/netfront drivers were disabled in
>> Makefile before.
>> > (Please confirm)  If netback/netfront doesn't work before,
>> it means that
>> > we already reach the same point as previous if you can
>> login into shell.
>> > And then we may manage to push out current fixes in first. Then
>> > netback/netfront will be taken as a subsequent welcome
>> feature to go...
>> > comments?
>> >
>> > Thanks,
>> > Kevin
>> >
>>
>> Yes, netfront/netback were not being built. (Note that this
>> has the side
>> effect of "xend start" screwing up your networking because the new
>> network-bridge script doesn't handle the case without a veth0
>> interface
>> correctly. The easiest hack is to put in a dummy
>> network-bridge script
>> for the moment.) So as soon as blkfront/blkback work, things
>> are as good
>> as they were before the xen-unstable merge, AFAIK.
>>
>> As a learning experience, I was working on porting Matt's changes to
>> netfront/netback and things got snarled up because of the differences
>> between xen-unstable and xen-ia64. Now that we are synched, I hope
>> things can be finished now.
>>
>> Probably another 1/2 hour for my patches.
>>
>> John Byrne
>>
>>
>> _______________________________________________
>> Xen-ia64-devel mailing list
>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-ia64-devel
>>

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