qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Prathmesh Kallurkar <prathmesh.kallurkar@gmail.com>
To: qemu-devel@nongnu.org
Cc: Prathmesh Kallurkar <prathmesh.kallurkar@gmail.com>
Subject: Re: [Qemu-devel] Qemu memory operations
Date: Tue, 14 Aug 2012 17:28:55 +0530	[thread overview]
Message-ID: <CAF_r1AaSGJE_Lf88TYkt+dpDnQPLmrzLFpBR4ChSd35ZKHqPsg@mail.gmail.com> (raw)
In-Reply-To: <CAF_r1AYNekV43LwBz1zqsspppqQzWQkrYWuoLLFWNPuq1YvB4Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Sorry friends for the misleading instructions in the previous mail.

cmp ecx, [r12+0x4]
mov r10b, [r13+0x0]
mov byte [rax+0xf0000], 0x0
mov byte [rax+rdx], 0x0

It seems all the above instructions are getting covered with the
tcg_gen_ld/st helpers.

But now I have stumbled upon another problem :
I initially thought that all the interactions with the guest memory happen
through the helper instructions in the translate.c file.
However, I found that the helper functions for some instructions like
*cmpxcgh8b
*and* cmpxchg16b* are actually accessing guest memory.

So, does it mean there are more than one entry points for reading guest
memory.
Can some one please explain how are the *ldq and stq* instructions
translated to access the guest memory ??

Thanks in advance.


Regards,
Prathmesh Kallurkar

[-- Attachment #2: Type: text/html, Size: 1045 bytes --]

  reply	other threads:[~2012-08-14 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-12 16:31 [Qemu-devel] Qemu memory operations Prathmesh Kallurkar
2012-08-14 11:58 ` Prathmesh Kallurkar [this message]
2012-08-14 18:44   ` Blue Swirl
2012-08-14 21:17 ` Steven
2012-08-15  8:57   ` Prathmesh Kallurkar
2012-08-15 17:21     ` Steven

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=CAF_r1AaSGJE_Lf88TYkt+dpDnQPLmrzLFpBR4ChSd35ZKHqPsg@mail.gmail.com \
    --to=prathmesh.kallurkar@gmail.com \
    --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).