qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: KONRAD Frederic <fred.konrad@greensocs.com>
To: Hao Bai <hb4vf@virginia.edu>
Cc: qemu-devel@nongnu.org, qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] Integrating a Memory Simulator
Date: Tue, 23 Feb 2016 13:15:57 +0100	[thread overview]
Message-ID: <56CC4D7D.4080608@greensocs.com> (raw)
In-Reply-To: <CACuU35h9da06gCgqEJVrB5oy1Ji5R4KoM-oL7ivpG7N_JT7Lvg@mail.gmail.com>

Hi,

Why do you target the user mode for that?
I think it might be easier with the softmmu.
But depending on what you want to do it won't be so easy.

I don't think there are any transaction to read the code basically the 
RAM MemoryRegion works with pointer.
You can create a MemoryRegion which will just create a transaction and 
passes that to your model but you won't
be able to execute code from it. So you would need to modify that.
But at the end you won't have the same access like in the real HW 
because cache are not modelled in QEMU and
it will be really slow :).

Fred

Le 22/02/2016 01:26, Hao Bai a écrit :
> Hi All,
>
> I was trying to integrate the DRAMSim2 memory simulator [1] into QEMU. 
> Basically I wanted to modify the current memory interface of QEMU so 
> that all memory accesses will be directed to DRAMSim2. Can anyone give 
> me hints/comments/thoughts on how to do this? I am targeting x86-64 
> architecture in user mode.
>
> [1] Repository: https://github.com/dramninjasUMD/DRAMSim2
> Paper: https://www.ece.umd.edu/~blj/papers/cal10-1.pdf 
> <https://www.ece.umd.edu/%7Eblj/papers/cal10-1.pdf>
>
> Cheers

      reply	other threads:[~2016-02-23 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  0:26 [Qemu-devel] Integrating a Memory Simulator Hao Bai
2016-02-23 12:15 ` KONRAD Frederic [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=56CC4D7D.4080608@greensocs.com \
    --to=fred.konrad@greensocs.com \
    --cc=hb4vf@virginia.edu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@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).