* [Qemu-devel] Reading and writing functions for QEMU emulated peripherals
@ 2017-10-15 16:47 Ramy Sameh
2017-10-15 16:50 ` Peter Maydell
0 siblings, 1 reply; 3+ messages in thread
From: Ramy Sameh @ 2017-10-15 16:47 UTC (permalink / raw)
To: QEMU Developers; +Cc: Mona Safar, Ahmed Aly, Watheq
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
Hello all,
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 ?
Thanks in advance for your support.
[image: Inline image 1]
--
Best Regards,
Ramy Sameh
Embedded Software Engineer
+2-010-172-777-14
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 12355 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Reading and writing functions for QEMU emulated peripherals
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
0 siblings, 1 reply; 3+ messages in thread
From: Peter Maydell @ 2017-10-15 16:50 UTC (permalink / raw)
To: Ramy Sameh; +Cc: QEMU Developers, Mona Safar, Ahmed Aly, Watheq
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Reading and writing functions for QEMU emulated peripherals
2017-10-15 16:50 ` Peter Maydell
@ 2017-10-15 18:49 ` Ramy Sameh
0 siblings, 0 replies; 3+ messages in thread
From: Ramy Sameh @ 2017-10-15 18:49 UTC (permalink / raw)
To: Peter Maydell; +Cc: QEMU Developers, Mona Safar, Ahmed Aly, Watheq
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-10-15 18:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).