qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Subject: Re: [Qemu-devel] how to get registers value in event of systemcall
Date: Tue, 27 May 2008 14:35:30 +0100	[thread overview]
Message-ID: <200805271435.30937.paul@codesourcery.com> (raw)
In-Reply-To: <f284c33d0805262017g7e86efdcgcaa116068c4c7c73@mail.gmail.com>

> > guest operating system at the moment of a system call. In my opinion i've
> > to work on file target-i386/translate.c in the case of 0x80 in the
> > function disas_insn(DisasContext *s, target_ulong pc_start). I can't
> > understand how to get registers value. I've just read documentation about
> > translation but I'm not able to get these informations.
>
> I think you should go to target-i386/translate.c:
> gen_intermediate_code_internal(CPUState *env,
>                                                  TranslationBlock *tb,
>                                                  int search_pc)
>
> specifically, in "env" there is "regs" which hold the CPU registers.

No, that won't work. Only a very limited subset of the CPU state is valid 
during translation. The same block may be executed many times with different 
inputs.  If you want register values you have to do it at execution time, 
e.g. in do_interrupt.

Paul

  reply	other threads:[~2008-05-27 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 17:48 [Qemu-devel] how to get registers value in event of systemcall Antonio Ricci
2008-05-27  3:17 ` Mulyadi Santosa
2008-05-27 13:35   ` Paul Brook [this message]
2008-05-27 18:33     ` Antonio Ricci
2008-05-27 20:15     ` Antonio Ricci
2008-06-03 17:20     ` Antonio Ricci
2008-06-03 17:48       ` Paul Brook
2008-06-03 17:50     ` Antonio Ricci
2008-06-03 19:42       ` Laurent Desnogues
2008-06-03 20:12         ` Antonio Ricci
  -- strict thread matches above, loose matches on Subject: below --
2008-05-27  7:44 ricciantonio
2008-05-27  9:10 ` Mulyadi Santosa

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=200805271435.30937.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=mulyadi.santosa@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).