Merging 64 bit changes to -HEAD

[Randall Stewart]

I would think small verifiable changes would be good.. that
way if something does break (and we miss it) we can more easily
figure out what it was...


R
On Jun 15, 2010, at 10:10 AM, Jayachandran C. wrote:

> On Tue, Jun 15, 2010 at 7:21 PM, M. Warner Losh <imp at bsdimp.com>  
> wrote:
>> In message: <AANLkTik8jFkB7FTIIhyjalkfv1c0yXqse57Jzz527uf_ at mail.gmail.com 
>> >
>>            "Jayachandran C." <c.jayachandran at gmail.com> writes:
>> : I have volunteered to merge Juli's 64-bit work into HEAD,  and
>> : hopefully get it to work on XLR too. The tree
>> : (http://svn.freebsd.org/base/user/jmallett/octeon) has quite a  
>> bit of
>> : changes, so I would like to do this over multiple changesets and
>> : without breaking the current o32 code.
>> :
>> : The first batch of changes are attached (also at
>> : http://people.freebsd.org/~jchandra/jmallett-merge/), the patches  
>> are:
>> :
>> : libc-asm.patch - change libc assembly code to use macros which  
>> work on o32/n64
>> : libc-other.patch - makecontext implemenation, and other cleanup
>> : ld.so.patch - change dynamic loader assembly code to use macros
>> : tlb-to-c.patch - move TLB operations to C, update TLB operations  
>> API
>> :
>> : I've tested this on XLR, but there is a chance that this might  
>> break
>> : other platforms. So please let me know your comments on both the
>> : patches and the merge process.
>>
>> I've reviewed these changes with Juli as she was committing them to
>> her branch.  I think they are good to go.
>
> Then, would you want to do it this way, or one big merge from Juli's
> branch would be okay?
>
> JC.
>

------------------------------
Randall Stewart
803-317-4952 (cell)