qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Antonio Ricci <ricciantonio@slacky.it>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] how to get registers value in event of systemcall
Date: Tue, 27 May 2008 20:33:19 +0200	[thread overview]
Message-ID: <483C53EF.4070900@slacky.it> (raw)
In-Reply-To: <200805271435.30937.paul@codesourcery.com>

Hi Paul,
thanks for your answer.
I've tried to have registers value from do interrupt and it seems to 
work. I've some questions for you:
1) Where these values are initialized? I can't find it.
2) Have I to work on each type of do_interrupt (that is do_interrupt, 
do_interrupt_user, etc.) to get register's value in all kind of syscalls?
3) If i want to avoid  the execution of some type of syscall based on 
parameters is it possible in this way?

Thanks for your help

--
Antonio
My Mobile Phone: +393286739562
My Public Key: http://tonyr.altervista.org/chiave_pubblica
MSN: ricciantonio@hotmail.it
Skype: tonyr81fg
Linux Member #374272
*********************************************************************
What is the difference between Jurassic Park and Microsoft?
One is an over-rated high tech theme park based on prehistoric 
information and populated mostly by dinosaurs, the other is a Steven 
Spielberg movie.
*********************************************************************
There are only 10 types of people in this world:
those who understand binary, and those who don't.
*********************************************************************

Paul Brook wrote:
>>> 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 18:34 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
2008-05-27 18:33     ` Antonio Ricci [this message]
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=483C53EF.4070900@slacky.it \
    --to=ricciantonio@slacky.it \
    --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).