From: sebastien Josse <sebastien.josse@aql.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] trigger a fault in host OS
Date: Thu, 06 Jul 2006 18:34:14 +0200 [thread overview]
Message-ID: <44AD3B86.20907@aql.fr> (raw)
Hello,
I’m trying to inject code in WinXP host operating system, starting from
intermediate code.
My objective is to trigger a page fault handler from the guest operating
system, in such a way I can read memory with cpu_memory_rw_debug without
error.
The idea is :
1. read memory in some location.
2. if cpu_memory_rw_debug return code !=0
1. forge a page fault intermediate code buffer
2. transform the intermediate code in host code with dyngen_code()
3. execute the host code buffer
3. attempt to read memory another time
I haven’t problem while making the intermediate code buffer :
opc_buf[]
opparam_buf[]
and forge a host code buffer with dyngen_code() :
code_buf[]
The problems arise when I want it to be executed by the host operating
system (step 2.c).
If I use neutral instructions, like:
opc_buf[0]=INDEX_nop;
opc_buf[1]=INDEX_op_exit_tb;
opc_buf[2]=INDEX_op_end;
I haven’t problem.
But if I trigger a fault, by using INDEX_op_ldsb_kernel_, etc.
Then Qemu seems to enter an infinite loop.
Do you see a solution to this problem ?
Thanks a lot.
Sebastien.
reply other threads:[~2006-07-06 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44AD3B86.20907@aql.fr \
--to=sebastien.josse@aql.fr \
--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).