From: Ramy Sameh <ramysameh26@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Mona Safar <Mona.Safar@eng.asu.edu.eg>,
Ahmed Aly <ahmedaly50@gmail.com>, Watheq <watheq@gmail.com>
Subject: Re: [Qemu-devel] Reading and writing functions for QEMU emulated peripherals
Date: Sun, 15 Oct 2017 20:49:31 +0200 [thread overview]
Message-ID: <CAF6HrYwPtrQU-wsTmSQcmoSC+7d7CHp-oVa6ksk+PG6_Q48WFQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-Um7zYLeSzFfSSL-nRsRKyRbKEwb2MEzcsGqoQDSuRqg@mail.gmail.com>
Many thanks Peter
On Sun, Oct 15, 2017 at 6:50 PM, Peter Maydell <peter.maydell@linaro.org>
wrote:
> On 15 October 2017 at 17:47, Ramy Sameh <ramysameh26@gmail.com> wrote:
> > I was tracking the calling of function pl011_read, and I noticed that it
> is
> > called from function *memory_region_read_accessor *in memory.c
> >
> > I also noticed that all peripherals reading functions (e.g. pl050_read,
> > pl190_read ... etc) in the emulated VersatilePB board, are called from
> the
> > same location in *memory_region_read_accessor.*
> >
> > *My question is*: Is this calling procedure done for the emulated
> > VersatilePB board *only*, or this is the case for the peripherals in all
> > emulated systems ?
>
> Broadly speaking, yes, all peripheral device read and write
> functions are invoked via the memory subsystem code (which
> is the part of QEMU that figures out what memory region
> covers whatever the physical address that the guest wrote
> to is).
>
> thanks
> -- PMM
>
--
Best Regards,
Ramy Sameh
Embedded Software Engineer
+2-010-172-777-14
prev parent reply other threads:[~2017-10-15 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 16:47 [Qemu-devel] Reading and writing functions for QEMU emulated peripherals Ramy Sameh
2017-10-15 16:50 ` Peter Maydell
2017-10-15 18:49 ` Ramy Sameh [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=CAF6HrYwPtrQU-wsTmSQcmoSC+7d7CHp-oVa6ksk+PG6_Q48WFQ@mail.gmail.com \
--to=ramysameh26@gmail.com \
--cc=Mona.Safar@eng.asu.edu.eg \
--cc=ahmedaly50@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=watheq@gmail.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;
as well as URLs for NNTP newsgroup(s).