All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Liviu Ionescu <ilg@livius.net>
Cc: QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] How to trigger faults for missing peripherals?
Date: Thu, 18 Jun 2015 15:59:06 +0100	[thread overview]
Message-ID: <CAFEAcA8tbHEo-Yv1T=MVO7rrE0NUiAh11N-pwxSuce3GSwgxbg@mail.gmail.com> (raw)
In-Reply-To: <F53B9A2C-D9DD-4E68-90F5-823599FE3513@livius.net>

On 18 June 2015 at 15:30, Liviu Ionescu <ilg@livius.net> wrote:
>
>> On 18 Jun 2015, at 13:21, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> ... "do_unassigned_access" is the QOM CPUClass hook for this,
>
> this hook seems associated with the "Trying to execute code outside
> RAM or ROM at 0x" error, which is a bit different, I want to catch
> read/write accesses, not execute accesses.

read/write accesses call the hook via the code path:
 unassigned_mem_{read,write}() -> cpu_unassigned_access()

(though this is part of the design issue I mentioned --
it means the hook gets called for *anything* that touches
an unassigned address, even if it was the DMA controller
and not the CPU at all. The hook calls need to be hoisted
out of those functions and up to a higher level in the
call tree.)

-- PMM

      reply	other threads:[~2015-06-18 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18  9:45 [Qemu-devel] How to trigger faults for missing peripherals? Liviu Ionescu
2015-06-18 10:21 ` Peter Maydell
2015-06-18 14:30   ` Liviu Ionescu
2015-06-18 14:59     ` Peter Maydell [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='CAFEAcA8tbHEo-Yv1T=MVO7rrE0NUiAh11N-pwxSuce3GSwgxbg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=Qemu-devel@nongnu.org \
    --cc=ilg@livius.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 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.