Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Nick Clifton <nickc@cambridge.redhat.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: Add support for RedBoot SWIs to ARM Simulator
Date: Thu, 09 May 2002 04:11:00 -0000	[thread overview]
Message-ID: <200205091111.MAA22264@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "09 May 2002 12:00:35 BST." <m3n0v9h9gs.fsf@north-pole.nickc.cambridge.redhat.com>

> Hi Richard,
> 
> > This may trample on the toes of somebody using that SWI as a real
> > trap into an OS.
> 
> Well it would if they were then trying to run code compiled for that
> OS on the simulator.
> 
> > We probably should have a way of configuring the simulator at 
> > run-time to allow emulation of a set of SWI values.  Either from a  
> > command-line switch (for the arm-...-run command) or a gdb hook (for use 
> > within gdb).
> 
> > Something like:
> > 
> > 	arm-elf-run -emul-swi={redboot|angel|demon|none}
> 
> Hmm, well that could be done.  Personally I would hold off doing it
> until there is actually a situation where it is needed.  At the moment
> support all three SWI interfaces simultaneously is not a problem.  So
> unless someone comes up with a real situation where it causes problems
> I would leave things as they are.  (Just my 2 cents worth).
> 
> Cheers
>         Nick
> 


Actually, we already have.   Look at the mess that is involved with 
testing for XScale -- saying that XScale doesn't support Demon swi's is 
nonsence -- especially when we default to enabling XScale extensions for 
some simulations.  I ran into something like this only the other day -- 
the simulator was turning on XScale (despite the fact that I wasn't using 
any of those extensions), and thus disabling the SWIs I wanted.

Note the comment at the top of ARMul_OSHandleSWI which really gives the 
game away:

  /* Intel do not want DEMON SWI support.  */
  if (state->is_XScale)
	...

R.


  reply	other threads:[~2002-05-09 11:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09  3:09 Nick Clifton
2002-05-09  3:22 ` Richard Earnshaw
2002-05-09  4:00   ` Nick Clifton
2002-05-09  4:11     ` Richard Earnshaw [this message]
2002-05-16  9:16       ` Add support for target switches in simulator Nick Clifton
2002-05-16  9:25         ` Richard Earnshaw
2002-05-17  1:58           ` Nick Clifton
2002-05-17  5:37             ` Richard Earnshaw
2002-05-17  6:46               ` Nick Clifton
2002-05-17 10:17                 ` Andrew Cagney
2002-05-17  7:33             ` Frank Ch. Eigler
2002-05-17 10:29             ` Andrew Cagney
2002-05-16  9:36         ` Frank Ch. Eigler
2002-05-16 11:08         ` Michael Snyder
2002-05-17 11:32         ` Andrew Cagney
2002-05-20  6:11           ` Nick Clifton
2002-05-20  7:12             ` Andrew Cagney
2002-05-20  7:19             ` Richard Earnshaw
2002-05-20  7:26               ` Nick Clifton
2002-05-09  7:35     ` Add support for RedBoot SWIs to ARM Simulator Frank Ch. Eigler

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=200205091111.MAA22264@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickc@cambridge.redhat.com \
    /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