From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Alex LIU <alex.liu@st.com>
Subject: Re: [uml-devel] question about UML sigcontext in tt mode
Date: Tue, 5 Apr 2005 13:20:45 -0400 [thread overview]
Message-ID: <200504051320.45424.rob@landley.net> (raw)
In-Reply-To: <20050404140011.GA1977@ccure.user-mode-linux.org>
On Monday 04 April 2005 10:00 am, Jeff Dike wrote:
> On Thu, Mar 31, 2005 at 06:03:34PM +0800, Alex LIU wrote:
> > union uml_pt_regs {
> > #ifdef UML_CONFIG_MODE_TT
> > struct tt_regs {
> > long syscall;
> > void *sc;
> > } tt;
> > #endif
> > };
> > -------------------------------------
> >
> > Then why the tt.sc is defined as void while not as struct sigcontext?
> > Thanks!
>
> Probably because you can't get a definition of struct sigcontext into
> processor.h and have it still compile.
>
> Try #including sigcontext.h there and you'll see what I mean.
I don't know about can't.
#define sigcontext WALRUS
#include <processor.h>
thingy
#undef WALRUS
Adviseable is another matter entirely. (Did I mention I have a knack for
coming up with disgusting solutions to impossible problems?)
Rob
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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
next prev parent reply other threads:[~2005-04-05 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 10:03 [uml-devel] question about UML sigcontext in tt mode Alex LIU
2005-04-01 18:51 ` Blaisorblade
2005-04-04 14:00 ` Jeff Dike
2005-04-05 17:20 ` Rob Landley [this message]
2005-04-05 20:59 ` Blaisorblade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200504051320.45424.rob@landley.net \
--to=rob@landley.net \
--cc=alex.liu@st.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox