From: "Alex Bennée" <alex.bennee@linaro.org>
To: Mahmoud Abd el-hameed <mahmoudmahgoub92@hotmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] how to understand proccessor codes in Qemu
Date: Thu, 15 Sep 2016 16:00:39 +0100 [thread overview]
Message-ID: <878tuti4x4.fsf@linaro.org> (raw)
In-Reply-To: <AM5PR0602MB28205F990FED17137DD19890C8EB0@AM5PR0602MB2820.eurprd06.prod.outlook.com>
Mahmoud Abd el-hameed <mahmoudmahgoub92@hotmail.com> writes:
> Hi all,
>
> I am a new developer at Qemu and i want to understand how the processors code works. I am get lost through google and didn't know where i can begin to understand the code.
>
> my aim is to understand how can we model the proccessors using qemu?
Are you looking for pointers on how the TCG DBT works or the general
device emulation?
>
>
>
> Thanks,
>
> Mahmoud
--
Alex Bennée
prev parent reply other threads:[~2016-09-15 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 12:57 [Qemu-devel] how to understand proccessor codes in Qemu Mahmoud Abd el-hameed
2016-09-15 9:17 ` Stefan Hajnoczi
2016-09-15 15:00 ` Alex Bennée [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=878tuti4x4.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=mahmoudmahgoub92@hotmail.com \
--cc=qemu-arm@nongnu.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 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).