All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Hofstetter <qemu@g3gg0.de>
To: Antony Pavlov <antonynpavlov@gmail.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Dumitrache" <broscutamaker@gmail.com>,
	"Giovanni Condello" <condellog@gmail.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	g3gg0 <georg.hofstetter@lx-networking.de>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] QEMU ARM946 emulation, DIGIC, and MPU fault handling
Date: Sat, 25 Jan 2014 10:13:13 +0100	[thread overview]
Message-ID: <52E38029.2080308@g3gg0.de> (raw)
In-Reply-To: <20140124123156.7ecda5d7a994df1097c89ef9@gmail.com>

Am 24.01.2014 09:31, schrieb Antony Pavlov:
> On Thu, 23 Jan 2014 22:25:36 +0000
> Peter Maydell <peter.maydell@linaro.org> wrote:
> 
>> Since the 946 doesn't provide any way to find out what the fault
>> address actually was (it has no DFAR or IFAR) I presume that all
>> guest software treats a data abort or prefetch abort as a fatal error,
>> which is probably part of why nobody's ever noticed this.

Hi,

speaking for EOS models: indeed the original manufacturer's OS does not
handle these cases very different. They pick up the context (including
LR, the failing instruction), print an error message and kill the
failing task.

So at least the original OS does not use MPU systematically, like it
would be necessary for some kind of swapping etc.

BR,
Georg

      reply	other threads:[~2014-01-25  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 22:25 [Qemu-devel] QEMU ARM946 emulation, DIGIC, and MPU fault handling Peter Maydell
2014-01-23 23:36 ` Andreas Färber
2014-01-23 23:52   ` Peter Maydell
2014-01-24  8:31 ` Antony Pavlov
2014-01-25  9:13   ` Georg Hofstetter [this message]

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=52E38029.2080308@g3gg0.de \
    --to=qemu@g3gg0.de \
    --cc=afaerber@suse.de \
    --cc=antonynpavlov@gmail.com \
    --cc=broscutamaker@gmail.com \
    --cc=condellog@gmail.com \
    --cc=georg.hofstetter@lx-networking.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.