From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] qemu-arm (was: [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support)
Date: Tue, 16 Nov 2010 14:54:18 +0100 [thread overview]
Message-ID: <4CE28D0A.2090909@free.fr> (raw)
In-Reply-To: <AANLkTi=cS2OZnKGyx6KO9EiXYaqrr-jSy=n5M24eh73D@mail.gmail.com>
Le 16/11/2010 14:42, Peter Maydell a ?crit :
> qemu does simulate data/insn aborts caused when the MMU is
> enabled and you try an access forbidden by the access permissions
> set up in the page table. That particular error message happens when
> you try to execute from a physical address which isn't RAM or ROM,
> so you'll only see it if you have not enabled the MMU or if you get
> your page tables wrong. There's no particular reason this couldn't
> be made to take a simulated fault instead, I think -- there's an #ifdef
> that means qemu for Sparc and MIPS will simulate a fault instead
> of aborting. (In theory I think the behaviour shouldn't necessarily
> always be to fault, but if there is a non-RAM non-ROM device at
> the address to simulate the effect of trying to fetch instructions
> from your serial device registers, for example :-))
>
> This is an example of a general tendency in qemu-arm for the
> modelling to be a bit weak for situations which will never be
> triggered by a correct program/OS but which nonetheless have
> well defined failure behaviour. Other examples include execution
> of various opcode values which should UNDEF (may trigger qemu
> internal error warnings or decode to some other instruction), and
> execution of VFP or Neon when the CPACR is set to disable
> access to cp10/11 (should fault but won't). Mostly these things
> don't cause a problem in practice, which is why they haven't
> been corrected yet.
Thanks Peter for the clarification. I imagine that "in practice" can
bear different meanings depending on the practice -- for software like
u-boot, which is very low-level and can encounter issues such as a RAM
controller misconfiguration (or plain bad BAR setting, mind) addressing
outside physically available space, including writing to RO memory or
fetching bad code, is something we can see in practice, at least in the
first times of a board's bring up.
I'll have a look and see if I can get a working setup for running u-boot
on qemu-arm.
> -- PMM
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-11-16 13:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 22:22 [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support Albert Aribaud
2010-11-04 22:22 ` [U-Boot] [PATCH V4 2/2] tx25: " Albert Aribaud
2010-11-04 22:27 ` [U-Boot] [PATCH V4 1/2] arm926ejs: " Albert ARIBAUD
2010-11-09 13:49 ` Albert ARIBAUD
2010-11-05 8:38 ` Reinhard Meyer
2010-11-05 9:04 ` Albert ARIBAUD
2010-11-09 18:24 ` Daniel Hobi
2010-11-09 18:47 ` Albert ARIBAUD
2010-11-09 18:55 ` Albert ARIBAUD
2010-11-09 19:30 ` Andreas Bießmann
2010-11-10 12:31 ` Daniel Hobi
2010-11-10 12:48 ` Albert ARIBAUD
2010-11-10 13:24 ` Daniel Hobi
2010-11-11 8:11 ` Albert ARIBAUD
2010-11-14 21:22 ` Wolfgang Denk
2010-11-15 11:01 ` Albert ARIBAUD
2010-11-15 11:09 ` Andreas Bießmann
2010-11-15 11:43 ` Sebastien Carlier
2010-11-16 7:38 ` Andreas Bießmann
2010-11-15 11:13 ` Wolfgang Denk
2010-11-15 11:49 ` Albert ARIBAUD
2010-11-15 11:55 ` Loïc Minier
2010-11-15 12:03 ` Wolfgang Denk
2010-11-15 14:06 ` Loïc Minier
2010-11-15 14:29 ` Albert ARIBAUD
2010-11-15 15:09 ` Loïc Minier
2010-11-16 13:42 ` Peter Maydell
2010-11-16 13:54 ` Albert ARIBAUD [this message]
2010-11-16 14:49 ` [U-Boot] qemu-arm (was: [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support) Peter Maydell
2010-11-16 16:02 ` [U-Boot] qemu-arm Albert ARIBAUD
2010-11-15 12:00 ` [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support Reinhard Meyer
2010-11-15 12:02 ` Wolfgang Denk
2010-11-15 12:13 ` Albert ARIBAUD
2010-11-15 12:16 ` Bas Mevissen
2010-11-10 13:02 ` [U-Boot] Timer Statics (was: arm926ejs: fix linker file for newer ld support) Reinhard Meyer
2010-11-09 19:27 ` [U-Boot] [PATCH V4 1/2] arm926ejs: fix linker file for newer ld support Andreas Bießmann
2010-11-09 19:31 ` Albert ARIBAUD
2010-11-09 23:43 ` Eric Cooper
2010-11-10 7:53 ` Albert ARIBAUD
2010-11-10 14:20 ` Eric Cooper
2010-11-11 7:33 ` Albert ARIBAUD
2010-11-15 14:15 ` Daniel Hobi
2010-11-15 14:37 ` Albert ARIBAUD
2010-11-15 19:14 ` Eric Cooper
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=4CE28D0A.2090909@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/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