Re: [uml-devel] UML on Alpha

[Cameron Patrick <cameron@patrick.wattle.id.au>]

On Sat, Dec 20, 2003 at 12:32:49PM -0500, Jeff Dike wrote:
| >         setup_arch_frame_raw(&raw_si->common.arch,
| >                              ucontext->uc_mcontext.fpregs, raw_si->common.sr);
[...]
| 
| >From /usr/include/asm/sigcontext.h on my laptop:
| 
| struct sigcontext {
| 	...
|         struct _fpstate * fpstate;
| 	...
| };

Yeah, but that's fpstate, not fpregs.  Looking at it more closely, on
i386, uc_mcontext is /not/ of type sigcontext, but mcontext_t, which
includes an fpregs member.  On alpha, uc_mcontext is a sigcontext, and
it has a sc_fpregs member.  I'm not sure that that's the appropriate
thing to change it to though - I'll have to look to see exactly what
it's using it for.

| > - Since Alpha is a 64-bit architecture, there are no *64 system calls
| >   either.  This also affects other parts of the kernel which use #if to
| >   check for Alpha/sparc64/S390/etc to determine whether or not we're on
| >   a 64-bit platform.  I've worked around this by adding a -D__um_alpha__
| >   to CFLAGS and changing some places which check for __alpha__ to also
| >   check for __um_alpha__.  This may not be the cleanest way to do things
| >   thought :(
| 
| This is a problem.  There should be a CONFIG_64BITS which all the 64 bit
| arches set, so we don't have to add #ifdef UML && UML_ALPHA to all these
| places.

Okay.  It doesn't seem to be there in 2.4.x, but I'll have a look at 2.6
some time and see if that makes this problem disappear.

| > cross-compile UML.  Unfortunately that would mean some way of getting
| > rid of mk_sc/mk_thread/mk_kern/etc, and I'm not sure what the best
| > approach to doing that would be :-/
| 
| There was a bit of work in that direction a while back.  What I think would
| be a good way to go is to have a arch_headers rule in the Makefile, which
| would execute on the target, and generate the headers.  They would land
| in a single directory, which you would then copy over to the build box.
| The build there would use those headers, or generate them itself if they
| weren't present.

Yeah, that sounds sensible.  I'll have a shot at munging the Makefiles
to do just that. :-)

Cheers,

Cameron.



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel