Hi Jeff, Here are the notes on the endian notes. On first blush it looks like the basic problems are related to I/O and structure alignment. Correcting the structure (in the compiler) might be enough (if is supports endian pragmas or some such. The traditional way is to hard code endian conversions of the data before it goes out over the network and converting back on return. There are macros in the networking code that do the core byte swaping function. I was looking from net_write() & net_read() to see where they were called and what was passed to them. struct chunksrv_req & struct chunksrv_resp_get seem to be the primary structures. Where to optimally put the changes is less clear.
I cobbled on a VM to get the PPC vm working. It seemed to boot, but needed more configuration than I had time to dope out. I was cool to see a mini-laptop (using the atom processor) run windows (yetch), support a VM running Fedora, support a VM running PPC code! I'm thinking a DVD could still run in the background, on an external monitor... - Rick >From: Jeff Garzik <j...@garzik.org> >Sent: Aug 4, 2009 9:26 PM >To: Pete Zaitcev <zait...@redhat.com> >Cc: Project Hail List <hail-devel@vger.kernel.org>, Rick Peralta ><f...@tiac.net> >Subject: Re: [Patch] chunkd: use port xxx82 to build > >Pete Zaitcev wrote: >> On Tue, 04 Aug 2009 21:00:36 -0400, Jeff Garzik <j...@garzik.org> wrote: >> >>> Speaking of chunkd... >>> >>> I don't think I will have time this week to fix chunkd's failure on big >>> endian machines. If you (or anyone else listening...) have an >>> opportunity to look into that, that would be most helpful. >> >> This looks like an ideal opportunity for Rick to read the code >> with a specific goal in mind, if he doesn't mind me saying so. > >CC'd :) > > >> Do we have a bug number for it? > >https://bugzilla.redhat.com/show_bug.cgi?id=514651 > > Jeff > > > -- To unsubscribe from this list: send the line "unsubscribe hail-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
